STOP 0x000000d1 (0x000000 0x000000 0x000002 0x00000000)

[danieleB]

Hello, when i *restart* my OS win xp home, it appears the death blue
screen with the stop advise in subject.
It happened i suppose after installing SP2 on the notebook (compaq
presario 733ea).
I tried with :
1) selecting paging file = 0
2) selecting creation of minidump file in case of system error
3) selecting creation of memory.dmp file in case of system error

For the last 2 points i downloaded and installed the winxp support
tools (dumpchk.exe in particular), but winxp does not create any "log"
file so i cannot analyse anything.
What can i do? I only know there's a driver faulty, but what?
If some power user or MS MVP can help me i will appreciate very very
much, thank you.

Daniele

 

[Kerry Brown]

Hello, when i *restart* my OS win xp home, it appears the death blue
screen with the stop advise in subject.
It happened i suppose after installing SP2 on the notebook (compaq
presario 733ea).
I tried with :
1) selecting paging file = 0
2) selecting creation of minidump file in case of system error
3) selecting creation of memory.dmp file in case of system error

For the last 2 points i downloaded and installed the winxp support
tools (dumpchk.exe in particular), but winxp does not create any "log"
file so i cannot analyse anything.
What can i do? I only know there's a driver faulty, but what?
If some power user or MS MVP can help me i will appreciate very very
much, thank you.

Daniele

Here's a link to help with troubleshooting stop errors.

http://aumha.org/win5/kbestop.php

As you have deduced it's probably a driver problem. Here's a link to help
with troubleshooting drivers.

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

Here's a search of Microsoft for that particular error.

http://search.microsoft.com/results.aspx?q=0x000000d1&l=en&OtherSite=&mkt=en-US&FORM=QBMA

Here's one of the results specific to notebooks

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

Sorry I couldn't do much more than post some links for you. Troubleshooting
stop errors is never easy. My first course of action is usually to test the
ram. Even though it seems to be related to installing SP2 it never hurts to
check the obvious, easy things first.

www.memtest.org

 

[danieleB]

Sorry I couldn't do much more than post some links for you. Troubleshooting
stop errors is never easy. My first course of action is usually to test the
ram. Even though it seems to be related to installing SP2 it never hurts to
check the obvious, easy things first.

www.memtest.org

I will try, even if i suppose that if the OS starts without problem it
shouldn't be a ram problem (i hope!). I hope anywhere that it could be
the real problem!
Thanks a lot for the links,I had just read many of this but the first
is fantastic!

daniele

 

[Kerry Brown]

I will try, even if i suppose that if the OS starts without problem it
shouldn't be a ram problem (i hope!). I hope anywhere that it could be
the real problem!
Thanks a lot for the links,I had just read many of this but the first
is fantastic!

daniele

Windows will often run with bad ram. Until the bad ram is accessed you won't
notice anything. Even when it is accessed you may not notice it. If it was
used for storing a document for example you may just get an odd character or
two in the document. If a driver or Windows itself is stored in the bad ram
then everything blows up. From your description I don't think it is ram but
it is an easy thing to check and often eliminates a wild goose chase. Make
sure you let the test run for several hours at least.