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

BSOD - "DPC Watchdog error"


  • Please log in to reply
4 replies to this topic

#1 Nagesh_n

Nagesh_n

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:30 AM

Posted 10 April 2015 - 06:30 AM

Hello,

 

Very often my new system crashes. Below is the abstract when i analysed with Whocrashed tool. i couldnt updload dump file, as it's size is larger then the max file size allowed. 

 

Any help would be really appreciated.

 

-----------------------------------------------------

computer name: SANJAYC
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: Latitude 3540, Dell Inc., 0MC4K5
CPU: GenuineIntel Intel® Core™ i5-4210U CPU @ 1.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8498667520 total


 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 4/2/2015 1:47:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040215-24625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0) 
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Thu 4/2/2015 1:47:35 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0x1A5) 
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



BC AdBot (Login to Remove)

 


#2 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:04:00 PM

Posted 10 April 2015 - 03:50 PM

Please upload the minidumps here



#3 Nagesh_n

Nagesh_n
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:30 AM

Posted 13 April 2015 - 12:29 AM

minidump Files are uploaded. Thanks.



#4 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:04:00 PM

Posted 13 April 2015 - 07:57 AM

STACK_TEXT:  
ffffd000`24d169f8 fffff800`b4ab008b : 00000000`deaddead 00000000`00000000 00000000`00000000 00000000`19187b88 : nt!KeBugCheckEx
ffffd000`24d16a00 00000000`deaddead : 00000000`00000000 00000000`00000000 00000000`19187b88 00000000`3c2a58ed : rspCrash64+0x108b
ffffd000`24d16a08 00000000`00000000 : 00000000`00000000 00000000`19187b88 00000000`3c2a58ed fffff801`28bdb9fa : 0xdeaddead

http://www.carrona.org/drivers/driver.php?id=rspCrash64.sys

 

Please uninstall or remove the WhoCrashed Program while we are troubleshooting.

BugCheck DEADDEAD, {0, 0, 19187b88, 3c2a58ed}
CPUID:        "Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz"
 
MaxSpeed:     1700
 
CurrentSpeed: 2394

Please stop overclocking while we troubleshoot. You can resume once your system is stable.

 

Also try to update the below third party drivers, prioritizing those with an older date. Information about the driver is listed under this code box.
 
Third party driver list - sorted by date of driver
**************************Thu Apr  9 01:13:58.542 2015 (UTC - 5:00)**************************
swvnic.sys                Sun Feb 22 21:04:50 2009 (49A21252)
vrvd5.sys                 Mon Sep  7 13:41:24 2009 (4AA553D4)
CLVirtualDrive.sys        Mon Dec 26 07:26:47 2011 (4EF87617)
ccSetx64.sys              Fri Jun 15 19:21:18 2012 (4FDBD17E)
DellRbtn.sys              Fri Aug  3 16:32:54 2012 (501C4386)
btath_lwflt.sys           Fri Nov  2 00:35:44 2012 (50935BB0)
rspCrash64.sys            Mon Nov  5 01:18:46 2012 (50976856)
btath_hcrp.sys            Tue Dec 18 03:54:54 2012 (50D03D6E)
btath_bus.sys             Mon Jan 21 03:18:42 2013 (50FD07F2)
btath_rcp.sys             Fri Jun 21 04:11:54 2013 (51C418DA)
Rt630x64.sys              Fri Jul 26 02:01:35 2013 (51F21ECF)
SYMEVENT64x86.SYS         Fri Jul 26 21:26:58 2013 (51F32FF2)
SRTSPX64.SYS              Fri Jul 26 21:45:06 2013 (51F33432)
Ironx64.SYS               Mon Jul 29 19:59:35 2013 (51F70FF7)
SYMDS64.SYS               Tue Jul 30 18:29:08 2013 (51F84C44)
iaStorA.sys               Thu Aug  1 20:39:52 2013 (51FB0DE8)
RtsUVStor.sys             Thu Aug  8 03:26:23 2013 (5203562F)
intelppm.sys              Thu Aug 22 03:46:35 2013 (5215CFEB)
btath_flt.sys             Thu Aug 22 22:46:29 2013 (5216DB15)
btath_avdt.sys            Wed Sep 18 03:42:14 2013 (52396766)
btath_a2dp.sys            Wed Sep 18 03:45:01 2013 (5239680D)
ccSetx64.sys              Mon Sep 23 22:58:04 2013 (52410DCC)
iwdbus.sys                Thu Sep 26 16:38:04 2013 (5244A93C)
dnelwf64.sys              Wed Oct  2 22:45:14 2013 (524CE84A)
athwbx.sys                Thu Oct 17 04:46:01 2013 (525FB1D9)
btfilter.sys              Thu Oct 24 04:40:59 2013 (5268EB2B)
igdkmd64.sys              Mon Oct 28 16:57:02 2013 (526EDDAE)
TeeDriverx64.sys          Wed Nov 27 11:56:32 2013 (52963250)
SWIPsec.sys               Tue Dec  3 18:51:01 2013 (529E7C75)
SynTP.sys                 Thu Jan 16 23:26:20 2014 (52D8BEFC)
Smb_driver_Intel.sys      Thu Jan 16 23:30:42 2014 (52D8C002)
SRTSP64.SYS               Mon Feb 10 17:04:55 2014 (52F95B17)
SYMNETS.SYS               Thu Feb 13 05:25:14 2014 (52FCAB9A)
SYMEFA64.SYS              Thu Feb 27 17:32:07 2014 (530FCAF7)
EX64.SYS                  Sat Nov 15 03:14:03 2014 (5467195B)
ENG64.SYS                 Sat Nov 15 03:15:33 2014 (546719B5)
EraserUtilRebootDrv.sys   Tue Nov 25 14:15:44 2014 (5474E370)
eeCtrl64.sys              Tue Nov 25 14:15:44 2014 (5474E370)
RTKVHD64.sys              Wed Dec 10 01:53:17 2014 (5487FBED)
BHDrvx64.sys              Thu Jan 22 18:46:20 2015 (54C199DC)
IDSvia64.sys              Tue Mar 17 18:43:19 2015 (5508BC17)
vrvd5.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

 

 

If this does not stop the BSOD's, then please run Driver Verifier according to these instructions:

 

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior. 

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point" 
Windows 8/8.1 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues. 

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

- Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode: 

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

Any other questions can most likely be answered by this article:

Using Driver Verifier to identify issues with Windows drivers for advanced users



#5 Nagesh_n

Nagesh_n
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:30 AM

Posted 14 April 2015 - 12:58 AM

Thanks a lot, will update the drivers and will enable the verifier, if BSOD happens again. Thanks a ton for your help and time.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users