Stop error while booting

skeetninjer · 04-29-2006, 04:44 PM

Yesterday after my randomly shut off (my power supply is a little screwy) i start up my comp and I get a blue screen of death. The error message is;

Stop:0x0000001e (0xC0000005, 0xB7A924D0, 0x00000000,0x00001028)
KMODE_EXCEPTION_NOT_HANDLED

This happens right after the windows 2k proffesional loading screen comes up. I checked microsoft knowlege base and they seem to have answers to every problem of this type except this one. Can anybody help me out?

skeetninjer · 04-30-2006, 02:22 PM

Does anybody know? Has this already been posted and the search engine didnt find it?

/sigh

**Bartender** · 05-06-2006, 08:53 AM

skeet -
Did you take a look at this one?

http://support.microsoft.com/?kbid=294728

Sounds like what you're describing. Of course, with Microsoft it's always someone else's fault. Googling your stop code I found others who'd fixed the problem by re-loading video drivers, etc.

Good luck

04-29-2006, 04:44 PM	#1 (permalink)
skeetninjer Registered User Join Date: Apr 2006 Posts: 3 OS: win2000	Stop error while booting Yesterday after my randomly shut off (my power supply is a little screwy) i start up my comp and I get a blue screen of death. The error message is; Stop:0x0000001e (0xC0000005, 0xB7A924D0, 0x00000000,0x00001028) KMODE_EXCEPTION_NOT_HANDLED This happens right after the windows 2k proffesional loading screen comes up. I checked microsoft knowlege base and they seem to have answers to every problem of this type except this one. Can anybody help me out? Last edited by skeetninjer; 04-29-2006 at 04:46 PM.

04-30-2006, 02:22 PM	#2 (permalink)
skeetninjer Registered User Join Date: Apr 2006 Posts: 3 OS: win2000	Does anybody know? Has this already been posted and the search engine didnt find it? /sigh

05-06-2006, 08:53 AM	#3 (permalink)
Bartender Mentally divergent Join Date: Jun 2005 Location: Chehalis, WA, USA Posts: 1,285 OS: W2K, Ubuntu 8.04	skeet - Did you take a look at this one? http://support.microsoft.com/?kbid=294728 Sounds like what you're describing. Of course, with Microsoft it's always someone else's fault. Googling your stop code I found others who'd fixed the problem by re-loading video drivers, etc. Good luck