Series of different BSOD crashes and freezes on boot

Page 1 of 2 12 LastLast

  1. Posts : 4
    Windows 10 Pro 64-bit
       #1

    Series of different BSOD crashes and freezes on boot


    Good Morning,

    Over the past few weeks or so I've been getting game crashing errors in Apex, BFV, and Rocket League.

    Finally I got tired of the crashes, and disabled my CPU overclock by resetting the BIOS to default, which rendered my PC unusable. I would get every BSOD in the book, and no amount of Windows' built-in repair tools were successful.

    A friend recommended I post here after trying over 12 hours of troubleshooting and reinstalling.

    There's a long history of troubleshooting that I think I can skip over and focus on the issue I'm having at this moment.

    Up until this point, I've completely disassembled my PC down to it's basic components and rebuilt, adding one component at a time to try and isolate the issue. I can't identify any individual component which triggers the BSOD / freeze, but it's still happening. The only component I haven't managed to isolate, is the PSU.

    After I reinstalled Win 10 Pro 64-bit last night onto a freshly wiped drive, the only BSOD I was getting was "WHEA_UNCORRECTABLE_ERROR". This would happen every time I booted, roughly 1 minute after Windows loads.

    Now, I rarely get the BSOD but rather the computer just freezes up and needs a reset after the same time frame.

    Attachment 239486

    Log files are attached, all help is appreciated. Thank you
      My Computer


  2. Posts : 392
    W10
       #2

    It sounds like you've done a lot of the work for us.
    From your description, you're looking at a hardware error (but this isn't 100% certain - but it is likely).

    How did you test the CPU, motherboard, RAM, and GPU? Did you use other parts when testing the system for hardware faults?

    I'd like to have a look at the Event Viewer - Administrative log (it shows a summary of all critical, error, and warning events)
    Please do the following:
    - open Event Viewer (run eventvwr.msc from the "Run" dialog)
    - expand the Custom Views category (left click on the > next to the words "Custom Views")
    - right click on the "Administrative Events" heading
    - select "Save all Events in Custom View as..."
    - save the file as Admin.evtx
    - zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
    - upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

    2 ways to test the PSU:
    - OCCT: Download the latest stable version from here: OCBASE / OCCT
    You can also run the rest of the tests that it has, but be careful as it can damage the system if left to run without supervision. Let us know what temperatures it shows for your components.
    If the system starts to act badly while using it - SHUT IT OFF IMMEDIATELY!!!
    - try another PSU. If you don't have one, either borrow one from a friend - or purchase one from a shop that will let you return it for your money back (if it's not needed).

    The memory dump shows a STOP 0xA BSOD error (IRQL_NOT_LESS_OR_EQUAL).
    There are no significant 3rd party drivers present in the memory dumps - so I am tempted to dismiss the possibility of it being a 3rd party driver (other possibilities are that it's a Windows driver or it's a hardware problem). To be sure, I'd like to ask you to run Driver Verifier according to these instructions: Driver Verifier Settings

    The Windows drivers are also likely to not be to blame (as you seem to have reinstalled Windows "clean" without any 3rd party programs/customizations)

    That leaves hardware as the item to blame.
    I'd suggest running (in addition to all of the OCCT tests):
    I suggest MemTest86 (not MemTest86+) for the RAM (memory) and Seagate Seatools for the hard drives

    I suggest MemTest86 as it will boot from UEFI - where MemTest86+ will require messing with the UEFI settings.
    MemTest86 - Official Site of the x86 Memory Testing Tool

    I haven't used the Seagate tools in a while. If using the bootable version, I don't know if you'll have to mess with UEFI settings or not
    SeaTools | Seagate Support US
    Regardless - run the Seatools on ALL drives when in Windows (if possible)
    If not possible, then run the bootable tool on all drives

    Run processor diagnostics.
    I only know of the Intel Processor Diagnostic Tool ( Download Intel(R) Processor Diagnostic Tool )
    Search the web for other processor tools

    Other disgnostics can't hurt. But be careful as some will stress the system to the point of breakage.
    Remember that diagnostics are software tools that are testing hardware components. As such, they may not be 100% accurate.
    Most common are video stress tools. You may want to try other overclocking utilities also.
    I'm impressed by the OCCT tool - but it's one that needs to have care exercised when using.
    - - - Updated - - -

    woops! BIOS/UEFI dates from 2014.
    I would suggest updating it to the latest available version from the Gigabyte website:
    rev 1.1: GA-Z97X-Gaming 3 (rev. 1.1) | Motherboard - GIGABYTE U.S.A.
    rev 1.0: GA-Z97X-Gaming 3 (rev. 1.0) | Motherboard - GIGABYTE U.S.A.

    Please note that the last update was a beta release in early 2016. As such, I have to wonder about Gigabyte's continued support of this motherboard. You may wish to contact them to see if they still support it for later versions of W10
      My Computer


  3. Posts : 4
    Windows 10 Pro 64-bit
    Thread Starter
       #3

    Hey thanks for the response.

    I haven't run any specific tests on the CPU, but determined that it works okay just because my PC always posts without issue. I assumed that a failed CPU wouldn't respond at all.

    I tested the RAM both through windows memory diagnostic and MemTest86+ with no errors. I also tried swapping the dimms in and out, different ports, and the crashes persisted in all cases.

    I determined it wasn't the GPU because again, it still crashes with the GPU removed.

    I haven't run any specific tests on the motherboard or PSU, but I can try buying a new PSU to see if that does the trick. The mobo is a bit trickier obviously as it requires a complete dismantle and I'm not even sure if my socket is supported anymore.

    Trying to pull the administrative log from event viewer now, the struggle is having windows run long enough for me to do that.

    the IRQL_NOT_LESS_OR_EQUAL was the most common bsod I was getting prior to WHEA_UNCORRECTABLE_ERROR. I will try running the driver verifier as suggested.

    Will update shortly.

    jdc1 said:
    It sounds like you've done a lot of the work for us.
    From your description, you're looking at a hardware error (but this isn't 100% certain - but it is likely).

    How did you test the CPU, motherboard, RAM, and GPU? Did you use other parts when testing the system for hardware faults?

    I'd like to have a look at the Event Viewer - Administrative log (it shows a summary of all critical, error, and warning events)
    Please do the following:
    - open Event Viewer (run eventvwr.msc from the "Run" dialog)
    - expand the Custom Views category (left click on the > next to the words "Custom Views")
    - right click on the "Administrative Events" heading
    - select "Save all Events in Custom View as..."
    - save the file as Admin.evtx
    - zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
    - upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

    2 ways to test the PSU:
    - OCCT: Download the latest stable version from here: OCBASE / OCCT
    You can also run the rest of the tests that it has, but be careful as it can damage the system if left to run without supervision. Let us know what temperatures it shows for your components.
    If the system starts to act badly while using it - SHUT IT OFF IMMEDIATELY!!!
    - try another PSU. If you don't have one, either borrow one from a friend - or purchase one from a shop that will let you return it for your money back (if it's not needed).

    The memory dump shows a STOP 0xA BSOD error (IRQL_NOT_LESS_OR_EQUAL).
    There are no significant 3rd party drivers present in the memory dumps - so I am tempted to dismiss the possibility of it being a 3rd party driver (other possibilities are that it's a Windows driver or it's a hardware problem). To be sure, I'd like to ask you to run Driver Verifier according to these instructions: Driver Verifier Settings

    The Windows drivers are also likely to not be to blame (as you seem to have reinstalled Windows "clean" without any 3rd party programs/customizations)

    That leaves hardware as the item to blame.
    I'd suggest running (in addition to all of the OCCT tests):


    - - - Updated - - -

    woops! BIOS/UEFI dates from 2014.
    I would suggest updating it to the latest available version from the Gigabyte website:
    rev 1.1: GA-Z97X-Gaming 3 (rev. 1.1) | Motherboard - GIGABYTE U.S.A.
    rev 1.0: GA-Z97X-Gaming 3 (rev. 1.0) | Motherboard - GIGABYTE U.S.A.

    Please note that the last update was a beta release in early 2016. As such, I have to wonder about Gigabyte's continued support of this motherboard. You may wish to contact them to see if they still support it for later versions of W10
      My Computer


  4. Posts : 392
    W10
       #4

    In most cases the test for a motherboard is ruling everything else out.
    It's painful, but it's the easiest way to avoid dismantling the system and reinstalling everything.

    Driver Verifier probably won't yield anything significant. If that's the case, then we assume it's hardware and continue with the troubleshooting.
      My Computer


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

    The Event Viewer logs are in the zip file Messsk uploaded:

    Attachment 239504
      My Computers


  6. Posts : 392
    W10
       #6

    Thanks Ztrucker! I prefer the Adminstrative .evtx file for the following reasons.

    - Text files aren't easily sortable as are the .evtx files
    - Application, System, and other events aren't all visible in the same window (for example, I'd like to see what was going on just before and after the BSOD occurred)
    - Occasionally errors from other logs are valuable to see - and they may not necessarily show up in the Application, System, or PNP Events logs

    - The Administrative log summarizes all errors (Critical, Error, and Warnings) from all of the event logs.and is easily sortable so one can look at a series of errors and/or view the error timing in relation to other errors. Unfortunately, I have not been able to discover a way to easily save the file - hence the complicated instructions.
      My Computer


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

    Okay, makes sense to me.

    I looked briefly at the dump and MS has still not loaded the right symbols on the symbol server for the 1903 release, so there is not much we can do with a dump.

    msinfo32 WER data shows 2 BSODs, Bugcheck A.
      My Computers


  8. Posts : 392
    W10
       #8

    I use kd.exe rather than windbg and find that there is some information in the dumps that is usable.
    I treat the missing symbols as I would a 3rd party driver (that doesn't have public symbols). But then again, I don't do much massaging of the dumps with different commands.

    Several years ago I had a friend who worked with the Microsoft symbol server.
    I'll see if I can locate his email and ask where the holdup is.
      My Computer


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

    1) Open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive


    Code:
    Crash dump found at C:\Windows\MEMORY.DMP
    Creation date: 07/06/2019 01:02:39
    Size on disk: 600 MB

    2) Open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) dism /online /cleanup-image /restorehealth
    5) chkdsk /scan
    6) wmic recoveros set autoreboot = false
    7) 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

    8) Make sure that there is no over clocking while troubleshooting.


    9) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
    FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
    FurMark - GPU Stress Test
    Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
    a) Record the maximum temperature and post the maximum temperature into the thread.
    b) Record the test duration and post the uninterrupted test duration into the thread.
    c) Aim for testing 1 hour.
    d) Use the Microsoft snipping tool to post images into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10



    10) Turn off windows fast startup:
    Turn On or Off Fast Startup in Windows 10


    11) Use file explorer or Everything voidtools to find and post a share link (one drive, drop box, or google drive) for: PoW32kWatchdog-20190706-0148.dmp

    Code:
    Name                             LastWriteTime          Size (MB)
    ----                             -------------          ---------
    PoW32kWatchdog-20190706-0148.dmp 2019-07-06 1:48:55 AM    1943.64
      My Computer


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

    jdc1 said:
    I use kd.exe rather than windbg and find that there is some information in the dumps that is usable.
    I treat the missing symbols as I would a 3rd party driver (that doesn't have public symbols). But then again, I don't do much massaging of the dumps with different commands.

    Several years ago I had a friend who worked with the Microsoft symbol server.
    I'll see if I can locate his email and ask where the holdup is.
    I (we) would be forever in your debt if you could shake the tree a bit. Thanks.

    Can you explain more about using kd instead of windbg. Like @axe0, I'm pretty new at the whole BSOD thing and anything I can learn that will allow me to help someone else I'm all for.

    What is it, how is it used. I'll see what I can find by doing some searches.
      My Computers


 

  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 06:06.
Find Us




Windows 10 Forums