Help
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
My computer just encountered a new BSOD today. It appears to be hardware-related; the screen itself said something about an 'UNCORRECTABLE HARDWARE ERROR'. I had just booted it up for the first time today; the crash happened seconds after I connected my iPod to sync it. Of course after rebooting I was able to connect my iPod fine (indeed, everything seemed OK), so no idea what caused it. I would think that a hardware problem would be more serious. I then tried to debug it the same way I successfully debugged my last BSOD using WinDbg; I've correctly set the symbol path and everything, but bizarrely it still complains that it doesn't have the right symbols. I can open all my old crash dumps just fine with the same symbol path; the one related to this new problem is the only one that for some reason can't use the symbol path. (It's online; SRV*c:\symbols*http://msdl.microsoft.com/download/symbols) I'm using a Toshiba Satellite A305-S6858 laptop running 64-bit Vista. Here is what WinDbg does give me, along with the complaining about symbols.
Does anyone know what could have happened, or how I can get the symbols to work properly this time? Should I be checking on my laptop's warranty?
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa80090df030, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: explorer.exe CURRENT_IRQL: f STACK_TEXT: fffff800`038f0c18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN Followup: MachineOwner
Does anyone know what could have happened, or how I can get the symbols to work properly this time? Should I be checking on my laptop's warranty?
This post has been edited by dpitch40: 16 November 2009 - 12:42 PM
Back to top
