BSOD Win8 Pro 64bit

JustAnotherGuy · Apr 10, 2013

So i have experienced 3 BSOD today in a row, it was while watching a movie on my laptop (maybe it's VGA related?)

Anyway all it said : dpc_watchdog_violation

I went ahead and installed BlueScreenView to read the dump file and it said the error was caused by hal.dll. This is the output i could copy:

==================================================
Dump File : 041013-54109-01.dmp
Crash Time : 10/04/2013 12:26:36
Bug Check String :
Bug Check Code : 0x00000133
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000281
Parameter 3 : 00000000`00000280
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+166b1
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7a040
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041013-54109-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9200
Dump File Size : 279,760
==================================================

==================================================
Dump File : 041013-54437-01.dmp
Crash Time : 10/04/2013 12:45:47
Bug Check String :
Bug Check Code : 0x00000133
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000281
Parameter 3 : 00000000`00000280
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+22e94
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7a040
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041013-54437-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9200
Dump File Size : 279,760
==================================================

==================================================
Dump File : 041013-53468-01.dmp
Crash Time : 10/04/2013 12:10:23
Bug Check String :
Bug Check Code : 0x00000133
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000281
Parameter 3 : 00000000`00000280
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+22e94
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7a040
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041013-53468-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9200
Dump File Size : 279,704
==================================================

Thank you for all your help !! :)

JustAnotherGuy · Apr 10, 2013

I used another tool called WhoCrashed to analyze the dump files, here is the ouput i got:

System Information (local)

computer name: OMAR-HP
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8535257088 total
VM: 2147352576, free: 1924550656

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 10/04/2013 10:44:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041013-54437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 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 Wed 10/04/2013 10:44:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalSetTimeIncrement+0x3F54)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 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.

On Wed 10/04/2013 10:25:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041013-54109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 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 Wed 10/04/2013 10:08:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041013-53468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 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.

Conclusion

4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

usasma · Apr 10, 2013

Please provide this information so we can provide a complete analysis: https://www.sysnative.com/forums/bs...d-posting-instructions-windows-8-7-vista.html

Try running Driver Verifier according to these instructions: Driver Verifier Settings

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

hpdskflt.sys Fri May 13 14:47:02 2011 (4DCD7CA6)
HP Mobile Data Protection System Disk Filter
http://www.carrona.org/drivers/driver.php?id=hpdskflt.sys

Accelerometer.sys Fri May 13 14:47:02 2011 (4DCD7CA6)
HP Mobile Data Protection System Accelerometer
http://www.carrona.org/drivers/driver.php?id=Accelerometer.sys

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Wed Apr 10 06:44:01.474 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041013-54437-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]0 days 0:18:23.172[/B]
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by :[B]tcpip.sys ( tcpip+9ca25 )[/B]
BugCheck [B]133, {0, 281, 280, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x133_DPC_tcpip+9ca25[/B]
CPUID:        "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: [B]2195[/B]
  BIOS Version                  F.1A
  BIOS Release Date             06/22/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Apr 10 06:25:01.976 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041013-54109-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]0 days 0:15:49.674[/B]
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by :[B]tcpip.sys ( tcpip+9ca25 )[/B]
BugCheck [B]133, {0, 281, 280, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x133_DPC_tcpip+9ca25[/B]
CPUID:        "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: [B]2195[/B]
  BIOS Version                  F.1A
  BIOS Release Date             06/22/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Apr 10 06:08:27.165 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041013-53468-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]0 days 13:05:46.862[/B]
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by :[B]tcpip.sys ( tcpip+9ca25 )[/B]
BugCheck [B]133, {0, 281, 280, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x133_DPC_tcpip+9ca25[/B]
CPUID:        "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed: [B]2195[/B]
  BIOS Version                  F.1A
  BIOS Release Date             06/22/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Wed Apr 10 06:44:01.474 2013 (UTC - 4:00)**************************
[COLOR=RED][B]hpdskflt.sys                Fri May 13 14:47:02 2011 (4DCD7CA6)[/B][/COLOR]
[COLOR=RED][B]Accelerometer.sys           Fri May 13 14:47:02 2011 (4DCD7CA6)[/B][/COLOR]
vmci.sys                    Mon Apr 30 21:14:27 2012 (4F9F38F3)
vsock.sys                   Mon Apr 30 21:15:24 2012 (4F9F392C)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
SYMEVENT64x86.SYS           Wed May 23 20:52:24 2012 (4FBD8648)
TurboB.sys                  Wed May 30 16:10:44 2012 (4FC67EC4)
IntcDAud.sys                Tue Jun 19 10:40:51 2012 (4FE08F73)
VMNET.SYS                   Sun Jul  8 03:58:34 2012 (4FF93DAA)
vmnetadapter.sys            Sun Jul  8 03:58:35 2012 (4FF93DAB)
vmnetbridge.sys             Sun Jul  8 03:59:19 2012 (4FF93DD7)
SYMNETS.SYS                 Fri Jul 20 22:07:07 2012 (500A0ECB)
Ironx64.SYS                 Mon Jul 23 20:34:50 2012 (500DEDAA)
RtsPStor.sys                Fri Jul 27 06:08:53 2012 (501268B5)
EraserUtilRebootDrv.sys     Tue Jul 31 19:36:50 2012 (50186C12)
eeCtrl64.sys                Tue Jul 31 19:36:51 2012 (50186C13)
hcmon.sys                   Wed Aug  1 20:10:29 2012 (5019C575)
vmnetuserif.sys             Wed Aug 15 16:31:54 2012 (502C073A)
vmx86.sys                   Wed Aug 15 18:05:11 2012 (502C1D17)
ccSetx64.sys                Thu Aug 16 17:18:11 2012 (502D6393)
[COLOR=RED][B]nusb3hub.sys                Tue Aug 21 00:12:54 2012 (50330AC6)[/B][/COLOR]
[COLOR=RED][B]nusb3xhc.sys                Tue Aug 21 00:12:55 2012 (50330AC7)[/B][/COLOR]
IDSvia64.sys                Tue Aug 28 22:48:40 2012 (503D8308)
SynTP.sys                   Fri Sep 28 12:43:34 2012 (5065D3B6)
Smb_driver_Intel.sys        Fri Sep 28 12:45:35 2012 (5065D42F)
RimSerial_AMD64.sys         Mon Oct 22 16:51:51 2012 (5085B1E7)
stwrt64.sys                 Wed Oct 24 23:58:55 2012 (5088B8FF)
btath_bus.sys               Fri Nov  2 01:35:15 2012 (50935B93)
intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
igdpmd64.sys                Tue Nov 20 22:01:04 2012 (50AC43F0)
atikmpag.sys                Sun Dec  2 02:13:21 2012 (50BAFF91)
atikmdag.sys                Sun Dec  2 03:21:53 2012 (50BB0FA1)
HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
EX64.SYS                    Thu Dec 20 04:22:39 2012 (50D2D8DF)
ENG64.SYS                   Thu Dec 20 04:24:21 2012 (50D2D945)
Rt630x64.sys                Thu Dec 27 19:04:06 2012 (50DCE1F6)
dump_iaStorA.sys            Mon Jan 14 13:00:27 2013 (50F447BB)
iaStorA.sys                 Mon Jan 14 13:00:27 2013 (50F447BB)
SYMDS64.SYS                 Wed Jan 16 20:56:45 2013 (50F75A5D)
SYMEFA64.SYS                Fri Jan 18 19:31:37 2013 (50F9E969)
SRTSP64.SYS                 Fri Jan 25 16:26:16 2013 (5102F878)
SRTSPX64.SYS                Fri Jan 25 16:30:05 2013 (5102F95D)
athw8x.sys                  Wed Feb 20 22:50:31 2013 (51259987)
BHDrvx64.sys                Sat Mar 16 01:18:38 2013 (514400AE)
[/font]

writhziden · Apr 10, 2013

In addition to the steps given by usasma, I see the hardware abstraction layer in the stack in the crashes, so this may be a hardware fault. We need the blue screen reports asked for in usasma's link for a full analysis to have more to go on in this regard.

usasma said:
Please provide this information so we can provide a complete analysis: https://www.sysnative.com/forums/bs...d-posting-instructions-windows-8-7-vista.html

Given that these are network related, the other prime suspects are VMWare and Norton, both of which are known to cause internet related crashes. Proceed with Verifier first, and then you can remove the software properly once it is disabled in 24 hours. Do not remove programs while Verifier is enabled.

Download and run the Norton Removal Tool to uninstall your Norton product.URL

https://www.sysnative.com/forums/wi...ntials-windows-7-windows-vista.html#post38471

Uninstall VMWare

-----

JustAnotherGuy · Apr 10, 2013

I ran jcgriff2 BSOD File Collection app and i'm stuck at "Waiting for SystemInfo". I placed it in My Documents as well as the other file (autorns.exe)

· OS - Windows 8 Pro
· x64
· Win7 was originally installed on system but i upgraded to win8 Pro 3 months ago and had no problems...
· I guess Win7 was an OEM version (came pre-installed on system) but i purchased win8 from Microsoft website
· Age of system (hardware): I bought this laptop (HP dv7) about a year ago.
· Age of OS installation - I just reinstalled Win8 3 days ago and have been upgrading all drivers...I'm pretty much sure that this is why i'm starting to have the BSoD now !

· CPU: intel i7 quadcore 2.2 GHz (2670QM)
· Video Card : 7690M XT 2 GB + Intel 3000 HD
· MotherBoard: not sure how to find out??
· Power Supply - brand & wattage (if laptop, skip this one): i do have a laptop

· System Manufacturer : HP
· Exact model number (if laptop, check label on bottom) : DV7-6C90EF

usasma · Apr 10, 2013

Just a bit more then - I've also seen a lot of network errors in systems that have the athw8x.sys driver.
I suggested Driver Verifier in order to rule out that, along with the Norton and the Virtual Machine stuff (all common errors that we see in Win8).

usasma · Apr 10, 2013

The SystemInfo takes a while at times. Just let it run and continue to use the system. If nothing happens in 15 to 20 minutes, post back for some other suggestions.

JustAnotherGuy · Apr 10, 2013

I uploaded the PERFORMN.html you asked for but the other app is still saying "Waiting for SystemInfo". It did create a folder named "Windows7_Vista_jcgriff2" and it managed to open autoruns which scanned everything...still don't get why it can't fetch that info & is still waiting for SystemInfo...

usasma · Apr 10, 2013

I have seen issues with MSINFO32 and the French language.
Check to see what's in the Windows7_Vista_jcgriff2 folder.
I need the MSINFO32.nfo report and the systeminfo.txt report

If unable to get it, try the tool here: How To Ask For Help With BSOD
It doesn't collect as much info as the jcgriff2 tool, but it'll do for starters.

JustAnotherGuy · Apr 10, 2013

I used : SF_Diagnostic_Tool which was suggested on Blue Screen of Death (BSOD) Posting Instructions

i attached the output.

usasma · Apr 10, 2013

The reports show about 38 STOP errors today (10 April) alone.
2 - STOP 0x117 in atikmpag.sys
4 - STOP 0x133 in tcpip.sys
29 - STOP 0x141 in atikmpag.sys
3 - STOP 0x144, but oddly it points to a device rather than a driver. The device is VEN_1033_DEV_0194 - a USB 3.0 controller

I'd focus on the video aspect for now

1) Run Driver Verifier according to these directions: Driver Verifier Settings
2) Update the video drivers for your laptop to the latest, Win8 compatible version
3) Troubleshoot using this link: https://www.sysnative.com/forums/bs...-video-tdr-timeout-0x116-0x117.html#post29532
4) Run these free diagnostics (focus on the video and memory tests): Hardware Diagnostics
5) Ensure that the laptop is not overheating, that it's being used on a flat, hard surface (preferably with a cooling pad), that the fan is working, and that the vents have been blown out with canned air (DO NOT use a vacuum or an air compressor as they can cause damage to the system).

JustAnotherGuy · Apr 10, 2013

Well the thing is, this Graphic card has been driving me nuts since i bought the laptop. There are so many forums where people are complaining about it (ATI 7690 M XT) i wish i had seen them before buying my laptop...

So like i use leshcatlabs drivers which seem to perform well while gaming but not so much while doing anything else...So i have various VGA crashes on daily basis but i can live with that...

I think i'll just format my laptop & reinstall Win8 in a week (can't do that now..)

However, I have never experienced BSoD because of the VGA drivers. But then again, i might have messed things up when i reinstalled them without whipping out old drivers after the windows 8 restore i did couple days ago. Is there anything else besides the graphic card causing the problem??

Anyway, thank you for your help.

usasma · Apr 11, 2013

It's hard to tell. The USB and TCPIP errors may/may not be related to the graphics issues.

The USB drivers could be related to:
- the graphics problem
- the USB 3.0 controller drivers
- the USB 3.0 controller itself
- any attached USB devices
- the drivers for any attached USB devices

The TCPIP driver problems could be related to:
- the graphics problem
- network device drivers
- network devices themselves (wired and/or wireless)
- other network aware drivers
- other network aware programs (examples include Norton/Symantec and VMWare)

I would suggest that the first step is to use the factory provided drivers. Please do this:
- download a fresh set of the factory video drivers (for both cards) - and any controlling software that may be required.
- uninstall the current drivers
- install the freshly downloaded drivers and software
- monitor for further BSOD"s

Another option is to restore the computer with the factory restore disks/partition. Then get ALL available Windows Updates and see if that fixes things.

BSOD Win8 Pro 64bit

JustAnotherGuy

Member

Attachments

JustAnotherGuy

Member

usasma

Retired Admin

writhziden

Administrator, .NET/UWP Developer

JustAnotherGuy

Member

usasma

Retired Admin

usasma

Retired Admin

JustAnotherGuy

Member

Attachments

usasma

Retired Admin

JustAnotherGuy

Member

Attachments

usasma

Retired Admin

JustAnotherGuy

Member

usasma

Retired Admin