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

Watchdog_Violation blue screen of death


  • Please log in to reply
9 replies to this topic

#1 godofsmoke

godofsmoke

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:13 AM

Posted 05 February 2015 - 05:34 AM

Hello,
So am i getting a problem while playing one game and its pretty scary, the blue screen of death with error message DPC_Watchdog_Violation. I cant get to solve it myself. Here is what i got out of the dump file but i dont know how read it, hope someone could help
p.s. sorry for the long text

 

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

Debugging Details:
------------------


DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff80325020ad6 to fffff80324fe0fa0

STACK_TEXT:
ffffd001`d9f93c98 fffff803`25020ad6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd001`d9f93ca0 fffff803`24f40f85 : 00000000`00000000 00000000`00000000 00000000`80000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2f626
ffffd001`d9f93d30 fffff803`24e257b5 : 00002830`00400a02 ffffe000`6d31f040 fffff800`6b85cab0 00000000`00007101 : nt!KeClockInterruptNotify+0x95
ffffd001`d9f93f40 fffff803`24f5c363 : ffffd001`d9f93f60 00000000`00000008 ffffd001`d9f93f50 00000000`00000010 : hal!HalpTimerClockIpiRoutine+0x15
ffffd001`d9f93f70 fffff803`24fe242a : fffff803`24e71d00 ffffd001`d9f84bb8 00000000`00000000 ffffe000`6d796000 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd001`d9f93fb0 fffff803`24fe280f : 00000000`00000000 00000000`00000004 00000000`00000000 00001600`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd001`d9f84990 fffff803`24f32c24 : ffffe000`6cc964bc ffffe000`6bcd17d0 ffffe000`6bc094c0 fffff803`24f86288 : nt!KiInterruptDispatchLBControl+0x11f
ffffd001`d9f84b20 fffff800`6cebc1d9 : ffffe000`6d796000 ffffe000`6bc094c0 ffffe000`6bc09050 ffffe000`6ca79c20 : nt!KxWaitForLockOwnerShip+0x34
ffffd001`d9f84b50 ffffe000`6d796000 : ffffe000`6bc094c0 ffffe000`6bc09050 ffffe000`6ca79c20 ffffe000`6c9af010 : igdkmd64+0x691d9
ffffd001`d9f84b58 ffffe000`6bc094c0 : ffffe000`6bc09050 ffffe000`6ca79c20 ffffe000`6c9af010 fffff800`6d2ce92d : 0xffffe000`6d796000
ffffd001`d9f84b60 ffffe000`6bc09050 : ffffe000`6ca79c20 ffffe000`6c9af010 fffff800`6d2ce92d 00000000`00000002 : 0xffffe000`6bc094c0
ffffd001`d9f84b68 ffffe000`6ca79c20 : ffffe000`6c9af010 fffff800`6d2ce92d 00000000`00000002 ffffe000`6cc9627c : 0xffffe000`6bc09050
ffffd001`d9f84b70 ffffe000`6c9af010 : fffff800`6d2ce92d 00000000`00000002 ffffe000`6cc9627c ffffe000`6bc091a0 : 0xffffe000`6ca79c20
ffffd001`d9f84b78 fffff800`6d2ce92d : 00000000`00000002 ffffe000`6cc9627c ffffe000`6bc091a0 ffffd001`00000001 : 0xffffe000`6c9af010
ffffd001`d9f84b80 ffffe000`6e79c830 : 00000000`00000000 ffffe000`6c36f000 00000000`05c40000 fffff800`6cf54824 : USBPORT!USBPORT_Core_QueueTransferUrb+0x22d
ffffd001`d9f84be0 00000000`00000000 : ffffe000`6c36f000 00000000`05c40000 fffff800`6cf54824 ffffe000`6beb8d01 : 0xffffe000`6e79c830


STACK_COMMAND: kb

FOLLOWUP_IP:
igdkmd64+691d9
fffff800`6cebc1d9 ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: igdkmd64+691d9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME: igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 548e644c

FAILURE_BUCKET_ID: 0x133_DPC_igdkmd64+691d9

BUCKET_ID: 0x133_DPC_igdkmd64+691d9

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_igdkmd64+691d9

FAILURE_ID_HASH: {23619fb7-eb93-c271-aeae-ffa1552675cb}

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

Debugging Details:
------------------


DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff80325020ad6 to fffff80324fe0fa0

STACK_TEXT:
ffffd001`d9f93c98 fffff803`25020ad6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd001`d9f93ca0 fffff803`24f40f85 : 00000000`00000000 00000000`00000000 00000000`80000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2f626
ffffd001`d9f93d30 fffff803`24e257b5 : 00002830`00400a02 ffffe000`6d31f040 fffff800`6b85cab0 00000000`00007101 : nt!KeClockInterruptNotify+0x95
ffffd001`d9f93f40 fffff803`24f5c363 : ffffd001`d9f93f60 00000000`00000008 ffffd001`d9f93f50 00000000`00000010 : hal!HalpTimerClockIpiRoutine+0x15
ffffd001`d9f93f70 fffff803`24fe242a : fffff803`24e71d00 ffffd001`d9f84bb8 00000000`00000000 ffffe000`6d796000 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd001`d9f93fb0 fffff803`24fe280f : 00000000`00000000 00000000`00000004 00000000`00000000 00001600`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd001`d9f84990 fffff803`24f32c24 : ffffe000`6cc964bc ffffe000`6bcd17d0 ffffe000`6bc094c0 fffff803`24f86288 : nt!KiInterruptDispatchLBControl+0x11f
ffffd001`d9f84b20 fffff800`6cebc1d9 : ffffe000`6d796000 ffffe000`6bc094c0 ffffe000`6bc09050 ffffe000`6ca79c20 : nt!KxWaitForLockOwnerShip+0x34
ffffd001`d9f84b50 ffffe000`6d796000 : ffffe000`6bc094c0 ffffe000`6bc09050 ffffe000`6ca79c20 ffffe000`6c9af010 : igdkmd64+0x691d9
ffffd001`d9f84b58 ffffe000`6bc094c0 : ffffe000`6bc09050 ffffe000`6ca79c20 ffffe000`6c9af010 fffff800`6d2ce92d : 0xffffe000`6d796000
ffffd001`d9f84b60 ffffe000`6bc09050 : ffffe000`6ca79c20 ffffe000`6c9af010 fffff800`6d2ce92d 00000000`00000002 : 0xffffe000`6bc094c0
ffffd001`d9f84b68 ffffe000`6ca79c20 : ffffe000`6c9af010 fffff800`6d2ce92d 00000000`00000002 ffffe000`6cc9627c : 0xffffe000`6bc09050
ffffd001`d9f84b70 ffffe000`6c9af010 : fffff800`6d2ce92d 00000000`00000002 ffffe000`6cc9627c ffffe000`6bc091a0 : 0xffffe000`6ca79c20
ffffd001`d9f84b78 fffff800`6d2ce92d : 00000000`00000002 ffffe000`6cc9627c ffffe000`6bc091a0 ffffd001`00000001 : 0xffffe000`6c9af010
ffffd001`d9f84b80 ffffe000`6e79c830 : 00000000`00000000 ffffe000`6c36f000 00000000`05c40000 fffff800`6cf54824 : USBPORT!USBPORT_Core_QueueTransferUrb+0x22d
ffffd001`d9f84be0 00000000`00000000 : ffffe000`6c36f000 00000000`05c40000 fffff800`6cf54824 ffffe000`6beb8d01 : 0xffffe000`6e79c830


STACK_COMMAND: kb

FOLLOWUP_IP:
igdkmd64+691d9
fffff800`6cebc1d9 ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: igdkmd64+691d9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME: igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 548e644c

FAILURE_BUCKET_ID: 0x133_DPC_igdkmd64+691d9

BUCKET_ID: 0x133_DPC_igdkmd64+691d9

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_igdkmd64+691d9

FAILURE_ID_HASH: {23619fb7-eb93-c271-aeae-ffa1552675cb}

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

Debugging Details:
------------------


DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff80325020ad6 to fffff80324fe0fa0

STACK_TEXT:
ffffd001`d9f93c98 fffff803`25020ad6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd001`d9f93ca0 fffff803`24f40f85 : 00000000`00000000 00000000`00000000 00000000`80000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2f626
ffffd001`d9f93d30 fffff803`24e257b5 : 00002830`00400a02 ffffe000`6d31f040 fffff800`6b85cab0 00000000`00007101 : nt!KeClockInterruptNotify+0x95
ffffd001`d9f93f40 fffff803`24f5c363 : ffffd001`d9f93f60 00000000`00000008 ffffd001`d9f93f50 00000000`00000010 : hal!HalpTimerClockIpiRoutine+0x15
ffffd001`d9f93f70 fffff803`24fe242a : fffff803`24e71d00 ffffd001`d9f84bb8 00000000`00000000 ffffe000`6d796000 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd001`d9f93fb0 fffff803`24fe280f : 00000000`00000000 00000000`00000004 00000000`00000000 00001600`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd001`d9f84990 fffff803`24f32c24 : ffffe000`6cc964bc ffffe000`6bcd17d0 ffffe000`6bc094c0 fffff803`24f86288 : nt!KiInterruptDispatchLBControl+0x11f
ffffd001`d9f84b20 fffff800`6cebc1d9 : ffffe000`6d796000 ffffe000`6bc094c0 ffffe000`6bc09050 ffffe000`6ca79c20 : nt!KxWaitForLockOwnerShip+0x34
ffffd001`d9f84b50 ffffe000`6d796000 : ffffe000`6bc094c0 ffffe000`6bc09050 ffffe000`6ca79c20 ffffe000`6c9af010 : igdkmd64+0x691d9
ffffd001`d9f84b58 ffffe000`6bc094c0 : ffffe000`6bc09050 ffffe000`6ca79c20 ffffe000`6c9af010 fffff800`6d2ce92d : 0xffffe000`6d796000
ffffd001`d9f84b60 ffffe000`6bc09050 : ffffe000`6ca79c20 ffffe000`6c9af010 fffff800`6d2ce92d 00000000`00000002 : 0xffffe000`6bc094c0
ffffd001`d9f84b68 ffffe000`6ca79c20 : ffffe000`6c9af010 fffff800`6d2ce92d 00000000`00000002 ffffe000`6cc9627c : 0xffffe000`6bc09050
ffffd001`d9f84b70 ffffe000`6c9af010 : fffff800`6d2ce92d 00000000`00000002 ffffe000`6cc9627c ffffe000`6bc091a0 : 0xffffe000`6ca79c20
ffffd001`d9f84b78 fffff800`6d2ce92d : 00000000`00000002 ffffe000`6cc9627c ffffe000`6bc091a0 ffffd001`00000001 : 0xffffe000`6c9af010
ffffd001`d9f84b80 ffffe000`6e79c830 : 00000000`00000000 ffffe000`6c36f000 00000000`05c40000 fffff800`6cf54824 : USBPORT!USBPORT_Core_QueueTransferUrb+0x22d
ffffd001`d9f84be0 00000000`00000000 : ffffe000`6c36f000 00000000`05c40000 fffff800`6cf54824 ffffe000`6beb8d01 : 0xffffe000`6e79c830


STACK_COMMAND: kb

FOLLOWUP_IP:
igdkmd64+691d9
fffff800`6cebc1d9 ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: igdkmd64+691d9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME: igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 548e644c

FAILURE_BUCKET_ID: 0x133_DPC_igdkmd64+691d9

BUCKET_ID: 0x133_DPC_igdkmd64+691d9

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_igdkmd64+691d9

FAILURE_ID_HASH: {23619fb7-eb93-c271-aeae-ffa1552675cb}

Followup: MachineOwner

 

 



BC AdBot (Login to Remove)

 


#2 Aura

Aura

    Bleepin' Special Ops


  • Malware Response Team
  • 19,697 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:13 PM

Posted 05 February 2015 - 06:34 AM

Hi godofsmoke :)

It looks like your BSODs are caused by the Intel graphic drivers. What game are you playing, and also what is your computer/laptop brand and model and exact version of Windows (8 or 8.1, 32 or 64-bits)?

animinionsmalltext.gif
unite_blue.png
Security Administrator | Sysnative Windows Update Senior Analyst | Malware Hunter | @SecurityAura
My timezone UTC-05:00 (East. Coast). If I didn't reply to you within 48 hours, please send me a PM.


#3 godofsmoke

godofsmoke
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:13 AM

Posted 05 February 2015 - 07:55 AM

The game i was playing is League of legends

I cant really give the exact details at the moment since im not at home but from what i can remember its:

Aspire v3-571

6GB RAM

i5 2.6Ghz Processor

Nvdia 730m videocard and some kind of intel video card which i dont remember

and windows 8.1 64 bits


Edited by godofsmoke, 05 February 2015 - 07:56 AM.


#4 Aura

Aura

    Bleepin' Special Ops


  • Malware Response Team
  • 19,697 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:13 PM

Posted 05 February 2015 - 08:29 AM

That's a good start :) All I need to know now is if you use Windows 7, 8 or 8.1.

animinionsmalltext.gif
unite_blue.png
Security Administrator | Sysnative Windows Update Senior Analyst | Malware Hunter | @SecurityAura
My timezone UTC-05:00 (East. Coast). If I didn't reply to you within 48 hours, please send me a PM.


#5 godofsmoke

godofsmoke
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:13 AM

Posted 06 February 2015 - 01:25 AM

Kinda late, but here are my full specs

 

Processor

Intel® Core™ i5-3230M CPU @ 2.60GHz

Manufacturer Intel

Speed 2.6 GHz

Number of Cores 4

 

Video Card 1

NVIDIA GeForce GT 730M

Manufacturer NVIDIA

Chipset GeForce GT 730M

Dedicated Memory 2.1 GB

Total Memory 3.9 GB

 

Video Card 2

Intel® HD Graphics 4000

Manufacturer Intel

Chipset Intel® HD Graphics 4000

Dedicated Memory 128 MB

Total Memory 1.8 GB

 

Memory 6.0 GB

 

Operating System

Microsoft Windows 8 Professional Edition (build 9200), 64-bit

 

Display Maximum Resolution

1360 x 768

 

DVD

DTSOFT Virtual CdRom Device

 

CD

DTSOFT Virtual CdRom Device

 

Drive 1

Size 640.0 GB

Free 108.4 GB

 

Drive 2

Size 58.5 GB

Free 15.4 GB


Edited by godofsmoke, 06 February 2015 - 01:31 AM.


#6 Aura

Aura

    Bleepin' Special Ops


  • Malware Response Team
  • 19,697 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:13 PM

Posted 06 February 2015 - 05:57 AM

I see that you are using Windows 8. Before we do anything else, could you upgrade to Windows 8.1? It's free, simply go in the Windows Store, and it's the first thing that they offer you once you get in it. Make sure that you have all your Important Windows Updates installed before doing so, since some of them are prerequisite to the installation of Windows 8.1.

animinionsmalltext.gif
unite_blue.png
Security Administrator | Sysnative Windows Update Senior Analyst | Malware Hunter | @SecurityAura
My timezone UTC-05:00 (East. Coast). If I didn't reply to you within 48 hours, please send me a PM.


#7 dinodod

dinodod

  • Members
  • 133 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 07 February 2015 - 06:00 PM

Why does this laptop have dual video cards?  Even the newest model only shows a NVIDIA card.  Was this an addon you did or know about?


Essential Tools for safe computing

https://sites.google.com/site/dinodod/pc-standards

 

Please leave a comment on anything relative and help me expand on it.

 


#8 godofsmoke

godofsmoke
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:13 AM

Posted 08 February 2015 - 02:30 PM

Why does this laptop have dual video cards?  Even the newest model only shows a NVIDIA card.  Was this an addon you did or know about?

 

I dont know, it was like this since i bought it.

 

@Aura, ill update the pc once i get to faster internet conection, maybe ill reinstall the game first since i found out only that game shows the error also whenever i play it, it sometimes pops up "low on memory warning" altho when i check control panel, everything looks normal, nothing like that happens when i play any other game either



#9 dinodod

dinodod

  • Members
  • 133 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 08 February 2015 - 03:23 PM

Sorry, I forgot that Intel CPU's are now bundled with their own HD Graphics, hence the dual video cards.  The NVIDIA card should be the primary display card that the monitor is using and not the Intel card (At least that's my thinking).  But try updating both drivers

 

 

Windows 8.1 Drivers

 

Intel Driver:  http://global-download.acer.com/GDFiles/Driver/VGA/VGA_Intel_10.18.10.3304_W81x64_A.zip?acerid=635171467692606844&Step1=NOTEBOOK&Step2=ASPIRE&Step3=ASPIRE%20V3-571&OS=81P1&LC=en&BC=ACER&SC=PA_6

 

NVIDIA Driver:  http://global-download.acer.com/GDFiles/Driver/VGA/VGA_NVIDIA_9.18.13.1130_W81x64W8x64W7x64_A.zip?acerid=635254307242226759&Step1=NOTEBOOK&Step2=ASPIRE&Step3=ASPIRE%20V3-571&OS=81P1&LC=en&BC=ACER&SC=PA_6


Essential Tools for safe computing

https://sites.google.com/site/dinodod/pc-standards

 

Please leave a comment on anything relative and help me expand on it.

 


#10 Aura

Aura

    Bleepin' Special Ops


  • Malware Response Team
  • 19,697 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:13 PM

Posted 08 February 2015 - 06:58 PM

Why does this laptop have dual video cards?  Even the newest model only shows a NVIDIA card.  Was this an addon you did or know about?

 
I dont know, it was like this since i bought it.
 
@Aura, ill update the pc once i get to faster internet conection, maybe ill reinstall the game first since i found out only that game shows the error also whenever i play it, it sometimes pops up "low on memory warning" altho when i check control panel, everything looks normal, nothing like that happens when i play any other game either


Alright that's good. Once you are fully upgraded to Windows 8.1, I suggest you to check manually for Important Windows Updates and when they are all installed, upgrade both your graphic card drivers, one at the time, with the links dinodod provided.

animinionsmalltext.gif
unite_blue.png
Security Administrator | Sysnative Windows Update Senior Analyst | Malware Hunter | @SecurityAura
My timezone UTC-05:00 (East. Coast). If I didn't reply to you within 48 hours, please send me a PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users