Win 8 x64 BSOD's - DPC_WATCHDOG_VIOLATION

SuperchargedSoup · Mar 12, 2013

Hi there,

A few months ago, I got an ASUS K55V laptop. Since then, I have purchased a Razer DeathAdder 3.5G mouse, and a Wacom Bamboo Pen and Touch Create tablet. These details may be irrelevant to a possible solution, but more information the better, right? Over the past few weeks, I've been getting BSOD's with an error code of DPC_WATCHDOG_VIOLATION. It isnt a regular thing, and I don't know what causes it (maybe conflicting drivers?), but I was hoping to get some much needed help on this; its driving me crazy, I keep losing progress on school work. If you need more information, don't hesitate to ask :)

Thanks in advance,
- SuperchargedSoup

writhziden · Mar 12, 2013

Hello, and welcome to Sysnative.

Please follow the blue screen posting instructions to provide us with your reports for analysis. I too hope we are able to help you find a solution.

https://www.sysnative.com/forums/bs...g-instructions-windows-8-7-windows-vista.html

SuperchargedSoup · Mar 12, 2013

Hi writhziden,

Im following those steps as we speak, and will get back to you ASAP with the results of the tests.
Sorry I didn't read the post you mentioned above :/

Thanks,
- SuperchargedSoup

SuperchargedSoup · Mar 12, 2013

Hi again,

Please find attached the files required.
· OS - Windows 8 - 64 bit
· What was original installed OS on system? Windows 8 - 64 bit
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM (see above)
· Age of system (hardware): Purchased in december 2012
· Age of OS installation - have you re-installed the OS? No, original OS installed.

· CPU: Intel Core i5 3rd Gen 2.50GHz
· Video Card: If this is also known as a graphics card, then Nvidia GeForce 610M
· MotherBoard: I have no idea. The stock one that comes with my laptop (see below for exact model number)

· System Manufacturer: ASUS
· Exact model number (if laptop, check label on bottom): K55V-SX071H

Thanks again,
- SuperchargedSoup

jcgriff2 · Mar 12, 2013

Hi -

I'm running the 6 dumps from March now.

I noticed that you had 2 earlier BSODs in January & Frbruary; then all quiet for a few weeks until now.

The 2 prior BSODs -

Code:

BugCheck 1E, {[COLOR="#FF0000"]ffffffffc0000047[/COLOR], fffff8027595a008, 0, 0}

0x1e = kernel threw an exception
0xc0000047 exception =

0xC0000047
STATUS_SEMAPHORE_LIMIT_EXCEEDED

An attempt was made to release a semaphore such that its maximum count would have been exceeded.

That is more than likely a driver issue.

BSOD #2:

Code:

BugCheck 133, {0, 281, 280, 0}

0x133 = DPC_WATCHDOG_VIOLATION - also could be a driver issue. In my case, it was NVIDIA driver issue that repeatedly occurred after installing Windows 8 on my Vista SP1 era laptop. Updating the NVIDIA driver solved it for me.

Did you do anything in particular to stop/fix these 2 BSODs?

Regards. . .

jcgriff2

jcgriff2 · Mar 12, 2013

Hi again. . .

5 of the 6 March 2013 BSODs named Norton Internet Security as the probable cause; specifically the 1st driver -

Code:

[font=lucida console][color=red]IDSvia64.sys                Tue Aug 28 22:48:40 2012 (503D8308)[/color] - Norton 
BHDrvx64.sys                Fri Jan 11 13:50:17 2013 (50F05EE9) - Norton 
ENG64.SYS                   Thu Dec 20 04:24:21 2012 (50D2D945) - Norton 
EX64.SYS                    Thu Dec 20 04:22:39 2012 (50D2D8DF) - Norton 
EraserUtilRebootDrv.sys     Tue Jul 31 19:36:50 2012 (50186C12) - Norton 
Ironx64.SYS                 Mon Jul 23 20:34:50 2012 (500DEDAA) - Norton 
SRTSP64.SYS                 Fri Jan 25 16:26:16 2013 (5102F878) - Norton 
SRTSPX64.SYS                Fri Jan 25 16:30:05 2013 (5102F95D) - Norton 
SYMDS64.SYS                 Wed Jan 16 20:56:45 2013 (50F75A5D) - Norton 
SYMEFA64.SYS                Fri Jan 18 19:31:37 2013 (50F9E969) - Norton 
SYMEVENT64x86.SYS           Wed May 23 20:52:24 2012 (4FBD8648) - Norton 
SYMNETS.SYS                 Fri Jul 20 22:07:07 2012 (500A0ECB) - Norton 
eeCtrl64.sys                Tue Jul 31 19:36:51 2012 (50186C13) - Norton 
ccSetx64.sys                Thu Aug 16 17:18:11 2012 (502D6393) - Norton 
[/font]

Code:

[font=lucida console]mfeapfk.sys                 Wed May 30 11:35:57 2012 (4FC63E5D)
mfeavfk.sys                 Wed May 30 11:36:18 2012 (4FC63E72) - McAfee
mfefirek.sys                Wed May 30 11:38:10 2012 (4FC63EE2) - McAfee
mfehidk.sys                 Wed May 30 11:35:13 2012 (4FC63E31) - McAfee
mfewfpk.sys                 Wed May 30 11:35:28 2012 (4FC63E40) - McAfee
[/font]

http://www.sysnative.com/drivers/driver.php?id=mfeapfk.sys
http://www.sysnative.com/drivers/driver.php?id=mfeavfk.sys
http://www.sysnative.com/drivers/driver.php?id=mfefirek.sys
http://www.sysnative.com/drivers/driver.php?id=mfehidk.sys
http://www.sysnative.com/drivers/driver.php?id=mfewfpk.sys

Run McAfee removal tool - http://kb.eset.com/esetkb/index?page=content&id=SOLN146

Reboot upon completion.

I would suggest running Microsoft Windows Defender (formerly MSE) until BSOD epidemic is over.

https://www.sysnative.com/forums/wi...urity-essentials-windows-7-windows-vista.html

Daemon Tools/Alcohol - known to cause BSODs. Please remove for now -

Code:

[font=lucida console]sptd.sys                    Sat Aug 18 17:05:38 2012 (503003A2)
[/font]

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

Razer HID known to cause BSODs in Windows 7; I'm sure it may have issues with Windows 8 too -

Code:

[font=lucida console]danew.sys                   Tue Mar 23 04:37:33 2010 (4BA87DCD) - New DeathAdder Mouse driver
[/font]

Check for update -
http://www.sysnative.com/drivers/driver.php?id=danew.sys

jcgriff2

BSOD SUMMARY

Code:

[font=lucida console]
Debug session time: Tue Mar 12 18:03:11.650 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031313-62703-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 16:13:41.390
*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
Probably caused by : IDSvia64.sys ( IDSvia64+337b9 )
BugCheck 133, {0, 281, 280, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Bugcheck code 00000133
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:  X64_0x133_DPC_IDSvia64+337b9
MaxSpeed:     2500
CurrentSpeed: 2494
BiosVersion = K55VD.404
BiosReleaseDate = 08/20/2012
SystemManufacturer = ASUSTeK COMPUTER INC.
SystemProductName = K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Mar 12 01:48:57.268 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031213-36484-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 2:24:44.007
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : UsbHub3.sys
BugCheck 9F, {4, 12c, fffffa80051fa840, fffff8800341b800}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000009F]DRIVER_POWER_STATE_FAILURE (9f)[/url]
Bugcheck code 0000009F
Arguments: 
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: fffffa80051fa840, The thread currently holding on to the Pnp lock.
Arg4: fffff8800341b800, nt!TRIAGE_9F_PNP on Win7
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_4_IMAGE_UsbHub3.sys
MaxSpeed:     2500
CurrentSpeed: 2494
BiosVersion = K55VD.404
BiosReleaseDate = 08/20/2012
SystemManufacturer = ASUSTeK COMPUTER INC.
SystemProductName = K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Mar 10 19:58:29.153 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031113-37078-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 17:41:07.891
*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
Probably caused by : IDSvia64.sys ( IDSvia64+545c1 )
BugCheck 133, {0, 281, 280, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Bugcheck code 00000133
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:  X64_0x133_DPC_IDSvia64+545c1
MaxSpeed:     2500
CurrentSpeed: 2494
BiosVersion = K55VD.404
BiosReleaseDate = 08/20/2012
SystemManufacturer = ASUSTeK COMPUTER INC.
SystemProductName = K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Mar  9 01:22:37.292 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030913-36546-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 23:07:52.031
*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
Probably caused by : IDSvia64.sys ( IDSvia64+60a45 )
BugCheck 133, {0, 281, 280, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Bugcheck code 00000133
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:  X64_0x133_DPC_IDSvia64+60a45
MaxSpeed:     2500
CurrentSpeed: 2494
BiosVersion = K55VD.404
BiosReleaseDate = 08/20/2012
SystemManufacturer = ASUSTeK COMPUTER INC.
SystemProductName = K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Mar  3 01:57:12.800 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030313-62859-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 2 days 0:33:11.531
*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
Probably caused by : IDSvia64.sys ( IDSvia64+60c6e )
BugCheck 133, {0, 281, 280, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Bugcheck code 00000133
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:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x133_DPC_IDSvia64+60c6e
MaxSpeed:     2500
CurrentSpeed: 2494
BiosVersion = K55VD.404
BiosReleaseDate = 08/20/2012
SystemManufacturer = ASUSTeK COMPUTER INC.
SystemProductName = K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Mar  1 01:23:28.874 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030113-61656-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 1 days 0:16:37.844
*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
Probably caused by : IDSvia64.sys ( IDSvia64+60cbe )
BugCheck 133, {0, 281, 280, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Bugcheck code 00000133
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:  X64_0x133_DPC_IDSvia64+60cbe
MaxSpeed:     2500
CurrentSpeed: 2494
BiosVersion = K55VD.404
BiosReleaseDate = 08/20/2012
SystemManufacturer = ASUSTeK COMPUTER INC.
SystemProductName = K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


         
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=http://mvp.microsoft.com/profiles/Griffith][color=#000055][u][url]http://mvp.microsoft.com/profiles/Griffith[/url][/u][/color][/url]   

           [url=https://www.sysnative.com][color=#000033][u][url]www.sysnative.com[/url][/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

SuperchargedSoup · Mar 12, 2013

Thanks for the prompt replies!

I had a feeling it might have been issues/conflicts between drivers. Maybe the Razer mouse drivers and Wacom tablet drivers are the culprits? Or do you think it would be the Video card drivers? Since both the Razer mouse and Wacom tablet are classified as input devices, maybe that would cause the conflict; what with the difference in settings and configs. Unfortunately, since I use both regularly, uninstalling one or the other isnt an option.
What do you suggest I do from here? I checked for Windows Updates yesterday, and came up with no hits. I will check for updates for all my drivers, and see what happens. Luckily, since the last one, there have been no other BSOD's yet; fingers crossed!

Thanks kindly,
- SuperchargedSoup

SuperchargedSoup · Mar 12, 2013

Hmm that doesnt sound promising. I dont really want to remove Norton if I can help it, since I have payed for a years subscription; its not cheap! I will remove McAfee ASAP, I thought I removed it before I installed Norton. Daemon Tools can go I guess, its just a nice tool to have. Would you recommend Magic Iso? On my family computer, we have had a pretty bad experience with MSE/MDE, and I dont really want to re-instate its service if at all possible...

Thanks again,
-Soup

jcgriff2 · Mar 12, 2013

Hi -

Remove McAfee with removal tool.

All of the virtual devices can cause BSODs. You can reintroduce Daemon once the BSODs have calmed down & judge for yourself.

Keep Norton for now if you wish as one dump indicated a USB device was involved. It could have been a standoff between Norton & the unknown USB device. I am simply not a big fan of the Internet Security suites since Vista as they tend to block local NETBIOS ports, interfering with system services. Then there is the 3rd party firewall...

But those are my [non]-preferences! I myself prefer Windows firewall, anti-virus, etc...

After removing McAfee, run Driver Verifier -

https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Regards. . .

jcgriff2

EDIT: Yes, Razer & Wacom are good candidates here for the actual cause.

NIS still cannot be ruled out though.

SuperchargedSoup · Mar 13, 2013

Hi there,

I have successfully removed McAfee and Daemon Tools, and I have activated Driver Verifier. I activated it earlier today, but noticed my system was considera slower; I stopped it and rebooted because it was too painstakingly slow. As I mentioned, I have re-activated it, but I noticed that when I went to step 2 of the activation (I noticed this the first time too), that the following were not available for me select:

▪ Concurrentcy Stress Test (Windows 8)
▪ DDI compliance checking (Windows 8)

I instead had to select "Security Checks (Windows 7)". Is this a serious problem, or is it merely a glitch?

Now, do I have to wait for Driver Verifier to force a BSOD for it work, or is it just to check if anything happens?

Thanks kindly,
- Soup

jcgriff2 · Mar 13, 2013

Hi -

Let Driver Verifier run for 24 hours minimum.

As you have noticed, DV can be resource intensive.

The goal here is for DV to flag a 3rd party driver, which will immediately force a BSOD & hopefully name the culprit.

It's possible that McAfee + spts.sys removal may have fixed things; more so McAfee, IMO as it was likely interfering with NIS.

Those 2 DV options are new to Windows 8; the other was new to Windows 7 (incl in W8). I'll see what I can find out about the 2 W8 & if they should appear in all W8 systems or not.

Regards. . .

jcgriff2

SuperchargedSoup · Mar 13, 2013

Hi jcgriff,

I will reactivate DV in a little bit. Do I have to leave my laptop running, or can I let it sleep/hibernate?

Thanks,
-Soup

writhziden · Mar 13, 2013

I usually recommend doing your normal routine with Verifier running, but I also recommend letting it run for 48-72 hours, preferably 72 hours.

If you are only going to enable it for 24 hours, you may want to leave it on and manually sleep and hibernate it to see if that causes any problems.

SuperchargedSoup · Mar 13, 2013

Hey there writhziden,

I will try running it for as long as I can bare. Unfortunately, being a graphic design and architecture student, this is going to be hard, with photoshop and revit architecture being resource intensive programs.

Thanks for the help,
-Soup

jcgriff2 · Mar 14, 2013

Run Driver Verifier in "shifts" if you wish.

i.e., you don't have to select ALL 3rd party drivers at once. Break the groups up. Keep an eye on DV Query to see which have completed testing. Get work done; go on to the next batch when time permits.

SuperchargedSoup · Mar 14, 2013

Hi,

So far its been pretty good, I think last night I experienced a BSOD, but I forgot to write down the error code. If you would like me to attach a file, just let me know. All I remember is that it had nothing to do with what the DV page said would happen; the error code was not linked to DV. Ill wait it out at least until tonight again (that will be 24 hours) and see what happens.

- Soup

SuperchargedSoup · Mar 15, 2013

Hi again,

So I have run it for 36 hours approx. I havent run into any real problems, apart from the amount of CPU capacity DV has been using. I remebered the BSOD that occured last night. The error code was: KMODE_EXCEPTION_NOT_HANDLED. Is this anything important?

Thanks again,
-Soup

jcgriff2 · Mar 15, 2013

Look in c:\windows\minidump -- get the dump, zip & attach.

SuperchargedSoup · Mar 15, 2013

Hi, once again,

Please find attached the compressed dump file of the KMODE_EXCEPTION_NOT_HANDLED BSOD.

Thanks,
-Soup

writhziden · Mar 15, 2013

Recommendations:

Disable Verifier first:

Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:

Code:

verifier /reset

-> Restart your computer.

Norton is still installed. Norton was directly blamed in six of your previous crashes. Remove it and re-enable Defender to see if the system is more stable. You can always add it back later and work with Norton support if it ends up providing stability with it off the system and stability reduces with Norton installed.

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

The most recent crash was caused by your New DeathAdder Mouse driver. The driver is pre-Windows 8 and may cause problems. See if an update is available, and if not, consider replacing the device with one that is Windows 8 compatible.

danew.sys Tue Mar 23 02:37:33 2010 (4BA87DCD)
New DeathAdder Mouse driver
http://www.carrona.org/drivers/driver.php?id=danew.sys

You also have some drivers that are known to cause blue screens installed. Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system by choosing to uninstall the software through the installer utility.

AiCharger.sys Thu Sep 22 20:04:40 2011 (4E7BE938)
Asus Charger Driver
Likely BSOD cause - haven't seen recently (15Jan2013)
http://www.carrona.org/drivers/driver.php?id=AiCharger.sys

sptd.sys Sat Aug 18 15:05:38 2012 (503003A2)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
http://www.carrona.org/drivers/driver.php?id=sptd.sys

Outdated and Problematic Drivers:

You should update/replace/remove the following drivers. Any drivers that are known to cause BSODs, please remove the software or remove the drivers and then remove the device; steps to do so are given after the list of outdated drivers. If you have ASACPI.sys installed, make sure it is updated and not pre-2009; pre-2009 versions are known to cause BSODs:

ASMMAP64.sys Thu Jul 2 03:13:26 2009 (4A4C7A36)
LENOVO ATK Hotkey ATK0101 ACPI UTILITY
http://www.carrona.org/drivers/driver.php?id=ASMMAP64.sys

VKbms.sys Thu Sep 30 10:16:33 2010 (4CA4B7E1)
HID mini driver for USB Fx2 Device (Razer driver)
http://www.carrona.org/drivers/driver.php?id=VKbms.sys

atkwmiacpi64.sys Tue Sep 6 19:44:52 2011 (4E66CC94)
ATK WMIACPI Utility
http://www.carrona.org/drivers/driver.php?id=atkwmiacpi64.sys

To update drivers, make sure to download the drivers from the manufacturer and not using 3rd party programs. Your drivers should be found from your motherboard support site (ASUS, Gigabyte, MSI, etc.) or your vendor support site (Dell, HP, Toshiba, Sony, etc.) first. If you have devices you bought yourself, the drivers for those devices need to be downloaded from the manufacturer support site for those devices. If you need help, let us know.

To remove drivers, do so by uninstalling the device or software associated with the driver. Devices can be uninstalled through device manager, and then the device itself should be physically removed from the system if no driver updates are available for the device. If it does not make sense to remove the device, i.e. the device is a motherboard, please ask us for further assistance.

Uninstall or change a program

Open Device Manager

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

Code:

[font=lucida console]**************************Thu Mar 14 01:35:01.568 2013 (UTC - 6:00)**************************
[COLOR=RED][B]ASMMAP64.sys              Thu Jul  2 03:13:26 2009 (4A4C7A36)[/B][/COLOR]
[COLOR=RED][B]danew.sys                 Tue Mar 23 02:37:33 2010 (4BA87DCD)[/B][/COLOR]
[COLOR=RED][B]VKbms.sys                 Thu Sep 30 10:16:33 2010 (4CA4B7E1)[/B][/COLOR]
[COLOR=RED][B]atkwmiacpi64.sys          Tue Sep  6 19:44:52 2011 (4E66CC94)[/B][/COLOR]
[COLOR=RED][B]AiCharger.sys             Thu Sep 22 20:04:40 2011 (4E7BE938)[/B][/COLOR]
GEARAspiWDM.sys           Thu May  3 13:56:17 2012 (4FA2E2E1)
SYMEVENT64x86.SYS         Wed May 23 18:52:24 2012 (4FBD8648)
AsHIDSwitch64.sys         Wed May 30 20:38:32 2012 (4FC6D9A8)
Rt630x64.sys              Tue Jun 12 07:37:53 2012 (4FD74631)
IntcDAud.sys              Tue Jun 19 08:40:51 2012 (4FE08F73)
HECIx64.sys               Mon Jul  2 16:14:58 2012 (4FF21D62)
RtsBaStor.sys             Mon Jul  2 23:55:21 2012 (4FF28949)
dump_iaStorA.sys          Mon Jul  9 14:42:33 2012 (4FFB4239)
iaStorA.sys               Mon Jul  9 14:42:33 2012 (4FFB4239)
RTKVHD64.sys              Tue Jul 17 07:11:37 2012 (50056489)
SYMNETS.SYS               Fri Jul 20 20:07:07 2012 (500A0ECB)
Ironx64.SYS               Mon Jul 23 18:34:50 2012 (500DEDAA)
igdkmd64.sys              Tue Jul 31 16:05:35 2012 (501856AF)
EraserUtilRebootDrv.sys   Tue Jul 31 17:36:50 2012 (50186C12)
eeCtrl64.sys              Tue Jul 31 17:36:51 2012 (50186C13)
kbfiltr.sys               Wed Aug  1 21:22:22 2012 (5019F26E)
athw8x.sys                Thu Aug 16 01:01:18 2012 (502C9ABE)
ccSetx64.sys              Thu Aug 16 15:18:11 2012 (502D6393)
[COLOR=RED][B]sptd.sys                  Sat Aug 18 15:05:38 2012 (503003A2)[/B][/COLOR]
IDSvia64.sys              Tue Aug 28 20:48:40 2012 (503D8308)
AsusTP.sys                Mon Oct 29 12:23:54 2012 (508EC9BA)
intelppm.sys              Mon Nov  5 20:55:02 2012 (50988A16)
wacomrouterfilter.sys     Thu Nov 15 10:39:44 2012 (50A528E0)
nvlddmkm.sys              Fri Nov 30 20:24:02 2012 (50B97852)
nvpciflt.sys              Fri Nov 30 20:24:28 2012 (50B9786C)
wachidrouter.sys          Mon Dec  3 17:31:47 2012 (50BD4473)
EX64.SYS                  Thu Dec 20 02:22:39 2012 (50D2D8DF)
ENG64.SYS                 Thu Dec 20 02:24:21 2012 (50D2D945)
BHDrvx64.sys              Fri Jan 11 11:50:17 2013 (50F05EE9)
SYMDS64.SYS               Wed Jan 16 18:56:45 2013 (50F75A5D)
SYMEFA64.SYS              Fri Jan 18 17:31:37 2013 (50F9E969)
SRTSP64.SYS               Fri Jan 25 14:26:16 2013 (5102F878)
SRTSPX64.SYS              Fri Jan 25 14:30:05 2013 (5102F95D)
[/font]

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

[font=lucida console]**************************Thu Mar 14 01:35:01.568 2013 (UTC - 6:00)**************************
Loading Dump File [C:\Users\writh ziden\Downloads\2013_03_15\SuperchargedSoup\031413-65734-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]1 days 0:22:37.307[/B]
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by :[B]danew.sys ( danew+6da )[/B]
BugCheck [B]1E, {ffffffffc0000047, fffff80008ce34d4, 100000001, fffffa8000000001}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
Arguments: 
Arg1: ffffffffc0000047, The exception code that was not handled
Arg2: fffff80008ce34d4, The address that the exception occurred at
Arg3: 0000000100000001, Parameter 0 of the exception
Arg4: fffffa8000000001, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000047
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x1E_c0000047_danew+6da[/B]
CPUID:        "Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: [B]2494[/B]
  BIOS Version                  K55VD.404
  BIOS Release Date             08/20/2012
  Manufacturer                  ASUSTeK COMPUTER INC.
  Product Name                  K55VD
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

Win 8 x64 BSOD's - DPC_WATCHDOG_VIOLATION

Member

Administrator, .NET/UWP Developer

Member

Member

Attachments

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

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

Member

Member

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

Member

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

Member

Administrator, .NET/UWP Developer

Member

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

Member

Member

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

Member

Attachments

Administrator, .NET/UWP Developer

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

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

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

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

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

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