Windows 8 and 8.1 Forums

Frequent BSODs

  1. #11


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


    Here's how to get rid of the 2 drivers. If you see any references to HotSpotShield or hssdrv6.sys - that's because I was rushed this morning (sorry!).....

    npf.sys:
    1) Create a Restore Point using System Restore
    2) Create a Repair disc (Recovery Drive in Win8.1):
    Win 7 - Go to Start...All Programs...Maintenance...Create a System Repair Disc
    Win 8 - Press "WIN" and "R" to open the Run dialog...type "RECDISC" (without the quotes) and press ENTER
    Win 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
    3) Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)
    4) Download this free program (Autoruns for Windows) and use it to disable any instances of npf.sys that are starting (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
    5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of npf.sys are "Uninstalled" (DO NOT DISABLE THESE).
    6) Check in the Services applet (services.msc) to be sure any instances of npf.sys are disabled.
    7) EXPERIMENTAL STEP (only try if you're certain of your abilities - I have not tried this step myself). Search the registry (use regedit.exe) to locate any entries that have the driver name (npf.sys). Delete these keys (it's advisable to back them up first - but you've also backed up the entire registry when creating a System Restore point in step 1. Alternatively, you can set the values in these keys to DISABLED (but the "how" of this is beyond the scope of this).
    8) Go to C:\Windows\System32\drivers and rename the npf.sys driver to npf.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers).


    In the event that the system doesn't boot:

    1) Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename npf.BAD to npf.sys
    Code:
    ren C:\Windows\System32\drivers\npf.BAD C:\Windows\System32\drivers\npf.sys
    21) Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.

    Good luck!

    tapoas.sys:
    1) Create a Restore Point using System Restore
    2) Create a Repair disc (Recovery Drive in Win8.1):
    Win 7 - Go to Start...All Programs...Maintenance...Create a System Repair Disc
    Win 8 - Press "WIN" and "R" to open the Run dialog...type "RECDISC" (without the quotes) and press ENTER
    Win 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
    3) Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)
    4) Download this free program (Autoruns for Windows) and use it to disable any instances of tapoas.sys that are starting (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
    5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of tapoas.sys are "Uninstalled" (DO NOT DISABLE THESE).
    6) Check in the Services applet (services.msc) to be sure any instances of tapoas.sys are disabled.
    7) EXPERIMENTAL STEP (only try if you're certain of your abilities - I have not tried this step myself). Search the registry (use regedit.exe) to locate any entries that have the driver name (tapoas.sys). Delete these keys (it's advisable to back them up first - but you've also backed up the entire registry when creating a System Restore point in step 1. Alternatively, you can set the values in these keys to DISABLED (but the "how" of this is beyond the scope of this).
    8) Go to C:\Windows\System32\drivers and rename the tapoas.sys driver to tapoas.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers).


    In the event that the system doesn't boot:

    1) Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename tapoas.BAD to tapoas.sys
    Code:
    ren C:\Windows\System32\drivers\tapoas.BAD C:\Windows\System32\drivers\tapoas.sys
    21) Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.

    Good luck!

      My System SpecsSystem Spec

  2. #12


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


    If it BSOD's after this, then run Driver Verifier according to these instructions: Driver Verifier Settings
      My System SpecsSystem Spec

  3. #13


    Posts : 16
    Windows 8.1


    After I went through the steps it continued crashing so I ran verifier. Attached is a file before verifier (labeled as before verifier) and another one for after I ran verifier (labeled as after verifier).
      My System SpecsSystem Spec

  4. #14


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


    Neither of the older drivers show up in the latest memory dump.
    Unfortunately, the verifier enabled memory dump doesn't point to a particular driver.
    It does hint at networking problems, so we'll have to work on the rest of the drivers that are related to networking. First we'll start with those that were released before Win8.1 (17 Oct 2013)

    The principal here is that you rule out all 3rd party drivers in order to determine if there's a hardware problem.
    So, start by checking to see if each of the following drivers is Win8.1 compatible. If unsure, install the latest, Win8.1 compatible version from the PC manufacturer's website. Do not worry about the drivers that are struckout - the dump_ one is only updated when you update the iaStorA.sys driver - and the intelppm.sys one is updated through Windows Update (so if you have all Windows Updates, it's the latest one). The easiest way to do this on a Sony system is to use Vaio Update first - then check for any that aren't updated.

    Code:
    **************************Sat Nov  8 18:59:52.949 2014 (UTC - 5:00)**************************
    sows.sys                Sun Jun 10 21:36:13 2012 (4FD54B8D)
    SFEP.sys                Mon Jun 18 04:11:46 2012 (4FDEE2C2)
    HECIx64.sys             Mon Jul  2 18:14:58 2012 (4FF21D62)
    RTKVHD64.sys            Tue Sep 25 08:06:24 2012 (50619E40)
    iBtFltCoex.sys          Thu Apr 18 10:17:24 2013 (51700074)
    btmaux.sys              Tue Apr 23 07:28:02 2013 (51767042)
    Rt630x64.sys            Fri May 10 05:59:08 2013 (518CC4EC)
    btmhsf.sys              Wed Jun 26 16:11:34 2013 (51CB4AF6)
    iwdbus.sys              Wed Jul 24 21:06:12 2013 (51F07A04)
    iaStorA.sys             Thu Aug  1 21:39:52 2013 (51FB0DE8)
    dump_iaStorA.sys        Thu Aug  1 21:39:52 2013 (51FB0DE8)
    intelppm.sys            Thu Aug 22 04:46:35 2013 (5215CFEB)
    tap0901.sys             Thu Aug 22 08:40:01 2013 (521606A1)
    RtsPStor.sys            Fri Aug 30 06:01:24 2013 (52206D74)
    igdkmd64.sys            Mon Sep  9 13:27:52 2013 (522E0518)
    SynTP.sys               Tue Sep 24 15:21:34 2013 (5241E63E)
    Smb_driver_Intel.sys    Tue Sep 24 15:24:08 2013 (5241E6D8)
    http://www.carrona.org/drivers/driver.php?id=sows.sys
    http://www.carrona.org/drivers/driver.php?id=SFEP.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=iBtFltCoex.sys
    http://www.carrona.org/drivers/driver.php?id=btmaux.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=btmhsf.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=tap0901.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPStor.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sat Nov  8 18:59:52.949 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\110814-20218-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    System Uptime:0 days 0:00:59.768
    Probably caused by :ntkrnlmp.exe ( nt!IopProcessWorkItem+80 )
    BugCheck C4, {9400b, fffff80009281ba0, ffffe0012914bbe0, ffffe0012914bc38}
    BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    Arguments: 
    Arg1: 000000000009400b, ID of the 'WlanTimedLinkQuality' rule that was violated.
    Arg2: fffff80009281ba0, A pointer to the string describing the violated rule condition.
    Arg3: ffffe0012914bbe0, Address of internal rule state (second argument to !ruleinfo).
    Arg4: ffffe0012914bc38, Address of supplemental states (third argument to !ruleinfo).
    BUGCHECK_STR:  0xc4_WlanTimedLinkQuality_XDV
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc4_WlanTimedLinkQuality_XDV_nt!IopProcessWorkItem
    CPUID:        "Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  R1021C8
      BIOS Release Date             03/13/2013
      Manufacturer                  Sony Corporation
      Product Name                  SVS151290X
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Nov  8 18:35:19.507 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\110814-24203-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    System Uptime:0 days 0:14:54.282
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    Probably caused by :igdkmd64.sys ( igdkmd64+628ca )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_igdkmd64+628ca
    CPUID:        "Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  R1021C8
      BIOS Release Date             03/13/2013
      Manufacturer                  Sony Corporation
      Product Name                  SVS151290X
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Nov  8 18:18:40.056 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\110814-29062-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    System Uptime:0 days 22:30:41.828
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  ffxiv.exe
    FAILURE_BUCKET_ID: ZEROED_STACK
    CPUID:        "Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  R1021C8
      BIOS Release Date             03/13/2013
      Manufacturer                  Sony Corporation
      Product Name                  SVS151290X
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Sat Nov  8 18:59:52.949 2014 (UTC - 5:00)**************************
    sows.sys                Sun Jun 10 21:36:13 2012 (4FD54B8D)
    SFEP.sys                Mon Jun 18 04:11:46 2012 (4FDEE2C2)
    HECIx64.sys             Mon Jul  2 18:14:58 2012 (4FF21D62)
    RTKVHD64.sys            Tue Sep 25 08:06:24 2012 (50619E40)
    iBtFltCoex.sys          Thu Apr 18 10:17:24 2013 (51700074)
    btmaux.sys              Tue Apr 23 07:28:02 2013 (51767042)
    Rt630x64.sys            Fri May 10 05:59:08 2013 (518CC4EC)
    btmhsf.sys              Wed Jun 26 16:11:34 2013 (51CB4AF6)
    iwdbus.sys              Wed Jul 24 21:06:12 2013 (51F07A04)
    iaStorA.sys             Thu Aug  1 21:39:52 2013 (51FB0DE8)
    dump_iaStorA.sys        Thu Aug  1 21:39:52 2013 (51FB0DE8)
    intelppm.sys            Thu Aug 22 04:46:35 2013 (5215CFEB)
    tap0901.sys             Thu Aug 22 08:40:01 2013 (521606A1)
    RtsPStor.sys            Fri Aug 30 06:01:24 2013 (52206D74)
    igdkmd64.sys            Mon Sep  9 13:27:52 2013 (522E0518)
    SynTP.sys               Tue Sep 24 15:21:34 2013 (5241E63E)
    Smb_driver_Intel.sys    Tue Sep 24 15:24:08 2013 (5241E6D8)
    nvlddmkm.sys            Mon Oct 28 17:38:03 2013 (526ED93B)
    nvpciflt.sys            Mon Oct 28 17:38:28 2013 (526ED954)
    NETwew00.sys            Thu Oct 31 10:01:47 2013 (527262CB)
    IntcDAud.sys            Fri Feb 21 08:50:26 2014 (530759A2)
    nvvad64v.sys            Fri Mar 28 09:32:06 2014 (533579D6)
    SCDEmu.SYS              Wed Oct  8 09:09:34 2014 (5435378E)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Nov  8 18:35:19.507 2014 (UTC - 5:00)**************************
    semav6thermal64ro.sys   Wed Dec 28 15:17:03 2011 (4EFB793F)
    t_mouse.sys             Mon Dec  3 01:19:30 2012 (50BC4472)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Nov  8 18:18:40.056 2014 (UTC - 5:00)**************************
    npf.sys                 Fri Jun 25 12:50:58 2010 (4C24DE72)
    
    http://www.carrona.org/drivers/driver.php?id=sows.sys
    http://www.carrona.org/drivers/driver.php?id=SFEP.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=iBtFltCoex.sys
    http://www.carrona.org/drivers/driver.php?id=btmaux.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=btmhsf.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=tap0901.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPStor.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=NETwew00.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
    http://www.carrona.org/drivers/driver.php?id=semav6thermal64ro.sys
    http://www.carrona.org/drivers/driver.php?id=t_mouse.sys
    http://www.carrona.org/drivers/driver.php?id=npf.sys
      My System SpecsSystem Spec

  5. #15


    Posts : 16
    Windows 8.1


    So when I was updating the drivers my computer randomly crashed and then it would crash every time I tried to start up my computer. I ended up having to revert back to a previous system restore point through the recovery menu to even get to the log in screen for my computer. Any advice?
      My System SpecsSystem Spec

  6. #16


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


    Which drivers were involved?
    What were you using to update them?
    Can we have a look at this report?:
    Please do the following:
    - open Event Viewer (run eventvwr.msc from the "Run" dialog))
    - expand the Custom Views category (left click on the > next to the words "Custom Views")
    - right click on Administrative Events
    - select "Save all Events in Custom View as..."
    - save the file as Admin.evtx
    - zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
    - upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).
      My System SpecsSystem Spec

  7. #17


    Posts : 16
    Windows 8.1


    I don't remember exactly which drivers they were but I think they were either one of the intel drivers or realtek drivers. My computer has crashed a few times since then so you might have to sift to find the proper reports. I can't remember exactly what the error said but it was something about a System Thread. Maybe System_thread_exception_not_handled? I attached the file from the SF_Diagnostic Tool but when I tried to go through the Event Viewer this is what happened.

    When I clicked on Administrative Events
    Gyazo - 089fd657885ccb8db0c9dde1cb62247d.png

    When I tried to save it
    Gyazo - d573ca171ec0e0093c809e22a2ea6467.png
      My System SpecsSystem Spec

  8. #18


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


    This is a common error with EventViewer - it involves stuff that wasn't updated for 8.1, so the event viewer panics.
    In most cases if you keep clicking on OK, it'll still open up the report and will let you save it.

    Here's a fix for the error:
    Error in Event Viewer (DxpTaskRingtone) - how to fix:
    1. Back up registry (set a System Restore point).
    2. Right click on Start.
    3. Choose 'Run'.
    4. Type "regedit" (without quotation marks)
    5. Choose 'Yes' when you're prompted by UAC.
    6. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\
    7. Right click on folder: Microsoft-Windows-DxpTaskRingtone/Analytic
    8. Choose 'Delete' and then 'Yes'.
    9. Close Registry Editor and restart your computer.
    This is from this topic: Error in Event Viewer (DxpTaskRingtone) after upgrading to - Microsoft Community
    Interestingly, the npf.sys driver is still present in the memory dumps from 10 November.
    Please re-do the instructions that I posted above (and in this case, also look for any info on WinPcap in the descriptions)
    Here it is again:
    1) Create a Restore Point using System Restore
    2) Create a Repair disc (Recovery Drive in Win8.1):
    Win 7 - Go to Start...All Programs...Maintenance...Create a System Repair Disc
    Win 8 - Press "WIN" and "R" to open the Run dialog...type "RECDISC" (without the quotes) and press ENTER
    Win 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
    3) Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)
    4) Download this free program (Autoruns for Windows) and use it to disable any instances of npf.sys (and anything that mentions WinPcap) that are starting (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
    5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of npf.sys (and anything that mentions WinPcap) are "Uninstalled" (DO NOT DISABLE THESE).
    6) Check in the Services applet (services.msc) to be sure any instances of npf.sys (and anything that mentions WinPcap) are disabled.
    7) EXPERIMENTAL STEP (only try if you're certain of your abilities - I have not tried this step myself). Search the registry (use regedit.exe) to locate any entries that have the driver name (npf.sys) Also search for anything that mentions WinPcap. Delete these keys (it's advisable to back them up first - but you've also backed up the entire registry when creating a System Restore point in step 1. Alternatively, you can set the values in these keys to DISABLED (but the "how" of this is beyond the scope of this).
    8) Go to C:\Windows\System32\drivers and rename the npf.sys driver to npf.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers).


    In the event that the system doesn't boot:

    1) Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename npf.BAD to npf.sys
    Code:
    ren C:\Windows\System32\drivers\npf.BAD C:\Windows\System32\drivers\npf.sys
    21) Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.

    Good luck!
    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Nov 10 22:28:44.116 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\111014-27281-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    System Uptime:0 days 22:22:45.890
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID: ZEROED_STACK
    CPUID:        "Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  R1021C8
      BIOS Release Date             03/13/2013
      Manufacturer                  Sony Corporation
      Product Name                  SVS151290X
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Nov  9 23:06:39.899 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\110914-23281-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    System Uptime:0 days 0:27:34.672
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  ffxiv.exe
    FAILURE_BUCKET_ID: ZEROED_STACK
    CPUID:        "Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  R1021C8
      BIOS Release Date             03/13/2013
      Manufacturer                  Sony Corporation
      Product Name                  SVS151290X
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Nov  9 22:38:41.007 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\110914-31000-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    System Uptime:0 days 8:10:32.781
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: ZEROED_STACK
    CPUID:        "Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  R1021C8
      BIOS Release Date             03/13/2013
      Manufacturer                  Sony Corporation
      Product Name                  SVS151290X
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Nov  9 12:58:03.229 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\110914-42203-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    System Uptime:0 days 0:00:23.003
    *** WARNING: Unable to verify timestamp for RTKVHD64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
    Probably caused by :RTKVHD64.sys ( RTKVHD64+153a0 )
    BugCheck 1000007E, {ffffffffc0000005, fffff8024776ab60, ffffd001d4307e48, ffffd001d4307650}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8024776ab60, The address that the exception occurred at
    Arg3: ffffd001d4307e48, Exception Record Address
    Arg4: ffffd001d4307650, Context Record Address
    PROCESS_NAME:  System
    BUGCHECK_STR:  AV
    FAILURE_BUCKET_ID: AV_RTKVHD64+153a0
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Mon Nov 10 22:28:44.116 2014 (UTC - 5:00)**************************
    npf.sys                 Fri Jun 25 12:50:58 2010 (4C24DE72)
    semav6thermal64ro.sys   Wed Dec 28 15:17:03 2011 (4EFB793F)
    sows.sys                Sun Jun 10 21:36:13 2012 (4FD54B8D)
    SFEP.sys                Mon Jun 18 04:11:46 2012 (4FDEE2C2)
    HECIx64.sys             Mon Jul  2 18:14:58 2012 (4FF21D62)
    RTKVHD64.sys            Tue Sep 25 08:06:24 2012 (50619E40)
    lvuvc64.sys             Mon Oct 22 22:12:08 2012 (5085FCF8)
    t_mouse.sys             Mon Dec  3 01:19:30 2012 (50BC4472)
    iBtFltCoex.sys          Thu Apr 18 10:17:24 2013 (51700074)
    btmaux.sys              Tue Apr 23 07:28:02 2013 (51767042)
    Rt630x64.sys            Fri May 10 05:59:08 2013 (518CC4EC)
    btmhsf.sys              Wed Jun 26 16:11:34 2013 (51CB4AF6)
    iwdbus.sys              Wed Jul 24 21:06:12 2013 (51F07A04)
    iaStorA.sys             Thu Aug  1 21:39:52 2013 (51FB0DE8)
    dump_iaStorA.sys        Thu Aug  1 21:39:52 2013 (51FB0DE8)
    intelppm.sys            Thu Aug 22 04:46:35 2013 (5215CFEB)
    tap0901.sys             Thu Aug 22 08:40:01 2013 (521606A1)
    RtsPStor.sys            Fri Aug 30 06:01:24 2013 (52206D74)
    igdkmd64.sys            Mon Sep  9 13:27:52 2013 (522E0518)
    SynTP.sys               Tue Sep 24 15:21:34 2013 (5241E63E)
    Smb_driver_Intel.sys    Tue Sep 24 15:24:08 2013 (5241E6D8)
    nvlddmkm.sys            Mon Oct 28 17:38:03 2013 (526ED93B)
    nvpciflt.sys            Mon Oct 28 17:38:28 2013 (526ED954)
    NETwew00.sys            Thu Oct 31 10:01:47 2013 (527262CB)
    IntcDAud.sys            Fri Feb 21 08:50:26 2014 (530759A2)
    nvvad64v.sys            Fri Mar 28 09:32:06 2014 (533579D6)
    SCDEmu.SYS              Wed Oct  8 09:09:34 2014 (5435378E)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Nov  9 23:06:39.899 2014 (UTC - 5:00)**************************
    lvrs64.sys              Mon Oct 22 22:11:24 2012 (5085FCCC)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Nov  9 12:58:03.229 2014 (UTC - 5:00)**************************
    RtsPStor.sys            Tue Jan  7 01:21:53 2014 (52CB9D01)
    RTKVHD64.sys            Wed May 14 06:28:52 2014 (53734564)
    
    http://www.carrona.org/drivers/driver.php?id=npf.sys
    http://www.carrona.org/drivers/driver.php?id=semav6thermal64ro.sys
    http://www.carrona.org/drivers/driver.php?id=sows.sys
    http://www.carrona.org/drivers/driver.php?id=SFEP.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
    http://www.carrona.org/drivers/driver.php?id=t_mouse.sys
    http://www.carrona.org/drivers/driver.php?id=iBtFltCoex.sys
    http://www.carrona.org/drivers/driver.php?id=btmaux.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=btmhsf.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=tap0901.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPStor.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=NETwew00.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
    http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPStor.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
      My System SpecsSystem Spec

  9. #19


    Posts : 16
    Windows 8.1


    That driver probably showed up in the more recent crashes as I had had to restore to a previous system restore point and the last one I had was right before I had disabled the npf and tapoas drivers. I went back and did that again and I applied the fix for the event viewer and am attaching that here. Thanks again for all the help.
      My System SpecsSystem Spec

  10. #20


    Posts : 16
    Windows 8.1


    Also I just got a notification from Windows Action Center about a sudden crash and Windows seems to be linking it to some Intel Graphics Driver but the solution it offers is to download a specific driver which is apparently not compatible with my system.
      My System SpecsSystem Spec

Page 2 of 3 FirstFirst 123 LastLast
Frequent BSODs
Related Threads
[Random/Frequent BSODs] DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
I am at a standstill ever since I recieved this BSOD. At first I thought it was just a random crash and that I would've resolved it later, however it became frequent in just a matter of minutes. Playing a game, browsing the internet, listening to music, anything I do will result in another BSOD...
Frequent BSODs in BSOD Crashes and Debugging
In the last months I have been experiencing many BSODs, with no particular pattern. Sometimes, the BSOD happens when I have left the computer alone for some minutes. Others, the system crashes when I am using it, primarily for work. Here I attach my diagnostic file. Thank you for your support.
Frequent BSODs in BSOD Crashes and Debugging
I've been getting pretty frequent BSODs, doesn't seem to be related to any particular activity or period of time... Sometimes they'll happen every 1-2 days, othertimes it'll be 3 times in an hour :( I'm attached data from the SF tool, if anybody could take a look and let me know what you think...
Frequent BSODs on my dell latitude E6430 in BSOD Crashes and Debugging
Hi I frequently have Blue screen of deaths on my dell latitude e6430 It usually comes out with these notices: -KERNAL DATA INPAGE ERROR -MEMORY MANAGEMENT -PAGE FAULT IN NONPAGED INDEX
Frequent yet, seemingly random BSODs in BSOD Crashes and Debugging
Hi, At the recommendation of one of the moderators on the Seven Forums, I am re-posting my problem here following a an upgrade to Windows 8 Pro. (original posts here: BSOD Memory Management Error - On Boot and in-game (GW2) - Windows 7 Support Forums) Basically, I am getting frequent BSODs in...
I built my first gaming rig in january 2013, and everything went well. However about 2 days later i recieved my first BS0Ds, which was very dissapointing. I neglected to fix the issues and now all these BSODS are driving me crazy. I don't know how to analyze dmp files so any help would be...
Acer Aspire One 725-0826 Immediately after Windows 8 was finished updating on February 16, I suffered my first BSOD ever in w8 and several more followed it on the same day until I gave up on Firefox entirely and avoided using any browser for the rest of the day. I hypothesized that Firefox +...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook