BSOD whenever gaming, errors 0x000000d1 & 0x0000001e

Here's a thread in which this problem was addressed on Tom's Hardware (it led me here.)

Forum used earlier: Multiple Errors Causing BSOD on Windows 10 - Windows 10

Dump Files: Attachment 107031

I play Battlefield 1 (now!) [BF1] and Rainbow Six Siege [R6S] pretty regularly. I used to have BSOD issues with R6S pretty regularly, but now I don't have them except for once and a while, so I got a bit lazy; but, now that BF1 is out, I have a BSOD, on average, every 5 minutes or so (in game, of course, not outside.)

Colif (the guy who helped me out on the other forum) said that the issues were all driver related (at the time.)

Thanks!

Attachment 108027


8 November BSOD:

Attachment 109314

Attachment 109327

The only problem I see is in one of the dumps and point to rtwlane_13.sys

Code:

ffff8b00`e23f4778  fffff808`1643c120Unable to load image \SystemRoot\System32\drivers\rtwlane_13.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rtwlane_13.sys
*** ERROR: Module load completed but symbols could not be loaded for rtwlane_13.sys
 rtwlane_13+0x3c120

This belongs to Realtek RTL8192CE Wireless LAN 802.11n PCI-E NIC.

I'm not having any luck finding a newer driver for it. See if you can. If yes, install it and see if that fixes the problem.

All the most recent dumps show a Bugcheck: D1:

Code:

BugCheck D1, {0, d, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+247

The dump from 10/28 at 8:17PM is similar but points to your Nvidia card/driver:

Code:

BugCheck D1, {ffffcc8cbc9767ba, 9, 0, fffff80eb56cadb4}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+dadb4 )

You can try some of the older Nvidia drivers, see if they work any better for you. The latest ones are definitely buggy.

================================================================
Remove and install latest Nvidia drivers:

I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

Then do a custom install of only the NVidia graphics driver and the PhysX driver.

See if that gets rid of the problem.
================================================================.

If that doesn't help see what enabling Driver Verifier shows us:

===================================================
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 will 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 BSOD with a mini dump that will tell us what driver caused it.

I followed the instructions, but the first thing did nothing, and the second didn't work because it ended in my having to go back to a system restore (infinite loop of bsods), so none of the information could be salvaged. I'm totally lost, and I still get bsods whenever I game :(

To be honest, I think it is driver conflicts, but I can't tell how to fix it...

the first thing did nothing - You followed the instructions (DDU then install latest Nvidia driver) and it made no difference or you were not able to use DDU or install new driver?

With a boot BSOD loop while verifier is active, pretty much means a significant driver problem.

You have some very old drivers on your computer:

Code:

2007/02/06 18:15:34   C:\WINDOWS\system32\drivers\AseUSBCC.sys
2008/09/24 14:28:20   C:\WINDOWS\system32\drivers\SiSRaid2.sys
2008/10/01 17:56:04   C:\WINDOWS\system32\drivers\sisraid4.sys
2010/02/18 10:17:53   C:\WINDOWS\system32\drivers\amdiox64.sys
2010/03/29 13:31:16   C:\WINDOWS\system32\drivers\tinspusb.sys
2010/04/07 14:56:42   C:\WINDOWS\system32\drivers\amdsata.sys
2010/04/07 14:56:44   C:\WINDOWS\system32\drivers\amdxata.sys
2011/04/11 14:48:16   C:\WINDOWS\system32\drivers\iaStorV.sys
2012/06/13 07:25:48   C:\WINDOWS\system32\Drivers\EtronSTOR.sys
2012/07/17 23:15:00   C:\WINDOWS\system32\drivers\asahci64.sys
2012/07/20 03:15:46   C:\WINDOWS\system32\Drivers\EtronXHCI.sys
2012/07/20 03:15:52   C:\WINDOWS\system32\Drivers\EtronHub3.sys
2012/10/22 22:10:38   C:\WINDOWS\system32\drivers\lvbflt64.sys
2012/10/22 22:11:24   C:\WINDOWS\system32\DRIVERS\lvrs64.sys
2012/10/22 22:12:08   C:\WINDOWS\system32\DRIVERS\lvuvc64.sys
2012/11/26 19:02:51   C:\WINDOWS\system32\drivers\stexstor.sys
2012/12/11 16:21:44   C:\WINDOWS\system32\drivers\amdsbs.sys
2013/01/21 14:00:28   C:\WINDOWS\system32\drivers\vstxraid.sys
2013/03/15 19:39:38   C:\WINDOWS\system32\drivers\lsi_sss.sys
2013/03/26 17:36:54   C:\WINDOWS\system32\drivers\HpSAMD.sys
2013/05/09 04:50:45   C:\WINDOWS\system32\drivers\AsrRamDisk.sys
2013/05/30 11:16:33   C:\WINDOWS\system32\DRIVERS\LGSHidFilt.Sys
2013/06/03 18:02:39   C:\WINDOWS\system32\drivers\megasr.sys

You may want to consider backing everything up then doing a Clean Install of Windows 10. That should get rid of most of the old drivers and may resolve your problem.

Follow this tutorial: Windows 10 - Clean Install

I decided to just go for the clean install by putting an install on a thumb drive and trying to load it up. I do not know why, but I get the same IRQL errors as before, but this time within the first 1 to 5 minutes of having started up. I thought the computer got rid of the drivers, but instead, I still get the BSODs. I cannot give any specific information about the BSODs, but I imagine that they are related to the old ones.

I am totally stuck. I will try to install Windows 10 again from the boot drive, but, unless I edit this later with new information, my computer is a brick, more or less.


Update:

One thing led to another and I decided to try Windows 7. It doesn't crash as quickly, but it still freezes. Even still, I don't understand why it would crash with so few drivers (for Windows 10 there were none.)


Second Update:

I thought for a bit that the reason that my computer might be freezing up is because of the GPU or the Network card, but, after loading up Windows 7 completely fresh with NOTHING added to it whatsoever, it still will just crash. No drivers or anything. Nothing. It just freezes up forever.

So where are you now, Win 7 or Win 10?

Try the latest Nvidia driver, 375.76. Last I saw you had 375.70. Use DDU as I showed before.

What is plugged into your computer?
Do you have any additional internal hardware?

I can't read the msinfo output as it's in German.

For Windows 7, I can potentially download things, but trying to launch a game will result in the system permanently freezing and windows update does not work. The only two drivers installed are one for my network card and the other being the latest nvidea drivers.

As for additional things plugged in, the only additional hardware is the mouse and keyboard.

I should also add that the freezing does not, unfortunately, save any information about why the crash occurred. There is no dump file from what I can tell and there is also no blue screen, just a permanently frozen monitor and an equally frozen keyboard.

Thankfully, my copy of Windows 7 is in English :)


Update:

I successfully got windows update to work, but the net framework refuses to install as of now. I'm trying to get that resolved.


Update 2:

Okay, so now my computer pretty much freezes up extremely quickly and seemingly at random. I'm not sure if this is a matter of software fixes or simple hardware.

What happens if you boot to Safe Mode with Networking?