BSOD randomly - help


  1. DEVILEE
    Posts : 7
    Microsoft Windows 10 Pro 64-bit Version 10.0.19041 Build 19041 2004
       New #1

    BSOD randomly - 0x124


    hello

    well... thank you for the great forum i do really enjoy reading those tutorials and guide about the pc world
    I'am having bad time with my desktop trying to fix the BSOD problem so , it occurs randomly no specific time or period the thing is i was using my computer normally as usual and suddenly blue screen .

    so i tried to run some guides trying to isolate the issue but it seems nothing is working
    i did run gpu stress test for 1 hour and cpu stress test for 2 hours and memtest with 6 passes also did the chkdsk /f /r ,did not show any error or bsod ,my last resort was installing clean windows and still same thing also I did reset my bios with no overclocking

    last thing it does say weha_uncorrectable_error on the blue screen with bugcheck 0x124

    the requested files is attached
    Last edited by DEVILEE; 17 Feb 2019 at 17:28.
      My Computer
    Quote Quote

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

    The CPU is reporting that

    Code:
    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 record is:

    Code:
    2: kd> !errrec ffffa80163203028
===============================================================================
Common Platform Error Record @ ffffa80163203028
-------------------------------------------------------------------------------
Record Id     : 01d4c6332b077e2c
Severity      : Fatal (1)
Length        : 864
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/16/2019 20:08:56 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa801632030a8
Section       @ ffffa80163203180
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   : 0x00000000000506e3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffa801632030f0
Section       @ ffffa80163203240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : e3 06 05 00 00 08 10 02 - bf fb fa 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

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffa80163203138
Section       @ ffffa80163203280
Offset        : 600
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 2 Bank 0)
  Status      : 0xb200000000010005

    It is an unknown error, it could be the CPU but it is difficult to know with any certainty. The only way to troubleshoot this is to test the hardware components and in some cases you can only do this by substituting them for a known good component. Make sure the inside of the PC is free from dust and that the fans are spinning. If you can get hold of another CPU I would try this first.
      My Computers
    Quote Quote

  4. DEVILEE
    Posts : 7
    Microsoft Windows 10 Pro 64-bit Version 10.0.19041 Build 19041 2004
    Thread Starter
       New #3

    philc43 said:
    The CPU is reporting that

    Code:
    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 record is:

    Code:
    2: kd> !errrec ffffa80163203028
===============================================================================
Common Platform Error Record @ ffffa80163203028
-------------------------------------------------------------------------------
Record Id     : 01d4c6332b077e2c
Severity      : Fatal (1)
Length        : 864
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/16/2019 20:08:56 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa801632030a8
Section       @ ffffa80163203180
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   : 0x00000000000506e3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffa801632030f0
Section       @ ffffa80163203240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : e3 06 05 00 00 08 10 02 - bf fb fa 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

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffa80163203138
Section       @ ffffa80163203280
Offset        : 600
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 2 Bank 0)
  Status      : 0xb200000000010005

    It is an unknown error, it could be the CPU but it is difficult to know with any certainty. The only way to troubleshoot this is to test the hardware components and in some cases you can only do this by substituting them for a known good component. Make sure the inside of the PC is free from dust and that the fans are spinning. If you can get hold of another CPU I would try this first.
    thank you for response i will try this method
      My Computer
    Quote Quote

  6. axe0
    Posts : 14,903
    Windows 10 Pro
       New #4

    As requested, a second opinion.

    I think it should/could be possible to get more information out of the dump to narrow things down, but basically I agree with Phil.
      My Computers
    Quote Quote

  7. DEVILEE
    Posts : 7
    Microsoft Windows 10 Pro 64-bit Version 10.0.19041 Build 19041 2004
    Thread Starter
       New #5

    thank you for helping guys , the problem solved by increasing the cpu core voltage from auto to manual
    from 1.97 to 1.3 v

    regards
      My Computer
    Quote Quote

  8. axe0
    Posts : 14,903
    Windows 10 Pro
       New #6

    I think you made a typo, because that isn't increasing but rather bringing the vcore back to stock.
      My Computers
    Quote Quote

  9. DEVILEE
    Posts : 7
    Microsoft Windows 10 Pro 64-bit Version 10.0.19041 Build 19041 2004
    Thread Starter
       New #7

    axe0 said:
    I think you made a typo, because that isn't increasing but rather bringing the vcore back to stock.
    im thinking of downgrading the bios to older version
      My Computer
    Quote Quote

  10. axe0
    Posts : 14,903
    Windows 10 Pro
       New #8

    Is there any particular reason for why you would want to downgrade the BIOS?
      My Computers
    Quote Quote

  12. DEVILEE
    Posts : 7
    Microsoft Windows 10 Pro 64-bit Version 10.0.19041 Build 19041 2004
    Thread Starter
       New #9

    axe0 said:
    Is there any particular reason for why you would want to downgrade the BIOS?
    i mean once i changed the voltage to manual fixed it
    so i though that bios firmware bugged or something

    anyway i will keep it manual as the bsod gone and that's good for me
      My Computer
    Quote Quote

  13. axe0
    Posts : 14,903
    Windows 10 Pro
       New #10

    That would be something with your CPU, not the BIOS, maybe the vcore needed to be lowered after time passed.
      My Computers
    Quote Quote

 

  Related Discussions
BSOD Randomly
in BSOD Crashes and Debugging

Hi everyone, I've been experiencing crashes since a Windows update earlier this month. Seems to happen randomly and most of the time the screen blacks out and then freezes. Not exactly sure where to go from here. Thanks
Randomly BSOD
in BSOD Crashes and Debugging

Hi friends 3 months ago I collected a system. Motherboard: B350 MSI Tomahawk Graphics Card: Asus Rog Strix RX580 Processor: Ryzen 1500x Ram: Crucial Elite 2666MHz 16GB PSU: Evga 700 Watt Bronze B1 I collected the system myself. No...
BSOD randomly
in BSOD Crashes and Debugging

so i'm having the same BSOD appear seemingly randomly; each time it says netio.sys is somehow associated with the cause of the BSOD, but I'll just attach this so the experts can help me out :)
BSOD Randomly
in BSOD Crashes and Debugging

I will BSOD while gaming, browsing, or while my computer is idle. There are several different error codes which appear, and the file I'm linking has most of them.83003 They happen fairly regularly, about once an hour.
BSOD randomly.
in BSOD Crashes and Debugging

Lately i have been getting a blue screen once everyday randomly they all have been saying IRQL_NOT_LESS_OR_EQUAL i have downloaded the thing in posting instructions and this is what it gave me...
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 19:38.
Find Us




Windows 10 Forums