Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Win 8.1 BSOD DPC_Watchdog_Vio


  • Please log in to reply
2 replies to this topic

#1 t0ggLe

t0ggLe

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:08:43 AM

Posted 02 June 2015 - 09:59 AM

· OS - Windows 8.1 Pro
· 64-bit
· Home Built, Original Win 8.1
· Purchased
· 1.5 yrs old
· 4 Days since wipe and fresh install

· CPU - i5-4670k
· Video Card - 2047MB NVIDIA GeForce GTX 770 (NVIDIA)
· MotherBoard - MSI-Z97-G45 Gaming
· Power Supply - Corsair - CX750m

· System Manufacturer - Me

 

Recently, after I moved back to Illinois (GF stayed in Cali for school and this is her computer), the computer started DPC_Watchdog_Violation BSODing. Typically happens when using browsers. Would Appreciate any info or help you guys could provide. I have done my research and and running into a roadblock so I now defer to the experts

 

Cpu is idling at ~30-35ºc

MB/SSD also around the same

Gcard is idling ~ 40ºc

 

I could not get perfmon to post the results via cmd - admin so it will not be in the attached file. Sorry =\

 

Thanks again guys!

Ryan

Attached Files


Edited by t0ggLe, 02 June 2015 - 10:00 AM.


BC AdBot (Login to Remove)

 


#2 t0ggLe

t0ggLe
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:08:43 AM

Posted 08 June 2015 - 09:13 PM

Update - been receiving driver failed to respond notices from nvidia drivers. Not sure if that helps at all but I am going to replace the graphics card with a spare to test.

#3 blueelvis

blueelvis

    Bleep Blop Bleep


  • Malware Response Team
  • 1,666 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:07:13 PM

Posted 09 June 2015 - 03:16 AM

Hi Ryan & Welcome to BC ^_^,
 
I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
 

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
 
According to the dump file, we see that the single DPC or ISR (Interrupt Service Routine) exceeded the time it was allotted to perform it's job. The amount of time allotted is highlighted in BLUE color.
Now, let's take a look at the stack and see if we can find the suspect -
1: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd000`2018dc98 fffff803`8d590c82 nt!KeBugCheckEx
01 ffffd000`2018dca0 fffff803`8d48daec nt! ?? ::FNODOBFM::`string'+0x1f6f2
02 ffffd000`2018dd30 fffff803`8db9ae5f nt!KeClockInterruptNotify+0x77c
03 ffffd000`2018df40 fffff803`8d4a6703 hal!HalpTimerClockInterrupt+0x4f
04 ffffd000`2018df70 fffff803`8d56252a nt!KiCallInterruptServiceRoutine+0xa3
05 ffffd000`2018dfb0 fffff803`8d56290f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
06 ffffd000`20108710 fffff803`8d4a62e0 nt!KiInterruptDispatchLBControl+0x11f
07 ffffd000`201088a0 fffff803`8d4a62a2 nt!KxWaitForSpinLockAndAcquire+0x20
08 ffffd000`201088d0 fffff800`01db5f83 nt!KeAcquireSpinLockRaiseToDpc+0x32
09 ffffd000`20108900 00000000`00000000 nvlddmkm+0xeff83
We see that the NVIDIA Driver was trying to acquire a spinlock but since it did not get it after some time, the DPC Watchdog which keeps track of such activity decided to crash the system.
 
If the system gets "Display Driver has failed to respond..." for like 5 times in a small interval, Windows decides to crash the system with the bugcheck which you are experiencing.
 
Kindly uninstall the currently installed NVIDIA Driver using the Display Driver Uninstaller from the below link -
 
 
Once the driver has been uninstalled, reboot the system.
 
After the reboot, try installing the driver from the Driver Disc which should have come with the GPU. If you cannot find that, try downloading an older version of the NVIDIA Driver and see if the crashes persist or not. In some cases, it has been observed that such kind of crashes are often resolved by installing the latest BETA Drivers from NVIDIA.
 
 
Let us know how it goes ^_^
 
-Pranav

Edited by blueelvis, 09 June 2015 - 03:17 AM.

Member of the Bleeping Computer A.I.I. early response team!


In case I have been helping you and you haven't received a reply from me in 48 hours, please feel free to PM me. Anything else? Still feel free to PM me :)

Did you read this? http://omgdebugging.com/5-tips-for-getting-the-best-bang-for-the-buck-at-fast-food-joints/




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users