Windows 8 and 8.1 Forums


BSOD driver_power_state failure when running games

  1. #1


    Posts : 3
    Windows 8.1

    BSOD driver_power_state failure when running games


    Hi there

    I've been getting quite a few BSOD when running games. The crash usually occurs after running a few application and games. For example, when I start World of Warcraft everything works fine, but when I close WoW and start WoW Beta (seperate client) the game shows up in the task manager but doesn't launch. This problem isn't excluded to World of Warcraft since I get this issues with Skyrim and Geforce Experience as well.

    I'm also unable to kill WoW Beta in the task manager. I can hear my fans working at high capacity, but the game simply doesn't 'show up'.

    I have removed my nVidia drivers manually and then the leftovers with Display Driver Uninstaller. I also formatted my hard disk and did a fresh install, but to no avail. Two weeks ago I also returned my laptop to the manufacturer I purchased it from (bto.eu), but they were unable to replicate the error. They did change the memory though...

    When I did a driververifier and rebooted, I got stuck in a BSOD bootloop with the following message: DRIVER_VERIFIER_DETECTED_VIOLATION (FPWinlo.sys or FPwinio.sys - not sure if it's was an 'l' or 'i'). Since I was unable to boot into Windows, I did a fresh install of Windows.

    Link State Power Management is also disabled.

    Thank you in advance

    Kind regards

      My System SpecsSystem Spec

  2. #2


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


    I'm late for work, but FPwinio.sys is a driver most likely associated with an EgisTech biometric device (fingerprint sensor?)
    Try updating the drivers for that. If that doesn't stop the BSOD's, then try disabling the device in the BIOS. If you can't disable it in the BIOS, then do so in Device Manager (BE SURE that you can get into the system without this device - you don't want to lock yourself out while testing!).

    I'll post back more within the next 24 hours or so.
      My System SpecsSystem Spec

  3. #3


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


    Only 51 Windows Updates installed. Most systems have 70 to 90 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

    Don't worry about the specific number, it's just important that you have checked and installed any updates that were available (and didn't experience any errors).

    This device is disabled. Is this deliberate? If so, why?
    Not Available ACPI\PNPC000\1 This device is disabled.
    In the past this identifier was used for telephone modems, but I am seeing more and more references to the Airplane Mode switch

    Most of the memory dumps don't point at anything in particular, but the Driver Verifier one does blame the biometric device.
    If the system continues to BSOD, we'll try the Driver Verifier again (after you've updated the biometric device).

    Please also update your VIA sound/audio drivers. The VMfilt64.sys driver dates from 2009.

    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.

    The drivers that are struckout don't have updates available (AFAIK).



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sat Sep  6 09:23:51.334 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090614-6515-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:20:59.011
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe00192fef880, ffffd0002059b930, ffffe00192fe3b40}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe00192fef880, Physical Device Object of the stack
    Arg3: ffffd0002059b930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00192fe3b40, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Sep  6 09:02:27.320 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090614-5234-02.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:10:00.998
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe00188797060, fffff800fde58930, ffffe00188453010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe00188797060, Physical Device Object of the stack
    Arg3: fffff800fde58930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00188453010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Sep  6 08:51:59.384 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090614-6281-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 2:43:41.062
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe0008d5a6880, ffffd000f1b2a930, ffffe0008d5d8010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0008d5a6880, Physical Device Object of the stack
    Arg3: ffffd000f1b2a930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0008d5d8010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Sep  6 06:07:55.043 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090614-5234-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 1:57:43.722
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe0000e393880, ffffd001e1e94930, ffffe0000e3d6af0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0000e393880, Physical Device Object of the stack
    Arg3: ffffd001e1e94930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0000e3d6af0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Sep  6 04:09:47.165 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090614-5359-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 1:14:38.843
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000171ed060, ffffd0004661b930, ffffe00019890010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000171ed060, Physical Device Object of the stack
    Arg3: ffffd0004661b930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00019890010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep  5 15:28:29.939 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090514-5515-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:36:37.615
    *** ERROR: Module load completed but symbols could not be loaded for pci.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000007ed060, fffff80171652840, ffffe000009dc610}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000007ed060, Physical Device Object of the stack
    Arg3: fffff80171652840, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000009dc610, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep  5 13:11:53.182 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090514-155500-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:12:33.858
    *** ERROR: Module load completed but symbols could not be loaded for pci.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe0000181f800, fffff80315659b90, ffffe00002172010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0000181f800, Physical Device Object of the stack
    Arg3: fffff80315659b90, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00002172010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep  5 12:56:57.242 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090514-5343-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:37:18.918
    *** ERROR: Module load completed but symbols could not be loaded for pci.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000007e8060, fffff8005d852840, ffffe0000034f450}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000007e8060, Physical Device Object of the stack
    Arg3: fffff8005d852840, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0000034f450, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep  5 07:53:37.982 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090514-5390-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
    System Uptime:0 days 15:06:50.656
    *** ERROR: Module load completed but symbols could not be loaded for pci.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000007e7880, ffffd00020a94960, ffffe000018a4740}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000007e7880, Physical Device Object of the stack
    Arg3: ffffd00020a94960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000018a4740, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Sep  4 00:40:47.618 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090414-5359-01.dmp]
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
    System Uptime:0 days 7:26:11.292
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 9F, {3, ffffe00000350880, ffffd00020a94960, ffffe00001e4ea00}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe00000350880, Physical Device Object of the stack
    Arg3: ffffd00020a94960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00001e4ea00, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: CORRUPT_MODULELIST
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep  3 15:49:54.759 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090314-11359-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:00:09.479
    *** WARNING: Unable to verify timestamp for FPWinIo.sys
    *** ERROR: Module load completed but symbols could not be loaded for FPWinIo.sys
    Probably caused by :FPWinIo.sys ( FPWinIo+6f66 )
    BugCheck C4, {f6, 334, ffffe0016640d900, fffff80125757f66}
    BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    Arguments: 
    Arg1: 00000000000000f6, Referencing user handle as KernelMode.
    Arg2: 0000000000000334, Handle value being referenced.
    Arg3: ffffe0016640d900, Address of the current process.
    Arg4: fffff80125757f66, Address inside the driver that is performing the incorrect reference.
    BUGCHECK_STR:  0xc4_f6
    PROCESS_NAME:  WUDFHost.exe
    FAILURE_BUCKET_ID: 0xc4_f6_VRF_FPWinIo+6f66
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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 Sep  6 09:23:51.334 2014 (UTC - 4:00)**************************
    VMfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    Rt630x64.sys                Fri May 10 05:59:08 2013 (518CC4EC)
    FPWinIo.sys                 Thu Aug  8 03:44:50 2013 (52034C72)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
    RtsPer.sys                  Fri Nov  8 01:59:21 2013 (527C8BC9)
    TeeDriverx64.sys            Wed Nov 27 12:56:32 2013 (52963250)
    viahduaa.sys                Mon Dec 16 00:58:10 2013 (52AE9672)
    SynTP.sys                   Fri Dec 20 12:45:21 2013 (52B48231)
    Smb_driver_Intel.sys        Fri Dec 20 12:50:17 2013 (52B48359)
    btmaux.sys                  Wed Mar 26 04:15:03 2014 (53328C87)
    nvvad64v.sys                Fri Mar 28 09:32:06 2014 (533579D6)
    btmhsf.sys                  Tue Apr 22 03:46:28 2014 (53561E54)
    ibtusb.sys                  Thu Jun  5 20:57:40 2014 (53911204)
    iwdbus.sys                  Tue Jun 17 17:54:22 2014 (53A0B90E)
    nvlddmkm.sys                Wed Jul  2 13:42:02 2014 (53B4446A)
    NETwbw02.sys                Tue Jul 22 06:29:40 2014 (53CE3D14)
    NvStreamKms.sys             Fri Jul 25 07:35:56 2014 (53D2411C)
    igdkmd64.sys                Tue Aug  5 11:47:18 2014 (53E0FC86)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep  5 13:11:53.182 2014 (UTC - 4:00)**************************
    NETwbw02.sys                Tue Feb 18 11:57:40 2014 (53039104)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep  5 07:53:37.982 2014 (UTC - 4:00)**************************
    NETwbw02.sys                Thu Sep 19 03:40:12 2013 (523AAA5C)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep  3 15:49:54.759 2014 (UTC - 4:00)**************************
    SvThANSP.sys                Fri Oct 11 23:08:38 2013 (5258BD36)
    iaStorA.sys                 Mon Oct 28 17:15:26 2013 (526ED3EE)
    dump_iaStorA.sys            Mon Oct 28 17:15:26 2013 (526ED3EE)
    iwdbus.sys                  Tue Dec 17 17:47:38 2013 (52B0D48A)
    igdkmd64.sys                Mon Dec 30 15:52:24 2013 (52C1DD08)
    RzFilter.sys                Thu Apr  3 11:39:47 2014 (533D80C3)
    RzDxgk.sys                  Thu Apr  3 11:39:50 2014 (533D80C6)
    rzudd.sys                   Mon May 19 02:43:44 2014 (5379A820)
    
    http://www.carrona.org/drivers/driver.php?id=VMfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    FPWinIo.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=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPer.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
    http://www.carrona.org/drivers/driver.php?id=btmaux.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=btmhsf.sys
    http://www.carrona.org/drivers/driver.php?id=ibtusb.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=NETwbw02.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    tmpD72C.tmp - 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.
    tmpC946.tmp - 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.
    tmp827C.tmp - 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=NETwbw02.sys
    http://www.carrona.org/drivers/driver.php?id=NETwbw02.sys
    SvThANSP.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=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=RzFilter.sys
    http://www.carrona.org/drivers/driver.php?id=RzDxgk.sys
    http://www.carrona.org/drivers/driver.php?id=rzudd.sys
      My System SpecsSystem Spec

  4. #4


    Posts : 3
    Windows 8.1


    Quote Originally Posted by usasma View Post
    *snip*
    Thank you so much for you thorough help. Really appreciated. I'll install all the updates, but I don't think this is the culprit. Before my RMA, the BSOD occured even after I had installed every update.

    Judging by your investigation, I think the the fingerprint scanner is reponsible for the crashes. I haven't experienced any problems today or yesterday, but I'll uninstall the fingerprint scanner software the moment it starts happening again.

    I'm currently looking for an updated driver for VMfilt64.sys here (VIA Drivers and Support Packages Download) but I can't find my device number. My device manager says it's called VIA HD Audio (Win 8.1) and System Information refers to it as VMfilt. My other audio devices are called:

    High Definition Audio Device (driver=hdaudio.sys)
    VIA HD Audio(Win8.1) (driver= viahduaa.sys)
    NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (driver= nvvad64v.sys)




    Where can I find the device of the VMfilt64.sys driver?

    The device I disabled was listed in device manager as an unknown device. When I try updating it, I get an error message saying: "windows found driver software for your device but encountered an error while attempting to install it" Insyde Airplane Mode HID mini-Driver. Drive is not intented for this platform.

    Thank you again for your help.
      My System SpecsSystem Spec

  5. #5


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


    Please enable the unknown device, then uninstall it, then reboot and see if it's recognized.

    I cannot find the program that uses the VMfilt64.sys driver
    We can attempt to remove it manually, but it's not a fun thing to do.
    In addition to the normal problems that a manual removal can cause, this can also mess up the audio on your laptop.
    Here's how I suggest doing it:

    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 VMfilt64.sys that are starting (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
    5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of VMfilt64.sys are "Uninstalled" (DO NOT DISABLE THESE).
    6) Check in the Services applet (services.msc) to be sure any instances of VMfilt64.sys are disabled.
    7) EXPERIMENTAL STEP (only try if you're certain of your abilities - I have not tried this step myself). Search the registry (use regedit.exe) to locate any entries that have the driver name (VMfilt64.sys) . Delete these keys (it's advisable to back them up first - but you've also backed up the entire registry when creating a System Restore point in step 1. Alternatively, you can set the values in these keys to DISABLED (but the "how" of this is beyond the scope of this).
    8) Go to C:\Windows\System32\drivers and rename the VMfilt64.sys driver to VMfilt64.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 VMfilt64.BAD to VMfilt64.sys
    Code:
    ren C:\Windows\System32\drivers\VMfilt64.BAD C:\Windows\System32\drivers\VMfilt64.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!
    If the BSOD's continue, try Driver Verifier according to these instructions: Driver Verifier Settings
      My System SpecsSystem Spec

  6. #6


    Posts : 3
    Windows 8.1


    Quote Originally Posted by usasma View Post
    Please enable the unknown device, then uninstall it, then reboot and see if it's recognized.

    I cannot find the program that uses the VMfilt64.sys driver
    We can attempt to remove it manually, but it's not a fun thing to do.
    In addition to the normal problems that a manual removal can cause, this can also mess up the audio on your laptop.
    Here's how I suggest doing it:

    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 VMfilt64.sys that are starting (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
    5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of VMfilt64.sys are "Uninstalled" (DO NOT DISABLE THESE).
    6) Check in the Services applet (services.msc) to be sure any instances of VMfilt64.sys are disabled.
    7) EXPERIMENTAL STEP (only try if you're certain of your abilities - I have not tried this step myself). Search the registry (use regedit.exe) to locate any entries that have the driver name (VMfilt64.sys) . Delete these keys (it's advisable to back them up first - but you've also backed up the entire registry when creating a System Restore point in step 1. Alternatively, you can set the values in these keys to DISABLED (but the "how" of this is beyond the scope of this).
    8) Go to C:\Windows\System32\drivers and rename the VMfilt64.sys driver to VMfilt64.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 VMfilt64.BAD to VMfilt64.sys
    Code:
    ren C:\Windows\System32\drivers\VMfilt64.BAD C:\Windows\System32\drivers\VMfilt64.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!
    If the BSOD's continue, try Driver Verifier according to these instructions: Driver Verifier Settings
    The driver associated with the Unknown Device is called Insyde Airplane Mode HiD Mini Driver. I've been unable to uninstall it and deleting the folder from program files also doesn't work. The file simply reappear...

    I did a Driver Verifier and now I'm getting a Driver Violation BSOD when tyring to reboot. Made a new SF package
    Last edited by Fadawah; 13 Sep 2014 at 11:41.
      My System SpecsSystem Spec

  7. #7


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


    Don't forget to turn off Driver Verifier. Do this by going into the program and selecting "Delete existing settings", then click on "Finish" and reboot in order for the changes to take effect.

    The Driver Verifier enabled memory dumps blame FPSensor.sys - a driver component of your Egis Technology Inc. Fingerprint Sensor.

    Your fingerprint driver dates from 2012, the downloadable setup file from Clevo dates from 2014
    I installed this in a Virtual Machine, and found that the FPwinio.sys driver dates from 2013 (the same as the version on your system) - but the driver blamed by Driver Verifier doesn't exist on my VM.

    Couple this with the difficulties with the Airplane Mode driver and I have to wonder if there's physical damage to your system. Have you had any power surges, water spills, drops, or other possible causes of hardware damage?

    Are you able to disable this device in the BIOS/UEFI of your system?
    If not, then try disabling it in Device Manager
    Let us know if that helps the BSOD's

    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
    Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
    Alternate link: Disk-Tools.com
    Manual procedure here: Registry and SPTD problems | DAEMON Pro Help



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sat Sep 13 12:34:05.850 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091314-10859-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:16:50.581
    *** WARNING: Unable to verify timestamp for FPSensor.sys
    *** ERROR: Module load completed but symbols could not be loaded for FPSensor.sys
    Probably caused by :FPSensor.sys ( FPSensor+48ef )
    BugCheck C4, {4100b, fffff8005ef3af60, 0, 0}
    BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    Arguments: 
    Arg1: 000000000004100b, ID of the 'RequestedPowerIrp' rule that was violated.
    Arg2: fffff8005ef3af60, A pointer to the string describing the violated rule condition.
    Arg3: 0000000000000000, Reserved (unused).
    Arg4: 0000000000000000, Reserved (unused).
    BUGCHECK_STR:  0xc4_RequestedPowerIrp_XDV
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc4_RequestedPowerIrp_XDV_VRF_FPSensor+48ef
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Sep 13 12:15:31.248 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091314-4609-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:17:07.963
    *** WARNING: Unable to verify timestamp for FPSensor.sys
    *** ERROR: Module load completed but symbols could not be loaded for FPSensor.sys
    Probably caused by :FPSensor.sys ( FPSensor+48ef )
    BugCheck C4, {4100b, fffff8018f307f60, 0, 0}
    BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    Arguments: 
    Arg1: 000000000004100b, ID of the 'RequestedPowerIrp' rule that was violated.
    Arg2: fffff8018f307f60, A pointer to the string describing the violated rule condition.
    Arg3: 0000000000000000, Reserved (unused).
    Arg4: 0000000000000000, Reserved (unused).
    BUGCHECK_STR:  0xc4_RequestedPowerIrp_XDV
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc4_RequestedPowerIrp_XDV_VRF_FPSensor+48ef
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep 12 01:34:42.828 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091214-5703-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 9:40:47.505
    *** ERROR: Module load completed but symbols could not be loaded for pci.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe0004f9f2060, ffffd00111e6a930, ffffe00052353a40}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0004f9f2060, Physical Device Object of the stack
    Arg3: ffffd00111e6a930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00052353a40, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep  9 00:52:22.377 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090914-8343-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 15:00:24.054
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe0000a5e3060, fffff8016aa89930, ffffe0000cd9c010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0000a5e3060, Physical Device Object of the stack
    Arg3: fffff8016aa89930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0000cd9c010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
    MaxSpeed:     2500
    CurrentSpeed: 2494
      BIOS Version                  4.6.5
      BIOS Release Date             04/08/2014
      Manufacturer                  Notebook                        
      Product Name                  W35xSS_370SS              
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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 Sep 13 12:34:05.850 2014 (UTC - 4:00)**************************
    SiSRaid2.sys                Wed Sep 24 14:28:20 2008 (48DA86C4)
    sisraid4.sys                Wed Oct  1 17:56:04 2008 (48E3F1F4)
    VMfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    iaStorV.sys                 Mon Apr 11 14:48:16 2011 (4DA34CF0)
    nvstor.sys                  Mon Sep 12 19:53:04 2011 (4E6E9B60)
    nvraid.sys                  Mon Sep 12 20:01:54 2011 (4E6E9D72)
    FPSensor.sys                Mon Aug  6 23:39:28 2012 (50208DF0)
    stexstor.sys                Mon Nov 26 19:02:51 2012 (50B4032B)
    amdsbs.sys                  Tue Dec 11 16:21:44 2012 (50C7A3E8)
    vstxraid.sys                Mon Jan 21 14:00:28 2013 (50FD904C)
    vsmraid.sys                 Wed Jan 23 15:35:43 2013 (5100499F)
    bxvbda.sys                  Mon Feb  4 14:47:18 2013 (51101046)
    lsi_sas3.sys                Fri Mar 15 19:38:40 2013 (5143B100)
    lsi_sss.sys                 Fri Mar 15 19:39:38 2013 (5143B13A)
    mvumis.sys                  Wed Mar 20 13:14:53 2013 (5149EE8D)
    HpSAMD.sys                  Tue Mar 26 17:36:54 2013 (515214F6)
    lsi_sas.sys                 Thu Mar 28 13:42:34 2013 (5154810A)
    lsi_sas2.sys                Thu Mar 28 13:45:05 2013 (515481A1)
    evbda.sys                   Mon Apr  8 10:30:03 2013 (5162D46B)
    3ware.sys                   Thu Apr 11 18:49:23 2013 (51673DF3)
    megasr.sys                  Mon Jun  3 18:02:39 2013 (51AD127F)
    amdxata.sys                 Mon Jul  8 18:45:00 2013 (51DB40EC)
    amdsata.sys                 Mon Jul  8 18:54:38 2013 (51DB432E)
    arcsas.sys                  Mon Jul  8 20:50:17 2013 (51DB5E49)
    ADP80XX.SYS                 Fri Jul 12 17:47:36 2013 (51E07978)
    megasas.sys                 Tue Jul 23 17:08:29 2013 (51EEF0CD)
    iaStorAV.sys                Wed Jul 31 20:00:49 2013 (51F9A531)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    agp440.sys                  Thu Aug 22 07:39:35 2013 (5215F877)
    nv_agp.sys                  Thu Aug 22 07:39:38 2013 (5215F87A)
    intelide.sys                Thu Aug 22 07:40:03 2013 (5215F893)
    dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
    
    TeeDriverx64.sys            Wed Nov 27 12:56:32 2013 (52963250)
    viahduaa.sys                Mon Dec 16 00:58:10 2013 (52AE9672)
    SynTP.sys                   Fri Dec 20 12:45:21 2013 (52B48231)
    Smb_driver_Intel.sys        Fri Dec 20 12:50:17 2013 (52B48359)
    dtsoftbus01.sys             Fri Feb 21 04:49:36 2014 (53072130)
    nvvad64v.sys                Fri Mar 28 09:32:06 2014 (533579D6)
    btmhsf.sys                  Tue Apr 22 03:46:28 2014 (53561E54)
    ibtusb.sys                  Thu Jun  5 20:57:40 2014 (53911204)
    nvlddmkm.sys                Thu Jun 12 20:18:13 2014 (539A4345)
    iwdbus.sys                  Tue Jun 17 17:54:22 2014 (53A0B90E)
    NETwbw02.sys                Tue Jul 22 06:29:40 2014 (53CE3D14)
    NvStreamKms.sys             Fri Jul 25 07:35:56 2014 (53D2411C)
    igdkmd64.sys                Tue Aug  5 11:47:18 2014 (53E0FC86)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Sep 13 12:15:31.248 2014 (UTC - 4:00)**************************
    Rt630x64.sys                Fri May 10 05:59:08 2013 (518CC4EC)
    RtsPer.sys                  Fri Nov  8 01:59:21 2013 (527C8BC9)
    nvlddmkm.sys                Wed Jul  2 13:42:02 2014 (53B4446A)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep  9 00:52:22.377 2014 (UTC - 4:00)**************************
    FPWinIo.sys                 Thu Aug  8 03:44:50 2013 (52034C72)
    btmaux.sys                  Wed Mar 26 04:15:03 2014 (53328C87)
    
    http://www.carrona.org/drivers/driver.php?id=SiSRaid2.sys
    http://www.carrona.org/drivers/driver.php?id=sisraid4.sys
    http://www.carrona.org/drivers/driver.php?id=VMfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorV.sys
    http://www.carrona.org/drivers/driver.php?id=nvstor.sys
    http://www.carrona.org/drivers/driver.php?id=nvraid.sys
    http://www.carrona.org/drivers/driver.php?id=FPSensor.sys
    http://www.carrona.org/drivers/driver.php?id=stexstor.sys
    http://www.carrona.org/drivers/driver.php?id=amdsbs.sys
    vstxraid.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=vsmraid.sys
    http://www.carrona.org/drivers/driver.php?id=bxvbda.sys
    lsi_sas3.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.
    lsi_sss.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.
    mvumis.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=HpSAMD.sys
    http://www.carrona.org/drivers/driver.php?id=lsi_sas.sys
    http://www.carrona.org/drivers/driver.php?id=lsi_sas2.sys
    http://www.carrona.org/drivers/driver.php?id=evbda.sys
    3ware.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=megasr.sys
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=amdsata.sys
    http://www.carrona.org/drivers/driver.php?id=arcsas.sys
    ADP80XX.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=megasas.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorAV.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=agp440.sys
    http://www.carrona.org/drivers/driver.php?id=nv_agp.sys
    http://www.carrona.org/drivers/driver.php?id=intelide.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
    http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=btmhsf.sys
    http://www.carrona.org/drivers/driver.php?id=ibtusb.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=NETwbw02.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPer.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=FPWinIo.sys
    http://www.carrona.org/drivers/driver.php?id=btmaux.sys
      My System SpecsSystem Spec

  8. #8


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


    Please provide a link to the download page that you're using.
    I'm not certain that I have the right model #, and I see that the FPWinIo.sys driver isn't present in the Driver Verifier memory dumps and is no longer shown in the Driver section of the MSINFO32 report.
      My System SpecsSystem Spec

BSOD driver_power_state failure when running games
Related Threads
Maybe this should be moved because it has more to do with my GPU. My main GPU appears in Device Manager, but when I play games they don't use/find my main GPU. -Original Post- Hey, my computer got stuck going into sleep mode. I seem to have lost a podcast file, but, otherwise, things seems to be...
I was playing borderland3, CS protable 1.6 and BSOD happend. It all started after i modify the registry according to this website Hyper-Linker: Counter Strike 1.6 Invalid CD-key Error Fix Then, i tried to find original valve registry online and overwrite the registry. I also do registry...
So far the only issues I've run into as far as older games(though I have more to re-install after my mobo/cpu/gpu upgrades) are games labelled "Games for windows" for which I've followed oodles of guides and all were epic fails. Specifically, I'm trying to install fallout 3 and expansions, all with...
Hi All, I have recently purchased a new HP Pavillion laptop that has Windows 8 on it. Ever since I have been using it, I have noticed that all the games I play on Facebook run extremely slow. I mainly use Google Chrome, but have tried to see if other internet browsers have the same problem and...
Solved BSOD when running games in BSOD Crashes and Debugging
I'm creating this topic to request the evaluation of crash dump. It usually happens after 15 or 30 minutes playing without problem and not in all games Note: My computer is new, about 1 month. I am Brazilian and I used google translator to translate some of the files generated by sf...
I came across a box of old computer games I played years ago. Games such as Space Quest ,Kings Quest to name a few. I doubt they will run in Windows 8 Pro 64 bit. I do have an old copy of Windows 98 SE. Can I run these games using Windows 98 in a VM. If so; What Vm do you recommend I use? TIA :)
Hey I am running dual monitors and I usually run VLC or chrome on the second monitor when I am playing games, but VLC and YouTube start jumping when I run games like BF3 and Far Cry 3. yet the audio is completely fine. it only happens when the game is active. i also changed VLCs video output to...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook