Rebooting with kmode exception not handled error

[Guest]

My 4 networked machines (Win 2K Pro)with installed SP 4 have started these ramdon acts of
rebooting every few hours. Nothing new was installed when
this first started and I'm at a loss of what it is. In the
event viewer log it says

The computer has rebooted from a bugcheck. The bugcheck
was
0x0000001e (0xc0000047, 0x8042c1b4, 0x00000000,
0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was
saved in: C:\WINNT\Minidump\Mini122903-02.dmp.

Except for the filename that it dumps to and the last set
of hex umbers, the error is always exactly the same. I
used dmpchk.exe to look at the file and it offers nothing
useful

I then changed the setting to give the blue screen and
send a full memory dump to a file. When it blue screens, I
get the same hex numbers and it says "kmode exception not
handled." And then lists the ntoskrnl.exe file

Any ideas what could be going on? Also - I can't figure
out how to look at the full memory dump file and
dmpchk.exe only lets you look at the 64kb files

 

[Guest]

-----Original Message-----
My 4 networked machines (Win 2K Pro)with installed SP 4

have started these ramdon acts of

rebooting every few hours. Nothing new was installed when
this first started and I'm at a loss of what it is. In the
event viewer log it says:

The computer has rebooted from a bugcheck. The bugcheck
was:
0x0000001e (0xc0000047, 0x8042c1b4, 0x00000000,
0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was
saved in: C:\WINNT\Minidump\Mini122903-02.dmp.

Except for the filename that it dumps to and the last set
of hex umbers, the error is always exactly the same. I
used dmpchk.exe to look at the file and it offers nothing
useful.

I then changed the setting to give the blue screen and
send a full memory dump to a file. When it blue screens, I
get the same hex numbers and it says "kmode exception not
handled." And then lists the ntoskrnl.exe file.

Any ideas what could be going on? Also - I can't figure
out how to look at the full memory dump file and
dmpchk.exe only lets you look at the 64kb files.

.

Did you check for viruses ??

 

[Greg Lirette [MS]]

With a bugcheck 1E it is really hard to say what the problem is without
looking at the dump. You may consider opening a PSS call to have the dump
reviewed.

This posting is provided "AS IS" with no warranties, and confers no rights.