Windows 8 and 8.1 Forums


Most likely driver issues but not sure how to resolve

  1. #1


    United States
    Posts : 5
    Windows 8.1 Preview

    Most likely driver issues but not sure how to resolve


    Hello, first time on these forums.

    I have been trouble shooting my PC since yesterday as the rate that I BSOD has been increasing dramatically. I am by far no expert in troubleshooting so I figured it is time for me to ask others for help and advice. I haven't the slightest clue on how to read dump files. Wouldn't mind learning though but that is a subject for another time.

    Any help would be appreciated greatly.

      My System SpecsSystem Spec

  2. #2


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


    General info on BSOD troubleshooting: BSOD

    First off, a disclaimer - I am not familiar w/8.1 so my analysis is based on Win8 RTM
    8.1 is (as I understand it) a Developer's Release - so it can be expected to have bugs.
    In the end, the only sure thing will be to revert to Win8 RTM and wait for the RTM version of 8.1

    Make sure that you have all available Windows Updates - it may take several trips to get them all.

    Please ensure that Driver Verifier is turned off. To do this, open up verifier.exe and select "Delete existing settings", then click on "Finish" in the lower right corner of the window. Reboot for the changes to take affect.

    SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:
    1) That the SSD firmware is the latest available for the SSD
    2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.
    These devices have issues in Device Manager:
    Programmable Root Enumerator ROOT\PROGRAMMING_SUPPORT\0001 This device is not working properly because Windows cannot load the drivers required for this device.

    Bluetooth Audio Device BTHENUM\{61118058-486C-4BB0-B4B8-ACE4DCADEC44}_LOCALMFG&0000\7&180D0F68&0&000000000000_00000000 This device cannot start.

    Bluetooth LWFLT Device BTHENUM\{DD533152-01F4-435C-ABFE-984BC21A2A65}_LOCALMFG&0000\7&180D0F68&0&000000000000_00000000 This device is not working properly because Windows cannot load the drivers required for this device.
    Similar Asus issue here: Computer Keeps Crashing Please follow that advice. It may be that there are not any Win8.1 drivers available for these devices. If so, you may have to install Win8 or Win7 drivers in compatibility mode.

    Lot's of Live Kernel Events without corresponding BSOD events.
    Please do the following:
    - open Event Viewer (eventvwr.msc)
    - 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).

    MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install it immediately!

    If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

    Uninstall Asus Smart Doctor/iTracker 2 - it's blamed in several of the memory dumps


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

    AsUpIO.sys Mon Aug 2 22:47:59 2010 (4C57835F)
    ASUS hardware monitoring software related
    http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys

    AiChargerPlus.sys Wed Apr 18 21:17:35 2012 (4F8F67AF)
    Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
    http://www.carrona.org/drivers/driver.php?id=AiChargerPlus.sys

    If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Hardware Diagnostics. Let us know the results and we can move on from there.



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Sep 10 06:00:04.663 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091013-23078-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 0:00:08.335
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** WARNING: Unable to verify timestamp for VerifierExt.sys
    *** ERROR: Module load completed but symbols could not be loaded for VerifierExt.sys
    Probably caused by :HIDCLASS.SYS ( HIDCLASS+18cf )
    BugCheck C9, {23b, fffff800758920b8, ffffcf800268cca0, 0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
    Arg2: fffff800758920b8, The address in the driver's code where the error was detected.
    Arg3: ffffcf800268cca0, IRP address.
    Arg4: 0000000000000000
    BUGCHECK_STR:  0xc9_23b
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_23b_VRF_HIDCLASS+18cf
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 10 05:45:43.852 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091013-12687-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 0:00:08.524
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** WARNING: Unable to verify timestamp for VerifierExt.sys
    *** ERROR: Module load completed but symbols could not be loaded for VerifierExt.sys
    Probably caused by :HIDCLASS.SYS ( HIDCLASS+18cf )
    BugCheck C9, {23b, fffff80031cac0b8, ffffcf8002768ca0, 0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
    Arg2: fffff80031cac0b8, The address in the driver's code where the error was detected.
    Arg3: ffffcf8002768ca0, IRP address.
    Arg4: 0000000000000000
    BUGCHECK_STR:  0xc9_23b
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_23b_VRF_HIDCLASS+18cf
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 10 03:12:07.811 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091013-10296-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 0:28:38.445
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe000019ed028, bf800000, 124}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe000019ed028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  rundll32.exe
    FAILURE_BUCKET_ID: 0x124_GenuineIntel__UNKNOWN
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  1405
      BIOS Release Date             08/19/2013
      Manufacturer                  ASUS
      Product Name                  All Series
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 10 02:32:36.404 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090913-121296-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 0:27:58.036
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe000043aa028, bf800000, 124}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe000043aa028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  aces.exe
    FAILURE_BUCKET_ID: 0x124_GenuineIntel__UNKNOWN
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  1405
      BIOS Release Date             08/19/2013
      Manufacturer                  ASUS
      Product Name                  All Series
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 10 01:15:56.726 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090913-22296-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 0:00:07.398
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** WARNING: Unable to verify timestamp for VerifierExt.sys
    *** ERROR: Module load completed but symbols could not be loaded for VerifierExt.sys
    Probably caused by :HIDCLASS.SYS ( HIDCLASS+18cf )
    BugCheck C9, {23b, fffff8025170a0b8, ffffcf80029dcca0, 0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
    Arg2: fffff8025170a0b8, The address in the driver's code where the error was detected.
    Arg3: ffffcf80029dcca0, IRP address.
    Arg4: 0000000000000000
    BUGCHECK_STR:  0xc9_23b
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_23b_VRF_HIDCLASS+18cf
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 10 00:52:12.492 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090913-22109-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 0:00:07.164
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** WARNING: Unable to verify timestamp for VerifierExt.sys
    *** ERROR: Module load completed but symbols could not be loaded for VerifierExt.sys
    Probably caused by :HIDCLASS.SYS ( HIDCLASS+18cf )
    BugCheck C9, {23b, fffff800fee920b8, ffffcf80028e4ca0, 0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
    Arg2: fffff800fee920b8, The address in the driver's code where the error was detected.
    Arg3: ffffcf80028e4ca0, IRP address.
    Arg4: 0000000000000000
    BUGCHECK_STR:  0xc9_23b
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_23b_VRF_HIDCLASS+18cf
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Sep  9 04:00:15.671 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090913-9515-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 0:05:10.303
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe0000445f028, bf800000, 124}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe0000445f028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  WiFi GO! Serve
    FAILURE_BUCKET_ID: 0x124_GenuineIntel__UNKNOWN
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Sep  8 14:42:27.761 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090813-61500-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 17:19:41.394
    *** WARNING: Unable to verify timestamp for IOMap64.sys
    *** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
    Probably caused by :IOMap64.sys ( IOMap64+3525 )
    BugCheck 1A, {1233, 10d, 3, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000001233, The subtype of the bugcheck.
    Arg2: 000000000000010d
    Arg3: 0000000000000003
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_1233
    PROCESS_NAME:  aprp.exe
    FAILURE_BUCKET_ID: 0x1a_1233_IOMap64+3525
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  1007
      BIOS Release Date             05/17/2013
      Manufacturer                  ASUS
      Product Name                  All Series
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep  6 21:07:49.948 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090613-7453-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 22:34:40.581
    *** WARNING: Unable to verify timestamp for IOMap64.sys
    *** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
    Probably caused by :IOMap64.sys ( IOMap64+3525 )
    BugCheck 1A, {1233, 10b, 0, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000001233, The subtype of the bugcheck.
    Arg2: 000000000000010b
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_1233
    PROCESS_NAME:  aprp.exe
    FAILURE_BUCKET_ID: 0x1a_1233_IOMap64+3525
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  1007
      BIOS Release Date             05/17/2013
      Manufacturer                  ASUS
      Product Name                  All Series
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep  4 22:22:27.284 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090413-9640-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 18:19:26.917
    *** WARNING: Unable to verify timestamp for IOMap64.sys
    *** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
    Probably caused by :IOMap64.sys ( IOMap64+3525 )
    BugCheck 1A, {1233, 191, 0, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000001233, The subtype of the bugcheck.
    Arg2: 0000000000000191
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_1233
    PROCESS_NAME:  aprp.exe
    FAILURE_BUCKET_ID: 0x1a_1233_IOMap64+3525
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  1007
      BIOS Release Date             05/17/2013
      Manufacturer                  ASUS
      Product Name                  All Series
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Tue Sep 10 06:00:04.663 2013 (UTC - 4:00)**************************
    AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
    AiChargerPlus.sys           Wed Apr 18 21:17:35 2012 (4F8F67AF)
    AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
    asmtufdriver.sys            Fri Sep 28 06:55:29 2012 (50658221)
    HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
    asahci64.sys                Wed Jan  9 21:52:36 2013 (50EE2CF4)
    dump_iaStorA.sys            Mon Jan 14 13:00:27 2013 (50F447BB)
    iaStorA.sys                 Mon Jan 14 13:00:27 2013 (50F447BB)
    athw8x.sys                  Thu Jan 17 04:15:39 2013 (50F7C13B)
    vmic_x64.sys                Wed Feb 27 04:06:50 2013 (512DCCAA)
    RTKVHD64.sys                Tue Mar  5 08:21:03 2013 (5135F13F)
    SaiMini.sys                 Tue Apr 16 13:17:23 2013 (516D87A3)
    SaiBus.sys                  Tue Apr 16 13:17:23 2013 (516D87A3)
    intelppm.sys                Sat Jun 15 17:47:58 2013 (51BCE10E)
    NdisVirtualBus.sys          Sat Jun 15 20:32:47 2013 (51BD07AF)
    ahcache.sys                 Sat Jun 15 20:35:57 2013 (51BD086D)
    werkernel.sys               Sat Jun 15 20:36:25 2013 (51BD0889)
    nvhda64v.sys                Sun Jun 16 08:38:07 2013 (51BDB1AF)
    e1d64x64.sys                Wed Jun 26 16:51:31 2013 (51CB5453)
    aswRdr2.sys                 Fri Aug 16 07:43:23 2013 (520E105B)
    aswTdi.sys                  Fri Aug 16 07:43:33 2013 (520E1065)
    aswSP.sys                   Fri Aug 16 07:43:56 2013 (520E107C)
    aswSnx.sys                  Fri Aug 16 07:44:30 2013 (520E109E)
    aswRvrt.sys                 Fri Aug 16 07:45:27 2013 (520E10D7)
    nvlddmkm.sys                Sun Aug 18 14:21:08 2013 (52111094)
    nvvad64v.sys                Tue Aug 20 07:29:10 2013 (52135306)
    aswVmm.sys                  Tue Aug 27 21:03:24 2013 (521D4C5C)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 10 03:12:07.811 2013 (UTC - 4:00)**************************
    IOMap64.sys                 Thu Feb  4 20:55:34 2010 (4B6B7A96)
    mbam.sys                    Mon Aug 20 12:49:41 2012 (50326AA5)
    btfilter.sys                Tue Dec 18 04:54:27 2012 (50D03D53)
    btath_rcp.sys               Tue Dec 18 04:54:50 2012 (50D03D6A)
    btath_hcrp.sys              Tue Dec 18 04:54:54 2012 (50D03D6E)
    LGSHidFilt.Sys              Thu Jan 17 15:15:00 2013 (50F85BC4)
    RTCore64.sys                Mon Mar 11 01:32:06 2013 (513D6C56)
    SaiK0762.sys                Tue Apr 16 13:11:20 2013 (516D8638)
    nvlddmkm.sys                Thu Jul 25 22:41:39 2013 (51F1E1E3)
    aswMonFlt.sys               Fri Aug 16 07:43:04 2013 (520E1048)
    aswFsBlk.sys                Fri Aug 16 07:43:14 2013 (520E1052)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 10 02:32:36.404 2013 (UTC - 4:00)**************************
    e1i63x64.sys                Wed Mar 20 03:37:29 2013 (51496739)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Sep  8 14:42:27.761 2013 (UTC - 4:00)**************************
    xusb22.sys                  Sat Jun 15 20:34:38 2013 (51BD081E)
    
    http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
    http://www.carrona.org/drivers/driver.php?id=AiChargerPlus.sys
    http://www.carrona.org/drivers/driver.php?id=AsIO.sys
    asmtufdriver.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=asahci64.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=athw8x.sys
    vmic_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=SaiMini.sys
    http://www.carrona.org/drivers/driver.php?id=SaiBus.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    NdisVirtualBus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    ahcache.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    werkernel.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    e1d64x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
    http://www.carrona.org/drivers/driver.php?id=aswTdi.sys
    http://www.carrona.org/drivers/driver.php?id=aswSP.sys
    http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
    http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
    http://www.carrona.org/drivers/driver.php?id=IOMap64.sys
    http://www.carrona.org/drivers/driver.php?id=mbam.sys
    http://www.carrona.org/drivers/driver.php?id=btfilter.sys
    http://www.carrona.org/drivers/driver.php?id=btath_rcp.sys
    http://www.carrona.org/drivers/driver.php?id=btath_hcrp.sys
    http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=RTCore64.sys
    SaiK0762.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswFsBlk.sys
    http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
    http://www.carrona.org/drivers/driver.php?id=xusb22.sys
      My System SpecsSystem Spec

  3. #3


    United States
    Posts : 5
    Windows 8.1 Preview


    Well you sir may be the single most helpful forum poster I have ever seen. Thanks for the very helpful reply.

    My SSD firmware is updated to the lastest firmware and I would assume that the chipset should have drivers more recent then 2012 as it is a 2013 produced board but I will look into that just in case.

    I have uninstalled AISuite III which is where I believe the ASUS hardware monitor drivers are coming from and I also uninstalled RivaTuner/PrecisionX. I am going to try to boot with verifier.exe active and see if I still get a BSOD.

    I also have the evtx file that you requested.

    Thank you again for being so helpful.


    Edit: That Programmable Root Enumerator driver shouldn't be installed as I have removed all MadCatz/Saitek software. The AsUpIO.sys and AiChargerPlus.sys also were not removed when I removed all ASUS software. If they are not being deleted when I uninstall the software, how can I safely remove them?

    Reedit: Was able to remove the Programmable Root Enumerator and the AiChargerPlus.sys. The only one left is AsUpIO.sys. I can not find an update for this driver and am not really sure what it does. I am willing to assume just hitting delete on it is a bad idea as well.
    Last edited by Burnt; 10 Sep 2013 at 21:12.
      My System SpecsSystem Spec

  4. #4


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


    Don't delete drivers - it may render your system unbootable.
    As for updating the AsUpIO.sys driver - I'd just leave it alone for now.
    It was picked up simply because the date on it was a bit older - not because of any problems that have been seen.
    I can offer ways to safely remove them - but don't think that that is needed at this point.

    Make sure that you turn Driver Verifier OFF - as it's purpose is to create BSOD's
    As you can see by the previous BSOD's - it didn't identify a driver earlier, so I doubt that it will this time.

    Some disk errors in Hard Disk 1 (I think that this is your external USB drive). Please remove the drive from the system and leave it off while we're troubleshooting. If needed, reattach it - use it - remove it again.
    As time allows, also run a hard drive diagnostic on it: Hard Drive Diagnostic Procedure

    Lot's of DCOM errors relating to Windows Search. I'm not real good w/DCOM stuff.
    Have you done anything to change/modify the Windows Search or it's services?

    Network Location Awareness service failed to start due to a dependency issue. Check it's dependencies in services.msc and make sure that they are started.
    On my system it depends on:
    - DHCP Client
    - Network Store Interface Service
    - Remote Procedure Call (RPC)
    - TCP/IP Protocol Driver
    I'm guessing that it's the DHCP Client service that's not starting.
    My hope here is that fixing the Network Location Awareness service will then fix the DCOM stuff.

    A couple of e1dexpress errors also - these are related to your network card drivers
    Please:
    - download a fresh copy of the latest, Win8 compatible drivers for yout wired Intel network card
    - uninstall the current drivers from your system
    - install the freshly downloaded drivers
    - monitor for further BSOD's

    Then we wait and see if you get any further BSOD's
    If you do, please zip up the contents of C:\Windows\Minidump and upload it with your next post.
      My System SpecsSystem Spec

  5. #5


    United States
    Posts : 5
    Windows 8.1 Preview


    I do actually use StartIsBack which I would assume is changing how Windows Search works but I am not actually sure about that. I have never had problems with it but who knows.

    I think I updated the network drivers you were referring to. "Intel(R) Ethernet Connection I217-V" is what I updated, couldn't really find anything else involving Intel and networking other then maybe some wireless drivers but I don't use wifi on this PC.

    My Network Location Awareness service had the exact dependencies you listed and all were running. I also unplugged my external drive. I will run some diagnostics on it tomorrow.

    I should probably state the fact that some of those BSOD were caused by running verifier. I have been running into memory management errors at very random times over the last month or so, watching a fullscreen video or playing minecraft, which lead me to running Memtest86+ but that came up with no errors with the RAM. I then read somewhere that rebooting with verifier running will can give you more info on BSOD error causes but I am assuming I was using that tool improperly now.

    I reseated the RAM yesterday and haven't run into any BSOD caused by memory management. I did end up looking in my BIOS and my CPU multiplier was still set to what was obviously an unstable overclock. I had thought that I had stopped my overclock but apparently I didn't. It is now back down to stock frequencies and no BSOD from that anymore.

    The only time in the last day that I have been able to get a BSOD error is when I restart with verifier.exe running. I will included the one file in the Minidump that that left if it is still work looking into otherwise I am leaving verifier turned off, I can't boot into windows with it running anyways. Am I out of the woods for the most part if I don't get anymore Memory Management errors?
      My System SpecsSystem Spec

  6. #6


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


    I picked errors from the Admin Event Viewer log that were repeated. This doesn't mean that they were the cause of the BSOD's - but that they could have caused issues with your system.

    The Intel Ethernet drivers were the correct ones. It's possible that the errors were fixed, but I didn't check for "Information" entries during my scan of the log file as it would have taken much longer. So, it's possible that this is also not related to your issues.

    Driver Verifier is a great tool, but doesn't always give helpful results.
    It's not a matter of using Driver Verifier inappropriately, it's that running it did generate info - but the info may not have given us any really useful hints. Usually this means that there's a hardware or a Windows problem - but there are still other possibilities. IMO the only hint that I saw was that the crashes were all due to HIDCLASS.sys - a Windows input device driver (I'll discuss this further later on in my post). Just FYI - if you look at the first code box that I posted, you'll see that the Driver Verifier memory dumps are identified as: Memory management errors can be hardware or software. If no errors are found with MemTest86+, then try Prime95 ( Prime95 ) Run the Blend test as that stresses RAM more than the other tests. Overclocking can also cause Memory Management errors - so it's important to leave the overclock off while we're troubleshooting.

    Just FYI - here's how I do BSOD analysis':
    - first I rule out 3rd party drivers (over 90% of BSOD's are due to this)
    - then I rule out hardware (less than 10% of BSOD's are due to this)
    - then I look at Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date).

    The Verifier enabled memory dumps are very consistent in blaming HIDCLASS.sys - which is a Windows driver related to input devices. Once we look at all the obvious 3rd party drivers, then I'll focus on drivers for the input devices (such as the Saitek device that has drivers loaded in the memory dumps - which, it appears, you've already updated). If that doesn't fix it, then I'll ask you to remove the device(s) to see if that helps. This may include both mouse and keyboard as they are also HID devices.

    In short, if you're still getting BSOD's and don't need the Saitek device, please uninstall it's software and physically remove the device from your system (in order to test to see if that's the cause). There are other suspicious devices (IMO again), but we'll have to see if this fixes things (or not) before moving on to the others.

    In the end, we wait to see if there are any more BSOD's (without Driver Verifier being enabled). That's the criteria for a "fix" - no more BSOD's. How long? Well, that's a different discussion - but generally it's a week or two (unless your BSOD were far apart).

    Good luck!

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Wed Sep 11 23:17:07.351 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091113-10453-01.dmp]
    Windows 8 Kernel Version 9431 MP (8 procs) Free x64
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    System Uptime:0 days 0:00:06.023
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** WARNING: Unable to verify timestamp for VerifierExt.sys
    *** ERROR: Module load completed but symbols could not be loaded for VerifierExt.sys
    Probably caused by :HIDCLASS.SYS ( HIDCLASS+18cf )
    BugCheck C9, {23b, fffff80144d1c0b8, ffffcf80027b8ca0, 0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
    Arg2: fffff80144d1c0b8, The address in the driver's code where the error was detected.
    Arg3: ffffcf80027b8ca0, IRP address.
    Arg4: 0000000000000000
    BUGCHECK_STR:  0xc9_23b
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_23b_VRF_HIDCLASS+18cf
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Wed Sep 11 23:17:07.351 2013 (UTC - 4:00)**************************
    AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
    AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
    HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
    asahci64.sys                Wed Jan  9 21:52:36 2013 (50EE2CF4)
    dump_iaStorA.sys            Mon Jan 14 13:00:27 2013 (50F447BB)
    iaStorA.sys                 Mon Jan 14 13:00:27 2013 (50F447BB)
    athw8x.sys                  Thu Jan 17 04:15:39 2013 (50F7C13B)
    btath_bus.sys               Mon Jan 21 04:18:42 2013 (50FD07F2)
    RTKVHD64.sys                Tue Mar  5 08:21:03 2013 (5135F13F)
    SaiBus.sys                  Tue Apr 16 13:17:23 2013 (516D87A3)
    SaiMini.sys                 Tue Apr 16 13:17:23 2013 (516D87A3)
    intelppm.sys                Sat Jun 15 17:47:58 2013 (51BCE10E)
    NdisVirtualBus.sys          Sat Jun 15 20:32:47 2013 (51BD07AF)
    ahcache.sys                 Sat Jun 15 20:35:57 2013 (51BD086D)
    werkernel.sys               Sat Jun 15 20:36:25 2013 (51BD0889)
    nvhda64v.sys                Sun Jun 16 08:38:07 2013 (51BDB1AF)
    e1d64x64.sys                Wed Jun 26 16:51:31 2013 (51CB5453)
    aswRdr2.sys                 Fri Aug 16 07:43:23 2013 (520E105B)
    aswTdi.sys                  Fri Aug 16 07:43:33 2013 (520E1065)
    aswSP.sys                   Fri Aug 16 07:43:56 2013 (520E107C)
    aswSnx.sys                  Fri Aug 16 07:44:30 2013 (520E109E)
    aswRvrt.sys                 Fri Aug 16 07:45:27 2013 (520E10D7)
    nvlddmkm.sys                Sun Aug 18 14:21:08 2013 (52111094)
    nvvad64v.sys                Tue Aug 20 07:29:10 2013 (52135306)
    aswVmm.sys                  Tue Aug 27 21:03:24 2013 (521D4C5C)
    
    http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
    http://www.carrona.org/drivers/driver.php?id=AsIO.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=asahci64.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=athw8x.sys
    http://www.carrona.org/drivers/driver.php?id=btath_bus.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=SaiBus.sys
    http://www.carrona.org/drivers/driver.php?id=SaiMini.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    NdisVirtualBus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    ahcache.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    werkernel.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    e1d64x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
    http://www.carrona.org/drivers/driver.php?id=aswTdi.sys
    http://www.carrona.org/drivers/driver.php?id=aswSP.sys
    http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
    http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
      My System SpecsSystem Spec

  7. #7


    United States
    Posts : 5
    Windows 8.1 Preview


    Should I proceed by process of elimination? I have about 6 USB devices currently hooked up. A mic, external DVD drive, the external HDD, a flash drive, and of course a mouse/keyboard.

    I am currently running HDTune on the HDD and it has picked up 0.1% of the drive as damaged. Its been running for about 5 hours, still has about a third left to check. It looks like the utility does 2 passes on the drive. I also uninstalled all my Saitek software but from the sounds of it some drivers may be sticking around. I'll look into that tomorrow after work.

    Also another question about verifier. It should be possible to boot into windows successfully with it running correct? I haven't seen it actually. This is my first time looking into solving any BSOD issues, I never really had them on my personal PC until around a month ago. I would rather actually solve the root of the problem rather then just hope that my PC doesn't BSOD while I am doing something important.
      My System SpecsSystem Spec

  8. #8


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


    Let's leave well enough alone for now. The problem with removing everything at once is you don't know what the actual problem is.
    But fixing (replacing) a damaged hard drive is probably the first order of business.

    When installing Windows, leave all USB devices disconnected (obviously you'll need a keyboard and a mouse - but nothing else). You can add all the extra stuff after the system is installed/activated/updated.

    Certain structures must load before Device Manager can function. But, by design, these occur early in the boot process. I used to think that they started after Safe Mode loaded - but Driver Verifier memory dumps have occurred earlier than that on a couple of occasions that I have seen.

    But, in most cases, you can boot into Windows with Driver Verifier enabled - and the system will work (but may be a bit slower depending on which options are chosen). In an ideal world, driver developers will follow all of Microsoft's guidance - but we don't live in an ideal world, so Driver Verifier may not work as it was designed to do based on un-cooperative 3rd party drivers.

    As for a "fix" - the "fix" for a BSOD is no more BSOD's. It's not real often that we have a simple one, and there's never anything that says "this is fixed". So the "fix" is simply waiting to see if there are any further BSOD's.

    Extended troubleshooting (doing things one-at-a-time and waiting for BSOD's) is the only reliable way to determine what causes the BSOD - but even this may not work on some. The strangest one's are those where you "fix" the BSOD and other problems crop up - such as black screen errors or an underlying hardware problem.
      My System SpecsSystem Spec

  9. #9


    United States
    Posts : 5
    Windows 8.1 Preview


    Well thank you for the time that you put into helping me. I will wait and see if I get another BSOD and work from there. The external drive is just used for mass storage of things like music/movies and my windows backups. It is about 4 years old so maybe it is but it doesn't run all too often. I also reformatted it a few months ago. Is the best route out right replacing the drive?
      My System SpecsSystem Spec

  10. #10


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


    The best thing would be to test the drive with one of the tests from here: Hard Drive Diagnostic Procedure
      My System SpecsSystem Spec

Most likely driver issues but not sure how to resolve
Related Threads
Driver issues after 8.1 upgrade in Drivers & Hardware
Hi, I upgraded to 8.1 and noticed issues with my graphics card driver (intel hd4000 10.18.10.3316), so I had to roll that back. Also, before the upgrade I had the Synaptics settings program for my touchpad driver, but after the update that seems to have disappeared. I've searched on Samsung's...
Windows 8 Print Driver Issues :( in Drivers & Hardware
My printer won't work at all on Windows 8 :( I get the following message: The print driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers Any assistance would be appreciated. Thanks Anne
Sidewinder x4 driver issues(?) in Drivers & Hardware
Hello people, first post/thread here... So the thing is I updated to windows 8 (pro 64 bits) recently, coming from windows 7 ultimate. I decided to "keep files/apps and personal settings", so basically I just didn't do a clean install. The problem now is that my keyboard (sidewinder x4) multimedia...
Won't Install / Driver Issues? in Installation & Setup
Trying to install Windows 8 Dev 64bit from USB (used Windows 7 DVD/USB Flash Tool from MS' site). It boots off USB fine, but then I get the errors shown in screenshot? Running netbook, ASUS UL20A. 20552056
Printer and driver issues in Drivers & Hardware
Hello I did a clean install of windows 8 pro 64 on a new ssd and have it running well (previously running vista 32). Do I need to install my old drivers? I tried to use the old gigabyte disk but it stuffed up the computer and couldn't recognise cd drive after reboot. Are they all necessary?
Bluetooth driver issues in Drivers & Hardware
Asus VX6 laptop, Razer Orochi mouse, Sennheiser MM 500 X headphones. None of this stuff will stay connected for more then an hour at a time. I am really disappointed in the bluetooth support in Win 8.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook