Dear Experts, Please help me understand the reason for my BSOD Stop. I was working with a MS Live Movie Maker, editing some pictures, when the problem occured. Thanks, beskio
Last edited by beskio; 02 Jun 2013 at 04:51. Reason: SF log files added
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8007e0a028, be200000, 5110a} Probably caused by : GenuineIntel Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * 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: fffffa8007e0a028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value. Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE Followup: MachineOwner --------- 3: kd> !errrec fffffa8007e0a028 =============================================================================== Common Platform Error Record @ fffffa8007e0a028 ------------------------------------------------------------------------------- Record Id : 01ce5f62f53e2743 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 6/2/2013 9:22:10 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa8007e0a0a8 Section @ fffffa8007e0a180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Generic Flags : 0x00 Level : 2 CPU Version : 0x00000000000206a7 Processor ID : 0x0000000000000003 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa8007e0a0f0 Section @ fffffa8007e0a240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000003 CPU Id : a7 06 02 00 00 08 10 03 - bf e3 9a 1f 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 @ fffffa8007e0a240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa8007e0a138 Section @ fffffa8007e0a2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : GCACHEL2_ERR_ERR (Proc 3 Bank 8) Status : 0xbe2000000005110a Address : 0x000000023e3836c0 Misc. : 0x000000d08202c086
TipStop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 Troubleshooting Strategy
If you are overclocking any hardware, STOP. Reset any changed values back to default.
Please run these tests and report back the results
1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure
Hi,
I have run sfc /scannov, Windows Resource Protection did not find any integrity violations
I have run chkdsk, that did not find any issues with the HDDs
I have also run the Samsung Hard Drive diagnostics, that did not find any issues as well
I have skipped the Clean Setup (that seemed to be too much work, and my BSOD did not happen since then).
I was not able to get the memory tests running, as booting from the USB stick halted with Boot Error.
In BIOS I did not have the possibility to select "USB - zip", I only had USB Fat32 option.
Any idea what could have gone wrong? I reformatted the USB about 4 times...
thanks,
beskio
Jonathon King said:
Did you follow 3 and 4 from the tutorial? You shouldn't have a "USB.zip" Let it run for at least EIGHT full passes, it will take a few hours. This may take some time to track down your issue. The 0x124 stop error usually is hardware related and often difficult to find.
Here is the memtest86+ file to use.
Attachment 271111
Hi Britton30,
Thanks for the support. I tried writing the iso file to DVD, that boots nicely, so I will run the memtests during the night.
/beskio
Hi,
I have run memory tests (13 passes), with no errors.
No BSOD happened during the last days.
Thanks for the great help from Sevenforums
/beskio
Quote