Rebooting with kmode exception not handled error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,

My machine (Win 2K Pro) has 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.

Thought about just reinstalling but that seems like a huge
pain.... Though, this rebooting every few hours isn't
exactly my idea of fun either.

Thanks in advance.
 
Hey anonymous,

It appears that you are not the only one with the same problem.
I have experience exactly same issue, even more it happens on 4 machines in the small network environment
Did you ever get any response from any one ?

Thanks for your response.

netgu

----- (e-mail address removed) wrote: ----

Hi all

My machine (Win 2K Pro) has 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

Thought about just reinstalling but that seems like a huge
pain.... Though, this rebooting every few hours isn't
exactly my idea of fun either

Thanks in advance
 

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

Back
Top