PC reboots when logon

G

Guest

My users run Win 2000 Prof SP4, all users has same a logon script
(allusers.bat) and it contained as follow:

NET USE H: \\PDC\PUBLIC

but when they logon their PC reboot .. I checked to the event viewer and it
contained as follow:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
(0xc0000005, 0x8044f718, 0x00000000, 0x6e697455). Microsoft Windows 2000
[v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010505-01.dmp.

what should I do?
 
D

David H. Lipman

One PC or all nodes ?

What if they don't run a Logon Script ?

--
Dave




| My users run Win 2000 Prof SP4, all users has same a logon script
| (allusers.bat) and it contained as follow:
|
| NET USE H: \\PDC\PUBLIC
|
| but when they logon their PC reboot .. I checked to the event viewer and it
| contained as follow:
|
| The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
| (0xc0000005, 0x8044f718, 0x00000000, 0x6e697455). Microsoft Windows 2000
| [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010505-01.dmp.
|
| what should I do?
|
|
 
G

Guest

I never try not to run Logon script because the script is only contained as
follow:

NET USE H: \\PDC\PUBLIC

and this problem only happened in some of clients .. any idea?


Regards
Winanjaya
 
D

David H. Lipman

Insufficient information.

--
Dave




| I never try not to run Logon script because the script is only contained as
| follow:
|
| NET USE H: \\PDC\PUBLIC
|
| and this problem only happened in some of clients .. any idea?
|
|
| Regards
| Winanjaya
|
| "David H. Lipman" wrote:
|
| > One PC or all nodes ?
| >
| > What if they don't run a Logon Script ?
| >
| > --
| > Dave
| >
| >
| >
| >
| > | > | My users run Win 2000 Prof SP4, all users has same a logon script
| > | (allusers.bat) and it contained as follow:
| > |
| > | NET USE H: \\PDC\PUBLIC
| > |
| > | but when they logon their PC reboot .. I checked to the event viewer and it
| > | contained as follow:
| > |
| > | The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
| > | (0xc0000005, 0x8044f718, 0x00000000, 0x6e697455). Microsoft Windows 2000
| > | [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010505-01.dmp.
| > |
| > | what should I do?
| > |
| > |
| >
| >
| >
 
P

Pegasus \(MVP\)

Winanjaya said:
My users run Win 2000 Prof SP4, all users has same a logon script
(allusers.bat) and it contained as follow:

NET USE H: \\PDC\PUBLIC

but when they logon their PC reboot .. I checked to the event viewer and it
contained as follow:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
(0xc0000005, 0x8044f718, 0x00000000, 0x6e697455). Microsoft Windows 2000
[v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010505-01.dmp.

what should I do?

What virus scanner do you use?
 
G

Guest

all of my users have same logon script but some of PCes always reboot when
logon,
the logon script is only contained below:

NET USE H: \\PDC\PUBLIC

by the way .. all of them also install Trust-No-Exe ..
(this is third party tool for executable filter) .. .. I also already
removed Trust-No-Exe .. but the same problem still occurs .. once again only
some of them reboots when logon .. please help .. any prompt reply would be
appreciated
thanks a lot in advance
 
P

Pegasus \(MVP\)

I repeat my question from my previous reply
(to which you did not respond):
"What virus scanner do you use?"
This could be relevant.


Winanjaya said:
all of my users have same logon script but some of PCes always reboot when
logon,
the logon script is only contained below:

NET USE H: \\PDC\PUBLIC

by the way .. all of them also install Trust-No-Exe ..
(this is third party tool for executable filter) .. .. I also already
removed Trust-No-Exe .. but the same problem still occurs .. once again only
some of them reboots when logon .. please help .. any prompt reply would be
appreciated
thanks a lot in advance


David H. Lipman said:
Insufficient information.

--
Dave




| I never try not to run Logon script because the script is only contained as
| follow:
|
| NET USE H: \\PDC\PUBLIC
|
| and this problem only happened in some of clients .. any idea?
|
|
| Regards
| Winanjaya
|
| "David H. Lipman" wrote:
|
| > One PC or all nodes ?
| >
| > What if they don't run a Logon Script ?
| >
| > --
| > Dave
| >
| >
| >
| >
| > | > | My users run Win 2000 Prof SP4, all users has same a logon script
| > | (allusers.bat) and it contained as follow:
| > |
| > | NET USE H: \\PDC\PUBLIC
| > |
| > | but when they logon their PC reboot .. I checked to the event viewer and it
| > | contained as follow:
| > |
| > | The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
| > | (0xc0000005, 0x8044f718, 0x00000000, 0x6e697455). Microsoft Windows 2000
| > | [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010505-01.dmp.
| > |
| > | what should I do?
| > |
| > |
| >
| >
| >
 
G

Guest

We use TrendMicro OfficeScan Corporate Edition ..
any idea?

Pegasus (MVP) said:
I repeat my question from my previous reply
(to which you did not respond):
"What virus scanner do you use?"
This could be relevant.


Winanjaya said:
all of my users have same logon script but some of PCes always reboot when
logon,
the logon script is only contained below:

NET USE H: \\PDC\PUBLIC

by the way .. all of them also install Trust-No-Exe ..
(this is third party tool for executable filter) .. .. I also already
removed Trust-No-Exe .. but the same problem still occurs .. once again only
some of them reboots when logon .. please help .. any prompt reply would be
appreciated
thanks a lot in advance


David H. Lipman said:
Insufficient information.

--
Dave




| I never try not to run Logon script because the script is only contained as
| follow:
|
| NET USE H: \\PDC\PUBLIC
|
| and this problem only happened in some of clients .. any idea?
|
|
| Regards
| Winanjaya
|
| "David H. Lipman" wrote:
|
| > One PC or all nodes ?
| >
| > What if they don't run a Logon Script ?
| >
| > --
| > Dave
| >
| >
| >
| >
| > | > | My users run Win 2000 Prof SP4, all users has same a logon script
| > | (allusers.bat) and it contained as follow:
| > |
| > | NET USE H: \\PDC\PUBLIC
| > |
| > | but when they logon their PC reboot .. I checked to the event viewer and it
| > | contained as follow:
| > |
| > | The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
| > | (0xc0000005, 0x8044f718, 0x00000000, 0x6e697455). Microsoft Windows 2000
| > | [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010505-01.dmp.
| > |
| > | what should I do?
| > |
| > |
| >
| >
| >
 
P

Pegasus \(MVP\)

I suspected so. The current version of the Trend scan engine has
a known flaw. You can easily prove it. Start one of the problem
PCs without a logon script, then do this:
1. Start a Command Prompt.
2. Type this command: net use x: \\YourServer\Netlogon
3. Type the same command again, without any change.

If the machine crashes instantly then you're a victim of this
particular problem It rears its ugly head whenever you're
trying to map a network connection to a drive letter that
is already in use (x: in this case).

The answer:
- Either ask Trend when they will address the problem and
distribute the updated engine (which has been around for
several months), or
- Avoid mapping the same letter twice.

If you ask Trend for assistance then you may be in for
a long wait. They are sometimes in denial mode.

Please confirm (or otherwise) if this is the cause of your
problem.


Winanjaya said:
We use TrendMicro OfficeScan Corporate Edition ..
any idea?

Pegasus (MVP) said:
I repeat my question from my previous reply
(to which you did not respond):
"What virus scanner do you use?"
This could be relevant.


Winanjaya said:
all of my users have same logon script but some of PCes always reboot when
logon,
the logon script is only contained below:

NET USE H: \\PDC\PUBLIC

by the way .. all of them also install Trust-No-Exe ..
(this is third party tool for executable filter) .. .. I also already
removed Trust-No-Exe .. but the same problem still occurs .. once
again
only
some of them reboots when logon .. please help .. any prompt reply
would
be
appreciated
thanks a lot in advance


:

Insufficient information.

--
Dave




| I never try not to run Logon script because the script is only contained as
| follow:
|
| NET USE H: \\PDC\PUBLIC
|
| and this problem only happened in some of clients .. any idea?
|
|
| Regards
| Winanjaya
|
| "David H. Lipman" wrote:
|
| > One PC or all nodes ?
| >
| > What if they don't run a Logon Script ?
| >
| > --
| > Dave
| >
| >
| >
| >
| > | > | My users run Win 2000 Prof SP4, all users has same a logon script
| > | (allusers.bat) and it contained as follow:
| > |
| > | NET USE H: \\PDC\PUBLIC
| > |
| > | but when they logon their PC reboot .. I checked to the event viewer and it
| > | contained as follow:
| > |
| > | The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
| > | (0xc0000005, 0x8044f718, 0x00000000, 0x6e697455). Microsoft Windows 2000
| > | [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010505-01.dmp.
| > |
| > | what should I do?
| > |
| > |
| >
| >
| >
 
G

Guest

Thanks, I tried it and nothing happen .. any suggestion?
TIA

Pegasus (MVP) said:
I suspected so. The current version of the Trend scan engine has
a known flaw. You can easily prove it. Start one of the problem
PCs without a logon script, then do this:
1. Start a Command Prompt.
2. Type this command: net use x: \\YourServer\Netlogon
3. Type the same command again, without any change.

If the machine crashes instantly then you're a victim of this
particular problem It rears its ugly head whenever you're
trying to map a network connection to a drive letter that
is already in use (x: in this case).

The answer:
- Either ask Trend when they will address the problem and
distribute the updated engine (which has been around for
several months), or
- Avoid mapping the same letter twice.

If you ask Trend for assistance then you may be in for
a long wait. They are sometimes in denial mode.

Please confirm (or otherwise) if this is the cause of your
problem.


Winanjaya said:
We use TrendMicro OfficeScan Corporate Edition ..
any idea?

Pegasus (MVP) said:
I repeat my question from my previous reply
(to which you did not respond):
"What virus scanner do you use?"
This could be relevant.


all of my users have same logon script but some of PCes always reboot when
logon,
the logon script is only contained below:

NET USE H: \\PDC\PUBLIC

by the way .. all of them also install Trust-No-Exe ..
(this is third party tool for executable filter) .. .. I also already
removed Trust-No-Exe .. but the same problem still occurs .. once again
only
some of them reboots when logon .. please help .. any prompt reply would
be
appreciated
thanks a lot in advance


:

Insufficient information.

--
Dave




| I never try not to run Logon script because the script is only
contained as
| follow:
|
| NET USE H: \\PDC\PUBLIC
|
| and this problem only happened in some of clients .. any idea?
|
|
| Regards
| Winanjaya
|
| "David H. Lipman" wrote:
|
| > One PC or all nodes ?
| >
| > What if they don't run a Logon Script ?
| >
| > --
| > Dave
| >
| >
| >
| >
| > | > | My users run Win 2000 Prof SP4, all users has same a logon script
| > | (allusers.bat) and it contained as follow:
| > |
| > | NET USE H: \\PDC\PUBLIC
| > |
| > | but when they logon their PC reboot .. I checked to the event
viewer and it
| > | contained as follow:
| > |
| > | The computer has rebooted from a bugcheck. The bugcheck was:
0x0000001e
| > | (0xc0000005, 0x8044f718, 0x00000000, 0x6e697455). Microsoft
Windows 2000
| > | [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini010505-01.dmp.
| > |
| > | what should I do?
| > |
| > |
| >
| >
| >
 
P

Pegasus \(MVP\)

If nothing happens then you do not appear to be affected
by this particular issue.

You should now do this:
- Turn on the "echo" in your logon script.
- Place a "pause" after each command.
- Find out which command causes the machine to crash.
- Report back here with the result.


Winanjaya said:
Thanks, I tried it and nothing happen .. any suggestion?
TIA

Pegasus (MVP) said:
I suspected so. The current version of the Trend scan engine has
a known flaw. You can easily prove it. Start one of the problem
PCs without a logon script, then do this:
1. Start a Command Prompt.
2. Type this command: net use x: \\YourServer\Netlogon
3. Type the same command again, without any change.

If the machine crashes instantly then you're a victim of this
particular problem It rears its ugly head whenever you're
trying to map a network connection to a drive letter that
is already in use (x: in this case).

The answer:
- Either ask Trend when they will address the problem and
distribute the updated engine (which has been around for
several months), or
- Avoid mapping the same letter twice.

If you ask Trend for assistance then you may be in for
a long wait. They are sometimes in denial mode.

Please confirm (or otherwise) if this is the cause of your
problem.


Winanjaya said:
We use TrendMicro OfficeScan Corporate Edition ..
any idea?

:

I repeat my question from my previous reply
(to which you did not respond):
"What virus scanner do you use?"
This could be relevant.


all of my users have same logon script but some of PCes always
reboot
when
logon,
the logon script is only contained below:

NET USE H: \\PDC\PUBLIC

by the way .. all of them also install Trust-No-Exe ..
(this is third party tool for executable filter) .. .. I also already
removed Trust-No-Exe .. but the same problem still occurs .. once again
only
some of them reboots when logon .. please help .. any prompt reply would
be
appreciated
thanks a lot in advance


:

Insufficient information.

--
Dave




| I never try not to run Logon script because the script is only
contained as
| follow:
|
| NET USE H: \\PDC\PUBLIC
|
| and this problem only happened in some of clients .. any idea?
|
|
| Regards
| Winanjaya
|
| "David H. Lipman" wrote:
|
| > One PC or all nodes ?
| >
| > What if they don't run a Logon Script ?
| >
| > --
| > Dave
| >
| >
| >
| >
| > | > | My users run Win 2000 Prof SP4, all users has same a logon script
| > | (allusers.bat) and it contained as follow:
| > |
| > | NET USE H: \\PDC\PUBLIC
| > |
| > | but when they logon their PC reboot .. I checked to the event
viewer and it
| > | contained as follow:
| > |
| > | The computer has rebooted from a bugcheck. The bugcheck was:
0x0000001e
| > | (0xc0000005, 0x8044f718, 0x00000000, 0x6e697455). Microsoft
Windows 2000
| > | [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini010505-01.dmp.
| > |
| > | what should I do?
| > |
| > |
| >
| >
| >
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Random "rebooted from a bugcheck" reboots 1
Why do I frequently get BSODs if I log in too fast? 2
Random Bugcheck Reboot 5
BugCheck 1
Crashing 2
Windows 2000 Pro restarts without warning 1
event 1001 1
Bugcheck 2

Top