Windows 10: Random Restarts with 0x124 Dump

Hi, and thanks in advance for any and all assistance, and sorry if this turns into a long post!
I have a problem that has been infuriating me for the past month or so. I was away for studies for about 5 months, and once I returned, fired up my PC again for the first time. All went well for a few days. Then suddenly, I would get a black screen for a few moments, before the computer just restarts. No BSOD, no screen tearing or strange noises from the case, no indication whatsoever that it was about to restart.

So I started trying to figure out what was wrong. Using Bluescreenviewer and WhoCrashed? I found out that it was a 0x124 error citing the ntoskrnl at fault. Reading online, it seemed that this was generally caused by either a thermal issue, hardware problem or in some cases driver problems.

I started updating everything I could. Graphics drivers, mouse drivers, keyboard drivers, BIOS drivers, etc. Still got the restarts. They seemed to be appearing only when I was playing games (don't use this particular PC for much else, so took a while to realize), so I decided to check thermal issues. Using MSI Afterburner and CPU-Z, I found that my CPU was never reaching any significant heat (my Hyper 212 EVO keeps it under or around 40C even under heavy load), and that while my graphics card got hot, it never went beyond 70, so it didn't seem to be a thermal issue there.

I ran memtest86 to try to identify ram issues, and it came back, after a night of running, clean. I did a dskcheck /r, and while it took a bit of time, it too came back alright. In order to truly rule out driver issues, i reinstalled windows 10, and still it kept happening.

I read online that there was a chance that the power supply could be acting up. Since I had been meaning to update my graphics card, and needed a new power supply to go with it, I decided to do that. I plugged in my new PSU, and my new GPU, and it went fine for about a day or two before the restarting resumed.

I tried playing with the case side open, to truly rule out cooling issues, and it still restarted. I moved the computer, and plugged it straight into the wall because I had a suspicion that maybe the extra cable wasn't giving it enough juice, but it still restarted.

I'm now at my wits end. I've tried everything I can think of. My new GPU never goes to high temps, my CPU seems to be running fine, I haven't found any ram memory problems, my new PSU can't be to blame, and so I don't know whats left. Any assistance or guidance would be much appreciated!

Tl;dr
Restarts started after some inactive time. Seems to be a 0x124 bsod error
Tried the following:
-update all drivers
-update BIOS
-re-roll to previous versions of graphics drivers
-re-install windows 10
-purchase new PSU and GPU
-memtest86 came back ok
-dskcheck /r came back ok
-tried playing with side off

MSI never shows the CPU or GPU going into any dangerous territory in terms of temps.

Thanks again! If I need to attach anything else, like raw dump files or Afterburner screens or something like that, let me know.

:)

 

Multiple BSODs with differen't errors

Try leaving off the side panel to see if air circulates better. If it makes a difference you could add an extra fan.

The latest dumpfile was bug check code 0x124 which indicates a hardware related problem. However, this is the first time I have noticed a code 0x124 dump on your system.

Bug Check 0x124 WHEA_UNCORRECTABLE_ERROR

 

Windows 10 crashing with bugcheck 0x124, blaming ntoskrnl.exe

The most common reason of 0X124 is a hardware fault.The resolutions are here for 0X124:

BugCheck Code 124

Edit:The dump says PCI Express port has some issue.Also a 2013 driver for Network Connect VPN software by Juniper Networks

is outdated.Update it and follow the Resolutions/

 

Hi fenr1r,

There are 2 types of the crashes, a write error and an observing error, all of them are on the same core and cache bank.
To be honest this looks like the motherboard is the problem.
We could try some hardware tests if you would like, but lets take a look at the possibilities.
A bus error (in this case an observing error) is usually caused by chipset drivers or the hardware where you already have ruled out most of them, only the CPU is left but it is ruled out by the bus error as (as mentioned) it is an observing error what simply means that the CPU noticed the error but didn't do a thing with it (requesting data or sending data).

My suggestion would be to replace the motherboard, there is no test for identifying if the motherboard is the cause besides of replacing it.

EDIT, what are the 3.3v, 5v and 12v values according to the BIOS?

Observing error
Code: 0: kd> !errrec ffffe0004f4258f8 =============================================================================== Common Platform Error Record @ ffffe0004f4258f8 ------------------------------------------------------------------------------- Record Id : 01d162b331fd6cb0 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/8/2016 20:56:39 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe0004f425978 Section @ ffffe0004f425a50 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f12 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe0004f4259c0 Section @ ffffe0004f425b10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 12 0f 60 00 00 08 04 00 - 0b 22 98 1e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe0004f425b10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0004f425a08 Section @ ffffe0004f425b90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4) Status : 0xba00001000020c0f[/quote] Write error
Code: 1: kd> !errrec ffffe000c5c9e8f8 =============================================================================== Common Platform Error Record @ ffffe000c5c9e8f8 ------------------------------------------------------------------------------- Record Id : 01d16373d8ae053e Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/9/2016 19:55:43 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe000c5c9e978 Section @ ffffe000c5c9ea50 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f12 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe000c5c9e9c0 Section @ ffffe000c5c9eb10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 12 0f 60 00 00 08 04 00 - 0b 22 98 1e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe000c5c9eb10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe000c5c9ea08 Section @ ffffe000c5c9eb90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHELG_WR_ERR (Proc 0 Bank 4) Status : 0xf300000200190127[/quote]

 

Hey Axe0, and thanks for the reply.

Gotta admit, not what I was expecting. I am a student so I don't have the money to replace a motherboard just yet, but if that really is the issue, I don't really have a choice.

I checked out those values you wanted, and this is what my BIOS states:
vCore: 1.304v
3.3V: 3.360v
5V: 5.112v
12V: 12.196v

If you are sure that it is the motherboard and there is nothing I can do with my current hardware to fix it, then I will see to getting a new one in the coming weeks.

Thanks again!

 

Unless a CPU test tells otherwise about the observe error (that the reported error wasn't correct) I don't see another possibility assuming that the replaced components aren't faulty. Did you test the replaced components?






Diagnostic Test

CPU TEST


Run Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums



Note If you're overclocking anything, please stop it and set everything back to default while troubleshooting


Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

Hi again Axe0,

I ran Prime95, and within an hour it got a fatal error. I uploaded the results.txt. It did not result in a BSOD however. Is the results.txt file from Prime95 enough or should I upload something else as well?

EDIT, Two new things have happened/I have realized now:
1. If the computer is put into sleep mode for more than just a minute, it cannot be woken up normally. Doing so starts the computer, but it doesn't display anything on the screen. In order to start it, I have to click my 'restart' button on my case, let it do the whole restart cycle, before booting into the same instance as when I left.
2. I had a new BSOD while using the above method. I have created another Debug zip which I have attached to this post.

I've read that the 1st issue is something that has a possibility of happening when using DDU, which I did when I installed my new graphics card. Any way to reverse it, and does it have anything to do with the problems I'm experiencing?

Thanks again!

 

What test exactly did you use with Prime95?
The more intensiver the test, the more of RAM is taken with it which would mean that more possibilities are opening or it could again be due to the motherboard

 

I followed the instructions according to the forum post you linked, so I did a Small FFTs Test in Prime95. Should I try running a different test?
Also, I edited my previous post at, apparently, the same time you replied, so there is some new information there as well, including a new Debug zip. The new BSOD I had, this time, actually showed a BSOD screen. My previous crashes have just been black screens and then directly to restart.

 

I am wondering something, before you powered on your system did you clean your system of any dust that may have come in the case while you were away? Or when you replaced some components?
Dust and other stuff may cause various problems including bluescreens.

 

Hi Axe0,

I did clean the computer when I first came home, but I followed your advice and did so again. I disconnected all the cables and used a Air-in-a-Can to clean out absolutely everything, before reconnecting all the cables and putting everything back. I did this two days ago, and the computer played fine for a while. However, I got another restart, so it seems the problem isn't yet fixed.

I created another log file, just in case, but I believe the latest BSOD is the same as the last few.
Could any of this have to do with the CPU being under or over charged? As in getting too many volts or too few? Someone who was actively overclocking seemed to have had a similar issue. I have never tried overclocking my cpu myself, but perhaps something has deteriorated with it? Or do you truly believe its the motherboard that is the issue?

Thanks once again!

 

Did you also replace the thermal paste and checked if everything is proper seated (reseated if necessary)?

The crashes are observing errors on the exact same core and cache bank.
As mentioned, in an observing error the CPU has nothing to do with it because the CPU does nothing with the data that is causing the crash.
To translate the error a bit more, the problem is a generic error on the bus that was observed by the CPU where the CPU noticed that there wasn't enough delay between the previous data and the data that caused it. Just to mention, this is a processor type error (also known as a Machine Check Exception (MCE) (more about the MCE: Troubleshooting Windows STOP Messages ) in previous operating systems, the 0x124 is the replacement of the MCE but the MCE sometimes still occurs). The processor type error occurs most frequently with the 0x124, however it does not mean the CPU is the cause because that depends on what the problem is.
This might be bit technical, because this requires a bit of knowledge of how the components work.
Code: 0: kd> !errrec ffffe001`d0c808f8 =============================================================================== Common Platform Error Record @ ffffe001d0c808f8 ------------------------------------------------------------------------------- Record Id : 01d166a4a916dc1a Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/13/2016 21:22:49 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe001d0c80978 Section @ ffffe001d0c80a50 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f12 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe001d0c809c0 Section @ ffffe001d0c80b10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 12 0f 60 00 00 08 04 00 - 0b 22 98 1e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe001d0c80b10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe001d0c80a08 Section @ ffffe001d0c80b90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4) Status : 0xba00001000020c0f[/quote]

 

I managed to find a good price for a motherboard, a GA-990FXA-UD3 to be precise. It will arrive later on this week. So I will install that in a few days when it arrives, making sure to reapply the thermal paste and that the socket fits correctly, and report back if the problem has gone away then. Thanks for all your help so far! If I don't get any restarts after I try the new motherboard I will mark this thread as solved.

 

You've checked for compatibility I hope?
Before I get something I make sure it is compatible with everything that has to do with it.

 

Yes I did *Smile It's also compatible with the future upgrade to my CPU that I want to do, as my current motherboard is a bit held back in that regards. It should also make my CPU more stable as it has better core voltage control than my current set-up.