BSOD on a new build after running fine for a week

  1.    #1

    BSOD on a new build after running fine for a week


    Just built a new PC and it's been running fine until getting a BSOD today after a game crashing a few times. Attached the V2 and DM zips, hoping someone knows what the cause may be.

    DESKTOP-6F344N1-(2019-07-15_22-15-17).zip
    DESKTOP-6F344N1-2019-07-15_221900_96.zip
      My ComputerSystem Spec

  2.    #2

    Please ensure that you check for and install any available Windows Updates

    There are 2 AMD chipset devices that don't have drivers installed. Please visit the MSI support website for your motherboard and install ALL of the latest updates (to include the AMD chipset/devices drivers).
    Code:
    PCI Device	PCI\VEN_1022&DEV_148A&SUBSYS_7C021462&REV_00\4&D573D7&0&0039	The drivers for this device are not installed.
    PCI Device	PCI\VEN_1022&DEV_1485&SUBSYS_7C021462&REV_00\4&1FDE7688&0&0041	The drivers for this device are not installed.

    With ALL of those updates, test and see if the BSOD's stop.
    If they don't, I'd suggest running Driver Verifier as the next step.

    Good luck!!!

    EDIT: FYI - I suspect these libraries/drivers as they've had BSOD issues in the past:
    WinRing0x64.sys Wed May 1 22:19:47 2013 (5181CD43)
    NTIOLib_X64.sys Sun Jul 9 22:13:57 2017 (5962E2E5)
      My ComputerSystem Spec

  3. axe0's Avatar
    Posts : 14,261
    Windows 10 Pro
       #3

    Please run driver verifier using the following settings for 48 hours.
    • Special Pool
    • Force IRQL checking
    • Pool Tracking
    • Deadlock Detection
    • Security Checks
    • Miscellaneous Checks
    • Power framework delay fuzzing
    • DDI compliance checking



    Warning: driver verifier could cause boot issues and/or performance issues.



    Resetting driver verifier options (recommended in this order)
    1. In normal mode open an administrator command prompt and enter the below command
    2. In safe mode open an administrator command prompt and enter the below command
    3. On 3 boot failures, you'll boot automatically to the recovery options,
      • click Troubleshoot
      • go to the advanced options
      • choose command prompt
      • enter the below command

    4. Boot with the recovery media, see above 4 steps in option 3.
    5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

    Code:
    verifier /reset


    Crashed when running driver verifier
    1. Reset driver verifier
    2. Boot in normal mode if necessary
    3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs




    Extra information about driver verifier
    When you run driver verifier, there are two things you're looking out for
    1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
    2. Driver verifier will find a driver violating something and thus the system will crash.

    The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.


    Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

    Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

    If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt

    Code:
    verifier /query
    If the command gives a result similar to this, it means driver verifier is running.


      My ComputersSystem Spec


 

Related Threads
Hello, I recently got a new GPU and fresh installed the drivers. For the first day, the PC booted up fine and there were no errors, but in the coming days after, when I start up the PC, it crashes with just a black screen (before entering windows...
Hello, I had a problem with my HDD and had been running scanning and repair for a week now where it stuck at 27% since the first day. I'm using chkdsk r/ f/ c: to check my 1Tb of HDD. It had been too long for me. What should I do next? Should I...
Hi there, I'm not sure where else to turn, as I've done lots of other 'fixes' (re-install drivers and clean install of Windows) but this BSOD never seems to go away. As the title states, it ONLY happens when I'm on the program Second Life, and it...
BSOD once a day, then fine after reboot in BSOD Crashes and Debugging
Hey I'm getting a BSOD once a day or every time my computer has been turned off for longer than just a reboot. When the computer reboots after the BSOD it runs just fine with no incidents until the next time its turned off for a bit. IIRC it...
Hi, I've been having a problem lately where after logging into windows I cant click anything, I can right click, but thats it. And if a window is open, if I left click, it deselects that window as if My mouse click clicks behind the open window....
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 12:00.
Find Us