Resolved Random BSOD

I am getting the BSOD at random times while working on my PC. Here is the minidump file report:


Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Kim Rinde\Desktop\Mini090512-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Sep 5 09:32:37.877 2012 (UTC - 5:00)
System Uptime: 0 days 13:11:05.479
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {20, 2, 0, b3fa2520}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image ɐĸɐĸɘĸɘĸɠĸɠĸɨĸɨĸɰĸɰĸɸĸɸĸʀĸʀĸʈĸʈĸʐĸʐĸ, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ɐĸɐĸɘĸɘĸɠĸɠĸɨĸɨĸɰĸɰĸɸĸɸĸʀĸʀĸʈĸʈĸʐĸʐĸ
*** ERROR: Module load completed but symbols could not be loaded for ɐĸɐĸɘĸɘĸɠĸɠĸɨĸɨĸɰĸɰĸɸĸɸĸʀĸʀĸʈĸʈĸʐĸʐĸ
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ???????????????????????????????????? ( ____________________________________+520 )

Followup: MachineOwner
---------


Can anyone help me figure out what is wrong?

Thanks.

Kim

 

How do I determine what the correct symbols are?

Thank you.

 

The link you posted, http://www.microsoft.com/en-us/download/details.aspx?id=8279, is for MS SDK 7.1 for Windows 7. I'm running Windows XP & I already have Debugging Tools for Windows (x86) on my PC.

Kim

 

I updated my video card drivers & haven't had a BSOD since then. Thanks!

 

I'm sorry. Thank you for your help.