[SOLVED] BSOD | DPC WatchDog Violation

[Subham2]

Recently, I have been having these BSOD.
From my little troubleshooting I found this from the event manager

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff80773573358). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 93ece01b-4d94-4138-963b-b2c002f547ad

P.s I tried to read the dump file but it was futile, I couldn't understand anything and how do I remove windbg? Do I just uninstall it through Settings or Do I have to do something else?
Ps. These BSOD previously only used to happen when waking the PC from sleep but this time it happened randomly.

The memory.dmp File Here: https://we.tl/t-tuPpiopnPB
The minidump here: https://we.tl/t-A0GCDu3JMz

 

[gardenman]

Hi, I ran the mini dump file through the debugger and got the following information: https://driftiermain.htmlpasta.com/

File information:	061520-31578-01.dmp (Jun 14 2020 - 14:42:15)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: msedge.exe)
Uptime:	1 Day(s), 11 Hour(s), 44 Min(s), and 56 Sec(s)

Unfortunately I don't have the time to download the memory.dmp now. At 1.8 GB, it would take me about 2 hours. But maybe someone else will want to review it so leave the link there.

Possible Motherboard page: https://www.asus.com/us/Motherboards/B85MG/
There is a BIOS update available for your system. You are using version 2001 and the latest is 3602. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Edit: How to remove WinDbg depends on which version you have. If it's the one from the Windows Store then you should be able to use the Windows Store or Control Panel to remove it. If it's one of the older ones then you can uninstall the Windows Software Development Kit from the Control Panel (if you are not using it for anything else). Also, the older debugger itself is only 30 megabytes or so and you can just leave it alone. Also after you remove it you might want to remove the C:\ProgramData\dbg folder which will have the symbols cache in it.

 

[Subham2]

Hi, I ran the mini dump file through the debugger and got the following information: https://driftiermain.htmlpasta.com/

File information:	061520-31578-01.dmp (Jun 14 2020 - 14:42:15)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: msedge.exe)
Uptime:	1 Day(s), 11 Hour(s), 44 Min(s), and 56 Sec(s)

Unfortunately I don't have the time to download the memory.dmp now. At 1.8 GB, it would take me about 2 hours. But maybe someone else will want to review it so leave the link there.

Possible Motherboard page: https://www.asus.com/us/Motherboards/B85MG/
There is a BIOS update available for your system. You are using version 2001 and the latest is 3602. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Edit: How to remove WinDbg depends on which version you have. If it's the one from the Windows Store then you should be able to use the Windows Store or Control Panel to remove it. If it's one of the older ones then you can uninstall the Windows Software Development Kit from the Control Panel (if you are not using it for anything else). Also, the older debugger itself is only 30 megabytes or so and you can just leave it alone. Also after you remove it you might want to remove the C:\ProgramData\dbg folder which will have the symbols cache in it.

Thank You for replying and sorry for replying late.
Yes, that's the correct motherboard.
Ok will wait for further updates before updating the BIOS
and I think I will keep WinDBG for now at least maybe I will get to it learn it someday well hopefully.

 

[PC Tailor]

Hello there! Thanks as always @gardenman for the debug (I can see the new link too!)

@Subham2

Just some initial pointers:

DPC Watchdog violation is generally a software issue, your "parameter 1" of your bugcheck is a 0 which indicates usually that it was a single DPC exceeded it's allotted time slot. This usually means it can be easier to diagnose.

So what I can see in your dump file:

STACK_TEXT:
fffff807`775eeb30 fffff807`8068ba1c : ffffb488`1a08b000 ffffb488`18600000 fffff807`775eed08 00000000`00000002 : nt!KeAcquireSpinLockRaiseToDpc+0x87
fffff807`775eeb60 fffff807`804760cd : 00000000`00000000 fffff807`6f46bf00 00000000`00000000 fffff807`775eebc8 : rtwlanu_oldIC!PlatformAcquireSpinLock+0xb0
fffff807`775eeb90 fffff807`8049b724 : ffffb488`1a08bd58 ffffb488`1ac00000 ffffb488`1845d268 ffffb488`11510540 : rtwlanu_oldIC!N6CSendSingleNetBufferListTimerCallback+0x49
fffff807`775eebc0 fffff807`76a3e788 : ffffb488`184438f8 00000000`00000000 ffffb488`1a0bb670 ffffb488`1845f1a0 : rtwlanu_oldIC!ndis6TimerCallback+0x94
fffff807`775eebf0 fffff807`730506ea : fffff807`6f46bf80 fffff807`775eed40 00000000`00000000 fffff807`775eee70 : ndis!ndisMTimerObjectDpc+0xd8

The important bit here is the rtwlanu_oldIC! bit. This is your Realtek WLAN Wireless USB 2.0 Adapter driver and appears initially to be the item causing the issue. So I would advise the following:

• See if you can update the driver from here: https://www.realtek.com/en/downloads
• Following that if you are using a USB adapter, it could be worth removing it and disabling the driver to see if the issue persists.

 

[Subham2]

OMG!!
I upvoted your posts because I was impressed by your style of helping the other poster and how helpful, patient, thorough and kind you where. Not only where you helping, you were also explaining everything along with it.

I didn't expect you to look up my Thread and help me as well.
You are on an another level my friend.
My respect for you has skyrocketed.

I wish you Good Health and hope you keep helping others the way you are doing.

Thank You!!

Just some initial pointers:

DPC Watchdog violation is generally a software issue, your "parameter 1" of your bugcheck is a 0 which indicates usually that it was a single DPC exceeded it's allotted time slot. This usually means it can be easier to diagnose.

"Sigh of relief" It's nice to hear that it is atleast easier to diagnose.

The important bit here is the rtwlanu_oldIC! bit. This is your Realtek WLAN Wireless USB 2.0 Adapter driver and appears initially to be the item causing the issue. So I would advise the following:

• See if you can update the driver from here: https://www.realtek.com/en/downloads
• Following that if you are using a USB adapter, it could be worth removing it and disabling the driver to see if the issue persists.

Thanks! Will try updating and removing the USB adapter and see what happens.

Ps. This issue usually occurs while trying to wake up from sleep mode but the 2 times it occurred outside of that was while turning on the wi-fi. I had lost all hope of ever fixing this issue but lo and behold you came like an angel.

 

[PC Tailor]

Whilst I am glad I can help, steady on! I'm a BSOD student in learning at the moment. It just appeared that this one is one I may be able to shed some more light on. And just because it should be easier, doesn't always mean it is. Either way, I'm glad I'm helping in some way.

It just so happens that the dump file you provided appears to give some useful information leading to my comment above, and hopefully, it should be the answer to the issue.

Either way, don't worry, we can resolve it, we just have to work our way to the answer. Let us know how it goes and if you encounter any more BSOD, post the dump files again but do so as per these instructions using the Sysnative file app; https://www.sysnative.com/forums/th...ing-instructions-windows-10-8-1-8-7-vista.68/

 

[Subham2]

Whilst I am glad I can help, steady on! I'm a BSOD student in learning at the moment. It just appeared that this one is one I may be able to shed some more light on. And just because it should be easier, doesn't always mean it is. Either way, I'm glad I'm helping in some way.

It just so happens that the dump file you provided appears to give some useful information leading to my comment above, and hopefully, it should be the answer to the issue.

Either way, don't worry, we can resolve it, we just have to work our way to the answer. Let us know how it goes and if you encounter any more BSOD, post the dump files again but do so as per these instructions using the Sysnative file app; https://www.sysnative.com/forums/th...ing-instructions-windows-10-8-1-8-7-vista.68/

Oooh Nice!

Hopefully this would be easy.

I will let you know and I will follow Sysnative instructions if there is any further BSOD.

 

[PC Tailor]

Oooh Nice!

Hopefully this would be easy.

I will let you know and I will follow Sysnative instructions if there is any further BSOD.

Also could I ask that you refresh the link to your dump files? The current ones have expired

 

[Subham2]

Also could I ask that you refresh the link to your dump files? The current ones have expired

Ahh Sorry for replaying late

Unfortunately I can't find the dump files anymore. 😢
Does Windows Update clean them up?

 

[Subham2]

@PC Tailor

AND
Good News
haven't seen any BSODS anymore.
Sleep mode is usable again.

Thank You so much for the help.
You saved my PC.

 

[PC Tailor]

Good News
haven't seen any BSODS anymore.

Really glad to hear it! And thanks for looking for the dump files again, but no worries if you can't find them anymore!

Let us know if anything does occur, but if you are happy, please select a best answer /solution for this thread (how to do is in my signature below - basically click the trophy icon) so that others visiting the forum can see the answer and see the thread is solved.