Windows 8 and 8.1 Forums


Recurring Watchdog Violation

  1. #11


    Posts : 5,139
    Win8.1Pro - Finally!!!


    We don't know if the drivers are still loading.
    The way to check is to wait for the next BSOD - and look at the dump file to see if they're still there.

    A "rough and ready" test is to rename those drivers (in C:\Windows\System32\drivers) to something else.
    Then reboot. If you get the inaccessible boot device - then they're most likely loading.
    But then you'll have to use System Restore and rename the files (as in the last part of my previous suggestion) in order to get back into Windows.

    If that's the case, then it's time to consider a fresh install (although there may be entries in the registry that haven't been checked)
    If the Silicone Image drivers come back after a "Clean" install of Windows - then you'll have to consider that this might be an incompatibility between your system and Win8.1 (another thing to check is in your UEFI/BIOS to see if there's a setting to turn off a Silicone Image controller).

    Unfortunately, the more complicated/advanced the system is - the more possibilities there are for problems. We'll keep looking at things until we find the problem - or decide if it's an unfixable incompatibility.

    Good luck!

      My System SpecsSystem Spec

  2. #12


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Just FYI, this poster had BSOD issues with a Silicone Image card and drivers that dated from 200y.
    They fixed them by removing the card (which, presumably stopped the drivers from loading.

    I think that if we manage to get rid of the Silicone Image drivers from your system - the BSOD's will most likely stop.
    Unfortunately, the only way to tell if they've stopped is to wait....
    How long? Well, that depends on a lot of things - but I generally say:
    - after 1 week it's safe to say that it may be fixed
    - after 2 weeks it's probably safe to say that it's fixed.

    Good luck!
      My System SpecsSystem Spec

  3. #13


    Posts : 8
    Windows 8.1 x64


    The card that used the SI drivers was long gone and the BSOD continued.

    I had not removed the devmg entries because they were hidden (thanks for that, I learned something new). I got rid of both entries.

    Also, updated the audio drivers to the very latest. (they had 2 updates inside of a week, and I checked everything else, chipset, lan etc to see if there had been yet another update.). I will also try going back 2 version of the video drivers. Hopefully these actions will solve the issue.

    I guess time will tell. I would do the fresh install (cheaper that a new computer) but I could still spend the hours doing it and end up with the same problem. Plus, MS doesn't make it easy for a fresh 8.1 install, but that's beside the point.

    I'll update as when I have more info. I'm keeping my fingers crossed.

    Thank you very much!!!

    TB
    Last edited by TangoBravo; 19 Nov 2013 at 23:48.
      My System SpecsSystem Spec

  4. #14


    Posts : 8
    Windows 8.1 x64


    "I thought I was out....and they pull me back in"

    I was jubilant and relieved...gone 2 whole days, of heavy usage...and no watchdog BSOD.....

    But no, showed up again....

    I've attached the SF output and a link to the kernel memory dmp.

    Kernel mem dump: http://sdrv.ms/1i0dKX3
    (about 700megs)

    Thank you again for you help and your patience in clearing this up.

    TB
      My System SpecsSystem Spec

  5. #15


    Posts : 5,139
    Win8.1Pro - Finally!!!


    No significant changes in this full memory dump - still a processor has hung and we don't have any decent info about what hung it.
    The only difference that I noted was the presence of USB drivers in the memory dump driver listing.

    What USB devices do you have? Do any have audio capabilities (sound in or out)?

    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\John\Downloads\MEMORY(1).DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Deferred                                       srv*c:\SymcachePublic*http://ctxsym.citrix.com/symbolsad/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;srv*c:\SymcachePublic*http://ctxsym.citrix.com/symbolsad/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    Machine Name:
    Kernel base = 0xfffff803`18803000 PsLoadedModuleList = 0xfffff803`18ac7990
    Debug session time: Thu Nov 21 15:25:32.369 2013 (UTC - 5:00)
    System Uptime: 0 days 22:49:34.093
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {18, 0, ffffd00020840180, 6}
    
    Page 4541f1 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454149 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd00020840180, The PRCB address of the hung processor.
    Arg4: 0000000000000006, 0.
    
    Debugging Details:
    ------------------
    
    Page 4541f1 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454149 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    Page 454600 not present in the dump file. Type ".hh dbgerr004" for details
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  d
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff803`1a232c58 fffff803`18974f13 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffd000`20840180 : nt!KeBugCheckEx
    fffff803`1a232c60 fffff803`1885781b : 00000000`00000001 fffff803`18af1180 00000000`00000001 fffff803`18af1180 : nt! ?? ::FNODOBFM::`string'+0x13d83
    fffff803`1a232cf0 fffff803`1885748c : 00000000`00000001 00000000`00000000 fffff803`1a232e30 fffff803`18a9d920 : nt!KiUpdateRunTime+0x57
    fffff803`1a232d30 fffff803`189d630c : fffff803`18acf3a8 fffff803`1885d813 fffff803`18af1180 00000000`00000002 : nt!KiUpdateTime+0x63c
    fffff803`1a232f10 fffff803`18f8ae5f : ffffd000`00400a02 00000000`00000001 fffff800`00c01ba0 00000000`00008101 : nt!KeClockInterruptNotify+0x5c
    fffff803`1a232f40 fffff803`18899343 : fffff803`18fd7900 00000000`00000008 fffff803`1a232f50 00000000`00000010 : hal!HalpTimerClockInterrupt+0x4f
    fffff803`1a232f70 fffff803`1895212a : fffff803`18fd7900 ffffe000`02680398 fffff803`1a224c58 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
    fffff803`1a232fb0 fffff803`18952a9b : 00000000`00000000 00000000`000000ff fffff803`1a224788 fffff803`18f8a627 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    fffff803`1a224760 fffff803`18897e00 : 00000000`00000000 ffffe000`03545000 00000000`00000002 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xfb
    fffff803`1a2248f0 fffff803`18897dc2 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x20
    fffff803`1a224920 fffff800`0272907e : ffff1726`ec0bacc0 ffffe000`0267fb40 00000000`00000000 ffffe000`04c3c1f0 : nt!KeAcquireSpinLockRaiseToDpc+0x32
    fffff803`1a224950 fffff800`02728885 : 00000000`00000006 fffff803`1885fa04 ffffe000`0267fac0 fffff803`1a224c58 : USBPORT!USBPORT_ProcessNeoStateChangeList+0x3e
    fffff803`1a2249c0 fffff803`188b0f64 : ffffe000`0267fb40 fffff803`1a224a79 fffff803`1a224c60 00000000`00000002 : USBPORT!USBPORT_DM_TimerDpc+0x25
    fffff803`1a224a00 fffff803`188b1478 : 00000000`00000000 ffffe000`0271f250 fffff803`18af1180 fffff803`18af5980 : nt!KiProcessExpiredTimerList+0x1d8
    fffff803`1a224ae0 fffff803`1890d478 : fffff803`18af1180 00000000`002d7800 00000000`002fd3a8 00000000`002fd3c0 : nt!KiExpireTimerTable+0x218
    fffff803`1a224b80 fffff803`1885dabc : ffffe000`0271f010 00000000`00000001 fffff803`1a224d50 fffff803`18858fbc : nt!KiTimerExpiration+0x148
    fffff803`1a224c30 fffff803`189547ea : fffff803`18af1180 fffff803`18af1180 00000000`001a3fe0 fffff803`18b49a80 : nt!KiRetireDpcList+0x19c
    fffff803`1a224da0 00000000`00000000 : fffff803`1a225000 fffff803`1a21f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_8_proc_analysis_inconclusive
    
    FAILURE_ID_HASH:  {f60c102e-9b2c-017b-9309-e4af1999e360}
    
    Followup: MachineOwner
    ---------
    
    0: kd> !prc 0
    No export prc found
    0: kd> !prcb 0
    PRCB for Processor 0 at fffff80318af1180:
    Current IRQL -- 13
    Threads--  Current fffff80318b49a80 Next ffffe00005564080 Idle fffff80318b49a80
    Processor Index 0 Number (0, 0) GroupSetMember 1
    Interrupt Count -- 0524d98c
    Times -- Dpc    00000448 Interrupt 0000056d 
             Kernel 001b9e1f User      0000d341 
    0: kd> !prcb 6
    PRCB for Processor 6 at ffffd00020840180:
    Current IRQL -- 0
    Threads--  Current ffffd0002084c340 Next ffffe000031f8880 Idle ffffd0002084c340
    Processor Index 6 Number (0, 6) GroupSetMember 40
    Interrupt Count -- 04b1d10d
    Times -- Dpc    000017f5 Interrupt 000005ae 
             Kernel 001b7508 User      0000fa3b 
    0: kd> !irql 0
    Debugger saved IRQL for processor 0x0 -- 13
    0: kd> !irql 6
    Debugger saved IRQL for processor 0x6 -- 0 (LOW_LEVEL)
    0: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff803`1a232c58 fffff803`18974f13 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffd000`20840180 : nt!KeBugCheckEx
    fffff803`1a232c60 fffff803`1885781b : 00000000`00000001 fffff803`18af1180 00000000`00000001 fffff803`18af1180 : nt! ?? ::FNODOBFM::`string'+0x13d83
    fffff803`1a232cf0 fffff803`1885748c : 00000000`00000001 00000000`00000000 fffff803`1a232e30 fffff803`18a9d920 : nt!KiUpdateRunTime+0x57
    fffff803`1a232d30 fffff803`189d630c : fffff803`18acf3a8 fffff803`1885d813 fffff803`18af1180 00000000`00000002 : nt!KiUpdateTime+0x63c
    fffff803`1a232f10 fffff803`18f8ae5f : ffffd000`00400a02 00000000`00000001 fffff800`00c01ba0 00000000`00008101 : nt!KeClockInterruptNotify+0x5c
    fffff803`1a232f40 fffff803`18899343 : fffff803`18fd7900 00000000`00000008 fffff803`1a232f50 00000000`00000010 : hal!HalpTimerClockInterrupt+0x4f
    fffff803`1a232f70 fffff803`1895212a : fffff803`18fd7900 ffffe000`02680398 fffff803`1a224c58 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
    fffff803`1a232fb0 fffff803`18952a9b : 00000000`00000000 00000000`000000ff fffff803`1a224788 fffff803`18f8a627 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea (TrapFrame @ fffff803`1a232e70)
    fffff803`1a224760 fffff803`18897e00 : 00000000`00000000 ffffe000`03545000 00000000`00000002 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xfb (TrapFrame @ fffff803`1a224760)
    fffff803`1a2248f0 fffff803`18897dc2 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x20
    fffff803`1a224920 fffff800`0272907e : ffff1726`ec0bacc0 ffffe000`0267fb40 00000000`00000000 ffffe000`04c3c1f0 : nt!KeAcquireSpinLockRaiseToDpc+0x32
    fffff803`1a224950 fffff800`02728885 : 00000000`00000006 fffff803`1885fa04 ffffe000`0267fac0 fffff803`1a224c58 : USBPORT!USBPORT_ProcessNeoStateChangeList+0x3e
    fffff803`1a2249c0 fffff803`188b0f64 : ffffe000`0267fb40 fffff803`1a224a79 fffff803`1a224c60 00000000`00000002 : USBPORT!USBPORT_DM_TimerDpc+0x25
    fffff803`1a224a00 fffff803`188b1478 : 00000000`00000000 ffffe000`0271f250 fffff803`18af1180 fffff803`18af5980 : nt!KiProcessExpiredTimerList+0x1d8
    fffff803`1a224ae0 fffff803`1890d478 : fffff803`18af1180 00000000`002d7800 00000000`002fd3a8 00000000`002fd3c0 : nt!KiExpireTimerTable+0x218
    fffff803`1a224b80 fffff803`1885dabc : ffffe000`0271f010 00000000`00000001 fffff803`1a224d50 fffff803`18858fbc : nt!KiTimerExpiration+0x148
    fffff803`1a224c30 fffff803`189547ea : fffff803`18af1180 fffff803`18af1180 00000000`001a3fe0 fffff803`18b49a80 : nt!KiRetireDpcList+0x19c
    fffff803`1a224da0 00000000`00000000 : fffff803`1a225000 fffff803`1a21f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    0: kd> ~6
    6: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    6: kd> r if
    if=0
    The Silicone Image drivers remain - and they are the most likely issue here. As you can't remove the Silicone Image drivers without rendering the system unbootable - I'd suggest that you try a "clean install" of Windows.
    Instructions here: Canned Speeches

    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! :

    SiWinAcc.sys Mon Nov 1 15:23:29 2004 (41868D31)
    Silicon Image driver - comes with package for the SIxxxx drivers
    http://www.carrona.org/drivers/driver.php?id=SiWinAcc.sys

    SiRemFil.sys Wed Oct 18 18:20:39 2006 (4536A8B7)
    Silicon Image driver
    http://www.carrona.org/drivers/driver.php?id=SiRemFil.sys



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Thu Nov 21 15:25:32.369 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\112113-7531-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 22:49:34.093
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {18, 0, ffffd00020840180, 6}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd00020840180, The PRCB address of the hung processor.
    Arg4: 0000000000000006, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    CPUID:        "Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz"
    MaxSpeed:     3070
    CurrentSpeed: 3051
      BIOS Version                  6.00 PG
      BIOS Release Date             08/25/2011
      Manufacturer                  OEM
      Product Name                  OEM
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Thu Nov 21 15:25:32.369 2013 (UTC - 5:00)**************************
    SiWinAcc.sys                Mon Nov  1 15:23:29 2004 (41868D31)
    SiRemFil.sys                Wed Oct 18 18:20:39 2006 (4536A8B7)
    truecrypt.sys               Tue Feb  7 04:09:36 2012 (4F30EA50)
    PxHlpa64.sys                Tue Apr 24 13:26:29 2012 (4F96E245)
    vmci.sys                    Fri May 17 21:19:18 2013 (5196D716)
    nvhda64v.sys                Sun Jun 16 08:38:07 2013 (51BDB1AF)
    VMNET.SYS                   Thu Jul 18 15:42:50 2013 (51E8453A)
    vmnetadapter.sys            Thu Jul 18 15:43:00 2013 (51E84544)
    vmnetbridge.sys             Thu Jul 18 15:43:47 2013 (51E84573)
    vsock.sys                   Wed Jul 31 22:46:10 2013 (51F9CBF2)
    Rt630x64.sys                Thu Aug 15 02:23:59 2013 (520C73FF)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
    tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
    hcmon.sys                   Wed Oct  9 11:03:51 2013 (52557057)
    vmnetuserif.sys             Fri Oct 18 14:19:38 2013 (52617BBA)
    vmx86.sys                   Fri Oct 18 15:34:39 2013 (52618D4F)
    SCDEmu.SYS                  Wed Oct 23 10:10:54 2013 (5267D8EE)
    RTKVHD64.sys                Tue Nov  5 06:39:41 2013 (5278D8FD)
    nvlddmkm.sys                Mon Nov 11 08:24:05 2013 (5280DA75)
    
    http://www.carrona.org/drivers/driver.php?id=SiWinAcc.sys
    http://www.carrona.org/drivers/driver.php?id=SiRemFil.sys
    http://www.carrona.org/drivers/driver.php?id=truecrypt.sys
    http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
    http://www.carrona.org/drivers/driver.php?id=vmci.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
    http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
    http://www.carrona.org/drivers/driver.php?id=vsock.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=tap0901.sys
    http://www.carrona.org/drivers/driver.php?id=hcmon.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
    http://www.carrona.org/drivers/driver.php?id=vmx86.sys
    http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
      My System SpecsSystem Spec

  6. #16


    Posts : 8
    Windows 8.1 x64


    Thanks U, for looking at this.

    I've already updated everything that I could and still keep a booting system. I tried going into the registry and taking out everything from SI. As you probably know, that didn't work.

    I do have a USB headset that I'm taking out.

    I wouldn't mind biting the bullet and doing a clean install over the Thanksgiving Holiday. My concern is that we don't really know for sure what the problem is. It's might be those old SI drivers, but I could do the clean install and still end up with the same problem.

    I'm also told that MS (in it's infinite wisdom) only allows one reactivation of W8. (mind you, this is after not allowing you to download a 8.1 ISO, but making a legal user go through pirate like tricks to get it. thanks to winsupersite on this).

    The best option is getting a new MB/processor but that's not an option right now. So I guess I'll just trug along expecting periodic BSODs.

    Funny thing is that I think that every time I get a "video driver has restarted error" the BSOD comes not long after that. So I guess I'll just restart once I get the video driver error.

    I tell you this, the reason MS is still in business is because of people like you who help out. MS could not support the biz model of actually have to support a problematic OS. (and yes, I blame the OS for allowing drivers and other things to interfere with it's operation. The buck has to stop somewhere. Just because we get used to expecting these problems doesn't make it right. After all, this isn't windows 1 or 2 or 3. Maybe around windows 59 the BSODs will be fewer ).

    Ok, enough pointless venting. Thanks again U, for you help.

    Maybe a miracle will solve it and I won't see that ever so popular BSOD screen. Then again, I find a lottery ticket on the sidewalk....

    Thanks again for your help.

    TB
    Last edited by TangoBravo; 23 Nov 2013 at 20:46.
      My System SpecsSystem Spec

  7. #17


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Do you have another video card that you can try?
    Other than that I think that the OS install is the next step - but you're right, it may not fix things.
    Good luck!
      My System SpecsSystem Spec

Page 2 of 2 FirstFirst 12
Recurring Watchdog Violation
Related Threads
Dpc Watchdog Violation (133) in BSOD Crashes and Debugging
Hi, I have a problem. But I do not know english. I uploaded the dump file. Thanks for help.
DPC WatchDog Violation in BSOD Crashes and Debugging
I have Samsung NP-RV515 A01-US. I upgraded to 128gb ssd. I got dpc watchdog violation for the first time today after runing updates. Uninstalling doesn't help. Upon boot every time after 60 seconds. No luck. I know there are threads here about this but not my exact issue. After running...
DPC Watchdog Violation Windows 8.1 in BSOD Crashes and Debugging
Lately I have been experiencing up multiple BSODs a day, all relating to DPC Watchdog Violation. This only happens when playing games and occurs usually during an initial loading screen. After about three restarts due to a BSOD I can finally load up the game and play. It is not confined to a single...
Solved BSOD DPC watchdog violation in BSOD Crashes and Debugging
hello there, ive upgraded from win7 to win 8 , and im having the same problem that the above dude is having, every while the BSOD appeares with eror DPC_WATCHDOG VILOLATION. Between, my laptop is a hp pavilion dv6 10404 i7 720 quad 1.6 6GB Ram ATI mobility HD 5650 VGA
Please help me out, DPC watchdog violation. in BSOD Crashes and Debugging
I am getting DPC watchdog violation issue when i turned on my laptop today...I dont know what to do now, please help me out.:cry:
DPC Watchdog Violation in BSOD Crashes and Debugging
Hello, I recently refreshed Windows 8 have been running into "Watchdog" reboots. My guess is that it is something network related. I am using a Linksys wmp54g adapter, which hasn't been supported by Linksys for a couple of years. The funny thing is that I never had this issue with my...
BSOD Watchdog Violation in BSOD Crashes and Debugging
I Upgraded from vista after trying the comusmer preview a few moths back(which worked flawlessly btw) and now after installed windows 8 I've come across this watchdog violation. I'm assuming its a driver error. I have an ati HD4870 and I know AMD will stop supporting these older graphics cards and...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook