3 bugcheck crashes in 1 week. (The bugcheck was: 0x00000124 )

Page 1 of 3 123 LastLast

  1. Posts : 10
    Windows 10
       #1

    3 bugcheck crashes in 1 week. (The bugcheck was: 0x00000124 )


    Hello, I've had this bugcheck error three times now and a Kernel-Power restart once over the past week. I am getting very worried, as I haven't changed any hardware or overclocked. After the first time (on the 3rd of December), I dusted the PC with compressed air because I read this issue could occur due to overheating and it was OK until the 8th of December when it happened again, and I realised that the problem may be much more severe than an overheating issue. It happened again yesterday (11th of December) and I knew I had to ask for help here.


    The full bugcheck error from event viewer is:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffdd8824f1b8f8, 0x0000000000000000, 0x0000000000000000).
    Ever since the first crash on the 3rd, when I boot sometimes the BIOS hangs at "verifying DMI pool data", which has made me open the case up and check if everything is seated properly. This has happened around 3-4 times this week.

    System specs:
    CPU: AMD FX 6300 3.5 Ghz
    Mobo: GA-78LMT-USB3
    RAM: 8GB DDR3 (sorry I can't remember the specifics)
    GPU: Nvidia GeForce GTX 750 Ti
    HDD: Toshiba 1TB HDWD110
    PSU: (not sure, it came with the case which is a CoolerMaster)

    The CPU, mobo, RAM, GPU and HDD were put together by me and were bought new in April of 2016. The PSU and case are from an older build.

    I have attached the DM log. I manually looked through the minidump folder and I could only see 1 minidump. This bugcheck error has occured on 2 other occasions so there should be 2 other minidumps, but they're not there. I don't know why.

    Thank you so much. I am very, very worried and I hope to have this solved.

    Edit: I uploaded some screenshots showing idle temps. (CPU idle temps have always been inaccurate for some reason, but when I'm gaming the highest they go to is 55C)
    Last edited by MrCvry; 11 Dec 2017 at 05:18.
      My Computer


  2. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #2

    Hello MrCvry and welcome to Tenforums :)

    This BSOD is hardware related as you can tell from its description.
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.

    The error is reported by the CPU as a BUS error:

    Code:
    5: kd> !errrec ffffdd8824f1b8f8
    ===============================================================================
    Common Platform Error Record @ ffffdd8824f1b8f8
    -------------------------------------------------------------------------------
    Record Id     : 01d37255533d9423
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 12/11/2017 7:55:01 (UTC)
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffdd8824f1b978
    Section       @ ffffdd8824f1ba50
    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   : 0x0000000000600f20
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffdd8824f1b9c0
    Section       @ ffffdd8824f1bb10
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e 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  @ ffffdd8824f1bb10
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffdd8824f1ba08
    Section       @ ffffdd8824f1bb90
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
      Status      : 0xf2000010000b0c0f

    It would be good if we could get confirmation that this error is consistent so please post the logfiles again if you can capture more mini-dumps.

    This type of error is observed by the CPU and usually points to a motherboard problem. If you also get a BSOD when running in safe mode it is a good confirmation that you have a hardware problem.
      My Computers


  3. Posts : 10
    Windows 10
    Thread Starter
       #3

    philc43 said:
    Hello MrCvry and welcome to Tenforums :)
    Thank you, Phil! I'll create new DM logs for every new crash. I was hoping it'd be a software issue, and not a hardware issue. What do you think could've caused this issue with the motherboard?
      My Computer


  4. Posts : 10
    Windows 10
    Thread Starter
       #4

    Sorry to bump the thread, but I was just wondering if resetting the CMOS or updating the BIOS would help with this kind of error?
      My Computer


  5. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #5

    MrCvry said:
    Sorry to bump the thread, but I was just wondering if resetting the CMOS or updating the BIOS would help with this kind of error?
    You could try a BIOS update if there is one. It has been known to fix errors that appear as hardware issues. Nothing to lose by trying!
      My Computers


  6. Posts : 10
    Windows 10
    Thread Starter
       #6

    philc43 said:
    You could try a BIOS update if there is one. It has been known to fix errors that appear as hardware issues. Nothing to lose by trying!
    Ah, nevermind, the BIOS updates are quite old (from 2014) on the gigabyte website, so probably won't do any good.
      My Computer


  7. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #7

    MrCvry said:
    Ah, nevermind, the BIOS updates are quite old (from 2014) on the gigabyte website, so probably won't do any good.
    Yep, you are already on the most recent :)
      My Computers


  8. Posts : 10
    Windows 10
    Thread Starter
       #8

    Crashed again just now. I've attached the DM log.
      My Computer


  9. Posts : 10
    Windows 10
    Thread Starter
       #9

    Crashed again.
      My Computer


  10. Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       #10

    The recurrent BSOD have all been bugcheck 0x124
    Debugging: BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
    Error Type : BUS error
    Severity : Fatal

    As philc43 noted these are often MB problems.

    Code:
    Event[1626]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2017-12-16T15:15:02.041  Event ID: 20  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: DESKTOP-TITQKKQ  Description: A fatal hardware error has occurred.Component: AMD NorthbridgeError Source: Machine Check ExceptionError Type: 11Processor APIC ID: 0The details view of this entry contains further information.
    Code:
    Event[1336]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2017-12-13T19:05:40.563  Event ID: 20  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: DESKTOP-TITQKKQ  Description: A fatal hardware error has occurred.Component: AMD NorthbridgeError Source: Machine Check ExceptionError Type: 11Processor APIC ID: 0The details view of this entry contains further information.
    Code:
    Event[1187]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2017-12-11T07:55:23.805  Event ID: 20  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: DESKTOP-TITQKKQ  Description: A fatal hardware error has occurred.Component: AMD NorthbridgeError Source: Machine Check ExceptionError Type: 11Processor APIC ID: 0The details view of this entry contains further information.
    Code:
    Event[906]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2017-12-08T07:32:21.539  Event ID: 20  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: DESKTOP-TITQKKQ  Description: A fatal hardware error has occurred.Component: AMD NorthbridgeError Source: Machine Check ExceptionError Type: 11Processor APIC ID: 0The details view of this entry contains further information.
    Code:
    Event[459]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2017-12-03T11:58:55.759  Event ID: 20  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: DESKTOP-TITQKKQ  Description: A fatal hardware error has occurred.Component: AMD NorthbridgeError Source: Machine Check ExceptionError Type: 11Processor APIC ID: 0The details view of this entry contains further information.
      My Computer


 

  Related Discussions
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 04:02.
Find Us




Windows 10 Forums