Windows 10: Random Restarts with 0x124 Dump Solved

Page 1 of 2 12 LastLast
  1.    09 Feb 2016 #1

    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.
      My System SpecsSystem Spec

  2. axe0's Avatar
    Posts : 11,073
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       10 Feb 2016 #2

    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
    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
    Last edited by axe0; 11 Feb 2016 at 05:12.
      My System SpecsSystem Spec

  3.    11 Feb 2016 #3

    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!
      My System SpecsSystem Spec

  4. axe0's Avatar
    Posts : 11,073
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       11 Feb 2016 #4

    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?




    Random Restarts with 0x124 Dump Diagnostic Test Random Restarts with 0x124 Dump
     CPU TEST

    Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

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

    warning   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.
      My System SpecsSystem Spec

  5.    11 Feb 2016 #5

    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!
    Last edited by fenr1r; 11 Feb 2016 at 10:22.
      My System SpecsSystem Spec

  6. axe0's Avatar
    Posts : 11,073
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       11 Feb 2016 #6

    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
      My System SpecsSystem Spec

  7.    11 Feb 2016 #7

    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.
      My System SpecsSystem Spec

  8. axe0's Avatar
    Posts : 11,073
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       11 Feb 2016 #8

    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.
      My System SpecsSystem Spec

  9.    13 Feb 2016 #9

    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!
      My System SpecsSystem Spec

  10. axe0's Avatar
    Posts : 11,073
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       14 Feb 2016 #10

    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
      My System SpecsSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
Semi Random Restarts (detailed) in BSOD Crashes and Debugging
This isnt short but I tried. Ive spent the better part of the last month even extending back before an upgrade about 5 months, oddly suspended the issue until about a month ago. I've tried about everything i can think of. Issue: Random...
Random BSODs, dump file included in BSOD Crashes and Debugging
Bluescreenview indicates: "caused by driver ntoskrnl.exe" Memtest showed 0 errors with the RAM. All graphics drivers etc should be up to date. Analysing dump file with windows debugging tools shows: Microsoft (R) Windows Debugger Version...
Hello, I have been fighting with my computer for about four weeks now, and I am not getting anywhere. In a nutshell, my computer started to randomly shut down and seldom reboot. There are no specific patterns I notice, except that when I try to...
Upgraded from Windows 8.1 Pro to 10 Pro. I think I took care of the update bug so I don't believe it is the issue. Updated GForce Drivers after using DisplayDriverUninstaller. SSD C: Drive firmware updated. Ran Memtest86+ on each stick for 8...
Random Restarts on HP ProBook in General Support
Hi I have fresh installed Win 10 x64 on my HP ProBook 450, yet every now and then it freezes with only the mouse cursor movable and then restarts the laptop. I though it was the upgrade from Win 8.1 but the same thing happens after a fresh...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:48.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums