BSOD - Gaming PC is getting old

Page 1 of 2 12 LastLast

  1. Posts : 13
    Windows 10
       #1

    BSOD - Gaming PC is getting old


    Hello, I built this PC over five years ago mainly to game on. It recently has been crashing a lot with the BSOD. It really ramped up when I started playing Dark Souls III. I want to beat that game but I hate this BSOD crashes. I hope it is not time to get a new PC as I can't afford one right now. Can my PC be fixed our upgraded? Any help would be greatly appreciated. Thanks in advance.

    Here is the crash log report:

    Dropbox - DESKTOP-U27RML8-(2020-02-13_21-42-37) - Simplify your life
      My Computer

  2. axe0's Avatar
    Posts : 14,785
    Windows 10 Pro
       #2

    Please run driver verifier using the following settings for 48 hours.
    • I/O Verification
    • IRP Logging



    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 Computers


  3. Posts : 13
    Windows 10
    Thread Starter
       #3

    Thanks. I am running the verifier now. My computer is not sluggish at all. When I type verifier / query into the command line I get a bunch of data scrolling in a black box so I think itís running properly.
      My Computer

  4. axe0's Avatar
    Posts : 14,785
    Windows 10 Pro
       #4

    Driver verifier is running properly yes.

    Please be aware, any sluggishness may not start immediately but could start to occur whilst working or gaming for example, it's completely normal with driver verifier enabled.
      My Computers


  5. Posts : 13
    Windows 10
    Thread Starter
       #5

    Got it. Thanks. So the idea here is to see if it crashes while running this verifier and if it does there will be a log to help diagnose the issue? If there is no crash after 48 hours I guess we can assume it is a hardware issue? I have always wondered if my 600 watt power supply was enough to drive my PC. It has done so for over 5 years with no issues, until now. Could that be the issue you think? I keep getting the "driver power state failure" BSOD.
      My Computer


  6. Posts : 207
    Windows 10 Pro
       #6

    Have you run Samsung Magician to see if there is a firmware update for your SSD and/or check the health of the drive? The 830 seems to be involved in the 0x9F bugchecks. Also, your motherboard support page shows "improve power on issue" as a fix for the F10 BIOS. I'm not sure what that means but I would assume it's power related. You're currently running the F9 BIOS.
      My Computer


  7. Posts : 13
    Windows 10
    Thread Starter
       #7

    Thanks for the suggestions cwsink. I'll try them tonight when I get home from work and report back.
      My Computer

  8. axe0's Avatar
    Posts : 14,785
    Windows 10 Pro
       #8

    tbone3969 said:
    Got it. Thanks. So the idea here is to see if it crashes while running this verifier and if it does there will be a log to help diagnose the issue?
    Unlike what many might be used to from other programs, driver verifier doesn't create any logs besides a dump file.
    If driver verifier catches a driver doing something bad, driver verifier will crash the system with a BSOD and a dump will be generated. Nothing else will be done, i.e. no text file will be generated of what driver verifier did.
      My Computers


  9. Posts : 13
    Windows 10
    Thread Starter
       #9

    ok well I came home from work and the PC was still running with no issues. The verifier was also still running. I surfed the web a bit and ripped some CDi games to my desktop. I also verified my two Samsung SSD are working properly and they both have the most up to date drivers installed. Then I started playing DS III around 8:45pm. After about 45 minutes of playing I got the same "Driver Power State Failure" BSOD.

    Any thoughts?

    Thank you.

    - - - Updated - - -

    Actually upon further investigation of the crash logs it doesn't seem like the game (DS III) crashed it this time. Its seems Windows itself crashed? I'm so confused. Here is a screen shot:

    Dropbox - 2.14.20 BSOD.docx
      My Computer

  10. Golden's Avatar
    Posts : 1,635
    Windows 10 Pro x64
       #10

    From the screencapture image, the 0x9F with parameter 1 =3 suggests the problem is a 3rd party driver. You need to upload the .dmp file so someone can analyse it further to see if they can determine which driver is at fault.

    I also suggest following the steps posted in post #6.
      My Computers


 
Page 1 of 2 12 LastLast

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




Windows 10 Forums