Windows 10: DPC Watchdog Violation/Freezing and Audio Loops

Windows isn't changing the driver that I downloaded from Asus's site, the same one is just showing up right after I reboot or if I uninstall it and try to install the one from Asus. It doesn't matter whether I'm disconnected from the internet or not, if I uninstall it, it just shows up again. I've been downloading the latest driver they have so maybe I'm at fault in some way here. I'm going to try rolling back.

And aren't those driver programs bad? I read up on them and most of them seem like scams designed to scare people into purchasing the product or having some subscription. Also they apparently cause more harm than good in the cases I've read by installing the wrong drivers or coming with their own viruses and other garbage programs that take up space. I've already used DriverEasy long before I made this thread anyhow and it was no help whatsoever.

 

Yeah I have the same impression as you and have never used them. It was the threads in other forums that use drive easy and others when they had no better alternatives.

 

This situation tells me that you have files in your C:\Windows\INF directory that are telling the OS which drivers to install and it is happening as soon as you boot up. If you look in that directory you will see various *.inf files for many of the devices attached to your PC. There may even be a rtwlane.inf file. Try moving this file to somewhere else to stop it working.

You could also look in the C:\Windows\System32\Drivers directory and remove the rtwlane.sys file if it is there.

Doing this should prevent the same driver being reinstalled and enable you to load the driver you want.

As you are playing around in the system files you should make sure you have restore points and system backups in place in case anything goes wrong. Let me know if you need directions for restore points or backups but there are plenty of tutorials that cover these areas.

 

@philc43 So I should just move the file, not delete it?

Also, I tried downloading the latest driver for the Lan PCI-E whatever and I'm still getting BSODs.
To test out if I'll get a BSOD or not I just let an hour long stream go on my computer while I did something else.
It only got 39:51 in before BSOD'ing.
I wanted to see if maybe there was a difference between downloading it directly from Asus and Realtek but the results the same for me, I guess.

I'll try rolling back while also doing what you suggested.

DM Log:
https://5.lithi.io/qc6zUJ.zip
@zbook
Do these Event Viewer and WhoCrashed things help anything really?
I want to hope they help or mean something at least.
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 7/2/2017 3:12:20 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\070217-31062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800BF475348)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 7/2/2017 3:12:20 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: rtwlane.sys (rtwlane+0x306C4)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800BF475348)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\rtwlane.sys
product: Realtek PCIEWireless LAN PCI-E NIC
company: Realtek Semiconductor Corporation
description: Realtek PCIE NDIS Driver 52611 27170
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtwlane.sys (Realtek PCIE NDIS Driver 52611 27170, Realtek Semiconductor Corporation ).
Google query: Realtek Semiconductor Corporation DPC_WATCHDOG_VIOLATION

 

The advantage of moving it is that you can put it back again if you make a mistake.

 

I cut the rtwlane.sys file out of where it originally was and just put it in my desktop for the time being.
So now I can just uninstall the realtek stuff with the device manager and it should work, right?
Ideally speaking.

 

Still no good, I moved the sys file out onto my desktop yet the moment I tried installing this:



The same drivers just came back. I'm pretty sure Qualcomm Atheros and Realtek aren't the same thing so I guess Windows can still bring back these same drivers no matter how many times I uninstall them and delete all their data.

I tried just about all the ones here and still I get the same one.




This same driver keeps popping up no matter what I do.
The PCIE GB Family Controller thing comes along with it as well.

I will be really bummed out if I have to reinstall Windows on this computer. I hate getting back all my backed up stuff. Not to mention Windows will probably just force me to update to this same broken update and put me back in the same situation. I don't want to have to speak to a support person on the phone about this because I really don't believe they'll be of any help either.

 

I think I would have chosen the next one down on the list, your MB is not the Kabylake.

 

Well, I downloaded the "Wireless Driver for M32CD"
And to my confusion it looks just like the one I already had....Which is what I'm assuming because absolutely nothing has changed. Either Realtek loves the name of this thing or Windows really enjoys putting me over a barrel with this constant magical reappearance of this driver after I uninstall it.
I guess I'll just let some YouTube videos play for a bit and come back to see if it blue screens within a few hours.
Hopefully this one rollback finally made the difference...or maybe I'm wasting my time.

 

Hi Carnival,

Lets hope it has made a difference. You have to dig a bit deeper in Device Manager to actually see if the driver has changed.

Let me show you the screens for my Network driver:

Attachment 142209

Double-click and select the driver tab to show this:
Attachment 142210

Click the driver details button to show the driver details:
Attachment 142211

 

@philc43




Here you go, there are no obvious changes like a name change or something so I'm a bit lost on how to dig deeper into this.

I'm not sure if this means anything but apparently what I downloaded is from 2015:



My drivers were up to date last time I checked but hey, no reason to still not check, better safe than sorry.

 

I've been letting YouTube videos play since 5:32 PM and nothing has happened yet.
It's way too early to say it's fixed since it likes to act up when I least expect it.
Things have been good so far though.

 

Well, I've been letting videos just play for about 8 or 9 hours now, I think I'm kind of sure it's fixed even though it'll probably show up again when I least expect it. I had to move all the way back to 3 years ago to get a good driver that wouldn't make just watching videos on YouTube a BSOD worthy decision. Wow. Just to make sure, that reg file that someone uploaded before it's absolutely sure to make sure that Windows doesn't try to package anymore driver updates along with it whenever it tries to update? I really don't need to go through something like this again.
Someone should really tell the people at Microsoft that there is something wrong with this latest update...assuming I didn't just mess up my driver somehow even though I never go poking around with my driver files.

But things have been going good so far so I can (finally) sleep a little bit easier now. I appreciate the help so far @zbook and @philc43 . I say so far because I might end up back here within a week or so, so please keep the thread open in case this all goes downhill for some reason. You guys are really patient and helpful.

Oh, and what do I do with that rtwlane.sys file just sitting on my desktop? Do I put it back now? I really don't want to end up back here again complaining if I do it and something goes wrong.

 

You may find that major W10 updates will cause the wrong driver to be loaded again. At least you now know how to select the older one and it should be a simple job to restore. *Smile

 

You can safely delete that file off your desktop now.

Please let us know if the older Realtek driver is working OK for you. A lot of recent posts have been about this type of BSOD and so anything you can share of your experience in fixing it will be appreciated.