I've tried what you said. I had to return to Last Known Good Configuration
to be able to boot up again, but for some reason there was no new crash dump
file for today.
I examined yesterdays and they kept making a reference to afd.sys, saying it
was trying to access a non-existent area of memory. I've searched my hard
drive for this file but can't find one.
To make things more confusing, Windows Update now loads in IE (which was
guaranteed to bring up the blue screen before), and ICQ5 does not work, just
gives the blue screen again.
I am fairly technical with computers, but this one has me confused.
Paul
"David Candy" <.> wrote in message
Type verifier in Start Run, follow the wizard but choose All Drivers. This
will slow down your computer and cause more blue screen crashes but will
pinpoint what is causing the crash (if the original error message didn't).
Once you fix it you rerun verifier and turn it off.
If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).
You will be creating a crash dump file in c:\windows\minidump every blue
screen. Make sure you are set to record minidumps (Small Memory Dumps) -
type it in Help to see how.
Then
If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx
)
Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Load the crash dump file into windbg
and read what it says. You may need to tell it where the symbols are. Read
it.
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)
If the above is too technical then email the crash dump files to david @
mvps.org. Don't send me lots of them. Just the one from your last crash
after you turn verifier on. And only one per mail.
You can look up specific details here
http://msdn.microsoft.com/library/d..._ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp
If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/windiag.asp
If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to
http://oca.microsoft.com
Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters that are memory addresses aren't that useful
for searching, but NTStatus codes are (plus you can look them up here
http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).
