BSOD while idle/gaming/re-installing windows, mostly 0x000000d1

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 10
    Windows
    Thread Starter
       #11

    Ztruker said:
    Your board only has one PCIE16 slot.
    So is there nothing that I can do, but replacing the GPU?
      My Computer


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

    Have you tried older versions of the Nvidia driver?
      My Computers


  3. Posts : 10
    Windows
    Thread Starter
       #13

    Ztruker said:
    Have you tried older versions of the Nvidia driver?
    Yes
      My Computer


  4. Posts : 926
    Windows 10 Pro
       #14

    Since there isnt much u can do besides trying another driver version or replacing the GPU for testing. Last thing u can try is to switch the second TFT to 60 hz. Maybe this changes something. ATM its running on 75 Hz but the native mode is 60 Hz:

    Code:
    Current Mode: 1440 x 900 (32 bit) (75Hz) 
    Monitor Name: Generic PnP Monitor 
    Monitor Model: unknown 
    Native Mode: 1440 x 900(p) (59.887Hz) 
    Output Type: HDMI

    U can unplug the TFT which connected via HDMI completely to check if this is the problem.
      My Computer


  5. Posts : 10
    Windows
    Thread Starter
       #15

    BSODHunter said:
    U can unplug the TFT which connected via HDMI completely to check if this is the problem.
    I tried unplugging the second monitor, and I still got the BSoD. I switched both of the monitors to 60 Hz just in case.
    Also I have updated some drivers via DriverEasy. I will keep you updated.
      My Computer


  6. Posts : 10
    Windows
    Thread Starter
       #16

    Nope... I just had a BSoD again... So replacing the GPU is the only option that I have?
      My Computer


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

    Before you replace the GPU, try running with Driver Verifier enabled to see if something else is possibly causing a problem.

    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier may run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to PART TWO and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    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 dm_log_collector and upload the resulting zip file.
      My Computers


  8. Posts : 926
    Windows 10 Pro
       #18

    Is there any news or did you fix the problem?
      My Computer


  9. Posts : 10
    Windows
    Thread Starter
       #19

    BSODHunter said:
    Is there any news or did you fix the problem?
    I wanted to post a few days after I check the stability of the PC but since you wrote here, I'll explain:
    So... after doing all the stuff mentioned in this thread, my PC was still getting a lot of BSoDs. So I sent my PC to a computer lab (just to give you a clue of the low hopes I had, my computer was 5 or more times sent to a lab, and they haven't found anything), and after a week of testing and checking, my computer returned to me with the result: no issues found. So at this point, I'm about to lose it. I turn on my computer, and something like 30-40 minutes passes, and I get a BSoD. Each time I turn it on again, the time between each crash is getting shorter and shorter, to the point that I can't access Windows nor it's automatic repair. I try to reinstall Windows, it crashes with the Driver_IRQL_Not_Less_Or_Equal error. I try using Linux Ubuntu, it freezes. Long story short, nothing works, the computer is a brick, I can only access the BIOS. The next day, I decided to plug my computer with different cables at a different place. Guess what? It worked like magic... So I bought new cables for the displays, an uninterpretable power supply, and connected the displays and the computer to it. It seems to work for now. If the problem is gone, I will mark this post as solved. So to summarize, the problem was either with the display cables, or the power supply cables.
      My Computer


  10. Posts : 926
    Windows 10 Pro
       #20

    This is Strange, but everything is possible. I say, if the problem doesnt occur again, something was strange with the monitor cables. As I wrote before, something was odd when I saw those 75 Hz. This probably caused the graphics card driver crash. Actually logical or? I would not have come to such a simple thing. Well done
      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 04:14.
Find Us




Windows 10 Forums