I am experiencing a frequent BSOD (upwards of 6 times a day). I've been doing some testing and I think I may have locked it down. I would appreciate some guidance on the next step to take.
My Specs
- OS: Windows 7 Ultimate
- Motherboard: AMD 990FXA-UD3
- CPU: AMD FX-8350
- GPU: NVIDIA GeForce GTX 580
- RAM: 8GB DDR3 1333
- Audio Driver: Realtek 64bit
What I've Witnessed
So far I've noticed that it doesn't happen when logged into my wife's user profile. This initially led me to believe it was related to software running on my profile. I've further noticed that anytime I have RaidCall (a VOIP) open on my profile I eventually get the BSOD regardless of who is the active user.
What I've Tried
I've re-installed RaidCall and my audio drivers. I've ran a chkdsk, virus scan, and defrag. I've activated windows driver verifier for all 3rd party drivers. I've rain AIDA64 Extreme Edition (trial) and received a hardware failure alert after stress-testing for 6 minutes.
Resuts
The BSOD that happened after driver verifier was running didn't give any valuable information. I was at work when it happened, but my wife reports that it mentioned a driver failure, but did not give any information about the driver. I had to stop verifier so she could use the computer. The next BSOD I got was also while I was at work, but this time it said "unrecoverable hardware failure".
Conclusion
I'm thinking thinking this is a problem with my motherboard. I've had mobo-related BSOD problems in my last 3 computers so it wouldn't surprise me. Is there anything else I can try before trying to see if the manufacturer will honor their warranty? Thanks! ^_^
Update 1
I got another BSOD. It was another "uncorrectable hardware error" this time. No RaidCall, no audio happening at all. Perhaps those things were just coincidence. In any case, my minidump directory was empty when I checked it which is most unfortunate, but one did appear after this most recent BSOD. Here is the link:
https://dl.dropboxusercontent.com/u/44699367/082013-26020-01.zip
Update 2
BSOD again (followed by a freeze w/o BSOD ~4m later. Dump link: https://dl.dropboxusercontent.com/u/44699367/082013-22120-01.zip
Answer
You have no driver issue, you have a L1 Cache issue with your AMD FX CPU:
You get this Bugcheck/BSOD:
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR
http://msdn.microsoft.com/en-us/library/ff557321%28v=vs.85%29.aspx
The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124.
This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows
Hardware Error Architecture (WHEA).
*******************************************************************************
* *
* 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: fffffa8009387028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bc800010, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000100149, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: Steam.exe
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre
STACK_TEXT:
nt!KeBugCheckEx
hal!HalBugCheckSystem
nt!WheaReportHwError
hal!HalpMcaReportError
hal!HalpMceHandler
hal!HalHandleMcheck
nt!KxMcheckAbort
nt!KiMcheckAbort
0x0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
FAILURE_ID_HASH_STRING: km:x64_0x124_authenticamd_processor_cache
===============================================================================
Common Platform Error Record
-------------------------------------------------------------------------------
Record Id : 01ce9e238a2c44a9
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 8/21/2013 4:22:25 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa80093870a8
Section @ fffffa8009387180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Data Write
Flags : 0x00
Level : 1
CPU Version : 0x0000000000600f20
Processor ID : 0x0000000000000006
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa80093870f0
Section @ fffffa8009387240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000006
CPU Id : 20 0f 60 00 00 08 08 06 - 0b 32 98 3e ff fb 8b 17
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0 @ fffffa8009387240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa8009387138
Section @ fffffa80093872c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL1_DWR_ERR (Proc 6 Bank 0)
Status : 0xbc80001000100149
BiosVersion = FA
BiosReleaseDate = 10/23/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = 990FXA-UD3
[CPU Information]
~MHz = REG_DWORD 4018
Identifier = REG_SZ AMD64 Family 21 Model 2 Stepping 0
ProcessorNameString = REG_SZ AMD FX(tm)-8350 Eight-Core Processor
VendorIdentifier = REG_SZ AuthenticAMD
As you can see you have L1 Cache Error when writing data to the L1 Cache. I can see that there is a BIOS update to Version FC, maybe this fixes it. Also run CPU stress test tools to see if the CPU is damaged. Also monitor the CPU temperature. Maybe this is the cause.
No comments:
Post a Comment