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

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[/quote]
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.

 

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

 

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.

 

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.

 

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

 

Debugging of the memory.dmp displayed
nvlddmkm
storport
storachi
tcpip
netio
Intelppm


Code: ffffc181`0b2fc458 fffff80e`f8361043 intelppm!PerfReadWrappingCounter+0x33[/quote] intelppm.sys Intel Processor driver Drivers & Software also at
See if uninstalling the Intel driver using the control panel and reinstalling from Drivers & Software
has a favorable impact on the bsod.

 

when using dps like this:

dps ffffc1810b2f6000 ffffc1810b2fd000

You should just have a look at those line beginning with this string: ERROR: Module load completed but symbols could not be loaded for

Code: ffffc181`0b2fa288 fffff80e`f89d2ad7*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys[/quote]
Since the MEMORY.DMP has more information, and an bigger stack, you will find more lines like this (those u posted):

Code: ffffc181`0b2fbe38 fffff80e`f4fd64bd storport!RaidAdapterAcquireInterruptLock+0x31 ffffc181`0b2fbf08 fffff80e`f4fa6092 storahci!AhciFormIo+0x2d2 ffffc181`0b2f9bd8 fffff80e`f545a71d tcpip!AlepFillEdgeInterfaceRelatedFields+0x3cd ffffc181`0b2f97a8 fffff80e`f534e87d NETIO!MatchValues+0x16d ffffc181`0b2fc458 fffff80e`f8361043 intelppm!PerfReadWrappingCounter+0x33[/quote]
but U can ignore those at first. Just have a look at those with

Module load completed but symbols could not be loaded for xxx.sys

When using !irp look at the lines begginning with:

\driver\xxx

And line beginning with "Probably caused by":

Probably caused by : xxx.sys


Those three strings u have to look for!