BSOD 0x124 - random - sometimes only freezes and then restarts

[SubjectX]

Hey peeps,

I need help

Recently my PC started to randomly getting 0x00000124 BSOD or just randomly freezes and restarts on its own.

Sometimes first startup is possible, sometimes I need to manually turn it off completely and then turn it on again to not get BSOD.

I have already ran memtest+, nothing. Everything is updated to the latest version (OS, drivers) and I didnt change anything in last few months..

 

[koolkat77]

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800d363028, f2000000, 20008f}

Unable to load image 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
Probably caused by : GenuineIntel

Followup: MachineOwner
---------
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: fffffa800d363028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000020008f, 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

CURRENT_IRQL:  0

STACK_TEXT:  
fffff800`00ba8c50 fffff800`0361a008 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeTryToAcquireSpinLockAtDpcLevel+0x35
fffff800`00ba8c90 fffff800`03619f0d : 00000000`00000008 00000000`00000000 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x54
fffff800`00ba8cd0 fffff800`0360de88 : 00000000`00000001 fffffa80`0d639000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`036c552c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`036c5393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`082d9c3e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03792900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`082d9c3e


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN

BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN

Followup: MachineOwner
---------

 

[SubjectX]

I have checked that list already, apart from fresh install of windows I already did all of them..

I cannot open dmp tho, can somebody check if there is a clue in there maybe?

 

[x BlueRobot]

Explain what you test you used for each step, and the duration of that test. For example, how many passes did you run MemTest86+ for? Post the results of all the tests completed.

PSHED.DLL is a Windows file which enables hardware errors to be logged and produced.

 

[SubjectX]

1. I have never OCed, runs on stock from the beginning..
2. My case is always open, all the fans are clear of dust and all are moving, my coretemp shows HI 32 degrees, catalyst overdrive shows 50 degrees.
3. All updated thru windows update or manual driver install like GPU for example.
4. Latest BIOS from official website
5. I have windows 7
6. Ran Memtest+ for three cycles, chkdsk-ed without errors, sfc /scannow doesnt find any integrity violations..
7. Didnt try it yet, since i have very delicate settings and configurations on current installation.
8. Did that with compressor, unplugged and plugged all cables, including power supply.
9. Cant really remove anything apart from 3 sticks on ram and only work on one..

 

[x BlueRobot]

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

Please upload the results of the sfc /scannow command and the chkdsk command, both tutorials listed here:

• http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html