Windows 8 BSOD DPC_watchdog_violation 0x133

averytare · Apr 14, 2013

Hello. I just built my new computer about 2 weeks ago and I have had random crashes every 2-3 days. It crashes while I'm just browsing the internet or playing games. Sometimes its a BSOD, sometime the screen freezes and the audio cuts out along with the monitor signal, and then sometimes the screen is just completely black yet I can still see my cursor and use the OS (opening task manager and hearing the sound).

computer specs:
Windows 8 x64 bit
Intel i5 3570k quad core
EVGA GTX 680 SC signature 2
Corsair vengeance LP 8 Gigs
Asus p8z77-v deluxe
PSU cooler master silent pro 850w
Samsung 840 pro SSD
WD black 1tb

Thanks for the help!

averytare · Apr 14, 2013

I would also like to say that WhoCrashed reported that this BSOD was likely to be caused by ntoskrnl.exe

jcgriff2 · Apr 15, 2013

Hi -

ntoskrnl.exe is the Windows NT Kernel and is listed in dumps as a default and is not the actual cause.

The sole dump had a bugcheck = 0x133 and named NVIDIA video

Your NVIDIA drivers are current -

Code:

nvlddmkm.sys        Thu Mar 14 21:37:00 2013 (51427B3C)

http://www.sysnative.com/drivers/driver.php?id=nvlddmkm.sys

This is likely a hardware issue given your description of black screen. I sit on the software side of the fence and will ask a hardware expert to look in on this thread.

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:


Debug session time: Fri Apr  5 16:18:48.659 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040513-5687-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 6:21:31.297
*** 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+18b286 )
BugCheck 133, {1, 780, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Bugcheck code 00000133
Arguments: 
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above. The offending component can usually be
	identified with a stack trace.
Arg2: 0000000000000780, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x133_ISR_nvlddmkm+18b286
MaxSpeed:     3400
CurrentSpeed: 3410
BiosVersion = 1805
BiosReleaseDate = 12/19/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Wrench97 · Apr 15, 2013

See this post you'll recognize most of the names there..... > Intermittent DPC Watchdog Violation BSODs occurring I think your looking at the same issue only with the video instead of the networking driver.

averytare · Apr 26, 2013

The issue is still not fixed however I found some information that may shed some light on what's wrong.

I used sfc scannow and it reported that some files in my computer may be corrupted however it wasn't able to fix the files.

I then used event log and found out that every time my computer crashed two errors appeared in the applications tab.

The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
&
The Open Procedure for service "BITS" in DLLWindows cannot load the extensible counter DLL rdyboost. The first four bytes (DWORD) of the Data section contains the Windows error code.

I tried researching how to fix this but came across nothing.

niemiro · Apr 27, 2013

Hello :)

It could be that some file detected by SFC is actually corrupt and is causing this problem. Let's find out for sure:

Export CBS folder

Click the Start button

then click Computer.
Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
Find and double click on the Logs folder.
Right-click on the CBS folder, and select Copy.
Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
A new file, also called CBS (CBS.zip), but this time with a different icon, will be created. Please upload it to your next post.

Thank you!

Richard

averytare · Apr 27, 2013

Thanks for the help but the CBS file is too large to upload (9.21MB)

However I found out after playing Torchlight 2 for about a hour that Action Center was reporting 19 errors.
All of the errors are kinda like this.

"Problem: Video hardware error

Files that help describe the problem:

WD-20130402-0613.dmp
sysdata.xml
WERInternalMetadata.xml"

niemiro · Apr 27, 2013

averytare said:
Thanks for the help but the CBS file is too large to upload (9.21MB)

However I found out after playing Torchlight 2 for about a hour that Action Center was reporting 19 errors.
All of the errors are kinda like this.

"Problem: Video hardware error

Files that help describe the problem:

WD-20130402-0613.dmp
sysdata.xml
WERInternalMetadata.xml"

Well, it does look like you might have a graphics card failure, or potentially graphics card driver problem, on your hands, but I am not the best person to advise you.

As for the CBS log, if you would like me to check it, did you zip it up as I said to in my instructions (zipping makes the file smaller), or is it too big even after zipping?

Thank you!

Richard

averytare · Apr 27, 2013

CBS folder before zip is 13.5 MB and then after is 9.21 MB.
Maybe I can just send you the text file inside the CBS folder or do you need the CAB files as well?

averytare · Apr 28, 2013

View attachment CBSlogInformation.zip

Well hopefully that's all you need. Uploaded just the log.

niemiro · Apr 28, 2013

This one needs the System Update Readiness Tool TBH.

However, at the moment, the primary focus should be on the BSODs, and I don't think that your SFC corruptions are the cause of your BSOD (although it is impossible to be absolutely sure). Hopefully someone else will be able to additionally advise you.

Richard

averytare · Apr 28, 2013

I really appreciate the help niemiro!

I ran the system update readiness tool in command prompt then re ran SFC scannow.
SFC scannow found no corruptions!

although Its too soon to say this was the root of my problem it was still a issue that has been fixed.
I guess the next logical step is to replace my GPU if the problem still occurs. I still have a question though.

can you explain these two errors that I found in event log?
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
&
The Open Procedure for service "BITS" in DLLWindows cannot load the extensible counter DLL rdyboost. The first four bytes (DWORD) of the Data section contains the Windows error code.

niemiro · Apr 29, 2013

That's great news with SFC! Unfortunately, I don't think it will be the root cause of your problem. It will have fixed Windows Update errors you didn't even know you had (they will only show themselves when Microsoft choose to update the actual components which were corrupt, they clearly haven't recently), however, I would not associate it with a BSOD problem.

However, can you please post your C:\Windows\Logs\CBS\CheckSUR.persist.log, just so I can make sure there are no more lingering problems?

Also, can you please download and run FSS: Farbar Service Scanner Download
putting a check in every box. I don't think this is the problem, but I want to check the simple stuff before digging deeper - it would be embarrassing to overlook the easy solution!

Thank you!

Richard

averytare · Apr 29, 2013

Here you go.

Search

Search

Windows 8 BSOD DPC_watchdog_violation 0x133

averytare

Member

Attachments

averytare

Member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Wrench97

Administrator, Hardware Expert

averytare

Member

niemiro

Senior Administrator, Windows Update Expert

averytare

Member

niemiro

Senior Administrator, Windows Update Expert

averytare

Member

averytare

Member

niemiro

Senior Administrator, Windows Update Expert

averytare

Member

niemiro

Senior Administrator, Windows Update Expert

averytare

Member

Attachments

Windows 8 BSOD DPC_watchdog_violation 0x133

Member

Attachments

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Administrator, Hardware Expert

Member

Senior Administrator, Windows Update Expert

Member

Senior Administrator, Windows Update Expert

Member

Member

Senior Administrator, Windows Update Expert

Member

Senior Administrator, Windows Update Expert

Member

Attachments

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)