Kmode fault on boot... what to do?

Message

abrogard · #1 Post by **abrogard** » Thu Feb 15, 2007 12:45 am

My T21 gradually got worse. Started off with the screen occasionally blacking out and then more and more and then throwing up dos text screens with a message about 'kmode exception...' (if I remember right) and now that's all it will do. I can't get any other response out of it.

What to do? Is it beyond fixing with some sort of cpu fault?

If it has gone forever can I rescue the contents of the disk somehow?

ab

egibbs · #2 Post by **egibbs** » Thu Feb 15, 2007 7:02 am

If you will write down the exact Kernel Mode exception error number and any parameters or text after it, we might be able to help.

You can also look it up here

Ed Gibbs

EDIT: Fixed link

abrogard · #3 Post by **abrogard** » Sun Feb 18, 2007 6:24 pm

Well how about that.... I posted a reply from the library computer on Saturday and it hasn't took...

Well, we finally got our ADSL enabled on our line today so I'm cooking with gas.

Here's the exact message:

Stop: 0x0000001E (0xC0000005,0xBFA984D0,0x00000000,0x00001028) KMODE_EXCEPTION_NOT_HANDLED

That's it.

I went to the location you indicated but found nothing there. The link is broken. Or was on Saturday. I will try again today.

regards,

ab

p.s. Yes, it is a 404, page not found, message.

SafeHarbor · #4 Post by **SafeHarbor** » Sun Feb 18, 2007 7:24 pm

Hi, Ab,

I posted the phrase into a Google search, and this was the first hit:

http://support.microsoft.com/kb/294728

See if that's your fix.

Lamar

abrogard · #5 Post by **abrogard** » Mon Feb 19, 2007 2:34 am

Hi...

Yes, I don't think that's the fix. The article applies to win2k server, which I don't have, and to NT. I've got standard win2k.

And their actual message is:
Error Message: STOP 0x00000001e KMODE_EXCEPTION_NOT_HANDLED in Win32k.sys

which isn't what I get.

The search continues.

ashleys · #6 Post by **ashleys** » Mon Feb 19, 2007 3:39 am

Looks like you got an access violation in storage. From the symptoms you've described most likely caused by by storage corruption or failure.

Look at this KB article for general troubleshooting on that STOP code.

http://support.microsoft.com/kb/275678

#7 Post by **RealBlackStuff** » Mon Feb 19, 2007 5:11 am

The original link from 'egibbs' was pasted in twice.
It should be: http://aumha.org/win5/kbestop.htm

Also check your memory sticks, reseat/swap them, try with 1 stick etc. Run memtest86 for at least 4 cycles on each individual RAM stick and on both together.

abrogard · #8 Post by **abrogard** » Mon Feb 19, 2007 4:01 pm

Thanks for this link: http://aumha.org/win5/kbestop.htm

It'll be a valuable resource for those unhappy times. I didn't know about it before.

I'll get to work, do what I can. The suggestions for replacing drivers and suchlike are going to have to wait until I can get into the computer.... I need a bootable cd I guess...

#9 Post by **RealBlackStuff** » Tue Feb 20, 2007 2:32 am

If you get the .iso version from memtest, you can burn a bootable CD from that

abrogard · #10 Post by **abrogard** » Tue Feb 20, 2007 6:35 am

Well that sort of worked - I got a bootable CD and I ran memtest and got no errors, even after about fifteen minutes of testing.

But exiting memtest simply made the machine boot back into memtest again - i.e. I couldn't look at my hard drive, search for known virus files or do any of that good stuff...

But now, at least, I know it isn't the memory.

Kmode fault on boot... what to do?

Kmode fault on boot... what to do?

Who is online