BSOD once a week with bug check code, 0x00000124

axe0 · 13 Nov 2015

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

rob909e · 15 Nov 2015

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.

axe0 · 15 Nov 2015

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.

rob909e · 15 Nov 2015

axe0 said:

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.

axe0 · 15 Nov 2015

Glad to hear that.

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

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.

rob909e · 17 Nov 2015

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

axe0 · 17 Nov 2015

Description of what you were doing and/or what happened would be helpful :)

rob909e · 17 Nov 2015

axe0 said:

Description of what you were doing and/or what happened would be helpful :)

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

axe0 · 18 Nov 2015

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.

rob909e · 18 Nov 2015

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.