Windows 10: BSOD once a week with bug check code, 0x00000124

According to the logs, there is a month between the last 2 dumps, if this is hardware then the crashes should occur more frequently like daily.
This means that either software or driver is causing you the crashes.
Some old drivers:
Code: MBfilt64 Fri Jul 31 05:40:32 2009 (4a7267b0) MBfilt64.sys WmXlCore Tue Apr 27 22:09:26 2010 (4bd74476) WmXlCore.sys WmBEnum Tue Apr 27 22:10:19 2010 (4bd744ab) WmBEnum.sys PaeFireStudioMidi Fri Jan 21 06:41:33 2011 (4d391c8d) PaeFireStudioMidi.sys // Presonic PaeFireStudioAudio Fri Jan 21 06:41:38 2011 (4d391c92) PaeFireStudioAudio.sys // Presonic PaeFireStudio Fri Jan 21 06:43:08 2011 (4d391cec) PaeFireStudio.sys // Presonic asahci64 Wed Sep 21 11:42:57 2011 (4e79b1a1) asahci64.sys AsrRamDisk Fri Jan 13 05:52:38 2012 (4f0fb896) AsrRamDisk.sys RTKVHD64 Tue Jan 31 11:55:06 2012 (4f27c88a) RTKVHD64.sys iusb3hcs Mon Feb 27 11:58:49 2012 (4f4b61e9) iusb3hcs.sys HECIx64 Tue Jul 03 00:14:58 2012 (4ff21d62) HECIx64.sys ScpVBus Sun May 05 23:31:26 2013 (5186cfae) ScpVBus.sys LGSHidFilt Thu May 30 17:16:33 2013 (51a76d51) LGSHidFilt.Sys k57nd60a Wed Oct 30 08:14:03 2013 (5270b1bb) k57nd60a.sys hfsplusrec Fri Nov 14 15:52:55 2014 (54661747) hfsplusrec.sys apmwin Fri Nov 14 15:53:52 2014 (54661780) apmwin.sys gpt_loader Fri Nov 14 15:54:12 2014 (54661794) gpt_loader.sys mounthlp Fri Nov 14 15:54:31 2014 (546617a7) mounthlp.sys[/quote] Update links:
Driver Reference Table - MBfilt64.sys
Driver Reference Table - WmXlCore.sys
Driver Reference Table - WmBEnum.sys
Update PreSonic software
Driver Reference Table - asahci64.sys
Driver Reference Table - AsrRamDisk.sys
Driver Reference Table - RTKVHD64.sys
Driver Reference Table - iusb3hcs.sys
Driver Reference Table - HECIx64.sys
Driver Reference Table - ScpVBus.sys
Driver Reference Table - LGSHidFilt.Sys
Driver Reference Table - k57nd60a.sys
Driver Reference Table - hfsplusrec.sys
Driver Reference Table - apmwin.sys
Driver Reference Table - gpt_loader.sys
Driver Reference Table - mounthlp.sys

 

My system BSOD with the same bugcheck code 124 about once or more every other week. The reason there is such a big gap in the logs is because I setup windows to use a full dump instead of the mini dump. I fixed it.

I can tell you for fact that the presonus software/driver is not responsible for any BSOD. My Presonus firestudio 2626 ( a firewire audio interface) is a legacy device and the company stopped updating the drivers for it as of windows 8. So I stopped using it through windows 8 and windows 8.1 and even windows 10. However, even with fresh installs of those Operating Systems, I still had the same amount and frequency of crashes, Code 124 BSOD, without EVER installing/attaching the Presonus interface. Since I know these BSOD happen with or without it, I opted to to install it with the latest drivers offered by Presonus for my make and model. As for the other drivers you listed, I will check those out.

In an earlier post, you said one of my CPU cores cache could be responsible..... Also, If it could be driver related, how does that explain the instability with my BIOS set to optimized defaults. Because my system will crash within an hour or less if I set my BIOS to optimized defaults.

 

With a 0x124 it is generally difficult to say what is causing the crash.
I didn't say the CPU could be responsible, but the data in the cache of the CPU is corrupted what the CPU noticed when the CPU was trying to read it. In fact, the CPU is the most stabilized component of the system. If the CPU is truly causing issues, depending on how much damage there is, you normally wouldn't be able to boot.

The drivers and BIOS are 2 different things, the drivers aren't related with the stability of the BIOS because the drivers are only in Windows active. If your BIOS is crashing when you load optimized default settings, after the optimization tweak a little to make it stable.

 

I've never had a BIOS crash, and sure, I know the drivers aren't related to BIOS's stability, I was just reminding you of my systems stability issues when I load the optimized defaults.

But I may have something here......

I looked at the links you posted and 2 of them were related to my Logitech Mouse. After some googling I found a thread on Tomshardware and this guy posted about issues relating to the Logitech software installed on his computer. Here's the link - http://www.tomsguide.com/answers/id-...-software.html
He mentioned BSOD across two different versions of Windows and how uninstalling fixed it. So I uninstalled it, rebooted my computer and for the first time, since I can remember, the windows chime played when my Computer booted. Weird? So, for now, I'm not installing the new gaming software/drivers until I get a BSOD.

 

Glad to hear that.

It seems you just have solved the problem yourself with a solution that isn't that often occuring *Smile
Well done *Thumbs

I have said it a lot of times on this forum, but I'll say it again with a little extra.
The 0x124 is mostly caused by hardware related things, or the BIOS and rarely due to software.

 

Unbelievable! Just Blue screened 0x124 Here's the Dm log.

 

Description of what you were doing and/or what happened would be helpful *Smile

 

Sorry about that.... I was playing fallout 4 and without any warning what so ever, blue screen.

 

Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Im using my Mac now as a way of communication.
Ok. I followed your directions, backed everything up, made a system image and a restore point, and also made the recovery disk. I can no longer boot into my computer, even after following the directions to a Tee. Once I setup and enabled driver verifier, I rebooted and my PC never made it past the Motherboard Manufactures splash screen. Just a black screen with the ASRock logo and on the bottom a spinning circle like windows is trying to boot, but it BSOD with the verifier message as the code. Once booted into the command prompt and typing verifier /bootmode resetonbootfail that gives me the same response listed on the thread you gave me for directions, but when I go to reboot, it gives me the same BSOD with the verifier as the problem.

Here are some pics I took with my iphone of the error messages I got when I tried to restore.



Seems like windows isn't installed right. I installed windows just like it said to on the windows 7 and 8 website.

 

How about just verifier/reset?

 

No. Does NOT work.

I don't think the driver verifier even had a chance to do its job. Remember, once I set it up, then restarted my pc, it never made it past the motherboard splashscreen. Did you look at the pics in the last couple of posts? What do the error messages indicate? Also, I've had windows 10 now well over the 30 days to revert back to Windows 7, but on the troubleshooting blue screen, It still shows that I can revert back, even though it fails. Here is a pick of that

I have finals next week. I really need that computer up and running!!

 

What OS do you specify when trying to restore?
You have 2 versions and it says you didn't have chosen the right one.

 

2 versions? What? I Only installed windows 7 on my SSD, then a few months ago, I did the upgrade from 7 to 10. I never had any other install, that I made, on my PC. Here is a pic of my boot options in BIOS. USB: USB DISK Pro PMAP and the UEFI: USB DISK Pro PMAP i'm assuming is the USB recovery drive that I made, Why its listed twice, I don't know....

 

Not sure if I mentioned this before, but both times I RMA'ed my PC back to Cyberpowerpc.com they said that the computer was fine and that both times I sent the computer in for repair, the OS wasn't installed right. The first time I sent it back it had Windows 7 64 Ultimate, the second time I sent it back, it had Windows 8 pro 64 on it. Every time and I mean EVERY time I installed windows, the computer only rebooted once and it was done with the install. The reason I'm bringing this up is because while the OS was installing, somewhere on the screen, it said something like, your computer will restart multiple times. It only restarted once. Not sure if that makes since, considering that I ended up running Check disk and sfc /scannow and those commands never returned any issues, I'm Thinking I might just start over..... again.... Realistically I've already done atleast 5 fresh reinstalls of windows 7, probably 5 more with windows 8... Now I need to do windows 10. Maybe I'm missing something in the install phase?

This is how I usually go about prepping my computer for a fresh install of windows.

• Format the HDD (data drive, not boot drive) once formatted, turn off the computer, unhook the SATA and power cables from the motherboard to the HDD.
• Secure erase the SSD (Boot drive) with Samsung's Secure Erase Software for SSD.
• Disconnect any external devices except mouse and keyboard.
• Load optimized defaults in the ASROCK UEFI BIOS.

At this point, I would begin the Install part of the OS. Before I list out my process, are there any settings in the BIOS that should be manually put in, making sure the installation goes off without a hitch? If you look through the thread, I uploaded screenshots of EVERY BIOS setting. Maybe you could look through them and tell me what should be set, enabled or disabled. How should the boot order be set in bios? SSD first then DVD Drive?

Process of Windows Install

• Put in Windows install disk into the DVD drive and the boot up the computer.
• follow the onscreen prompts until I find my SSD and select it for the OS.
• Files take about 30min to expand
• the computer gets to a percentage way through (can't remember exact number but no where near %100 then the computer restarts.
• When the computer finishes booting, it goes directly to windows desktop.

Should've the computer booted back the install dvd? I fell like the computer should've installed more then rebooted a few more times...

• Once at the desktop, I install all windows updates, (Usually get BSOD every 5 min, leading to the computer crashing during an update, which leaves me no other choice but to reinstall the os again, hoping that it makes it through the updates before it crashes.
• Once I'm able to get the updates installed (which I have set to let windows decide automatic) I try to get my MOBO updates installed.
• While praying that I don't get another BSOD, I update my graphics drivers

Usually at this point, the BSOD are so bad, I end up googling around and finding windows updates that I have to uninstall to get the system more stable. EX KB 3004394, KB2670838. Probably more, just cant think of anymore at this moment.

I really need some sound advice here.