BSOD in Win 7...same error code

B

BodyBagz

Limp Gawd
Joined
Jan 12, 2006
Messages
333
Hello all...hopefully someone can help out with this aggravating issue. Sorry if I missed a post related to this thread...I did look.

I put this system together a week or so ago. Roughly 3 days after completion I started getting BSOD`s with the error code 124. Now after researching on the internet, I can not find anything concrete to attribute this error message to other than a basic "hardware issue"...

The only hardware that I have installed is normal hardware; mobo, proc, memory, vid card, and dvd-rw drive and a media card reader. Of those items, the only thing not being driven by Win 7 drivers is the video card as it is being run from Catalyst 10.2 driver package. I have uninstalled and re-installed said driver package with no change, still getting the BSOD.

I have run a memory check through Win 7 diagnostics and it returned "no errors found".

Anyone else have this issue? Anyone know a fix/cure for it? Anyone got an idea if I take the card out and reset it if this might be the issue?

System Specs below:
Windows 7 x64 Ultimate
AMD Athlon XII 7850 BE @ stock 2.8ghz w/stock cooling
MSI 785GTM-E45
Corsair CM2X2048-6400C5 RAM @ 800mhz
ATI Radeon HD4350 512nb @ stock - core-110mhz, mem-400mhz
MSI DVD-RW
 
Heres the latest info from my last BSOD...just 2 minutes ago...

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80053CD038
BCP3: 00000000B2004000
BCP4: 0000000098000175
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\032210-25615-01.dmp
C:\Users\Shane Cochran\AppData\Local\Temp\WER-36660-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
 
You need to install Debugging Tools for Windows - Native x64 and configure the online server for symbols, then load the crash dump (minidump) to see what caused the crash, if you dont have the tools handy, upload the minidump to any free hosting site and any of us will analize it for you.
 
OldMX said:
You need to install Debugging Tools for Windows - Native x64 and configure the online server for symbols, then load the crash dump (minidump) to see what caused the crash, if you dont have the tools handy, upload the minidump to any free hosting site and any of us will analize it for you.
Click to expand...

Thanks for the reply. I looked at downloading the Debugging Tools from MS...but as much as of a geek I am, that stuff actually seemed above my head...lol Am I reading to much difficulty in to this?

As far as the minidump file...do you mean to host the actual minidump file that is in the minidump folder, or am I totally confused? Thanks in advance for any help...
 
Well, if you already downloaded the debugger, configure the symbols server

http://support.microsoft.com/kb/311503

Once configured to use the online symbols server, load the crash dump from windows\minidump, after some seconds the debugger will show you what caused the problem.
 
Ok, downloaded the Debugging Tool...no idea as to how to go about using it...I even downloaded and installed the Symbols Package as well. Each time I try to open a .dmp file, the debugger says that the "symbol path" is not right...*see below*


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


Loading Dump File [C:\Windows\Minidump\031510-17206-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Users\Shane Cochran\Symbol
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Mon Mar 15 12:20:46.492 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:25.240
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
....
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80053fb038, b218c000, 185}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** 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!_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: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : hardware

Followup: MachineOwner
---------
 
this is what i see in that debug spew
Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information
and
Probably caused by : hardware

Followup: MachineOwner


start running memtest and make sure nothing is overheating (northbridge, video card etc...)
 
Looked for Memtest, but I am assuming I am a complete retard, cause all I have found report to x86 and I am running under x64...anyone got a link for the inept?

Also, I pulled my video card and attached an old "slocket" cpu fan to it...so far no BSODS. I noticed the majority of the BSOD`s came when I was doing something video based such as trying to convert video files via Handbrake or AnyVideo...I chalked it up to a driver issue, but even after re-installing the Catalyst drivers the problem persisted.

So I did what ATI should have did, I installed a fan on the vid card...and so far it seems to e doing the trick. I have completely re-encoded 4 films so far after this fix and no BSODs.

Thanks to those who answered...
 
Load the memory dump file again
Run .symfix
run .reload
then run !analyze -v
 
Tawnos said:
Load the memory dump file again
Run .symfix
run .reload
then run !analyze -v
Click to expand...

I see all that, and yet I have no idea as to how to go about "running" any of it. Is this all ran from the command line of Windows, or are these commands in the debugger tool itself?

I appreciate any and all help and offer a thanks in advance...
 
Ok, here is what i got from following above instructions after looking around...any ideas on what all this means?

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: fffffa80053fb038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b218c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000185, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff880`009f1a08 fffff800`03204903 : 00000000`00000124 00000000`00000000 fffffa80`053fb038 00000000`b218c000 : nt!KeBugCheckEx
fffff880`009f1a10 fffff800`02d9b513 : 00000000`00000001 fffffa80`053a5010 00000000`00000000 fffffa80`053a5060 : hal!HalBugCheckSystem+0x1e3
fffff880`009f1a50 fffff800`032045c8 : 00000000`00000728 fffffa80`053a5010 fffff880`009f1db0 00000000`00001000 : nt!WheaReportHwError+0x263
fffff880`009f1ab0 fffff800`03203f1a : fffffa80`053a5010 fffff880`009f1db0 fffffa80`053a5010 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f1c00 fffff800`031f7e8f : fffff880`009e9180 00000000`00000001 fffff880`009f1e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f1c40 fffff800`02c857ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`009f1c70 fffff800`02c85613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f1db0 fffff800`02d2cd22 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`023b54c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeInvalidateRangeAllCaches+0x72

STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
Followup: MachineOwner
 
Yeah, the idea: your hardware is failing. Likely some path that only gets executed in specific circumstances. I've seen it in the lab before, unfortunately it's a process of elimination. I'd start with your memory, then video card, then network card, then processor.
 
Tawnos said:
Yeah, the idea: your hardware is failing. Likely some path that only gets executed in specific circumstances. I've seen it in the lab before, unfortunately it's a process of elimination. I'd start with your memory, then video card, then network card, then processor.
Click to expand...

With it primarily happening while doing video encoding, that would lead me to believe it was either the processor or the video card...am I wrong to think this? I made sure my processor was setting at default speed, no OC at all through Overdrive...CPUID shows it tooling along at 2.8ghz as it should.

I thought the vid card might be overheating a bit, so thats why I dropped a fan onto the heatsink since this cheap card didnt come with one installed from retail. As of this writing, I have re-encoded about (7) 700-1400mb avi films down to 350mb h.264 files for use on my iPod Touch and have had 0 BSODs since the fan installation.

Sorry to keep pestering you, and if I am pestering you, please let me know...I only want to learn as much about this area as I can since I have little experience in actually debugging Windows. Thanks for all the relies and advice so far...it is appreciated.
 
Are you running the latest bios for the motherboard? If so, are memory timmings and voltage correctly detected? you can check that with cpu-z.
 
OldMX said:
Are you running the latest bios for the motherboard? If so, are memory timmings and voltage correctly detected? you can check that with cpu-z.
Click to expand...

Memory reads accordingly as it should based on the specs from Corsair, as shown by CPU-Z. The BIOS is dated 12/16/2009, so it is only 4 months old, but I have not checked to see if there is an update as of yet...but that is my next task...
 
If more than one stick of memory, pull one and see what happens... if it still does it, swap.....
 
Well, I just updated the BIOS from 8.0 to 8.4...and was that a fu**ing nightmare! :(System wouldnt even load the Windows Boot animation! I dicked with it for almost 2 full hours...finally getting it to boot from USB where I had downloaded the older 8.0 revision...except when it would post it showed that 8.4 was running. Finally got into Windows and sure enough, CPU-Z shows the BIOS as 8.4...

Dont know what I did wrong, right or otherwise...but I am back up and running... I flashed the BIOS through the MSI Live Update application...all seemed to go as it should...right up until the initial reboot...lol...then shit went sideways quickly...

Oh well, yet another lesson to learn from...:cool:
 
You must log in or register to reply here.
Back
Top