DPC Watchdog Error

I got a DPC watchdog BSOD on my fairly new laptop. I have Win 8 on the host machine, and VMWare running on an external SSD with Win 7. I run nothing on the Win 8 machine other than VMWare.
I saved the dump file which I've uploaded. unfortunately the anti-spam is not allowing me to post the link so I'll have to resort to showing it in pieces.
Protocol: https followed by colon slash slash
Server: skydrive.live.com followed by slash
Request: redir followed by question mark
Query: resid=93FB9BB36FEFB0AA!106&authkey=!AJdhZ_mSxN_LUwE
After I clicked OK it rebooted the Win 8 host, and then it said it was configuring windows updates! Though, nothing shows up for today in the Win 8 Update log.
Recent activity on this machine:
installed and then removed Skype on host
Updated recommended drivers from Samsung
A windows update failed on the 19th and then was successful on the 20th

Rich
You could upload it to Skydrive (or another file sharing service) and give us a link to it
 We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers
were loaded, and what was responsible.
You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
If you are overclocking stop.  (chances are if you dont know if you are, you are not)a
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.
The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)
 *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
Link for how to  upload below.
http://www.wikihow.com/Use-SkyDrive
To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
Please also run MSinfo32 and upload the output as well.
To run MSinfo32 please go to start>run>MSinfo32
Go to "file" "save" and upload the saved file with the DMPS
(Instructions for XP, Vista, Win 7, Win 8)
Team Zigzag3143.com
MS-MVP 2010, 2011, 2012 Team ZigZag

Similar Messages

  • Windows 8 Dpc Watchdog Violation error

    please i would like to know how to fix this watchdog violation error i am getting since monday.
    here is the link to dump files
    http://www.mediafire.com/download.php?ney1rln6fgumnsn

    * 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: 0000000000000283, The DPC time count (in ticks).
    Arg3: 0000000000000282, 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: avgnsa.exe
    CURRENT_IRQL: d
    TAG_NOT_DEFINED_c000000f: FFFFF800EF4A0FB0
    LAST_CONTROL_TRANSFER: from fffff800ef7dd6ef to fffff800ef684040
    STACK_TEXT:
    fffff800`ef4a0618 fffff800`ef7dd6ef : 00000000`00000133 00000000`00000000 00000000`00000283 00000000`00000282 : nt!KeBugCheckEx
    fffff800`ef4a0620 fffff800`ef6aff06 : 00000000`00000005 00000000`0003fb67 fffff800`ef4a07a0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13c80
    fffff800`ef4a06a0 fffff800`efd74eca : fffffa80`04d16870 00000000`000000dd 00000000`8068aecd 00000000`00000001 : nt!KeUpdateTime+0x41b
    fffff800`ef4a0890 fffff800`ef67dbfa : 00000009`7a925d51 00000000`89ed155a fffff800`efd9e580 fffff880`00000000 : hal!HalpTimerClockInterrupt+0x86
    fffff800`ef4a08c0 fffff800`ef673903 : 00000000`00000001 fffff800`ef88d000 00000000`00000001 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x1aa
    fffff800`ef4a0a50 fffff800`ef6b0315 : 00000000`00000002 fffff800`ef88d000 fffff880`01541180 fffff800`ef6ad033 : nt!KxWaitForSpinLockAndAcquire+0x23
    fffff800`ef4a0a80 fffff880`01b68ff2 : fffff800`ef4a0b49 fffff800`ef8ff180 00000009`7494f883 fffff800`ef88d000 : nt!KeAcquireSpinLockRaiseToDpc+0x35
    fffff800`ef4a0ab0 fffff880`019b3626 : 00000000`00000000 fffffa80`03fe33f0 fffffa80`03fe3280 fffffa80`03fe33f0 : tcpip!TcpEnqueueTcbSend+0x72
    fffff800`ef4a0b80 fffff880`019b307b : fffffa80`042651a0 fffffa80`04d16870 00000000`00000000 000009a8`73d17274 : NETIO!StreamInjectRequestsToStack+0x23e
    fffff800`ef4a0c60 fffff880`019b2f21 : fffffa80`042651a0 00000000`00000000 00000000`00000008 ffff87fc`ec58fef4 : NETIO!StreamPermitDataHelper+0x5f
    fffff800`ef4a0c90 fffff800`ef679f38 : fffff800`ef901f00 fffff800`ef4a0e00 fffffa80`090463a0 00000000`00000000 : NETIO!StreamPermitRemoveDataDpc+0x81
    fffff800`ef4a0d00 fffff800`ef6aaeb0 : fffff800`ef8ff180 00000009`532a8f50 fffffa80`073b4680 00000000`00000025 : nt!KiExecuteAllDpcs+0x198
    fffff800`ef4a0e40 fffff800`ef6aa8a5 : 00000000`00000000 fffff800`ef8ff180 fffff880`0c8bc270 fffffa80`090463a0 : nt!KiRetireDpcList+0xd0
    fffff800`ef4a0fb0 fffff800`ef6aa6a9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    fffff880`0c8bc1c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    NETIO!StreamInjectRequestsToStack+23e
    fffff880`019b3626 8bf0 mov esi,eax
    IMAGE_NAME: NETIO.SYS
    fffff880`0197b000 fffff880`019ea000 NETIO (pdb symbols) c:\sym\dl\netio.pdb\F6A6ADDF9B3C4AECAFFCADC1489938262\netio.pdb
    Loaded symbol image file: NETIO.SYS
    Mapped memory image file: c:\sym\dl\NETIO.SYS\507656246f000\NETIO.SYS
    Image path: \SystemRoot\system32\drivers\NETIO.SYS
    Image name: NETIO.SYS
    Timestamp: Thu Oct 11 07:16:20 2012 (50765624)
    CheckSum: 000798F6
    ImageSize: 0006F000
    File version: 6.2.9200.16433
    Product version: 6.2.9200.16433
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 3.6 Driver
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: netio.sys
    OriginalFilename: netio.sys
    ProductVersion: 6.2.9200.16433
    FileVersion: 6.2.9200.16433 (win8_gdr.121010-1704)
    FileDescription: Network I/O Subsystem
    LegalCopyright: © Microsoft Corporation. All rights reserved.
    Update all your network driver and tools like AVG.
    "A programmer is just a tool which converts caffeine into code"

  • DPC WATCHDOG VIOLATION error.. Help please!

    I have a fairly new computer, like 1 month old and it's been having no trouble at all!
    But recently, there's this error that's been bugging me... "DPC_WATCHDOG_VIOLATION"
    Anyways, I've tried looking for solutions and none of them worked at all!
    Those people with similar problems posted their minidumps folder so here is mine https://skydrive.live.com/redir?resid=8890455B2D279646%21360
    This error randomly happens (mainly when I watch a video or play games) and it's really annoying!
    Thanks in advanced.

    MR A
    These were all Related to
    rtl8192su.sys RTL8192S USB NDIS Driver from Realtek Semiconductor Corporation.  YOurs is 4 years old.  I would install the newest driver available.
    BugCheck 133, {0, 501, 500, 0}
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 133, {0, 501, 500, 0}
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 133, {0, 501, 500, 0}
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 133, {0, 501, 500, 0}
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck D1, {0, 2, 0, fffff80000a5b688}
    Probably caused by : RTL8192su.sys ( RTL8192su+11d79 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    SYSTEM UP-TIME
    System Uptime: 0 days 3:05:42.735
    System Uptime: 0 days 1:08:18.344
    System Uptime: 0 days 5:00:43.657
    System Uptime: 0 days 5:33:28.469
    System Uptime: 0 days 7:48:15.074
    **************************Fri Jan 17 21:20:40.097 2014 (UTC - 5:00)**************************
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\SysnativeBSODApps\011714-21875-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: c:\symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff801`69214000 PsLoadedModuleList = 0xfffff801`694d8990
    Debug session time: Fri Jan 17 21:20:40.097 2014 (UTC - 5:00)
    System Uptime: 0 days 3:05:42.735
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 133, {0, 501, 500, 0}
    *** WARNING: Unable to verify timestamp for RTL8192su.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    Followup: MachineOwner
    0: kd> kd: Reading initial command '!analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q'
    * 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: LolClient.exe
    CURRENT_IRQL: d
    LAST_CONTROL_TRANSFER: from fffff80169385f7c to fffff80169361ca0
    STACK_TEXT:
    fffff801`6ac86c58 fffff801`69385f7c : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    fffff801`6ac86c60 fffff801`6926881b : fffff801`699e89b0 fffff801`69502180 ffffe000`04620038 00002385`29df0c24 : nt! ?? ::FNODOBFM::`string'+0x13ddc
    fffff801`6ac86cf0 fffff801`6926848c : 00000000`00000001 fffff801`6ac86d70 fffff801`6ac86e30 fffff801`694ae920 : nt!KiUpdateRunTime+0x57
    fffff801`6ac86d30 fffff801`693e731c : fffff801`694e03d8 fffff801`6926e813 fffff801`69502180 00000000`00000002 : nt!KiUpdateTime+0x63c
    fffff801`6ac86f10 fffff801`6999be5f : ffffd000`00400a02 ffffd000`20f105b0 fffff800`0272e090 ffffd000`00006101 : nt!KeClockInterruptNotify+0x5c
    fffff801`6ac86f40 fffff801`692aa343 : fffff801`699e8900 00000000`00000008 fffff801`6ac86f50 00000000`0000000c : hal!HalpTimerClockInterrupt+0x4f
    fffff801`6ac86f70 fffff801`6936312a : fffff801`699e8900 ffffe000`03e60060 ffffe000`0462003c ffffe000`03f3aa01 : nt!KiCallInterruptServiceRoutine+0xa3
    fffff801`6ac86fb0 fffff801`6936350f : ffffe000`03c20010 fffff801`6ac7ebd0 00000000`00000000 ffffe000`03c21500 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    fffff801`6ac7e9e0 fffff801`692a8e03 : ffffe000`04a47031 ffffe000`03ef7a5e ffffe000`03ef7740 ffff8eaa`316a9fd9 : nt!KiInterruptDispatchLBControl+0x11f
    fffff801`6ac7eb70 fffff801`692a8dc2 : 00000000`00000002 ffffe000`0462003c ffffe000`03e60000 00000000`00000001 : nt!KxWaitForSpinLockAndAcquire+0x23
    fffff801`6ac7eba0 fffff800`02b4eb26 : ffffe000`04a47001 ffffe000`03ef7750 00000000`00000001 ffffe000`03c660d9 : nt!KeAcquireSpinLockRaiseToDpc+0x32
    fffff801`6ac7ebd0 ffffe000`04a47001 : ffffe000`03ef7750 00000000`00000001 ffffe000`03c660d9 ffffe000`03c60025 : RTL8192su+0x3ab26
    fffff801`6ac7ebd8 ffffe000`03ef7750 : 00000000`00000001 ffffe000`03c660d9 ffffe000`03c60025 fffff800`02b4cc9f : 0xffffe000`04a47001
    fffff801`6ac7ebe0 00000000`00000001 : ffffe000`03c660d9 ffffe000`03c60025 fffff800`02b4cc9f ffffe000`03e60000 : 0xffffe000`03ef7750
    fffff801`6ac7ebe8 ffffe000`03c660d9 : ffffe000`03c60025 fffff800`02b4cc9f ffffe000`03e60000 fffff800`02b4eeda : 0x1
    fffff801`6ac7ebf0 ffffe000`03c60025 : fffff800`02b4cc9f ffffe000`03e60000 fffff800`02b4eeda ffffe000`03ef7750 : 0xffffe000`03c660d9
    fffff801`6ac7ebf8 fffff800`02b4cc9f : ffffe000`03e60000 fffff800`02b4eeda ffffe000`03ef7750 ffffe000`03ef7740 : 0xffffe000`03c60025
    fffff801`6ac7ec00 ffffe000`03e60000 : fffff800`02b4eeda ffffe000`03ef7750 ffffe000`03ef7740 ffffe000`03ef7720 : RTL8192su+0x38c9f
    fffff801`6ac7ec08 fffff800`02b4eeda : ffffe000`03ef7750 ffffe000`03ef7740 ffffe000`03ef7720 ffffe000`0462003c : 0xffffe000`03e60000
    fffff801`6ac7ec10 ffffe000`03ef7750 : ffffe000`03ef7740 ffffe000`03ef7720 ffffe000`0462003c ffffe000`03e60000 : RTL8192su+0x3aeda
    fffff801`6ac7ec18 ffffe000`03ef7740 : ffffe000`03ef7720 ffffe000`0462003c ffffe000`03e60000 fffff800`02b58d26 : 0xffffe000`03ef7750
    fffff801`6ac7ec20 ffffe000`03ef7720 : ffffe000`0462003c ffffe000`03e60000 fffff800`02b58d26 00000000`00000000 : 0xffffe000`03ef7740
    fffff801`6ac7ec28 ffffe000`0462003c : ffffe000`03e60000 fffff800`02b58d26 00000000`00000000 00000000`0000000a : 0xffffe000`03ef7720
    fffff801`6ac7ec30 ffffe000`03e60000 : fffff800`02b58d26 00000000`00000000 00000000`0000000a 00000000`000000a0 : 0xffffe000`0462003c
    fffff801`6ac7ec38 fffff800`02b58d26 : 00000000`00000000 00000000`0000000a 00000000`000000a0 00000000`000000a0 : 0xffffe000`03e60000
    fffff801`6ac7ec40 00000000`00000000 : 00000000`0000000a 00000000`000000a0 00000000`000000a0 00000000`00000000 : RTL8192su+0x44d26
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    RTL8192su+3ab26
    fffff800`02b4eb26 ?? ???
    SYMBOL_STACK_INDEX: b
    SYMBOL_NAME: RTL8192su+3ab26
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: RTL8192su
    IMAGE_NAME: RTL8192su.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 4cedfd9f
    FAILURE_BUCKET_ID: 0x133_DPC_RTL8192su+3ab26
    BUCKET_ID: 0x133_DPC_RTL8192su+3ab26
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • DPC Watchdog Violation in windows 8

    Hello everyone,
    my uncle just purchased my toshiba laptop model P55-A5200 last week. i had this problem now, when my pc is configuring windows updates at 15 % ,it  freezes and is having  DPC Watchdog Violation bluescreen errors and then when it was  about to restart, still appears the same, it can't proceed to windows 8. Instead, in the blue screen a "Recovery" appears and made me choose either restart my pc or see advanced repair options. i tried to choose "restart my pc" but still the same. when i choose "see advanced repair option" i don't know where to choose to. I also had this problem, I was not able to create recovery media in my usb.  PLEASE HELP ME. I don't know what to do ... see these images here that i attached. please please please help me...
    Attachments:
    imm_2013_09_18_07_34_07_320.JPG ‏26 KB
    imm_2013_09_18_07_34_24_9.JPG ‏26 KB
    imm_2013_09_18_07_35_11_929.JPG ‏25 KB

    Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Caused By Driver  : tm.sys
    Bug Check 0x133 DPC_WATCHDOG_VIOLATION
    Caused By Driver  : hal.dll
    The other dmp file was corrupt.
    The two files mentioned here don't help us, because they are Windows core system files.
    Attach a few more. Maybe we'll get better clues. You might zip up a bunch of them.
    Did you do a Refresh as I suggested?
    ==================================================
    Dump File         : 092013-58343-01.dmp
    Crash Time        : 9/20/2013 5:55:01 AM
    Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code    : 0x000000d1
    Parameter 1       : 00000000`00000aa0
    Parameter 2       : 00000000`00000002
    Parameter 3       : 00000000`00000000
    Parameter 4       : fffff880`1742c33b
    Caused By Driver  : tm.sys
    Caused By Address : tm.sys+1675433b
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Computer Name     :
    Full Path         : C:\Test\092013-58343-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 9200
    ==================================================
    ==================================================
    Dump File         : 091413-33500-01.dmp
    Crash Time        : 9/20/2013 5:54:52 AM
    Bug Check String  :
    Bug Check Code    : 0x00000133
    Parameter 1       : 00000000`00000001
    Parameter 2       : 00000000`00001e00
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : hal.dll
    Caused By Address : hal.dll+22e94
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Computer Name     :
    Full Path         : C:\Test\091413-33500-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 9200
    ==================================================
    -Jerry

  • GT60 2OC-030UK DPC Watchdog Violation

    Hi all. I bought a GT60 2OC laptop about two weeks ago for my studies and gaming at University and it has been nothing but a nightmare. At first it would bluescreen randomly but I managed to track the error down to the Killer drivers that were preinstalled. Slightly annoying that a laptop could be sold not in working condition but I updated them and all seemed to be well.
    Then the dreaded bluescreen struck again, while listening to music. It said DPC Watchdog Violation which from a bit of googling appears to be related to SSDs not being compatible with Windows 8. I'm sure this is not the case as surely nobody would sell a laptop with parts that aren't compatible, but I would like to know if there is a fix for this issue as it's happened within two weeks of me buying the laptop and I really want everything to be working before university.
    I'm also very disappointed with the laptop in general, my old PC had 3 BSOD's in it's 4 years of use, this laptop has had 4 BSOD's in two weeks. Any help would be greatly appreciated as I spent quite a lot of money on this and it's very upsetting that it doesn't work.

    Quote from: darkhawk on 29-August-13, 21:45:45
    Also....
    [can't post external links]
    Knowing that, were you trying to do anything at the time when the BSoD happened? Like plug headphones in or something to that effect?
    It might even be better to get the information from the system log to see what the exact error code was regarding the DPC Watchdog Violation. There might also be a driver associated with it that is causing the problem.
    I was listening to music like I usually do and it was halfway through a track. The music just stopped and when I turned to look at the screen it looked exactly like the image in the link you posted. I hadn't tried to do anything when the BSOD happened, it just sort of happened randomly. It's not done it again yet but the next time it does I will snap a picture on my phone if it will help.

  • Windows DPC Watchdog Violation

    My windows partition automatically installed updates overnight.  When I re-booted I received a DPC Watchdog Violation.  The power button re-booted the machine and it appears to be running ok.  Do I have a problem that needs to be addressed?  Appreciate any info and suggestions.

    perhaps this could help;
    http://pc.net/helpcenter/answers/windows_8_dpc_watchdog_violation

  • [linux-3.2] watchdog: error registering /dev/watchdog

    Today, kmod replaced module-init-tools, and after upgrading my system, noticed this error after udev loaded:
    Jan 6 07:44:41 localhost kernel: [ 4.528051] watchdog: INTCAMT: cannot register miscdev on minor=130 (err=-16).
    Jan 6 07:44:41 localhost kernel: [ 4.528088] watchdog: error registering /dev/watchdog (err=-16).
    Jan 6 07:44:41 localhost kernel: [ 4.528113] mei: unable to register watchdog device.
    Thankfully, nothing else happened and my system didn't go kaput. But reading the manpage, watchdog does appear to be important. Since udev errors were expected with the kmod upgrade, and this error never occurred before today (checked my /var/log/everything.log), it appears kmod is the likely culprit.
    Edit: Tried posting this to the ML, and discovered that the general public does not have write access to the ML. So if some developer thinks this is important, hopefully that person will see this post.
    Last edited by Sara (2012-01-09 00:12:41)

    I finally found some time to dig in the kernel source a bit and found that I was wrong. Sorry for the confusion. There's nothing wrong with the Intel MEI watchdog driver and the softdog is not involved at all. The truth is that the watchdog core functions only support 1 watchdog device via /dev/watchdog [1]. If the iTCO_wdt driver would use the watchdog core [2], we'd get the correct "only one watchdog can use /dev/watchdog." message and the IMEI watchdog registration would not be attempted. But it doesn't. It registers in a different way [3] and so the core does not "know" about another watchdog being already registered, attempts to register the IMEI watchdog and fails with the confusing "cannot register miscdev..." message.
    The bottom line is that the kernel supports only one watchdog and we (administrators) have to decide which device we want to use.
    [1] http://lxr.linux.no/linux+v3.2/drivers/ … dev.c#L344
    [2] http://lxr.linux.no/linux+v3.2/drivers/ … dog_core.c
    [3] http://lxr.linux.no/linux+v3.2/drivers/ … wdt.c#L854
    Last edited by laloch (2012-01-08 15:34:41)

  • MSI GT70-2OD - DPC Watchdog Violation

    Anybody having this issue with random blue screen of deaths, DPC Watchdog Violation?
    Today, I got two BSOD watching twitch streams. I thought it was a graphic driver issue, so I went back to a non-beta driver, but still getting the BSOD's.
    Any suggestions?
    BIOS version: E1763IMS.703
    EC Firmware version: 1763EMS1.513
    NVIDIA driver version: 335.23

    Quote from: Svet;103301
    flash your BIOS to the latest version .70W
    http://www.msi.com/product/nb/GT70_2OD.html#download
    I am scared of flashing the BIOS because I am on my second notebook, where I flashed the BIOS and I had the black screen of death. It didn't boot at all. No MSI splash screen.
    I don't remember on the first notebook if I chose the wrong file, but I followed the information to the letter.
    If it is the only way to fix it, then I guess I have no choice. I hope it does not mess it up.

  • Watchdog errors over the top

    Does anyone know or understand what this means:
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    This is a watchdog error coming from the following log:
    11-04-30 8:40:24 AM    kernel    45, Logic Pro (16722, 5051) delta from wd: 698250 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 5191) delta from wd: 993797 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 5332) delta from wd: 1221316 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 5470) delta from wd: 1481233 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 5609) delta from wd: 1686704 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 5746) delta from wd: 1913799 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 5885) delta from wd: 2165906 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 6024) delta from wd: 2576477 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 6171) delta from wd: 2848610 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 2 watchdogs for pid 3445, Logic Pro (16722, 6310) delta from wd: 216110 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 6449) delta from wd: 473097 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 6588) delta from wd: 727412 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 6728) delta from wd: 938213 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 6865) delta from wd: 1179726 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 7004) delta from wd: 1409492 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 7142) delta from wd: 1671657 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 7282) delta from wd: 1943231 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 7422) delta from wd: 2192631 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 7560) delta from wd: 2416331 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 7699) delta from wd: 2672049 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 2 watchdogs for pid 3445, Logic Pro (16722, 7838) delta from wd: 52727 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 7978) delta from wd: 268854 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16722, 8115) delta from wd: 509047 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16723, 62) delta from wd: 733408 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16723, 200) delta from wd: 970607 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16723, 1363) delta from wd: 1177856 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16723, 2524) delta from wd: 1401198 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16723, 3686) delta from wd: 1638339 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16723, 4848) delta from wd: 1814549 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16723, 6008) delta from wd: 2032219 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16723, 7171) delta from wd: 2282174 ns
    11-04-30 8:40:24 AM    kernel    performClientOutput returned e00002ee
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16724, 141) delta from wd: 2519894 ns
    11-04-30 8:40:24 AM    kernel    did 1 watchdogs for pid 3445, Logic Pro (16724, 1303) delta from wd: 2738454 ns
    This happens in LOGIC, GARAGEBAND, and when using FIREFOX.
    When this ERROR occurs all AUDIO is dropped out for a split second.
    I cannot work with audio drop outs -  as I do recording.
    Thanks

    Hi Andylloyd,
    I would like to take a look at your BT account for you. Please could you drop me an email to the email address found in my profile. Please make sure to include your BT account details and a link to this thread.
    Thanks
    Paddy,
    BTCare Community Mod
    If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
    We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)

  • 9i RAC watchdog error message

    My oracle 9i rac database shutdown during a long querying,and I found message in $ORACLE_HOME/oracm/log/nm.log:
    WatchdogPing failed.
    what can I do?

    I ran the OC4J, and java applet was started but still got the error message:
    "FRM-40010:cannot read form (my file's path goes here)userid='scott/tiger@machine's name'ssouserid=" debug='no'...."
    what's the problem now?

  • DPC Watchdog Violations

    This error in my laptop occurred twice
    and during both the errors I was pc was connected to internet and the internet connection was shared with my mobile phone.
    I want to know why this error occurred and is there any way out to this error
    PLEASE HELP ME.  

    It may help to look at the minidump files from the blue screen crashes with a debugger.
    Can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via a public folder on OneDrive or similar site?
    Here's a couple of links on using OneDrive (SkyDrive):
    http://windows.microsoft.com/en-ca/skydrive/add-photos-files-faq
    http://windows.microsoft.com/en-ca/onedrive/share-file-folder
    If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop
    Also, you do not necessarily have to zip up the minidump files, you can upload them one at a time

  • DPC Watchdog Violation - Fingerprint related?

    I get intermittent failures to load Windows 10 64.  I generally use hibernate and bring the PC up with a FP scan at the BIOS power on prompt.  I get to the Windows lock screen but the cursor is frozen.  It thinks about it for 5 or 10 seconds then blue screens me with the message that it's telling MS about the problem and it flags the subject error  as the cause.  PC then restarts and is generally OK on the second try.  I don't know how to troubleshoot this.  T440p

    Thanks for the suggestions - I've looked at the websites and they refer to Windows 8. Before I try anything, can you confirm that these solutions will also work with Windows 10?And as this started when I was using Windows 8 and then continued when I upgraded to Windows 10 I'm not sure that refreshing my version of Windows will help. Thanks Jemima

  • DPC Watchdog Violation

    I have been getting the BSOD in May. I bought this laptop in January and it didn't have this problem until May. Am trying to figure out a way to fix this problem. Currently I am running a full scan with Windows Defender to check if theres a virus. Can anybody suggest ways to fix this problem and what causes this problem?

    Hi, Please try:    https://www.xtremerain.com/tech/solutions/blog-id-552 Good luck.

  • DPC_WATCHDOG_VIOLATION Help!

    I'm having bsod lately while playing games and weird thing is it's only happens to some games only by far it only happens to The Wolf Among Us and The Walking Dead Season 2 which are telltale games and whenever I play them they freeze and the BSOD DPC_WATCHDOG_VIOLATION
    but what's bugging me is it's never happened to me while I'm playing TWD before but now after installing and playing The Wolf Among Us, both games starts freezing and THE BSOD dpc watchdog error appears.
    My laptop is not SSD cause it's 1tb and it doesn't happen to other games and it ONLY happens to Telltale games :(
    Please Help! (O_O)

    Hi,
    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
    If you don't know where .DMP files are located, here's how to get to them:
    1. Navigate to the %systemroot%\Minidump folder.
    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
    between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
    much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
    choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
    If you are going to use Onedrive but don't know how to upload to it, please visit the following:
    Upload photos and files to Onedrive.
    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
    Share files and folders and change permissions and view 'Get a link'.
    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
    If your computer is not generating .DMP files, please do the following:
    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
    drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
    log'.
    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
    4. Double check that the WERS is ENABLED:
    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
    Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
    If you cannot get into normal mode to do any of this, please do this via Safe Mode.
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • Watchdog timout errors on NI-7356 (-70035 NIMC_watchdogTimoutError)

    Hi,
    I have a test setup based on a NI-7356 controller. It controls 6-axis, performs contouring and high speed capture.
    I have two types of watchdog errors:
    1. The computer has to be cold started twice before the controller works. The first startup results in a watchdog timeout error making it unusable without a new cold start.
    2. Random watchdog errors (-70035 NIMC_watchdogTimoutError) occur when running the program. They usually occur on completion of a simple move or while intermediately halting a move. This can happen with or without high speed capture/contouring. These errors require a reset of the controller (no power cycling).
    I already reduced the number of calls to the controller (e.g. checking for motion complete every 50ms or more, updating contour buffers every 200ms, reading high speed capture buffers every 200ms) so it doesn't get flooded.
    Any ideas why this is happening? How can I solve this?
    Kind regards,
    Wouter

    Hello Thierry,
    I'm using Win7. I do not have the possibility to test on another system/OS.
    I've attached the requested reports. Thank you for taking the time to look into this.
    Best regards,
    Wouter
    Attachments:
    ni_support.zip ‏700 KB
    System Information.txt ‏4 KB

Maybe you are looking for

  • Creation of local field in ABAP Query

    Hi Please let me know how to create a local field in ABAP query. I am finding the option inactive in SQ01. Regards Priyadarshini

  • Updated my itouch gen 4 32g to Ios 5 and now itunes can't find music files

    I did a search and could not find anything about my specific issue.  I was hoping to get some help if possible. So I did the update to IOS 5 and everything went fine..........except for one thing.  I have all my music stored on an external hard drive

  • Re-load request

    I have loaded the data into PSA, and the request is loaded into Data Target successfully. For some reason, is there a way for me to reload this request (from PSA) into the Data Target again? How should I go about this? Pleasea advice, thanks.

  • Facetime with Google Chat

    On GMail you have the capability to open a video chat while in a chat with someone online.  I know that facetime operates off the same principal of contacting you through your e-mail address and I was wondering if it was possible to use facetime (or

  • Reader extensions render failed. What would be problem?

    Dear All, The form which I created using designer is working fine with acrobat, but when it opens in adobe reader all the scripts seems to be not working! Do we need to render the form with reader extensions before proceeding with adobe reader? With