Yep, you summed it up right. I've also monitored all temps and found nothing overheating even when the crashes occur. Motherboard is a long shot for the BSOD issue, because it'd have to be 2 separate mobos (different model) with the same problem in a row.
The bios problem could be unrelated, so I don't know what to make of it...
You've also enabled Driver Verifier for at least 24 hours and it found nothing right?
If not then please enable it by following these instructions.
Driver Verifier - Enable and Disable
Oh, I only enabled it for 1 crash. I thought it improved the crash log somehow. What is the benefit of keeping it on for 24 hours? Does it create a special diagnosis after a certain point?
The purpose behind running Driver Verifier for 24hrs is to give it sufficient time to completely stress all the drivers, maximizing its ability to cause a BSOD in which the faulting driver can be identified.
If you receive a BSOD shortly after using the PC with Driver Verifier enabled, then it has done its job. You can then disable it, and upload the .dmp files using this tool so it can be analysed:
DM Log Collector.exe
Ahhh, thanks for the explanation. I certainly don't need the help in generating BSODs : P
I don't know if there's any additional info here that isn't attached to the first post, but just in case, I've attached the latest dm log, which should also include the crash caused with Driver Verifier.
Update: the new hard drive didn't fix it. : (
Well these 0x124 bugchecks indicate the CPU is at fault but you've already ran Prime95. Please run it again for around 2 hours.
Code:=============================================================================== Common Platform Error Record @ fffffa8005223028 ------------------------------------------------------------------------------- Record Id : 01cf4dfda1fb8de4 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 4/1/2014 23:12:58 Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa80052230a8 Section @ fffffa8005223180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Data Read Flags : 0x00 Level : 1 CPU Version : 0x0000000000100f43 Processor ID : 0x0000000000000002 Instr Pointer : 0x0x000000006741f162
Uuugh... what the heck...! Prime95 tested perfectly before, but now I get crashes within a few minutes! Maybe the behavior changed because of all the replaced parts. I don't even know.
Anyway, the 'good' news is Prime95 crashes real quick. When I run 'Blend' tests, I get a BSOD "uncorrectable hardware error" -- the same I get when gaming -- within 2-5 minutes. This is easily replicatable with Blend tests. The bugcheck code is 0x00000124. Whocrashed points toward hal.dll for these.
When I run 'Short' tests, in 20+ minutes (sometimes it lasts a while, sometimes it happens quite quickly) I get a BSOD saying "clock interrupt was not received on a secondary processor within the allocated time interval." Error 0x00000101. Whocrashed says the error is either hal.dll or ntoskrnl.exe for this kind of crash.
So... hopefully this is useful information for diagnosis. I just wish it had shown up earlier. At least all the part replacements I tried were upgrades...
Right, that definitely sounds like a CPU issue, I would highly recommend replacing it.
I'm sorry that you had to replace lots of parts but unfortunately that ends up being the best route to go down when dealing with 0x124 bugchecks, it's mostly trial and error.
Yeahhh, I've gone ahead and ordered a new one. It's actually a good thing I replaced my motherboard for one that supports AM3+, however, since apparently AM3 CPUs are being discontinued (couldn't find any non-used ones for sale, anyway).
The old parts aren't going to waste regardless, so it's cool.
I'll post an update when I get the new CPU.
Quote