Random frequent BSOD 0x124 / 0x00000124 ntoskrnl.exe?

Circle said:

Because the voltages aren't controlled by the processor this could also be either your motherboard or PSU.

x BlueRobot said:

... which means the CPU has detected a hardware problem and the address points to a processor error because the CPU has found one, so it could be a different form of hardware which is causing the issue. Thanks to Archie for pointing this out to me.

• Stop 0x124 - what it means and what to try

If all the hardware checks and swaps seem to be fine, then it could be due to a bad motherboard.

Is there any way to confidently determine exactly which one is problematic? Funds are a bit tight

I installed windows xp as a last resort and the reboots have continued though the bc code has changed. Attached a new set of minidumps.

Memory:

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 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:

• Screenshots and Files - Upload and Post in Seven Forums

Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.

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

• Disk Check

Use this command with Disk Check:

Code:

chkdsk C: /f /r