Random BSOD's with either 156 or 292 as BugCheckCode

Page 1 of 5 123 ... LastLast

  1. Posts : 19
    Windows 10
       #1

    Random BSOD's with either 156 or 292 as BugCheckCode


    Hi,

    I have had a problem with my computer ever since I upgraded some hardware back in August. More specifically, over 60 BSOD's at random and very unpredictable times. Sometimes it crashes three times in an hour, other times I can sit for three days with no problem at all. I have tried every possible solution I could find online, but nothing seems to work. I even went and got a new PSU to rule out that as an issue, and am currently running with the case open so that I can be sure it's not an overheating issue due to restricted airflow. Every crash report I get has one of two BugCheckCodes; 156 and 292, which translate to WHEA_UNCORRECTABLE_ERROR and MACHINE_CHECK_EXCEPTION, respectively. Everything I can find online points to this being a hardware issue, so I've reset BIOS to standard (no overclocking of any kind, not even automatic) and run 10 passes of a full Memtest86 with 0 errors. All the hard drives are also reporting 0 errors, and I even got a new magnetic disk to be able to transfer everything from the old drives in case that was the issue. However, after doing all of this and nothing helping (I still get the exact same errors), I am beginning to suspect it might actually be a faulty processor and/or motherboard, and I still have three months left on the warranty for it. I can't be sure though - and therefore I am humbly asking for any help in pinpointing the error, if at all possible. I have collected the requested data with the v2 Log viewer tool, and here's the link: DESKTOP-E6C97SD-(2020-05-10_09-48-26).zip - Google Drive

    Computer specs: Operating System
    Windows 10 Pro 64-bit
    CPU
    Intel Core i5 @ 3.70GHz 33 °C
    Kaby Lake 14nm Technology
    RAM
    32,0GB Dual-Channel Unknown @ 1069MHz (15-15-15-36)
    Motherboard
    ASUSTeK COMPUTER INC. ROG STRIX Z390-F GAMING (LGA1151) 33 °C
    Graphics
    BenQ GL2450 (1920x1080@60Hz)
    ASUS VG32V (2560x1440@144Hz)
    4095MB NVIDIA GeForce GTX 970 (ASUStek Computer Inc) 55 °C
    Storage
    3726GB Seagate ST4000DM004-2CV104 (SATA ) 31 °C
    465GB Samsung SSD 860 EVO 500GB (SATA (SSD)) 29 °C
    931GB Seagate ST1000DM000-9TS15E (SATA ) 37 °C
    238GB SanDisk SDSSDHP256G (SATA (SSD)) 30 °C
    1863GB Western Digital WDC WD20EARX-00PASB0 (SATA ) 33 °C
    Optical Drives
    TSSTcorp CDDVDW SH-224DB
    Audio
    NVIDIA Virtual Audio Device (Wave Extensible) (WDM)

    Any kind of help would be greatly appreciated. Peace out!
      My Computer


  2. Posts : 1,538
    Windows 8.1 Enterprise x64
       #2
      My Computer


  3. Posts : 19
    Windows 10
    Thread Starter
       #3

    Already did, as well as all drivers. Should also add that these logs are old because for some reason the dumps aren't saved anymore, even though they are collected, but it's the same errors anyway so I don't think it matters much.
      My Computer


  4. Posts : 19
    Windows 10
    Thread Starter
       #4

    It's weird how the computer can sit idle for days, but as soon as I start playing games it crashes. Could it be a processor issue maybe?
      My Computer


  5. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #5

    All the dumps are the same:

    Code:
    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: ffff8a04de403028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.
    Code:
    1: kd> !errrec ffff8a04de403028
    ===============================================================================
    Common Platform Error Record @ ffff8a04de403028
    -------------------------------------------------------------------------------
    Record Id     : 01d6161863940c0d
    Severity      : Fatal (1)
    Length        : 872
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 4/19/2020 7:07:42 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffff8a04de4030a8
    Section       @ ffff8a04de403180
    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   : 0x00000000000906ec
    Processor ID  : 0x0000000000000002
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffff8a04de4030f0
    Section       @ ffff8a04de403240
    Offset        : 536
    Length        : 64
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000002
    CPU Id        : ec 06 09 00 00 08 10 02 - ff 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    @ ffff8a04de403138
    Section       @ ffff8a04de403280
    Offset        : 600
    Length        : 272
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : Unknown (Proc 1 Bank 0)
      Status      : 0xb200000000030005
    May be a defective CPU (heat sensitive). You can try hwinfo64 or speedfan to monitor temps and see if that may be the cause of your problem.
    This could also be caused be a flaky device driver but I doubt it. You can check for this using Driver Verifier as follows:

    Run Driver Verifier


    Driver Verifier-- tracking down a mis-behaving driver.

    Following the instructions in the above link will check for problems in all non-Microsoft drivers.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive or Google Drive and post a link to it here.

    To check if verifier is active, open a Command Prompt and enter:

    verifier /query

    If not active it will respond with

    No drivers are currently verified.

    If you have questions, see this additional tutorial which may help to clear things up.

    Enable and Disable Driver Verifier in Windows 10

    I believe this is probably a defective CPU though. If you have another you can try that would be the best way to check this.
      My Computers


  6. Posts : 392
    W10
       #6

    IF you suspect the CPU, try these free tests:
    - Prime95 (it stresses the Memory Controller and CPU Cache): GIMPS - Free Prime95 software downloads - PrimeNet
    Run Stress Test until temps level out. If temps get in the *edit* HIGH 90's (Centigrade), stop the test immediately!

    - Intel Processor Diagnostic Tool; Download Intel(R) Processor Diagnostic Tool
    Last edited by jdc1; 18 May 2020 at 06:15. Reason: Added "HIGH"
      My Computer


  7. Posts : 19
    Windows 10
    Thread Starter
       #7

    Alright, good advice!

    I tried Driver Verifier with almost all options enabled, which caused a boot failure and then a page file bsod when restarting it after disabling Driver Verifier through Safe mode. Not sure if related, since the faulty driver was the Microsoft wifi driver, but at least there was a minidump generated this time. I tried again with only the suggested options enabled, and that at least made it possible to boot the system. I then tried playing a game that I knew would cause a BSOD almost immediately (Warcraft 3 Reforged) but it worked.

    Regarding the CPU theory, it is definitely a possibility. The BSOD's started immediately after upgrading, and at first I just thought it was because I didn't do a fresh install of Windows, but as time has passed and I've done almost everything I can think of, including replacing the PSU and flashing BIOS, it seems more and more likely. I will do a stress test too to figure out if it's heat related, but I've had those kinds of problems before in an old computer and it wasn't quite the same. Then it would just randomly shut off without freezing, and when I checked inside the case there was a thick layer of dust on the processor fan and very little air circulation, and when I fixed that it was much smoother. This time I'm running with the case open and properly working fans, and when I tried stress testing earlier it would barely be noticeable on the core temps even though I ran it for 15 minutes straight on maximum load. I did it again this morning for 15 minutes with all fans enabled, and it would average around 70 degrees centigrade and peak at around 80. It would make sense if it was some random heat sensitivity though, since I've noticed certain games or activities are much more likely to trigger it. For instance, long periods of using Discord with a lot of browser tabs open, or some games but not others, which would be compatible with the idea of it being activities that put more stress on the CPU. It's still weird how I can play other games for hours with no incident, and that it crashes repeatedly even on games that are quite light on the computer's resources. I'm just wondering if there could be something I've done wrong when installing it, since I built the machine myself and this was the first time actually handling the CPU and motherboard without anyone helping out.

    It's been working for the entire morning now though, so I'll report back if and when I trigger the next "proper" BSOD.
      My Computer


  8. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #8

    PRIME95 as @jdc1 suggested is a good idea.

    Can you run the V2 log collector and upload the zip so we can look at the latest data?
      My Computers


  9. Posts : 19
    Windows 10
    Thread Starter
       #9

    I ran Prime95 for 15 minutes earlier, which caused the temps to rise to around 80 degrees in the processor, and then average out around 75.

    Of course, now that I've finally asked for help with the issue, the machine has been performing exemplary, with not a single crash since I activated driver verifier, despite 12 hours of continuous use today and several hours yesterday with a mix of games and other things. However, I don't trust this to work indefinitely, so as soon as it crashes I'll post it here. At least I know it gives me reports now as there was a page file crash connected to rebooting out of safe mode, but I don't think it's related to the other issues. I am very grateful for the help, and there's exactly 3 months left on my warranty period so hopefully the problem will have been pinpointed and sorted out until then. :)
      My Computer


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

    The logs are in a foreign language and cannot be scanned.
    Please use English as the default language and upload each V2 and DM into this thread:

    https://www.tenforums.com/tutorials/...dows-10-a.html
    Change Display Language in Windows 10

    BSOD - Posting Instructions



    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) bcdedit /enum {badmemory}

    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    14) Make sure that there is no over clocking while troubleshooting
      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 03:11.
Find Us




Windows 10 Forums