Windows 8 and 8.1 Forums


BSOD random - Win 8.1 DRIVER_VERIFIER_DETECTED_VIOLATION

  1. #1


    Posts : 10
    Windows 8.1 64bit

    BSOD random - Win 8.1 DRIVER_VERIFIER_DETECTED_VIOLATION


    I've done all that I could to figure out my problem with google and youtube (The Same?). Anyway, I've been getting these BSODs for seemingly no reason at all. In fact, it happens at idle sometimes. I then ran memtest for many hours one stick at a time to only find that I pretty much wasted a bunch of time, No errors reported. Which lead me to finally run the driver verifier and needless to say, it crashed. But hey, at least I can get in to windows. Any help resolving this would change my life forever. I think. lol

    Blue screen view seems to blame ntokrnl.exe a bunch for my issues. Not sure if that information helps at all. Let me know if anymore information is required.
    Last edited by SirBizz41; 06 Aug 2014 at 05:17. Reason: Because i think im posting wrong. No replies.

      My System SpecsSystem Spec

  2. #2


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


    Just FYI - ntoskrnl.exe is the kernel (core) of the Windows Operating System. As such, if it were to blame, you'd be seeing many more issues other than just the occasional BSOD. We use other techniques (including Driver Verifier) to help coax out the actual offending driver.

    You have 3 hard drives. What is the make/model/wattage and age of your Power Supply?

    This device is disabled. Is this deliberate? If so, why?
    avast! SecureLine TAP Adapter v3 ROOT\NET\0000 This device is disabled.
    I would suggest uninstalling it if you're not using it.

    Driver Verifier blames your Avast. I'd suggest uninstalling it and testing with Windows Defender and the Windows Firewall enabled. Feel free to reinstall the latest version of Avast if you'd like - but please wait until we're finished troubleshooting.

    Please uninstall XFastLAN and XFastUSB software as it is known to cause BSOD's on some Windows systems

    Out of 11 memory dumps there were 7 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - missing Windows Updates
    - compatibility issues (3rd party hardware/drivers) - and older systems
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

    You can get a head start on the hardware diagnostics if you'd like - they are located here: Hardware Diagnostics

    Please uninstall Corsair Link as it's known to cause BSOD's on some Windows systems.

    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
    NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.
    Please uninstall your Western Digital software. The wdcsam64.sys driver dates from 2008 and is known to cause BSOD's on some Windows systems.

    Please uninstall MalwareBytes - it is running at the same time as Avast and may be causing conflicts. Feel free to reinstall the latest version, but DO NOT allow it to run while Avast is running (as long as we're troubleshooting).

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

    vtimidi.sys Wed Apr 22 14:34:07 2009 (49EF631F)
    Virus TI WDM MIDI 64bit Driver by Kemper Digital Gmbh
    vtimidi.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.

    synusb64.sys Fri Jun 26 09:30:11 2009 (4A44CD63)
    Suyin USB 2.0 Webcam driver
    http://www.carrona.org/drivers/driver.php?id=synusb64.sys

    AsrAppCharger.sys Tue May 10 04:28:46 2011 (4DC8F73E)
    ASRock App Charger Likely BSOD cause - haven't seen recently (15Jan2013)
    http://www.carrona.org/drivers/driver.php?id=AsrAppCharger.sys

    MxEFUF64.sys Thu Oct 20 12:24:05 2011 (4EA04B25)
    Matrox Graphics Extio Function Upper Filter Driver[br](discussion about this driver here: DriverPack Graphics B-"super-generic" Matrox Extio PCI-PCI bridge installs on ATI/nV HW (Page 1) - DriverPack Graphics - DriverPacks.net Forum )
    http://www.carrona.org/drivers/driver.php?id=MxEFUF64.sys

    Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.




    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Aug  5 19:53:29.265 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080514-29421-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:01:52.069
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {18, 0, ffffd001d7c8a180, 5}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd001d7c8a180, The PRCB address of the hung processor.
    Arg4: 0000000000000005, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    PROCESS_NAME:  LogonUI.exe
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_VRF_ANALYSIS_INCONCLUSIVE
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug  5 19:51:12.630 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080514-38046-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:02:07.431
    *** WARNING: Unable to verify timestamp for aswSP.sys
    *** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
    Probably caused by :aswSP.sys ( aswSP+3501e )
    BugCheck C4, {0, 0, 1, 0}
    BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    Arguments: 
    Arg1: 0000000000000000, caller is trying to allocate zero bytes
    Arg2: 0000000000000000, current IRQL
    Arg3: 0000000000000001, pool type
    Arg4: 0000000000000000, number of bytes
    BUGCHECK_STR:  0xc4_0
    PROCESS_NAME:  SearchIndexer.
    FAILURE_BUCKET_ID: 0xc4_0_VRF_aswSP+3501e
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug  5 19:30:41.644 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080514-32921-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:57:54.378
    *** WARNING: Unable to verify timestamp for amd_sata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys
    Probably caused by :amd_sata.sys
    BugCheck 9F, {3, ffffe001054b8060, fffff802cbd1f8b0, ffffe00106821010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001054b8060, Physical Device Object of the stack
    Arg3: fffff802cbd1f8b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00106821010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_disk_IMAGE_amd_sata.sys
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug  5 15:42:19.406 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080514-34281-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:48:18.140
    Probably caused by :memory_corruption ( nt!MiAgeWorkingSet+2cb )
    BugCheck 50, {fffff690000c96b8, 0, fffff8022baec58b, 2}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
    Arguments: 
    Arg1: fffff690000c96b8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff8022baec58b, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  mbamservice.ex
    FAILURE_BUCKET_ID: AV_nt!MiAgeWorkingSet
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug  3 17:57:56.900 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080314-32234-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 8:59:16.634
    Probably caused by :memory_corruption ( ONE_BIT )
    BugCheck 1A, {41792, fffff68000072200, 800000000000, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
        the PTE. Parameters 3/4 contain the low/high parts of the PTE.
    Arg2: fffff68000072200
    Arg3: 0000800000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41792
    PROCESS_NAME:  mbamservice.ex
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug  3 08:02:46.251 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080314-32078-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:19:42.985
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :win32k.sys ( win32k+15c27a )
    BugCheck 50, {fffff901467eabc4, 1, fffff9600017127a, 0}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
    Arguments: 
    Arg1: fffff901467eabc4, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff9600017127a, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000000, (reserved)
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  InstallManager
    FAILURE_BUCKET_ID: AV_win32k+15c27a
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug  3 04:53:05.672 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080314-31609-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 2:05:36.406
    Probably caused by :memory_corruption ( nt!MiAgeWorkingSet+2cb )
    BugCheck 50, {fffff6ff7dbed7f8, 0, fffff80029e9058b, 2}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
    Arguments: 
    Arg1: fffff6ff7dbed7f8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80029e9058b, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  NIHardwareServ
    FAILURE_BUCKET_ID: AV_nt!MiAgeWorkingSet
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug  3 02:47:05.779 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080314-31843-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:41:59.515
    Probably caused by :memory_corruption ( nt!MiAgeWorkingSet+2cb )
    BugCheck 50, {fffff680800b89d0, 0, fffff8016fe8258b, 2}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
    Arguments: 
    Arg1: fffff680800b89d0, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff8016fe8258b, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  mbamservice.ex
    FAILURE_BUCKET_ID: AV_nt!MiAgeWorkingSet
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jul 31 12:01:08.411 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\073114-31593-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:19:17.146
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :win32k.sys ( win32k+1edbb5 )
    BugCheck 139, {2, ffffd0011a786c60, ffffd0011a786bb8, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
        buffer overrun.
    Arg2: ffffd0011a786c60, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd0011a786bb8, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID: 0x139_2_win32k+1edbb5
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jul 31 11:41:28.462 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\073114-31484-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:12:27.198
    Probably caused by :memory_corruption ( ONE_BIT )
    BugCheck 1A, {41792, fffff6800002fe38, 10000000000, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
        the PTE. Parameters 3/4 contain the low/high parts of the PTE.
    Arg2: fffff6800002fe38
    Arg3: 0000010000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41792
    PROCESS_NAME:  mbamscheduler.
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jul 31 10:28:38.828 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\073114-32031-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:18:53.563
    *** WARNING: Unable to verify timestamp for SamsungRapidDiskFltr.sys
    *** ERROR: Module load completed but symbols could not be loaded for SamsungRapidDiskFltr.sys
    Probably caused by :SamsungRapidDiskFltr.sys ( SamsungRapidDiskFltr+18d07 )
    BugCheck 1000007E, {ffffffffc0000005, fffff8019ef38d07, ffffd000241fb848, ffffd000241fb050}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8019ef38d07, The address that the exception occurred at
    Arg3: ffffd000241fb848, Exception Record Address
    Arg4: ffffd000241fb050, Context Record Address
    PROCESS_NAME:  System
    BUGCHECK_STR:  AV
    FAILURE_BUCKET_ID: AV_SamsungRapidDiskFltr+18d07
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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 Aug  5 19:53:29.265 2014 (UTC - 4:00)**************************
    wdcsam64.sys                      Wed Apr 16 04:39:08 2008 (4805BB2C)
    vtimidi.sys                       Wed Apr 22 14:34:07 2009 (49EF631F)
    synusb64.sys                      Fri Jun 26 09:30:11 2009 (4A44CD63)
    MBfilt64.sys                      Thu Jul 30 23:40:32 2009 (4A7267B0)
    AsrAppCharger.sys                 Tue May 10 04:28:46 2011 (4DC8F73E)
    FNETTBOH_305.SYS                  Fri May 13 01:09:28 2011 (4DCCBD08)
    MxEFUF64.sys                      Thu Oct 20 12:24:05 2011 (4EA04B25)
    LPCFilter.sys                     Tue Mar  6 09:58:27 2012 (4F562613)
    FNETURPX.SYS                      Wed May 30 23:00:47 2012 (4FC6DEDF)
    VirusUSB.sys                      Thu Jul 26 11:51:33 2012 (50116785)
    vtiaudio.sys                      Thu Jul 26 12:19:39 2012 (50116E1B)
    usbfilter.sys                     Tue Aug 28 21:27:12 2012 (503D6FF0)
    iLokDrvr.sys                      Wed Nov  7 14:00:02 2012 (509AAFB2)
    amdide64.sys                      Tue Dec  4 04:49:28 2012 (50BDC728)
    vidsflt.sys                       Thu Feb 14 02:04:41 2013 (511C8C89)
    e1i63x64.sys                      Wed Mar 20 03:37:29 2013 (51496739)
    RTKVHD64.sys                      Fri Mar 29 09:40:06 2013 (515599B6)
    Tpkd.sys                          Thu Apr 11 17:04:30 2013 (5167255E)
    AsrRamDisk.sys                    Thu May  9 04:50:45 2013 (518B6365)
    cfosspeed6.sys                    Wed May 29 12:47:24 2013 (51A6311C)
    S3XXx64.sys                       Thu May 30 01:42:54 2013 (51A6E6DE)
    CORK30.sys                        Thu Jun  6 21:52:30 2013 (51B13CDE)
    EtronXHCI.sys                     Wed Jul 17 02:23:45 2013 (51E63871)
    EtronHub3.sys                     Mon Oct 28 22:14:59 2013 (526F1A23)
    mbam.sys                          Wed Oct 30 12:11:45 2013 (52712FC1)
    pikbd.sys                         Sat Nov 30 07:32:29 2013 (5299DADD)
    amdkmpfd.sys                      Fri Dec 13 00:33:34 2013 (52AA9C2E)
    ysusb64.sys                       Mon Dec 16 23:23:33 2013 (52AFD1C5)
    AODDriver2.sys                    Tue Feb 11 06:06:52 2014 (52FA044C)
    sshid.sys                         Tue Feb 25 16:50:04 2014 (530D100C)
    AMDACPKSL.SYS                     Tue Mar 11 19:49:44 2014 (531FA118)
    AtihdWB6.sys                      Tue Mar 11 19:50:02 2014 (531FA12A)
    asstor64.sys                      Thu Mar 13 23:38:20 2014 (532279AC)
    amd_sata.sys                      Thu Mar 20 23:01:59 2014 (532BABA7)
    amd_xata.sys                      Thu Mar 20 23:02:02 2014 (532BABAA)
    aswHwid.sys                       Thu Jun 26 07:31:26 2014 (53AC048E)
    aswMonFlt.sys                     Thu Jun 26 07:32:51 2014 (53AC04E3)
    aswRdr2.sys                       Thu Jun 26 07:33:28 2014 (53AC0508)
    aswKbd.sys                        Thu Jun 26 07:34:01 2014 (53AC0529)
    aswSnx.sys                        Thu Jun 26 07:34:44 2014 (53AC0554)
    aswRvrt.sys                       Thu Jun 26 07:35:39 2014 (53AC058B)
    aswVmm.sys                        Thu Jun 26 07:35:49 2014 (53AC0595)
    aswNdisFlt.sys                    Thu Jun 26 07:36:26 2014 (53AC05BA)
    aswStm.sys                        Thu Jun 26 07:47:09 2014 (53AC083D)
    aswSP.sys                         Wed Jul  2 13:38:12 2014 (53B44384)
    atikmpag.sys                      Wed Jul  9 11:19:51 2014 (53BD5D97)
    atikmdag.sys                      Wed Jul  9 11:34:34 2014 (53BD610A)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug  5 19:51:12.630 2014 (UTC - 4:00)**************************
    TuneUpUtilitiesDriver64.sys       Fri May 25 06:28:19 2012 (4FBF5EC3)
    iqvw64e.sys                       Thu Nov 14 10:22:43 2013 (5284EAC3)
    mwac.sys                          Tue Mar  4 16:47:40 2014 (531649FC)
    MBAMSwissArmy.sys                 Thu Mar 20 18:12:35 2014 (532B67D3)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug  5 19:30:41.644 2014 (UTC - 4:00)**************************
    CorsairLINK_HardwareMonitor.sys   Sat Jul 26 09:29:37 2008 (488B26C1)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug  5 15:42:19.406 2014 (UTC - 4:00)**************************
    SamsungRapidDiskFltr.sys          Mon May 19 10:24:16 2014 (537A1410)
    SamsungRapidFSFltr.sys            Mon May 19 10:24:18 2014 (537A1412)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug  3 17:57:56.900 2014 (UTC - 4:00)**************************
    xusb22.sys                        Tue Mar 18 04:18:41 2014 (53280161)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug  3 04:53:05.672 2014 (UTC - 4:00)**************************
    e1q63x64.sys                      Tue Jul 10 19:16:09 2012 (4FFCB7B9)
    
    http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
    vtimidi.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=synusb64.sys
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=AsrAppCharger.sys
    http://www.carrona.org/drivers/driver.php?id=FNETTBOH_305.SYS
    http://www.carrona.org/drivers/driver.php?id=MxEFUF64.sys
    http://www.carrona.org/drivers/driver.php?id=LPCFilter.sys
    http://www.carrona.org/drivers/driver.php?id=FNETURPX.SYS
    VirusUSB.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.
    vtiaudio.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=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=iLokDrvr.sys
    http://www.carrona.org/drivers/driver.php?id=amdide64.sys
    http://www.carrona.org/drivers/driver.php?id=vidsflt.sys
    http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=Tpkd.sys
    http://www.carrona.org/drivers/driver.php?id=AsrRamDisk.sys
    http://www.carrona.org/drivers/driver.php?id=cfosspeed6.sys
    http://www.carrona.org/drivers/driver.php?id=S3XXx64.sys
    CORK30.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=EtronXHCI.sys
    http://www.carrona.org/drivers/driver.php?id=EtronHub3.sys
    http://www.carrona.org/drivers/driver.php?id=mbam.sys
    pikbd.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=amdkmpfd.sys
    http://www.carrona.org/drivers/driver.php?id=ysusb64.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    sshid.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=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=asstor64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=aswHwid.sys
    http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
    http://www.carrona.org/drivers/driver.php?id=aswKbd.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=aswVmm.sys
    http://www.carrona.org/drivers/driver.php?id=aswNdisFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswStm.sys
    http://www.carrona.org/drivers/driver.php?id=aswSP.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=TuneUpUtilitiesDriver64.sys
    http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
    http://www.carrona.org/drivers/driver.php?id=mwac.sys
    http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
    CorsairLINK_HardwareMonitor.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=SamsungRapidDiskFltr.sys
    http://www.carrona.org/drivers/driver.php?id=SamsungRapidFSFltr.sys
    http://www.carrona.org/drivers/driver.php?id=xusb22.sys
    http://www.carrona.org/drivers/driver.php?id=e1q63x64.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 10
    Windows 8.1 64bit


    First off I want to thank you for taking the time out to help me. I went through all of your recommendations and performed them as best I can. The information I think you need is as follows:

    Power Supply is the Corsair RM 750 and its about 3-4 months old.

    My Bios is up to date per ASROCK's website.

    No windows updates were available. However, I did see that I could turn on more features. Should I?

    I changed my overclock back stock setting in BIOS.

    Uninstalled Malwarebytes, AVAST anti-virus, XFastLAN, XFastUSB, Asrock App Charger, Asrock Ramdisk, and CorsairLink (this isn't going to my processor at risk is it?).

    The drivers were a crazy trip. I was able to work on a lot of them some of them wouldn't update without BSOD.

    I was not able to do anything for the Western Digital driver as I have no software other than the driver installed. Should I use their Software? Or remove the external drive from the system? Updating firmware didn't work as expected and I am thinking installing the software will be pointless. I am willing to try it upon your recommendation.

    The SynUSB64 driver was not related to a cam. It is used by my e-licenser software for audio production plugins. I uninstalled the software and the driver was gone. Then I updated to the newest software available, only to find I got the same driver again. This scenario also occurred with the vtimidi driver.

    The MAXTOR driver was a challenge as I do not know what software it is related to. It seems to be related to the case plugs and switch but I'm am not completely certain. Could use some direction on this one.

    I have attached notes on what occurred with all of the drivers that are older than the release date of Windows 8. A few of them caused BSOD and I have also attached the SF zip for more insight.

    I also uninstalled the graphics drivers by using the Programs method, also used Driver Fusion to be sure I removed it. I can not be certain that I removed the AODDriver2.sys because I could not find its location to begin with. This is why I have not reinstalled the new drivers until I hear from you. I was also concerned on how to only install the drivers to the cards because it seems that you would have to run the software which gives you more than you want by default.

    Well I hope I addressed everything... Let me know if I missed anything.
      My System SpecsSystem Spec

  4. #4


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


    You've done a very good job of making the changes that I requested. Thank you!
    In general what we do is we fix what we can, then we see if that's helped you.
    If not, then we dig deeper (and this may be one of those that we have to continue digging for a while.
    I would strongly suggest starting on the hardware diagnositics - as this may be a hardware problem: Hardware Diagnostics

    No need to turn more features on. The number of updates needed is just an average - so it may not apply to your system. All that matters is that you've checked to see if updates are needed - and that you got them if they were available.

    Removing these programs won't put your processor at risk. Should you start to overclock again, I'd suggest checking your temps regularly. I suggest this free temp monitoring tool as I haven't seen BSOD's associated with it: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

    I added the eLicenser software to the Driver Reference Table. Interestingly, when I installed it on my system I didn't get a copy of that driver!

    I'm uncertain if you're referring to the Maxtor or the Matrox driver. Regardless, you've done enough now that it's save to leave this one be for now. If the BSOD's continue we can address it later on.

    This is the procedure to install only the video driver (and not the AMD OverDrive): ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

    Please uninstall the e-Licenser software and leave it uninstalled while we're troubleshooting.
    I prefer to use the uninstallers as we may break things if we try to manually remove a lot of drivers.

    Please note that the AMD OverDrive driver is still installed. Did you remove the drivers after the latest BSOD (the latest one uploaded was from Wed Aug 6 11:53:16.124 2014
    Had you performed all of the things that you mentioned prior to this?
    Please note that the drivers that are listed below are very similar to what you started with:

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Wed Aug  6 11:53:16.124 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080614-17843-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:29:44.860
    *** WARNING: Unable to verify timestamp for cpudrv64.sys
    *** ERROR: Module load completed but symbols could not be loaded for cpudrv64.sys
    Probably caused by :cpudrv64.sys ( cpudrv64+1912 )
    BugCheck 3B, {c0000096, fffff801cea9d912, ffffd00028e96cc0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c0000096, Exception code that caused the bugcheck
    Arg2: fffff801cea9d912, Address of the instruction which caused the bugcheck
    Arg3: ffffd00028e96cc0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  inteldriver.ex
    FAILURE_BUCKET_ID: 0x3B_cpudrv64+1912
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Aug  6 11:23:07.548 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080614-19140-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:03:57.282
    Probably caused by :ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+59b )
    BugCheck C5, {8, 2, 0, fffff802b8310a5b}
    BugCheck Info: DRIVER_CORRUPTED_EXPOOL (c5)
    Arguments: 
    Arg1: 0000000000000008, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff802b8310a5b, address which referenced memory
    BUGCHECK_STR:  0xC5_2
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Aug  6 11:18:45.549 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080614-19406-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:16:40.283
    *** WARNING: Unable to verify timestamp for EtronXHCI.sys
    *** ERROR: Module load completed but symbols could not be loaded for EtronXHCI.sys
    Probably caused by :EtronXHCI.sys ( EtronXHCI+ca20 )
    BugCheck D1, {c, 2, 0, fffff80139ab5a20}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 000000000000000c, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff80139ab5a20, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_EtronXHCI+ca20
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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 Aug  6 11:53:16.124 2014 (UTC - 4:00)**************************
    vtimidi.sys                   Wed Apr 22 14:34:07 2009 (49EF631F)
    synusb64.sys                  Fri Jun 26 09:30:11 2009 (4A44CD63)
    cpudrv64.sys                  Tue Aug 11 12:39:13 2009 (4A819EB1)
    ivusb.sys                     Thu May 13 22:42:27 2010 (4BECB893)
    MxEFUF64.sys                  Thu Oct 20 12:24:05 2011 (4EA04B25)
    LPCFilter.sys                 Tue Mar  6 09:58:27 2012 (4F562613)
    TuneUpUtilitiesDriver64.sys   Fri May 25 06:28:19 2012 (4FBF5EC3)
    VirusUSB.sys                  Thu Jul 26 11:51:33 2012 (50116785)
    vtiaudio.sys                  Thu Jul 26 12:19:39 2012 (50116E1B)
    usbfilter.sys                 Tue Aug 28 21:27:12 2012 (503D6FF0)
    iLokDrvr.sys                  Wed Nov  7 14:00:02 2012 (509AAFB2)
    amdide64.sys                  Tue Dec  4 04:49:28 2012 (50BDC728)
    vidsflt.sys                   Thu Feb 14 02:04:41 2013 (511C8C89)
    e1i63x64.sys                  Wed Mar 20 03:37:29 2013 (51496739)
    Tpkd.sys                      Thu Apr 11 17:04:30 2013 (5167255E)
    S3XXx64.sys                   Thu May 30 01:42:54 2013 (51A6E6DE)
    CORK30.sys                    Thu Jun  6 21:52:30 2013 (51B13CDE)
    EtronXHCI.sys                 Wed Jul 17 02:23:45 2013 (51E63871)
    EtronHub3.sys                 Mon Oct 28 22:14:59 2013 (526F1A23)
    pikbd.sys                     Sat Nov 30 07:32:29 2013 (5299DADD)
    amdkmpfd.sys                  Fri Dec 13 00:33:34 2013 (52AA9C2E)
    ysusb64.sys                   Mon Dec 16 23:23:33 2013 (52AFD1C5)
    AODDriver2.sys                Tue Feb 11 06:06:52 2014 (52FA044C)
    sshid.sys                     Tue Feb 25 16:50:04 2014 (530D100C)
    AMDACPKSL.SYS                 Tue Mar 11 19:49:44 2014 (531FA118)
    AtihdWB6.sys                  Tue Mar 11 19:50:02 2014 (531FA12A)
    asstor64.sys                  Thu Mar 13 23:38:20 2014 (532279AC)
    amd_sata.sys                  Thu Mar 20 23:01:59 2014 (532BABA7)
    amd_xata.sys                  Thu Mar 20 23:02:02 2014 (532BABAA)
    RTKVHD64.sys                  Wed May 14 06:28:52 2014 (53734564)
    aswHwid.sys                   Thu Jun 26 07:31:26 2014 (53AC048E)
    aswMonFlt.sys                 Thu Jun 26 07:32:51 2014 (53AC04E3)
    aswRdr2.sys                   Thu Jun 26 07:33:28 2014 (53AC0508)
    aswKbd.sys                    Thu Jun 26 07:34:01 2014 (53AC0529)
    aswSnx.sys                    Thu Jun 26 07:34:44 2014 (53AC0554)
    aswRvrt.sys                   Thu Jun 26 07:35:39 2014 (53AC058B)
    aswVmm.sys                    Thu Jun 26 07:35:49 2014 (53AC0595)
    aswNdisFlt.sys                Thu Jun 26 07:36:26 2014 (53AC05BA)
    aswStm.sys                    Thu Jun 26 07:47:09 2014 (53AC083D)
    aswSP.sys                     Wed Jul  2 13:38:12 2014 (53B44384)
    atikmpag.sys                  Wed Jul  9 11:19:51 2014 (53BD5D97)
    atikmdag.sys                  Wed Jul  9 11:34:34 2014 (53BD610A)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Aug  6 11:23:07.548 2014 (UTC - 4:00)**************************
    iqvw64e.sys                   Thu Nov 14 10:22:43 2013 (5284EAC3)
    
    vtimidi.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=synusb64.sys
    http://www.carrona.org/drivers/driver.php?id=cpudrv64.sys
    ivusb.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=MxEFUF64.sys
    http://www.carrona.org/drivers/driver.php?id=LPCFilter.sys
    http://www.carrona.org/drivers/driver.php?id=TuneUpUtilitiesDriver64.sys
    VirusUSB.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.
    vtiaudio.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=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=iLokDrvr.sys
    http://www.carrona.org/drivers/driver.php?id=amdide64.sys
    http://www.carrona.org/drivers/driver.php?id=vidsflt.sys
    http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
    http://www.carrona.org/drivers/driver.php?id=Tpkd.sys
    http://www.carrona.org/drivers/driver.php?id=S3XXx64.sys
    CORK30.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=EtronXHCI.sys
    http://www.carrona.org/drivers/driver.php?id=EtronHub3.sys
    pikbd.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=amdkmpfd.sys
    http://www.carrona.org/drivers/driver.php?id=ysusb64.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    sshid.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=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=asstor64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=aswHwid.sys
    http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
    http://www.carrona.org/drivers/driver.php?id=aswKbd.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=aswVmm.sys
    http://www.carrona.org/drivers/driver.php?id=aswNdisFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswStm.sys
    http://www.carrona.org/drivers/driver.php?id=aswSP.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
      My System SpecsSystem Spec

  5. #5


    Posts : 10
    Windows 8.1 64bit


    Thanks for the reply. I have uninstalled e-licenser after creating the new DMP file. I find it weird that you didn't get the same driver that I did. Hopefully its not because of some sort of corruption. Unfortunately I got another BSOD after all we've done. Seems to be pointing to the Samsung Magician software or something. Not sure what to do about that.

    I decided not to fool around with the AMD graphics anymore. They seem to be trouble than its worth. So now I have an NVIDIA card. So no more AMD overdrive. Hopefully that will bring some happiness to my system. I also changed my power supply as I thought that may have been an issue as well. Its the same make and model but it now provides 850W, which I think should cover all my concerns for power.

    I found something very interesting. I did some research after reading your advice on windows updates. I clicked the installed updates link and it said that no updates are installed on this computer. Not sure if that is default dialog or not but I felt that it was something I needed to reveal. Another thing is that I currently have Windows 7 running on another hard drive. Its for business reasons as the company uses software not yet compatible on windows 8. For example, some of our websites are only compatible with IE 9 and 10. So thats poses a problem for me running 8.1. Which is why I have the dual boot thing going on. I just thought I'd put that out there as well. I'm not even sure its configured correctly but its been working thus far. I haven't accessed it yet but I'm certain that I have to do a driver overhaul once I access it. Any recommendations are welcome as I value your help and knowledge base. Lastly, I've attached the more recent BSOD DMP.
      My System SpecsSystem Spec

  6. #6


    Posts : 10
    Windows 8.1 64bit


    Received another after the last post. Here's for insight. Think I'm thru for the day. lol
      My System SpecsSystem Spec

  7. #7


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


    Most of what we do here is we remove known/suspected problems, then see what's left.
    If we identify more problems, then we remove them, etc, etc, etc
    After a while we may run out of known/suspected problems - and if the BSOD's haven't stopped by then - we move on to hardware and/or Windows troubleshooting.

    It's not surprising for us to remove a set of problems - only to find another set popping up. I suspect that it's due to conflicts between 3rd party drivers (rather than problems within Windows) - so we have 2 (or more) sets of problems to attempt to deal with.

    In this case, it looks as if the problem drivers from e-Licenser are still on the system.
    So it's time to try and manually remove them.
    To do this, start with these instructions:
    1) Create a Restore Point using System Restore
    2) Create a Repair disc (Recovery Drive in Win8.1):
    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 synusb64.sys that are starting (or any other e-Licenser entries) (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 synusb64.sys (or any other e-Licenser entries) are "Uninstalled" (DO NOT DISABLE THESE).
    6) Check in the Services applet (services.msc) to be sure any instances of synusb64.sys or any other e-Licenser entries are disabled.
    7) Go to C:\Windows\System32\drivers and rename the synusb64.sys driver to synusb64.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 synusb64.BAD to synusb64.sys
    Code:
    ren C:\Windows\System32\drivers\synusb64.BAD C:\Windows\System32\drivers\synusb64.sys
    2) 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!
    More info in the next post.....
      My System SpecsSystem Spec

  8. #8


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


    The ivusb.sys driver is from 2010 and is an Initio Driver for USB Default Controller (some sort of USB controller for hard drives).
    Most likely from Your Akai Pro Vyzex MPK88-61 device Please either update it to the latest, Win8.1 compatible version - or uninstall it and remove the device while we're troubleshooting.

    IMO let's just fix these 2 problems (the e-Licenser and the Vyzex device and then see what happens.
    I'm a bit leery of manually removing a bunch of stuff all at once - as we can bust a bunch of things and still not achieve anything.

    Here's the results of the BSOD analysis:

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sat Aug  9 18:48:56.708 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080914-14734-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:00:17.448
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :win32k.sys ( win32k+27b24 )
    BugCheck 3B, {c0000005, fffff960001a8b24, ffffd0002148ece0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960001a8b24, Address of the instruction which caused the bugcheck
    Arg3: ffffd0002148ece0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  TuneUpUtilitie
    FAILURE_BUCKET_ID: 0x3B_win32k+27b24
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug  9 13:41:14.419 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080914-16500-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 2:15:03.160
    *** WARNING: Unable to verify timestamp for SamsungRapidDiskFltr.sys
    *** ERROR: Module load completed but symbols could not be loaded for SamsungRapidDiskFltr.sys
    Probably caused by :SamsungRapidDiskFltr.sys ( SamsungRapidDiskFltr+18d07 )
    BugCheck 1000007E, {ffffffffc0000005, fffff801cd0add07, ffffd00024c95848, ffffd00024c95050}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff801cd0add07, The address that the exception occurred at
    Arg3: ffffd00024c95848, Exception Record Address
    Arg4: ffffd00024c95050, Context Record Address
    PROCESS_NAME:  System
    BUGCHECK_STR:  AV
    FAILURE_BUCKET_ID: AV_SamsungRapidDiskFltr+18d07
      BIOS Version                  P1.70
      BIOS Release Date             06/04/2014
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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 Aug  9 18:48:56.708 2014 (UTC - 4:00)**************************
    synusb64.sys                  Fri Jun 26 09:30:11 2009 (4A44CD63)
    ivusb.sys                     Thu May 13 22:42:27 2010 (4BECB893)
    MxEFUF64.sys                  Thu Oct 20 12:24:05 2011 (4EA04B25)
    MFWCtwl.sys                   Fri Dec 23 08:13:58 2011 (4EF47E96)
    LPCFilter.sys                 Tue Mar  6 09:58:27 2012 (4F562613)
    TuneUpUtilitiesDriver64.sys   Fri May 25 06:28:19 2012 (4FBF5EC3)
    usbfilter.sys                 Tue Aug 28 21:27:12 2012 (503D6FF0)
    iLokDrvr.sys                  Wed Nov  7 14:00:02 2012 (509AAFB2)
    amdide64.sys                  Tue Dec  4 04:49:28 2012 (50BDC728)
    vidsflt.sys                   Thu Feb 14 02:04:41 2013 (511C8C89)
    e1i63x64.sys                  Wed Mar 20 03:37:29 2013 (51496739)
    Tpkd.sys                      Thu Apr 11 17:04:30 2013 (5167255E)
    S3XXx64.sys                   Thu May 30 01:42:54 2013 (51A6E6DE)
    CORK30.sys                    Thu Jun  6 21:52:30 2013 (51B13CDE)
    nvhda64v.sys                  Thu Nov 28 08:38:09 2013 (52974741)
    pikbd.sys                     Sat Nov 30 07:32:29 2013 (5299DADD)
    amdkmpfd.sys                  Fri Dec 13 00:33:34 2013 (52AA9C2E)
    ysusb64.sys                   Mon Dec 16 23:23:33 2013 (52AFD1C5)
    sshid.sys                     Tue Feb 25 16:50:04 2014 (530D100C)
    asstor64.sys                  Thu Mar 13 23:38:20 2014 (532279AC)
    xusb22.sys                    Tue Mar 18 04:18:41 2014 (53280161)
    amd_sata.sys                  Thu Mar 20 23:01:59 2014 (532BABA7)
    amd_xata.sys                  Thu Mar 20 23:02:02 2014 (532BABAA)
    nvvad64v.sys                  Fri Mar 28 09:32:06 2014 (533579D6)
    RTKVHD64.sys                  Wed May 14 06:28:52 2014 (53734564)
    SamsungRapidDiskFltr.sys      Mon May 19 10:24:16 2014 (537A1410)
    SamsungRapidFSFltr.sys        Mon May 19 10:24:18 2014 (537A1412)
    nvlddmkm.sys                  Wed Jul  2 13:42:02 2014 (53B4446A)
    NvStreamKms.sys               Fri Jul 25 07:35:56 2014 (53D2411C)
    
    http://www.carrona.org/drivers/driver.php?id=synusb64.sys
    ivusb.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=MxEFUF64.sys
    http://www.carrona.org/drivers/driver.php?id=MFWCtwl.sys
    http://www.carrona.org/drivers/driver.php?id=LPCFilter.sys
    http://www.carrona.org/drivers/driver.php?id=TuneUpUtilitiesDriver64.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=iLokDrvr.sys
    http://www.carrona.org/drivers/driver.php?id=amdide64.sys
    http://www.carrona.org/drivers/driver.php?id=vidsflt.sys
    http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
    http://www.carrona.org/drivers/driver.php?id=Tpkd.sys
    http://www.carrona.org/drivers/driver.php?id=S3XXx64.sys
    CORK30.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
    pikbd.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=amdkmpfd.sys
    http://www.carrona.org/drivers/driver.php?id=ysusb64.sys
    sshid.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=asstor64.sys
    http://www.carrona.org/drivers/driver.php?id=xusb22.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=SamsungRapidDiskFltr.sys
    http://www.carrona.org/drivers/driver.php?id=SamsungRapidFSFltr.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
      My System SpecsSystem Spec

  9. #9


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


    PS - I'm not convinced that the Samsung software is at fault. I suspect other low-level problems that occurred just when the Samsung stuff was in memory.
      My System SpecsSystem Spec

  10. #10


    Posts : 10
    Windows 8.1 64bit


    Thanks for getting back to me and on a weekend!!! That's awesome. I confirmed that system restore point does in fact work. Thanks for that. I hope I don't need it but it's there and that's great. Anyway, I am at a decision point that was not referenced in your directions. I used the autorun software to disable the elicenser and synusb thing. I went to the device manager to "uninstall" it but I noticed a check box for deleting the driver. During the stare down, I realized that I had been beaten and took these screen shots to get further advice from you. Do I click the delete box? I have also attached services screen captures to show that neither of these items are on the list. I did not change the driver name yet, as I still need help as explained before.

    In greater news. I think I defeated the ivusb.sys driver. Turns out that it was directly related to my Western Digital External HD. So I unistalled the hard drive (WD SES??) from the Device Manager list and the other occurrence thats listed it specifically disappeared from device manager as well. However, despite my win... It is still present under system32/drivers. Should I rename it or delete. I have no plans to continue the use of the Hard Drive for the sake of a stable system.

    I wish I had saw your opinion on the Samsung software earlier. As I have disabled rapid mode and uninstalled Samsung Magician. I'm not too hurt by it though. After research it seems that the gains are quite negligible in the real world application. I'm going to do another SF capture for you so that we are on the same page. Thanks again.

    Oh and one more thing.... when using the autorun program, I noticed some red and yellow entries. How much concern should I have?
      My System SpecsSystem Spec

Page 1 of 3 123 LastLast
BSOD random - Win 8.1 DRIVER_VERIFIER_DETECTED_VIOLATION
Related Threads
Random BSOD at random times in BSOD Crashes and Debugging
Hello, Im new here so bare with me :think: I built my custom pc a year ago now. Since day one iv been experiencing BSOD. At first it happened during or just after the first boot up of that day and was always Memory Management error. Soon after, i upgraded my ram from 4gb to 8 gb. After doing this...
I have been getting a ton of bsods I have re installed video drivers, updated and reinstalled windows 8. Did countless hardware test(Video ram, check memory, Cpu test) all passed temperatures stay around 25-35 c. Recently uninstalled all video drivers and re installed. The bsods sometimes go away...
BSOD When playing games random Bsod messages in BSOD Crashes and Debugging
Hey I have a problem with my pc I got a few weeks ago It keeps getting the bsod and turning on and off randomly at times I use it mostly to play games and watch youtube , twitch ext. also internet can sometimes crash pointing this out Bsod can happen when playing a game and when on the web...
BSOD at Random Times for Random Reasons in BSOD Crashes and Debugging
DCP Watchdog, Memory Management, Kernel Security Failure and several others at random times - especially during large file transfers between drives. I did a memory test and it stated there was an issue but I removed the culprit and the random BSOD continues. Thanks for your help
Can you help me with this BSOD ? I'm having same problem with windows 7 and windows 8.1 64bit DRIVER_VERIFIER_DETECTED_VIOLATION Bug Check code : 0x000000c4 Parameter : 00000000`00091001 fffff800`00243e40 ffffe000`021dda10 ffffe000`021dda98 Caused by address :...
Hey guys, so I am in a bit of a pickle. I have an HP m6-k015dx laptop and it is giving me hell. I will get random BSOD's, usually at or a short while after login. They usually happen consecutively and then stop. I was able to enable driver verifier in order to see what was wrong. After it was...
I started getting a blue screen yesterday when I switch on my Windows 8 Pro PC with error Driver_Verifier_Detected_Violation. I did not install anything new nor did any changes to my PC the last time I used it. After the system restart itself, it prompted me to do a refresh so as not to lose...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook