New
#1
Daily BSOD 0x124 (few times a day)
Don't know what to do!
Getting this BSOD on Windows 7, Windows 8 (fresh install) so it must be a Hardware failure/problem.
The system just freezes (mouse, keyboard, sound) picture is still there and then restarts or I have to push the restart button
Have 4 minidumps from win7 and 3 from win8 (installed 2 day ago) all the same
System:
Q6600 G0 (stock 2.4GHz) cooled with Scythe Mugen (2x 120mm)
Asus P5QL-E
8GB DDR2 (2x2GB Corsair, 2x2GB Kingston)
Asus nVidia 560Ti (320.49 drivers)
PSU: 850w LC Power Arkangel (looks same as the Thermaltake Toughpower / same internals)
OS: Windows 7 Pro x64 and Windows 8 Pro x64 (currently)
All the BSOD's are the same.
My dump analysis:
And error report:Code:******************************************************************************* * * * 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: fffffa8008b688f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`02df76f0 fffff800`10777687 : 00000000`00000000 fffffa80`08b688d0 fffff800`106f2020 00000000`20206f49 : nt!WheapCreateLiveTriageDump+0x81 fffff880`02df7c20 fffff800`1056a0e7 : fffffa80`08b688d0 fffff800`1056b028 fffff800`106f2020 00000000`00000001 : nt!WheapCreateTriageDumpFromPreviousSession+0x3b fffff880`02df7c50 fffff800`1056b04d : fffff800`106f1fc0 fffff800`1056b028 fffff800`106f2020 fffffffe`9a5f4400 : nt!WheapProcessWorkQueueItem+0x57 fffff880`02df7c90 fffff800`104a12a1 : fffff800`1068f110 fffffa80`06a1b380 fffff800`104b1b00 fffff800`1068f100 : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`02df7cc0 fffff800`10435fd9 : 00000000`00000000 00000000`00000080 fffff800`104a1160 fffffa80`06a1b380 : nt!ExpWorkerThread+0x142 fffff880`02df7d50 fffff800`104ea7e6 : fffff880`009bf180 fffffa80`06a1b380 fffff880`009cae40 fffffa80`06a21040 : nt!PspSystemThreadStartup+0x59 fffff880`02df7da0 00000000`00000000 : fffff880`02df8000 fffff880`02df2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_PRV BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_PRV Followup: MachineOwner
Eventviewer reports: For Processor APIC ID: 0,1,2 and 3 (all 4 cores)Code:=============================================================================== Common Platform Error Record @ fffffa8008b688f8 ------------------------------------------------------------------------------- Record Id : 01ce8f4bf47c66ba Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/2/2013 6:46:13 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa8008b68978 Section @ fffffa8008b68a50 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 0 CPU Version : 0x00000000000006fb Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa8008b689c0 Section @ fffffa8008b68b10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : fb 06 00 00 00 08 04 00 - bd e3 00 00 ff fb eb bf 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 @ fffffa8008b68b10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa8008b68a08 Section @ fffffa8008b68b90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0) Status : 0xb200004000000800
What I tryed/did:Code:A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Bus/Interconnect Error Processor APIC ID: 0 The details view of this entry contains further information.
- Memtest86 for 16h all pass (9 total)
- OCCT CPU Test (4h) max temp 62°C (143F) no errors
- Prime95 FFT still running (4h+ at the moment) max temp 58°C (136F) pass (still running)
- Reinstalled Windows (from 7 to 8) fresh install
- Checked HDD, Seagate DOS tool, Windows CHKDSK, SFC /SCANNOW... (HHD is OK)
- Removed/reinstalled graphics drivers (latest WHQL, previous working 314,07)
My suggestions:
- Power supply (will try with another one tomorrow)
- Graphics card (will try with another one after PSU check)
- CPU (don't know how to test it other than replacing it or trying it in another system)
- Motherboard (if the CPU isn't the problem)
Bonus:
Can play games (BF3...) with no problems at all, system doesn't crash)
Can run stress test (CPU, GPU...) with no problems at all, system doesn' crash)
As long as the system isn't idling, stationary. (the system is at load, games, stress...) it's all fine.
When surfing or doing normal work (word) it's going to BSOD (0x124) or it's going to happen later on.
The BSOD sometimes happens on windows starting (after BIOS post).
All that started on one day that I was not at home but the PC was running an few power outages happend (so the system started over and over / power outage on startup)
Last edited by Djsajmy; 02 Aug 2013 at 08:56.