BSOD when watching youtube videos (DSP_WATCHDOG_VIOLATION)

I have been getting BSOD with stop code DSP_WATCHDOG_VIOLATION. It has happened 7 times in the past 2 weeks, all of them occur when I am watching a youtube video. My computer will completely freeze for about 5-10 seconds while a video is playing and then BSOD will occur. I have attached the output of the script. Thanks!

Attachment 146383

Hi wanderyonder ,

There were 7 bsod mini dump files submitted and all were bug check 131.
They all indicated that the Realtek wireless LAN driver was the misbehaving driver.
This driver unfortunately has been a very common source of bsod with Asus laptops over the last few months.
Initially updating the driver produced bsod.
Rolling back the driver was a fix until just recently.
So now it is trial and error.
There was corruption noted on the drive.
There were problems noted in the event log for TPM.

Open the Asus website and enter your computers serial or product number.
Then see the available drivers for windows 10.
Post all of them into the link.
Then see if there are additional drivers for changing the windows operating system to windows 8.1 or 7.0
Post any Asus approved driver approved for your computer's configuration.
Then open the Realtek website. And again view all available drivers for your computers configuration. Include windows 10, 8.1, 7.0
Once you have all of the drivers posted into the link it will be trial and error.
Again the roll back has worked until very recently so if you want to try that first you can do that.
This is the method:
1) open device manager
2) expand network adapters
3) identify Realtek wireless LAN 8
4) right click on the driver and click properties
5) click on the driver details
6) make sure that you see rtwlane.sys
7) close this window and go back to the previous screen and click rollback driver.
8) reboot and wait to see if you get another bsod
You now know the problem driver.
The question is which driver version and from which source (Asus or Realtek) will work without bsod with your computer's configuration.
Again this has been one of our most frequent bsod drivers over the past few months. If you can communicate with both Realtek and Asus that may lead to a better driver or a quicker solution.
9) Open administrative command prompt and type or copy and paste:
10) sfc /scannow
11) dism /online /cleanup-image /restorehealth
12)When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
13) chkdsk /x /f /r
14) Run HDTune on all drives to
check the health,
scan for errors, no quick scan but full scan
run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark including the following:
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials


Windows Trusted Platform Module Management Step-by-Step Guide

Code:

{Registry Hive Recovered} Registry hive (file): '\??\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\WINDOWS\System32\config\DRIVERS' was corrupted and it has been recovered. Some data might have been lost.

Code:

{Registry Hive Recovered} Registry hive (file): '\??\Volume{21a1aa2b-6a18-4e2d-8777-dc20da122f18}\System Volume Information\SPP\SppCbsHiveStore\{cd42efe1-f6f1-427c-b004-033192c625a4}{237E6FAA-63DA-49AC-9986-87B711966EB5}' was corrupted and it has been recovered. Some data might have been lost.

{Registry Hive Recovered} Registry hive (file): '\??\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\WINDOWS\System32\config\DRIVERS' was corrupted and it has been recovered. Some data might have been lost.

Code:

The Trusted Platform Module (TPM) hardware on this computer cannot be provisioned for use automatically.  To set up the TPM interactively use the TPM management console (Start->tpm.msc) and use the action to make the TPM ready.Error: Authentication failed.

Code:

The Trusted Platform Module (TPM) hardware on this computer cannot be provisioned for use automatically.  To set up the TPM interactively use the TPM management console (Start->tpm.msc) and use the action to make the TPM ready.Error: Authentication failed.

Code:

The Trusted Platform Module (TPM) hardware on this computer cannot be provisioned for use automatically.  To set up the TPM interactively use the TPM management console (Start->tpm.msc) and use the action to make the TPM ready.Error: Authentication failed.

Code:

The Trusted Platform Module (TPM) hardware failed to execute a TPM command.

Code:

The driver detected a controller error on \Device\Harddisk1\DR1.

Code:

7/22/2017 8:03 AM    Windows Error Reporting    Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: ea032c20-fa3b-4262-963e-c619621410c7

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff800b7a7a348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\072217-30421-01.dmp
\\?\C:\Windows\Temp\WER-59984-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCCB1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD02C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1A4.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_294ababdb3e9b4b3da46ffa07cd990cf6421f44b_00000000_cab_06b60b9e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 4b7a27c1-9efa-44a6-9329-9acdba8726d7
Report Status: 268435456
Hashed bucket:7/29/2017 11:58 PM    Windows Error Reporting    Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: c847904c-ee19-4a68-af55-0c50e166d32a

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff802473ed348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\072917-23906-01.dmp
\\?\C:\Windows\Temp\WER-109234-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER284E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C17.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C47.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_b6ae8afb3af089683ca5c2b715421e26248e9be1_00000000_cab_17c65c8d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 865f4387-0580-4a22-95d9-7542a349fa8a
Report Status: 268435456
Hashed bucket:7/9/2017 3:24 AM    Windows Error Reporting    Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: c2291937-238e-4660-842f-b347ef963181

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff802649f5348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070817-26500-01.dmp
\\?\C:\Windows\Temp\WER-180531-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DCC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F14.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F63.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_31e9d6a0fe41ac3c824e708e4ad6a3bf42e865_00000000_cab_235bab83

Analysis symbol: 
Rechecking for solution: 0
Report Id: dc1bb6f3-ec3f-4c3c-8805-41f982fd43fa
Report Status: 268435456
Hashed bucket:7/18/2017 8:25 PM    Windows Error Reporting    Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 955a842a-f1c8-4b87-9ac6-4400c1ecfe10

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff80059a64348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\071817-31046-01.dmp
\\?\C:\Windows\Temp\WER-149062-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREDD2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF78.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREFD7.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_96a7f3e11d1b6db1752fafc8870d18a7175390_00000000_cab_2b1f8328

Analysis symbol: 
Rechecking for solution: 0
Report Id: 664e650f-2f06-4209-93ce-f3f2be7f0e8c
Report Status: 268435456
Hashed bucket:7/9/2017 1:47 AM    Windows Error Reporting    Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 4a1b8d47-1b1f-4dce-ba64-380b9adb56d2

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff8018926e348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070817-49968-01.dmp
\\?\C:\Windows\Temp\WER-79375-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6E2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD78E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD7DD.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_8e23fce81748854996ecc227642826be950b0c8_00000000_cab_039a0a95

Analysis symbol: 
Rechecking for solution: 0
Report Id: a97e845d-c831-42f4-89d1-1f5f9edcbc95
Report Status: 268435456
Hashed bucket:7/9/2017 3:46 AM    Windows Error Reporting    Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 231229ba-d44d-4888-9370-2ef6d2a25f0e

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff801c65e2348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070817-28328-01.dmp
\\?\C:\Windows\Temp\WER-146750-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER103D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1195.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER11C5.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_1f56fb84f5cb99ad38f1563c75329cbf1fcf5b_00000000_cab_0ddf59d9

Analysis symbol: 
Rechecking for solution: 0
Report Id: 40a59290-9cba-47d3-8458-d4fb0440aff1
Report Status: 268435456
Hashed bucket:7/9/2017 12:35 AM    Windows Error Reporting    Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 09806c4d-91ac-47e9-a21f-dd43104154d1

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff800265fb348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070817-51031-01.dmp
\\?\C:\Windows\Temp\WER-106546-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD346.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD347.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD3A6.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_8e7c9386f7a3cb49207563f10ecb2bfc5d92a10_00000000_cab_330515ce

Analysis symbol: 
Rechecking for solution: 0
Report Id: dcffeb29-92e6-4b0f-b882-88c1cb474f0c
Report Status: 268435460
Hashed bucket:

Code:

+++ WER8 +++:Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0Event Name: BlueScreenResponse: Not availableCab Id: ea032c20-fa3b-4262-963e-c619621410c7Problem signature:P1: 133P2: 0P3: 501P4: 500P5: fffff800b7a7a348P6: 10_0_15063P7: 0_0P8: 768_1P9: P10:

Code:

RTWlanE      Realtek Wireless LAN 8 Realtek Wireless LAN 8 Kernel        Manual     Running    OK         TRUE        FALSE        4,096             3,551,232   0          5/17/2017 10:17:33 PM  C:\WINDOWS\system32\drivers\rtwlane.sys

rtwlane.sys

Realtek PCI-E Wireless LAN NIC NDIS Driver

http://www.realtek.com.tw/downloads/...Level=4&Conn=3

Code:

BugCheck 133, {0, 501, 500, fffff802649f5348}*** WARNING: Unable to verify timestamp for rtwlane.sys*** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys
Probably caused by : rtwlane.sys ( rtwlane+30918 )

It must not be overdone!

Thank you for your thorough response zbook! I contemplated whether or not I should rollback the driver because the previous driver had lots of its own issues (would always disconnect spontaneously). In the last few days, however, I haven't noticed any issues and haven't gotten a BSOD. I may just leave it be for the time being unless the issue comes back again. If it does I will contact Asus/Realtek as you recommended. Thanks again!

Which method did you use to fix the driver?
Update, rollback, or reinstall?
Were your steps only using device manager or did you download from the Asus website?
Please post a new zip: BSOD - Posting Instructions - Windows 10 Forums

Sorry, I was not clear in my last post! While I looked into both rolling back the driver in Device Manager and downloading the driver from Asus, but I *did not do either of those things*.

I ultimately decided not to change the driver because the issue hasn't been happening anymore for some reason. I will update once again if the issue comes back!

That's ok.
You can perform the preventative maintenance or wait for problems.
For the preventative maintenance:
See post #2 for operating system, and drive testing: steps 9 - 14

Another option is to run windows driver verifier to find misbehaving drivers.
Windows driver verifer is a tool that will repetitively produce bsod creating mini dump files.
The mini dump files are then debugged to find misbehaving drivers.
The drivers are then updated, uninstalled and reinstalled, or rolled backed.
Once there are no more bsod windows driver verifier is run for 36 hours of typical computer use.
If there are no more bsod during the 36 hours the troubleshooting will be complete.
The fixes will have been completed and preventative maintenance will be completed.

I was having the same issue with my Asus laptop when I stumbled upon this post from Google. Other common fixes were to update all my drivers and a bunch of silly things that didn't work (verifying my memory, removing fast start up, etc.)

Rolling back the realtek wireless lan driver to driver date 10/14/16 fixed my issue. Thanks!

Glad you got it fixed.
The roll back was suggested in post #2.
Let us know if you encounter any other problems.

Hi zbook,

Unfortunately the BSOD came back as you predicted. I rolled the Reaktek driver back to 10/14/16 as the previous user mentioned using Device Manager. However I quickly got 2 BSODs after just 10 minutes of using it (DRIVER IRQL NOT LESS OR EQUAL, rtwlane.sys failed)

I have performed the steps you listed in post #2, steps 9-14. Here is the copy/paste of the scan and 3 screenshots using HDTune 2.55. Thanks!

*****************************************************

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


************************************************************


Attachment 147915Attachment 147916Attachment 147917