Windows 10: DPC Watchdog Violation/Freezing and Audio Loops

Windows by default will install many drivers.
This feature can be turned off.
If the drivers were corrupt then replacing the driver with the identical one should work.
If the driver needs to be rolled backward or if there is other software that is conflicting in the computer environment this can be determined by what happens with time. If there are no more bsod then the misbehaving driver has been fixed. If there are more bsod it will require further troubleshooting.

 

I let some some videos play on YouTube while I was asleep to see if it would crash before I woke up and it did.
From the looks of it nothing really changed.

https://5.lithi.io/xzMYw0B.zip

Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 7/1/2017 12:07:27 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\070117-35453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF802055F1348)
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 Sat 7/1/2017 12:07:27 AM 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, 0xFFFFF802055F1348)
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



On Fri 6/30/2017 1:51:23 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-33328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF802539F1348)
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.




Conclusion
3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

rtwlane.sys (Realtek PCIE NDIS Driver 52611 27170, Realtek Semiconductor Corporation )

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Is there anyway I can find wireless lan drivers that work for an Asus M32CD that don't come from Realtek?
Or should I just rollback on the drivers I have?
And how would I stop the ntrokrnl thing from happening?

 

If @zbook does not mind me stepping in I would like to make the recommendation that you update the BIOS for your PC. There have been several improvements made to the BIOS and it is now at ver 0604 with several improvements for system stability. The ASUS manual should have details about how to do this.

 

@philc43 The ASUS manager allows me to update the BIOS, which is what the site that the manual redirected me to said to use.
I downloaded the latest BIOS update which is a .CAP file.









I tried browsing for the file in the manager and using it to update like that but it said the image didn't match the ROM I was currently using.





When I tried connecting to the server to find the BIOS update from the manager it said there were no critical updates needed.
I've never had to do this before and the manual or the site isn't really giving me much help. I don't want to do this incorrectly and end up not even being able to boot my computer or having to reinstall Windows or something.

 

OK, I would not want you to perform a risky operation so if you get the message that the file does not match then it is better not to proceed.

ASUS often provide alternative ways of updating such as doing it from within a DOS environment - I'm not sure if that is the case for your system. It might be that you need to contact ASUS to ask if they can explain what is happening.

 

I just looked again at the list of new BIOS files, there seem to be different versions depending on which MB you have. I think yours may require a different file (e.g. ver 1004 updated Jan 2017 if yours is a DDR4 MB or ver 0602 if a DDR3 MB).

 

Version 0602 worked, it came out 10/28/15. I was hoping to have something more around this year but hopefully that just means this version is so stable they haven't needed to update for a good while.



So what now, do I just do what I usually do and wait to see if it crashes again?
Also, I genuinely appreciate the help you guys, or rather, you two have been giving so far.

 

Yes, it would have been good if there was an even newer version but let's see if it helps. If you get another BSOD just post up a new set of logfiles and we will take a look.

 

@philc43 Well, 9 hours without a crash until now.
https://6.lithi.io/Fvs0e.zip




It really seems like no matter what I do I cannot get rid of this DPC watchdog issue. And it's the same reason for a crash every single time. This is really bumming me out. I hope if it comes down to me actually needing to call someone at ASUS that they actually help me or I won't need to just reinstall Windows.

What confuses me even more is that for a good 3 of those 9 hours I spent without crashes I was on a game in full resolution and on the highest possible settings with no issues, but the moment I decide to watch a video on YouTube it freezes up and crashes.

I looked in Event Viewer and pulled this up if it's any help:

 

Code: rtwlane.sys[/quote] rtwlane.sys Realtek PCI-E Wireless LAN NIC NDIS Driver http://www.realtek.com.tw/downloads/...Level=4&Conn=3
Code: 7/2/2017 3:33 AM Windows Error Reporting Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0 Event Name: BlueScreen Response: Not available Cab Id: ebfeca50-fc06-4d6b-b9f9-06e9cdd4846d Problem signature: P1: 133 P2: 0 P3: 501 P4: 500 P5: fffff80202df8348 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\070117-32312-01.dmp \\?\C:\Windows\Temp\WER-87812-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6A5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD4C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD6D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_a1c6cbb346a880eae0e1670e396c1355aa1b_00000000_cab_20a71fbb Analysis symbol: Rechecking for solution: 0 Report Id: 62d97053-228f-43ba-8251-31acaf55e7f1 Report Status: 268435456 Hashed bucket:[/quote] Windows error reporting and all three bsod minidmp file debugging indicate that rtwlane.sys is the misbehaving driver.


On the Asus web site enter your computers serial or product number and operating system and look for an Asus approved driver for wireless LAN. Download this driver to the desktop. Do not install it now.
If the Asus web site does not have an approved driver use the Realtek web site: Realtek

Disconnect your computer from the internet.

Open device manager and uninstall the Realtek PCI-E wireless driver.

place the computer in clean boot:
Open administrative command prompt and type or copy and paste these commands:

5) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)


6) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)


7) shutdown /r (you will reboot the computer so that it is in clean boot)


Install the driver that was downloaded to the desktop.

reboot.

Turn on wireless and connect to the internet.

 

I have seen more than one report that this is happening, it's too soon to be sure but I'm beginning to see a pattern that the latest rtwlane.sys is not working with the latest W10 update. Rolling back to an earlier driver seems to help for some people. See this thread for an example: BSOD watching videos on youtube, error Watchdog Violation.

You will need to find this driver in Device Manager and make sure it is rolled back or updated with an earlier version.

 

Whenever I installed the Wireless Lan driver before it says it's something like a Qualcomm Wireless Lan and Blutooth adapter yet for some reason the Realtek PCI-E NIS driver is the only one to show. It's like the Qualcomm driver is being replaced automatically with the Realtek one or like I was installing the Realtek PCI driver the whole time even if there was no update to Windows.



If I do this I should see just the Qualcomm driver and still be able to connect to the net, right?

Hopefully if this doesn't work I can system restore and just roll back on the driver and that finally works.

 

Drivers can be downloaded to the desktop. The computer can be disconnected from the internet. The driver(s) can be installed. Then the computer can be reconnected to the internet.
Alternatively you can prevent windows from automatically updating drivers.

 

Alright, I don't know why but my computer hates @zbook's method of fixing this issue, every time I try to uninstall the realtek lan PCI-E driver it reinstalls itself once I clean boot or if I just try to install another lan driver right after I uninstall it. I literally cannot do anything to stop it, it's like Windows is just built to reinstall these drivers automatically if you try to uninstall them. I even disabled Windows from doing stuff like that automatically, or at least I BELIEVED I did.

I'm just going to try and rollback on the drivers and see what happens.
EDIT: I looked at the link zbook provided and there's no link to earlier versions of the driver on the realtek site can someone provide a link to an earlier version from a reliable source?

 

When all else fails there is always the driver websites. On this forum some have used drive easy. They are supposed to provide one free driver. There may be better sites. I've not used any of them.

When you are disconnected from the internet how is windows changing the driver when you install the one that you downloaded to the desktop? Windows should not be able to make any changes unless you reboot.