Page 2 of 2 FirstFirst 12
  1.    25 Jan 2016 #11
    Join Date : Jan 2016
    Posts : 13
    Windows 10
    Thread Starter

    Hi,
    So now another BSOD while just using chrome..Still WHEA_UNCORRECTABLE_ERROR on screen. But this time there was no minidump files created, I checked that my settings for the dump files are correct.
    Anyways, here is the error zip, thanks in advance!

    Attachment 60721
      My ComputerSystem Spec
  2.    26 Jan 2016 #12
    Join Date : Jan 2016
    Posts : 643
    windows 10 Pro

    There are many WER about your Steelseries Diablo mouse you need Engine 3 with windows 10 https://steelseries.com/engine

    Being the dumpfiles
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, ffffe00110aae028, b2000000, 100402}
    Probably caused by : GenuineIntel
    Followup: MachineOwner
    ---------
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    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.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe00110aae028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000100402, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  f
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    STACK_TEXT:  
    ffffd000`530f06f8 fffff802`d6414f1f : 00000000`00000124 00000000`00000000 ffffe001`10aae028 00000000`b2000000 : nt!KeBugCheckEx
    ffffd000`530f0700 fffff802`d5e23e48 : ffffe001`10aae028 ffffe001`0fccf370 ffffe001`0fccf370 ffffe001`0fccf370 : hal!HalBugCheckSystem+0xcf
    ffffd000`530f0740 fffff802`d641540c : 00000000`00000728 00000000`00000003 ffffd000`530f0b30 00000000`00000000 : nt!WheaReportHwError+0x258
    ffffd000`530f07a0 fffff802`d6415764 : ffffe001`00000010 ffffe001`0fccf370 ffffd000`530f0948 ffffe001`0fccf370 : hal!HalpMcaReportError+0x50
    ffffd000`530f08f0 fffff802`d641564e : ffffe001`0fccecc0 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
    ffffd000`530f0940 fffff802`d641588e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
    ffffd000`530f0980 fffff802`d6415a10 : ffffe001`0fccecc0 ffffd000`530f0bb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
    ffffd000`530f09b0 fffff802`d5d5f27b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    ffffd000`530f09e0 fffff802`d5d5f031 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffd000`530f0b20 fffff802`d5c31f51 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    ffffd000`530fb8b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmIdleExecuteTransition+0x3a1
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: GenuineIntel
    IMAGE_NAME:  GenuineIntel
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  
    FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE
    BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae
    FAILURE_ID_HASH:  {7c95de0c-286c-8226-45c2-422b4de101d6}
    Followup: MachineOwner
    It could also be that your CPU is faulty ,with the mentioning of fatal hardware error and HAL (= Hardware Abstraction Layer) and processor MAE in the dumpfiles.

    Test your CPU with
    - IntelProcessor Diagnostic Tool (works in Windows)
    x64 -
    http://downloadcenter.intel.com/Deta...mples&lang=eng

      My ComputerSystem Spec
  3.    26 Jan 2016 #13
    Join Date : Jan 2016
    Posts : 13
    Windows 10
    Thread Starter

    Quote Originally Posted by lifetec View Post
    There are many WER about your Steelseries Diablo mouse you need Engine 3 with windows 10 https://steelseries.com/engine

    Being the dumpfiles
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, ffffe00110aae028, b2000000, 100402}
    Probably caused by : GenuineIntel
    Followup: MachineOwner
    ---------
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    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.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe00110aae028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000100402, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  f
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    STACK_TEXT:  
    ffffd000`530f06f8 fffff802`d6414f1f : 00000000`00000124 00000000`00000000 ffffe001`10aae028 00000000`b2000000 : nt!KeBugCheckEx
    ffffd000`530f0700 fffff802`d5e23e48 : ffffe001`10aae028 ffffe001`0fccf370 ffffe001`0fccf370 ffffe001`0fccf370 : hal!HalBugCheckSystem+0xcf
    ffffd000`530f0740 fffff802`d641540c : 00000000`00000728 00000000`00000003 ffffd000`530f0b30 00000000`00000000 : nt!WheaReportHwError+0x258
    ffffd000`530f07a0 fffff802`d6415764 : ffffe001`00000010 ffffe001`0fccf370 ffffd000`530f0948 ffffe001`0fccf370 : hal!HalpMcaReportError+0x50
    ffffd000`530f08f0 fffff802`d641564e : ffffe001`0fccecc0 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
    ffffd000`530f0940 fffff802`d641588e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
    ffffd000`530f0980 fffff802`d6415a10 : ffffe001`0fccecc0 ffffd000`530f0bb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
    ffffd000`530f09b0 fffff802`d5d5f27b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    ffffd000`530f09e0 fffff802`d5d5f031 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffd000`530f0b20 fffff802`d5c31f51 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    ffffd000`530fb8b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmIdleExecuteTransition+0x3a1
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: GenuineIntel
    IMAGE_NAME:  GenuineIntel
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  
    FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE
    BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae
    FAILURE_ID_HASH:  {7c95de0c-286c-8226-45c2-422b4de101d6}
    Followup: MachineOwner
    It could also be that your CPU is faulty ,with the mentioning of fatal hardware error and HAL (= Hardware Abstraction Layer) and processor MAE in the dumpfiles.

    Test your CPU with
    - IntelProcessor Diagnostic Tool (works in Windows)
    x64 -
    http://downloadcenter.intel.com/Deta...mples&lang=eng

    Hi, thanks for the reply, I have tested the CPU and the CPU was all good. I tried to reset CMOS again, and now it looks like my bios has completely died. It won't boot pass the blue screen with gigabye uefi dual bios hanging on the top. Cannot do anything to adjust the settings now. No error beep sound either, all the fans are running normally upon booting. I ordered some rams to test things up, but now it seems like I have to get a new mobo or switch out mobo+cpu together since 1155 socket is hard to find now. But that would mean a completely new pc for me.. I will try to boot into bios now, and will keep this updated.
      My ComputerSystem Spec
  4.    26 Jan 2016 #14
    Join Date : Jun 2015
    Posts : 12,673
    Windows 10 Pro

    The CPU is pretty much always reporting the 0x124 errors hence the reason why you see 'processor' in failure_bucket_id and bucket_id.
    Most of what is marked is pretty much useless with this kind

    Running the !errrec command on the 2nd parameter of the bugcheck reveals more information although also not much useful, but if it is consistent in the crashes then it might give a lead.
    In this case it shows an internal unclassified (undocumented) error, to find out what exactly is the problem we would need a tech from Intel because of the undocumented part.
    The usual thing to start with is hardware troubleshooting, because the 0x124 is known for being a difficult crash which mostly is caused by hardware (related stuff)
    Code:
    3: kd> !errrec ffffe00110aae028
    ===============================================================================
    Common Platform Error Record @ ffffe00110aae028
    -------------------------------------------------------------------------------
    Record Id     : 01d156deeb9c2628
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 1/24/2016 19:39:53 (UTC)
    Flags         : 0x00000000
    
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00110aae0a8
    Section       @ ffffe00110aae180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000306a9
    Processor ID  : 0x0000000000000003
    
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00110aae0f0
    Section       @ ffffe00110aae240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Local APIC Id : 0x0000000000000003
    CPU Id        : a9 06 03 00 00 08 10 03 - bf e3 9a 7f ff fb eb bf
                    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  @ ffffe00110aae240
    
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00110aae138
    Section       @ ffffe00110aae2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Error         : Internal unclassified (Proc 3 Bank 4)
      Status      : 0xb200000000100402
      My ComputersSystem Spec
  5.    26 Jan 2016 #15
    Join Date : Jan 2016
    Posts : 13
    Windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    The CPU is pretty much always reporting the 0x124 errors hence the reason why you see 'processor' in failure_bucket_id and bucket_id.
    Most of what is marked is pretty much useless with this kind

    Running the !errrec command on the 2nd parameter of the bugcheck reveals more information although also not much useful, but if it is consistent in the crashes then it might give a lead.
    In this case it shows an internal unclassified (undocumented) error, to find out what exactly is the problem we would need a tech from Intel because of the undocumented part.
    The usual thing to start with is hardware troubleshooting, because the 0x124 is known for being a difficult crash which mostly is caused by hardware (related stuff)
    Code:
    3: kd> !errrec ffffe00110aae028
    ===============================================================================
    Common Platform Error Record @ ffffe00110aae028
    -------------------------------------------------------------------------------
    Record Id     : 01d156deeb9c2628
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 1/24/2016 19:39:53 (UTC)
    Flags         : 0x00000000
    
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00110aae0a8
    Section       @ ffffe00110aae180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000306a9
    Processor ID  : 0x0000000000000003
    
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00110aae0f0
    Section       @ ffffe00110aae240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Local APIC Id : 0x0000000000000003
    CPU Id        : a9 06 03 00 00 08 10 03 - bf e3 9a 7f ff fb eb bf
                    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  @ ffffe00110aae240
    
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00110aae138
    Section       @ ffffe00110aae2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Error         : Internal unclassified (Proc 3 Bank 4)
      Status      : 0xb200000000100402
    Hello, thanks for the reply. I just saved the bios by resetting cmos again.. I started hardware trouble shooting a while ago actually. Tested hard disk, cpu, even switched power supply, and graphic cards. The only thing I was not able to test recently would be my memory bars. Memtest86 can pass once or twice, but it will reboot the system during second or third test for sure. I am going to keep trying memtest86, if any error occurs I will just buy new memories to test things out. As mentioned above, motherboard memory slots are unlikely damaged since I have successfully tested each slot with one working memory stick by memtest86. I also got a high-end new psu which would probably not be faulty as I had people tested it out on their pcs for me.

    The problem for me has temporarily being narrowed to the memories, I will try test them out one by one again after. My schoolwork has been left behind, so probably need to catch things up, I will update this when new problems occurs.

    Also, Lifetec, I have installed the driver for my mouse, and ran the intel cpu test tool several times with no errors. Just got my pc running again, so I will see if anything happens again. Thanks for your patient!
      My ComputerSystem Spec
  6.    27 Jan 2016 #16
    Join Date : Jan 2016
    Posts : 13
    Windows 10
    Thread Starter

    So the fixing is still not going very well. I could not post dump files cause my pc is kinda dead right now. There was no BSOD after my last post, but pc starts to randomly reboot while using chrome, playing games, or just stay in the idle. Memtest86 still reboots my pc, as well as the windows memory diagnostic tool. Runs for several minutes then just reboots. I suspected there might be something wrong with my new psu, and took it to my friend, connected the psu to his pc, and ran the system for about an hour nothing happened. I was not able to test my ram on his pc, since my ram does not fit in his mobo.

    Would you happen to know if rebooting during memory test means failing rams? I did a lot of research online but nothing was helpful. Also, after several reboots, I cannot even get it to post and just stuck in bootloop. Reset CMOS, and use onboard graphic with just one ram helps a bit, and it will show the "main bios is corrupted, recovering from backup bios" message, but sometimes pc will even reboot with the replacing process unfinished. I will have to reset the CMOS multiple times to get it to post. Then system starts to reboot while I am doing somwthing, no oc for sure, and bios settings were correct after reset. This is getting really weird for me..
      My ComputerSystem Spec
  7.    28 Jan 2016 #17
    Join Date : Jan 2016
    Posts : 643
    windows 10 Pro

    More and more it looks like a hardware problem.
    I suspect that your RAM is at fault.
    Or the mobo is the culprit.
      My ComputerSystem Spec
  8.    28 Jan 2016 #18
    Join Date : Jan 2016
    Posts : 13
    Windows 10
    Thread Starter

    Quote Originally Posted by lifetec View Post
    More and more it looks like a hardware problem.
    I suspect that your RAM is at fault.
    Or the mobo is the culprit.
    I think you are correct. I was going to give it a last chance today. And after breadboarding heard double beep code, which means cmos error, but it still somehow boots up. I immediately reset the pc, and tried stress testing the cpu, where everything was good, pc ran for about 8 hours with nothing happening, I installed only the video card driver and the cpu testing tools. So I go for the ram tests. Started with 4 sticks ram together (I don't even want to know which one is bad..) using windows memory diagnostic tool, and then when the progress reaches about 40%, it rebooted.

    Now I am having trouble booting the system, but at least I could say that it is very likely ram problems.
    I ordered new rams right way, and awaiting the new results, which will probably be up next week.

    Just one thing to confirm, if system reboots just when testing the memory, it is more likely to be ram problem than a mobo problem right?
      My ComputerSystem Spec
  9.    28 Jan 2016 #19
    Join Date : Jan 2016
    Posts : 13
    Windows 10
    Thread Starter

    Sorry guys, my mobo just died, will not post no matter what. Ordering a new mobo+cpu right now.. Will update if everything is good after. Thanks for the patience on solving my problem!
      My ComputerSystem Spec

 
Page 2 of 2 FirstFirst 12


Similar Threads
Thread Forum
Solved BSOD while gaming (vermintide.exe + other causes)
About 2 months ago I went for a full-on upgrade and splurged on a new mobo, ram, cpu, AIO cooler and monitor, and decided to take the plunge and finally do a fresh install of Windows 10. Recently I've been hit with relentless bluescreens however. ...
BSOD Crashes and Debugging
Solved BSOD While Gaming (Kernel_Security_Check_Failure)
Anyone that could help, I appreciate it! This issue started yesterday, and I can't pinpoint what started it. I finished my last final for the semester, and I went to open Batman: Arkham Knight. The launcher opened and got to the main menu, but then...
BSOD Crashes and Debugging
BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL while gaming
Hello, I'm using a laptop I bought last week, came with windows 8.1, free upgraded to windows 10. Installed all the updates before and after upgrading, and to my knowledge I have all the latest updates currently available. I was playing a game a...
BSOD Crashes and Debugging
hal.dll and ntoskrnl.exe BSOD only when gaming
Hi Jordan here. I've recently been getting a lot of blue screens whilst gaming, this problem occurred when I was on Windows 7 too but I upgraded to 10 when I done a clean install of windows. I'm not really sure what is causing the problem....
BSOD Crashes and Debugging
BSOD when gaming and not gaming
BSOD persists after fresh install of Windows 10 from windows 8.1, happens when playing heroes of the storm quite often but has happened while browsing pinterest/facebook.
BSOD Crashes and Debugging
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 02:24.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums