Blue screen ***STOP error

ainsane

Distinguished
Dec 16, 2001
15
0
18,510
Hi. Im having this problem with my computer.

In windows 2000 I'll randomly (often) get a *** STOP (bunch of numbers), KMODE_EXCEPTION_NOT_HANDLED error on a blue screen.

I tried to install Windows XP on a formatted partition, but I get a very similar error, with just the '*** stop part', and it says something about memory.

If anyone has any idea what this means, please help me out.

Thanks a lot!
 

Toejam31

Distinguished
Dec 31, 2007
2,989
0
20,780
You didn't give out quite enough information, IMO. Those "bunch of numbers" mean something, unlike the confusing and often useless error messages you've probably seen in Win9x.

When using the Microsoft Knowledge Base, those numbers, as well as the error message, are searchable.

Here's a basic start in your search for an answer:

<A HREF="http://search.microsoft.com/default.asp?so=RECCNT&qu=KMODE_EXCEPTION_NOT_HANDLED&boolean=ALL&i=00&i=01&i=02&i=03&i=04&i=05&i=06&i=07&i=08&i=09&ig=01&ig=02&ig=03&ig=04&ig=05&ig=06&ig=07&ig=08&ig=09&ig=10&p=2&nq=NEXT&fqu=KMODE_EXCEPTION_NOT_HANDLED&siteid=us" target="_new">http://search.microsoft.com/default.asp?so=RECCNT&qu=KMODE_EXCEPTION_NOT_HANDLED&boolean=ALL&i=00&i=01&i=02&i=03&i=04&i=05&i=06&i=07&i=08&i=09&ig=01&ig=02&ig=03&ig=04&ig=05&ig=06&ig=07&ig=08&ig=09&ig=10&p=2&nq=NEXT&fqu=KMODE_EXCEPTION_NOT_HANDLED&siteid=us</A>

If you want a definitive answer to a question, you <i>must</i> be as specific as possible with the details. It's very hard to troubleshoot a system from a distance without a certain amount of information from the user.

For example, if you were to document the error message that "says something about memory", and post it here, it would be much easier to lend you a hand.

Later ...

Toejam31

<font color=red>My Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">http://www.anandtech.com/mysystemrig.html?rigid=6847</A>
______________________________________________________________

<font color=purple>"Procrastination on your part does not constitute an emergency on my part."</font color=purple>
 

ainsane

Distinguished
Dec 16, 2001
15
0
18,510
Sorry, stupid me.

Ok the Windows 2000 blue screen crash says this exactly:
*** STOP: 0x0000001E (0xC000001D, 0xA0018CFB, 0x00000038, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED

the Windows XP installation error says this:
*** STOP: 0x00000001A (0x00000780, 0xC0352E00, 0x81076020, 0x80000CD8)

and then the 'says something about memory' thing I was talking about is it just gives you a possible reason for the numbers. It says to try disabling shadowing or somethign in the bios, but mine already is.

Also, the numbers arent exaclty the same every time.

Thanks in advance,
Adam.
 

Toejam31

Distinguished
Dec 31, 2007
2,989
0
20,780
You aren't stupid, Adam; you just didn't know. It's not an uncommon scenario.

Here's a troubleshooting page on this kind of error message:

<A HREF="http://www.microsoft.com/WINDOWS2000/techinfo/reskit/en/ProRK/prhd_exe_bddb.htm" target="_new">http://www.microsoft.com/WINDOWS2000/techinfo/reskit/en/ProRK/prhd_exe_bddb.htm</A>

You should look in the Event Viewer and see if a file is associated with the error message, in case the problem is due to a driver.

You should also check and make sure that your hardware is compatible with Win2K and WinXP:

<A HREF="http://www.activewin.com/winxp/winxphclx86.txt" target="_new">http://www.activewin.com/winxp/winxphclx86.txt</A>

<A HREF="http://www.microsoft.com/windowsxp/home/howtobuy/upgrading/default.asp" target="_new">http://www.microsoft.com/windowsxp/home/howtobuy/upgrading/default.asp</A>

What the error message was talking about was a setting in the BIOS for memory <i>caching</i>. Disable this, if you haven't already. You might need to refer to your mainboard manual for an explanation of the different settings in the BIOS. If you don't have one ... you might find it on the manufacturer's website in a downloadable form.

If you still can't figure out what is going on after browsing through these links, I'll need even more information, and this time, on your system specifications. Sorry. I have a pretty good idea of what the error message is about now, and it's likely to be a driver, or a problem with a memory setting in the BIOS. Or an older device that is not compatible with either of the operating systems.

However ... I have no idea what that hardware is; you haven't told me yet.

I'll need to know everything possible, from the processor type/speed to the mainboard type, brand/model number. The hard drive, brand and model number. Sound card. Peripherals. In other words, an accurate list of your entire system configuration ... all the things that I would normally be able to see if the system was right in front of me.

This might sound like an enormous pain-in-the-whatsis, but again, this is a very normal request when doing technical support. Some computers are Buicks, some are Fords ... some are Volvo's. Some are "white box", and may have been built by a local shop, or by your neighbor across the street. For all intents and purposes, they are meant for the same kind of functions, but in many respects, absolutely nothing alike.

Check my signature for an example, if you please.

Toejam31


<font color=red>My Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">http://www.anandtech.com/mysystemrig.html?rigid=6847</A>
______________________________________________________________

<font color=purple>"Procrastination on your part does not constitute an emergency on my part."</font color=purple>
 

ttaylor

Distinguished
Jan 30, 2001
12
0
18,510
I just finished fighting a similar problem in a Win2000
installation I just made. Since I was building a test
system using an ancient P133 motherboard for driver
debugging purposes, I suspected everything but what it
turned out to be. I decreased the PIO mode on the disks
from 4 to 2. I removed every adapter but the video.
All BIOS caching and shadow memory was turned off.
External cache was disabled. The latest BIOS was flashed.

The problem turned out to be an intermittent bit
error in DRAM. I used a free memory tester that I
downloaded from http://www.teresaudio.com/memtest86 ,
but there are many other free and shareware testers
available. I suggest you try this after you've
eliminated the other options, but be patient! Only
test # 3 in memtest86 would cause the error to occur
(cached access, walking bit), and even then it did
not occur on every pass. I would go at least 3 passes.

I could kick myself because memory errors used to be
a big problem back in 386 days, but I've seen less
and less of these problems recently to the point that
I don't even think about it.

For the record, my errors also occurred at random
positions. Sometimes in ntoskrnl.exe, some in
win32k.sys, sometimes KBDUS.DLL wouldn't load,
sometimes tcpip.sys wouldn't load.

Tom Taylor