Page 1 of 2 12 LastLast
  1.    17 Jun 2017 #1
    Join Date : Oct 2015
    Minsk
    Posts : 30
    Windows 10x64 PRO

    DRIVER_POWER_STATE_FAILURE, 0x0000009f - during PC is going to sleep


    Hi all, I would very much appreciate your help as far as I didn't manage to find proper information about what causes these bluescreens.

    Please, see the dumps in the file attached. There are 4 there, the last 2 are connected with the topic header DRIVER_POWER_STATE_FAILURE. The first 2 are about 0x00000139 bug check string is empty.

    I ran sfc, dism and started driver verifier. Memory was also tested - is ok. From my own observation it may be somehow connected with virtual box, idk, because every time I receive such bluescreens I use VB before.

    If you need more info I''provide it asap.
    Attachment 139936
      My ComputerSystem Spec
  2.    18 Jun 2017 #2
    Join Date : Apr 2017
    Posts : 8,784
    windows 10 professional version 1607 build 14393.969 64 bit

    Hi toouur,

    Code:
    BugCheck 139, {3, ffffb401d58f6f80, ffffb401d58f6ed8, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
    Code:
    BugCheck 139, {3, ffffc18142146800, ffffc18142146758, 0}
    
    *** 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+12dca )
    samsungrapiddiskfltr.sys
    Samsung RAPID Mode Disk Filter driver
    Samsung Download Center: Owner's Manuals, Firmware Updates & Drivers | Samsung US


    Code:
    BugCheck 9F, {4, 12c, ffffa586464f2200, fffff802cf7ad910}
    
    Implicit thread is now ffffa586`464f2200
    Probably caused by : USBXHCI.SYS
    USBXHCI.sys
    USB XHCI Driver
    Info - WindowsÂ*8: What's new for USB (Windows Drivers)
    Windows Update

    Code:
    BugCheck 9F, {4, 12c, ffffd68ab3202040, fffff803421ad910}
    
    Implicit thread is now ffffd68a`b3202040
    Probably caused by : USBXHCI.SYS

    Installation Failure: Windows failed to install the following update with error 0x80070103: NVIDIA - Display - 5/1/2017 12:00:00 AM - 22.21.13.8205.

    There were multiple windows update failures.

    Open administrative command prompt and type or copy and paste:

    1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)

    2) sfc /scannow

    3) dism /online /cleanup-image /restorehealth

    4) chkdsk /scan

    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread

    5) Uninstall all Samsung drivers. Reinstall the Samsung drivers from the Asus web site with your product or serial number and operating system. If the driver (s) is not listed then download from the Samsung web site.

    6) Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.
    Memtest86+ - Advanced Memory Diagnostic Tool When it has completed please make an image and post into the thread.

    7) perform windows updates. If there are any failures please post the KB# and the error code.

    8) run one of these drive tests (SMART) and post images into the thread:
    CrystalDiskInfo - Software - Crystal Dew World
    http://www.hdtune.com/
    Hard Disk Sentinel - HDD health and temperature monitoring
      My ComputerSystem Spec
  3.    18 Jun 2017 #3
    Join Date : Oct 2015
    Minsk
    Posts : 30
    Windows 10x64 PRO
    Thread Starter

    Hi, thanks for the reply.

    1. Strange, I have the latest magician ver. 5.01 installed. Well, I'll try to reinstall rapid mode drivers. Btw, it seems logical, that they can cause BSOD's, because they use ram and while going to hybrid sleep PC also uses ram, so maybe there is a conflict between them.

    2. USB, hm. I ran into another BSOD yesterday after I enabled driver verifier(DRIVER_VERIFIER_IOMANAGER_VIOLATION, 0x000000c9). It happened after I inserted A-DATA USB 3.0 flash drive. Guess, it was because of Asus USB bot drivers. But still, it shouldn't affect going to sleep.

    3. >Installation Failure: Windows failed to install the following update with error 0x80070103: NVIDIA - Display - 5/1/2017 12:00:00 AM - 22.21.13.8205.

    That's really strange, because I made clean install in the beginning of June.

    4. Version 1703 (OS Build 15063.413)

    5. Microsoft Windows [Version 10.0.15063]
    (c) 2017 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\Windows\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0

    Image Version: 10.0.15063.0

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\Windows\system32>chkdsk /scan
    The type of the file system is NTFS.
    Volume label is System.

    Stage 1: Examining basic file system structure ...
    1887488 file records processed.
    File verification completed.
    8289 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    2264954 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    188734 data files processed.
    CHKDSK is verifying Usn Journal...
    38337272 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    487806975 KB total disk space.
    226406832 KB in 1690404 files.
    475368 KB in 188735 indexes.
    0 KB in bad sectors.
    2009595 KB in use by the system.
    65536 KB occupied by the log file.
    258915180 KB available on disk.

    4096 bytes in each allocation unit.
    121951743 total allocation units on disk.
    64728795 allocation units available on disk.

    C:\Windows\system32>

    6. Done

    7. Well, no way for me to wait so long. I have 3x8 GB ram, I started memtest overnight, it was runnning for 9 hours and only 3 pass were made. But I'm completely sure with my crucial ram.
    Attachment 140064

    8. Updated, no errors.

    9. ----------------------------------------------------------------------------
    CrystalDiskInfo 7.0.5 (C) 2008-2016 hiyohiyo
    Crystal Dew World : Crystal Dew World
    ----------------------------------------------------------------------------

    OS : Windows 10 Professional [10.0 Build 15063] (x64)
    Date : 2017/06/18 14:31:55

    -- Controller Map ----------------------------------------------------------
    + Intel(R) 9 Series Chipset Family SATA AHCI Controller [ATA]
    - Samsung SSD 850 EVO 500GB
    - Crucial_CT256MX100SSD1
    - TOSHIBA DT01ACA300
    - TOSHIBA DT01ACA300
    - ASUS DRW-24F1ST a
    - Microsoft Storage Spaces Controller [SCSI]

    -- Disk List ---------------------------------------------------------------
    (1) Samsung SSD 850 EVO 500GB : 500.1 GB [0/0/0, pd1] - sg
    (2) Crucial_CT256MX100SSD1 : 256.0 GB [1/0/0, pd1] - mi
    (3) TOSHIBA DT01ACA300 : 3000.5 GB [2/0/0, pd1]
    (4) TOSHIBA DT01ACA300 : 3000.5 GB [3/0/0, pd1]

    ----------------------------------------------------------------------------
    (1) Samsung SSD 850 EVO 500GB
    ----------------------------------------------------------------------------
    Model : Samsung SSD 850 EVO 500GB
    Firmware : EMT02B6Q
    Serial Number : S2RBNX0J256964D
    Disk Size : 500.1 GB (8.4/137.4/500.1/500.1)
    Buffer Size : Unknown
    Queue Depth : 32
    # of Sectors : 976773168
    Rotation Rate : ---- (SSD)
    Interface : Serial ATA
    Major Version : ACS-2
    Minor Version : ATA8-ACS version 4c
    Transfer Mode : SATA/600 | SATA/600
    Power On Hours : 142 hours
    Power On Count : 29 count
    Host Writes : 833 GB
    Wear Level Count : 1
    Temperature : 38 C (100 F)
    Health Status : Good (100 %)
    Features : S.M.A.R.T., 48bit LBA, NCQ, TRIM, DevSleep
    APM Level : ----
    AAM Level : ----
    Drive Letter : C:

    -- S.M.A.R.T. --------------------------------------------------------------
    ID Cur Wor Thr RawValues(6) Attribute Name
    05 100 100 _10 000000000000 Reallocated Sector Count
    09 _99 _99 __0 00000000008E Power-on Hours
    0C _99 _99 __0 00000000001D Power-on Count
    B1 _99 _99 __0 000000000001 Wear Leveling Count
    B3 100 100 _10 000000000000 Used Reserved Block Count (Total)
    B5 100 100 _10 000000000000 Program Fail Count (Total)
    B6 100 100 _10 000000000000 Erase Fail Count (Total)
    B7 100 100 _10 000000000000 Runtime Bad Block (Total)
    BB 100 100 __0 000000000000 Uncorrectable Error Count
    BE _62 _57 __0 000000000026 Airflow Temperature
    C3 200 200 __0 000000000000 ECC Error Rate
    C7 100 100 __0 000000000000 CRC Error Count
    EB _99 _99 __0 000000000002 POR Recovery Count
    F1 _99 _99 __0 000068355C67 Total LBAs Written

    ----------------------------------------------------------------------------
    (2) Crucial_CT256MX100SSD1
    ----------------------------------------------------------------------------
    Model : Crucial_CT256MX100SSD1
    Firmware : MU02
    Serial Number : 14510E1BED05
    Disk Size : 256.0 GB (8.4/137.4/256.0/256.0)
    Buffer Size : Unknown
    Queue Depth : 32
    # of Sectors : 500118192
    Rotation Rate : ---- (SSD)
    Interface : Serial ATA
    Major Version : ACS-2
    Minor Version : ATA8-ACS version 6
    Transfer Mode : SATA/600 | SATA/600
    Power On Hours : 3962 hours
    Power On Count : 1452 count
    Host Writes : 16821 GB
    Wear Level Count : 136
    Temperature : 31 C (87 F)
    Health Status : Good (96 %)
    Features : S.M.A.R.T., APM, 48bit LBA, NCQ, TRIM, DevSleep
    APM Level : 00FEh [ON]
    AAM Level : ----
    Drive Letter : D:

    -- S.M.A.R.T. --------------------------------------------------------------
    ID Cur Wor Thr RawValues(6) Attribute Name
    01 100 100 __0 000000000010 Raw Read Error Rate
    05 100 100 __0 000000000000 Reallocated NAND Blocks
    09 100 100 __0 000000000F7A Power On Hours
    0C 100 100 __0 0000000005AC Power Cycle Count
    AB 100 100 __0 000000000000 Program Fail Count
    AC 100 100 __0 000000000000 Erase Fail Count
    AD _96 _96 __0 000000000088 Average Block-Erase Count
    AE 100 100 __0 0000000000AC Unexpected Power Loss Count
    B4 __0 __0 __0 00000000086F Unused Reserve NAND Blocks
    B7 100 100 __0 000000000000 SATA Interface Downshift
    B8 100 100 __0 000000000000 Error Correction Count
    BB 100 100 __0 000000000000 Reported Uncorrectable Errors
    C2 _69 _55 __0 002D000F001F Temperature
    C4 100 100 __0 000000000000 Reallocation Event Count
    C5 100 100 __0 000000000000 Current Pending Sector Count
    C6 100 100 __0 000000000000 Smart Off-line Scan Uncorrectable Error Count
    C7 100 100 __0 000000000000 Ultra DMA CRC Error Rate
    CA _96 _96 __0 000000000004 Percent Lifetime Used
    CE 100 100 __0 000000000000 Write Error Rate
    D2 100 100 __0 000000000000 Successful RAIN Recovery Count
    F6 100 100 __0 000836B25FB8 Total Host Sector Writes
    F7 100 100 __0 000049137D24 Host Program Page Count
    F8 100 100 __0 00017BD7368F Background Program Page Count

    ----------------------------------------------------------------------------
    (3) TOSHIBA DT01ACA300
    ----------------------------------------------------------------------------
    Model : TOSHIBA DT01ACA300
    Firmware : MX6OABB0
    Serial Number : Z4N3BTSGS
    Disk Size : 3000.5 GB (8.4/137.4/3000.5/3000.5)
    Buffer Size : Unknown
    Queue Depth : 32
    # of Sectors : 5860533168
    Rotation Rate : 7200 RPM
    Interface : Serial ATA
    Major Version : ATA8-ACS
    Minor Version : ATA8-ACS version 4
    Transfer Mode : SATA/600 | SATA/600
    Power On Hours : 9131 hours
    Power On Count : 1472 count
    Temperature : 37 C (98 F)
    Health Status : Good
    Features : S.M.A.R.T., APM, 48bit LBA, NCQ
    APM Level : 0080h [ON]
    AAM Level : ----
    Drive Letter : E: F: G: H:

    -- S.M.A.R.T. --------------------------------------------------------------
    ID Cur Wor Thr RawValues(6) Attribute Name
    01 100 100 _16 000000000000 Read Error Rate
    02 139 139 _54 000000000047 Throughput Performance
    03 164 164 _24 000801820138 Spin-Up Time
    04 100 100 __0 0000000006A7 Start/Stop Count
    05 100 100 __5 000000000000 Reallocated Sectors Count
    07 100 100 _67 000000000000 Seek Error Rate
    08 124 124 _20 000000000021 Seek Time Performance
    09 _99 _99 __0 0000000023AB Power-On Hours
    0A 100 100 _60 000000000000 Spin Retry Count
    0C 100 100 __0 0000000005C0 Power Cycle Count
    C0 _98 _98 __0 000000000A67 Power-off Retract Count
    C1 _98 _98 __0 000000000A67 Load/Unload Cycle Count
    C2 162 162 __0 002C00120025 Temperature
    C4 100 100 __0 000000000000 Reallocation Event Count
    C5 100 100 __0 000000000000 Current Pending Sector Count
    C6 100 100 __0 000000000000 Uncorrectable Sector Count
    C7 200 200 __0 000000000002 UltraDMA CRC Error Count

    ----------------------------------------------------------------------------
    (4) TOSHIBA DT01ACA300
    ----------------------------------------------------------------------------
    Model : TOSHIBA DT01ACA300
    Firmware : MX6OABB0
    Serial Number : Z4V4TGZGS
    Disk Size : 3000.5 GB (8.4/137.4/3000.5/3000.5)
    Buffer Size : Unknown
    Queue Depth : 32
    # of Sectors : 5860533168
    Rotation Rate : 7200 RPM
    Interface : Serial ATA
    Major Version : ATA8-ACS
    Minor Version : ATA8-ACS version 4
    Transfer Mode : SATA/600 | SATA/600
    Power On Hours : 8501 hours
    Power On Count : 1299 count
    Temperature : 38 C (100 F)
    Health Status : Good
    Features : S.M.A.R.T., APM, 48bit LBA, NCQ
    APM Level : 0080h [ON]
    AAM Level : ----
    Drive Letter : I:

    -- S.M.A.R.T. --------------------------------------------------------------
    ID Cur Wor Thr RawValues(6) Attribute Name
    01 100 100 _16 000000000000 Read Error Rate
    02 140 140 _54 000000000045 Throughput Performance
    03 145 145 _24 00080189018B Spin-Up Time
    04 100 100 __0 0000000006ED Start/Stop Count
    05 100 100 __5 000000000000 Reallocated Sectors Count
    07 100 100 _67 000000000000 Seek Error Rate
    08 124 124 _20 000000000021 Seek Time Performance
    09 _99 _99 __0 000000002135 Power-On Hours
    0A 100 100 _60 000000000000 Spin Retry Count
    0C 100 100 __0 000000000513 Power Cycle Count
    C0 _97 _97 __0 000000001080 Power-off Retract Count
    C1 _97 _97 __0 000000001081 Load/Unload Cycle Count
    C2 157 157 __0 002B00120026 Temperature
    C4 100 100 __0 000000000000 Reallocation Event Count
    C5 100 100 __0 000000000000 Current Pending Sector Count
    C6 100 100 __0 000000000000 Uncorrectable Sector Count
    C7 200 200 __0 000000000000 UltraDMA CRC Error Count
      My ComputerSystem Spec
  4.    18 Jun 2017 #4
    Join Date : Oct 2015
    Minsk
    Posts : 30
    Windows 10x64 PRO
    Thread Starter

    Had another BSOD today while restarting PC, that went for ages and then bluescreen. Again, worked in VB before.
      My ComputerSystem Spec
  5.    18 Jun 2017 #5
    Join Date : Apr 2017
    Posts : 8,784
    windows 10 professional version 1607 build 14393.969 64 bit

    Which link did you use for the windows driver verifier customization settings?
    What are the current settings? Please post images including test type and drivers.
    Please continuously update or post new zip files so we can view the minidumps and the log files.
    What have you done so far with uninstalling and reinstalling drivers?
      My ComputerSystem Spec
  6.    18 Jun 2017 #6
    Join Date : Oct 2015
    Minsk
    Posts : 30
    Windows 10x64 PRO
    Thread Starter

    1. Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

    This one. I have already disabled it.

    2. Here are all the dumps.
    Attachment 140155
    ps. I am 99% confident it's because of virtual box. Once I run it I can't restart PC or run it into sleep. I just can't guess what a service hangs on the system=\
      My ComputerSystem Spec
  7.    18 Jun 2017 #7
    Join Date : Oct 2015
    Minsk
    Posts : 30
    Windows 10x64 PRO
    Thread Starter

    ps2. I have done everything from your 1-st post. Nothing more yet.
      My ComputerSystem Spec
  8.    19 Jun 2017 #8
    Join Date : Apr 2017
    Posts : 8,784
    windows 10 professional version 1607 build 14393.969 64 bit

    Code:
    BugCheck 9F, {4, 12c, ffffa586464f2200, fffff802cf7ad910}
    
    Implicit thread is now ffffa586`464f2200
    Probably caused by : USBXHCI.SYS
    Code:
    BugCheck 9F, {4, 12c, ffffd68ab3202040, fffff803421ad910}
    
    Implicit thread is now ffffd68a`b3202040
    Probably caused by : USBXHCI.SYS
    Code:
    BugCheck 9F, {4, 12c, ffffaf0d838d9040, fffff800cb5ad910}
    
    Implicit thread is now ffffaf0d`838d9040
    Probably caused by : USBXHCI.SYS
    Code:
    BugCheck C9, {24d, fffff803ae5ff17a, ffffd70c9fe61060, 0}
    
    *** WARNING: Unable to verify timestamp for hcmon.sys
    *** ERROR: Module load completed but symbols could not be loaded for hcmon.sys
    Probably caused by : hcmon.sys ( hcmon+3232 )
    Code:
    BugCheck C9, {24d, fffff800a658b17a, ffffdb834571e060, 0}
    
    *** WARNING: Unable to verify timestamp for hcmon.sys
    *** ERROR: Module load completed but symbols could not be loaded for hcmon.sys
    Probably caused by : hcmon.sys ( hcmon+3232 )
    USBXHCI.sys
    USB XHCI Driver
    Info - WindowsÂ*8: What's new for USB (Windows Drivers)
    Windows Update

    hcmon.sys
    VMware USB monitor
    VMware Support Data Center Virtualization

    On you computer search for: KMSTMNW.exe
    Is this related to your Kyocera printer?
    If so please uninstall it.
    If you need it immediately please reinstall it.
    If you can temporarily do without it please do so while we are looking for bsod.

    How do you connect the printer to your computer? Wifi? USB?

    What else is connected to the computer via USB?

    Search for these on your computer and indicate what they are related to:
    Tardsplaya.exe
    WCChromeNativeMessagingHost.exe
    BTHENUM

    Open device manager to view Bluetooth. Are there any non-Microsoft drivers? Please uninstall and reinstall with up to date driver.

    For any VM Ware software or applications or drivers please uninstall and reinstall them.
    Last edited by zbook; 19 Jun 2017 at 03:42.
      My ComputerSystem Spec
  9.    19 Jun 2017 #9
    Join Date : Oct 2015
    Minsk
    Posts : 30
    Windows 10x64 PRO
    Thread Starter

    So, what I've done for now.

    Reinstalled vbox, VMware, installed vmware and vbox extension pack. Made this Configuring Windows Hosts for Use with USB Monitors (Sniffers) (1679) | VMware KB

    So, maybe vmware drivers conflicted with vb ones, IDK. At least I know it's only USB related now. I tried VMware, then vbox - managed to cleanly restart. That's much better. So, I'll keep on testing and will keep you updated on my issue.

    Regarding your questions: yes, I have Kyocera, USB connected. But it's not related I have it for more than a year. Tardsplaya is a small application for twitch streams. I don;t know what is google about, will see. Btenum should be a bluetooth enumerator. I have Bluetooth, latest Broadcom drivers installed.
      My ComputerSystem Spec
  10.    19 Jun 2017 #10
    Join Date : Apr 2017
    Posts : 8,784
    windows 10 professional version 1607 build 14393.969 64 bit

    This is information on the Kyocera:

    18/06/2017 23:43 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc0000005
    Fault offset: 0x0001a62e
    Faulting process id: 0x1be8
    Faulting application start time: 0x01d2e88cbaf3c8f6
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: 277fc845-b05f-448c-9b2d-d961253d21fa
    Faulting package full name:
    Faulting package-relative application ID:
    18/06/2017 23:36 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc000041d
    Fault offset: 0x0001a62e
    Faulting process id: 0xed4
    Faulting application start time: 0x01d2e88bbbb4a9f4
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: 29000017-a4fa-46e4-a3fa-3bca4b7f3e62
    Faulting package full name:
    Faulting package-relative application ID:
    18/06/2017 23:36 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc0000005
    Fault offset: 0x0001a62e
    Faulting process id: 0xed4
    Faulting application start time: 0x01d2e88bbbb4a9f4
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: 52d25d24-1edd-4cfb-979c-30c96f4f1d2e
    Faulting package full name:
    Faulting package-relative application ID:
    18/06/2017 20:18 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc000041d
    Fault offset: 0x0001a62e
    Faulting process id: 0x12e8
    Faulting application start time: 0x01d2e86ba8bf1f05
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: 39c25fe4-6a23-4256-8b90-3aeb90c1db18
    Faulting package full name:
    Faulting package-relative application ID:
    18/06/2017 20:18 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc0000005
    Fault offset: 0x0001a62e
    Faulting process id: 0x12e8
    Faulting application start time: 0x01d2e86ba8bf1f05
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: 38dd3719-5e95-4a17-b703-dc58b2e96a63
    Faulting package full name:
    Faulting package-relative application ID:
    18/06/2017 11:49 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc000041d
    Fault offset: 0x0001a62e
    Faulting process id: 0x364c
    Faulting application start time: 0x01d2e828e87c5621
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: 685f21d7-a99d-4265-9481-b0701605015a
    Faulting package full name:
    Faulting package-relative application ID:
    18/06/2017 11:49 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc0000005
    Fault offset: 0x0001a62e
    Faulting process id: 0x364c
    Faulting application start time: 0x01d2e828e87c5621
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: af413568-bfee-49f6-9b91-985d34a4f1c1
    Faulting package full name:
    Faulting package-relative application ID:
    17/06/2017 19:21 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc000041d
    Fault offset: 0x0001a62e
    Faulting process id: 0x4de4
    Faulting application start time: 0x01d2e79ee49891e6
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: b148d349-09a2-446a-823c-d3782993c77a
    Faulting package full name:
    Faulting package-relative application ID:
    17/06/2017 19:21 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc0000005
    Fault offset: 0x0001a62e
    Faulting process id: 0x4de4
    Faulting application start time: 0x01d2e79ee49891e6
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: 3b0c8316-0211-4309-beea-c91423be4513
    Faulting package full name:
    Faulting package-relative application ID:
    17/06/2017 11:00 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc000041d
    Fault offset: 0x0001a62e
    Faulting process id: 0x3934
    Faulting application start time: 0x01d2e758f226557f
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: 7dfafbd4-09f3-47c4-9642-eab5f79449bc
    Faulting package full name:
    Faulting package-relative application ID:
    17/06/2017 11:00 Application Error Faulting application name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Faulting module name: KMSTMVM.exe, version: 1.1.27.12, time stamp: 0x513ec276
    Exception code: 0xc0000005
    Fault offset: 0x0001a62e
    Faulting process id: 0x3934
    Faulting application start time: 0x01d2e758f226557f
    Faulting application path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Faulting module path: C:\Program Files\Kyocera\ClientTool\KMSTMVM.exe
    Report Id: 75ff38ab-96f3-4591-9ae2-5e12c27c1ba1
    Faulting package full name:
    Faulting package-relative application ID:
      My ComputerSystem Spec

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
DRIVER_POWER_STATE_FAILURE after trying to go Sleep or Hibernate
I have DRIVER_POWER_STATE_FAILURE after trying to go Sleep or Hibernate. It may caused by PlexTurbo ver.3.0.0.8, it uses 1Gb of 4 Gb RAM to optimize SSD write operations, but don't know exactly. Sometimes Sleep succeeds, I think when available...
BSOD Crashes and Debugging
DRIVER_POWER_STATE_FAILURE on Sleep
This has been happening for a while. Doesn't seem to be any new drivers on the ASUS site that I don't already have. It seems to do it almost every time it goes to sleep. TIA for your help! 77615
BSOD Crashes and Debugging
BSOD:DRIVER_POWER_STATE_FAILURE (0x0000009f)
(Updated 2015/12/01) I formatted my computer and installed a whole new windows 10, but it showed BSOD in the first restart. Please help me. Please read the new attached file. Thank you very much. ==================== (I am a new user here and...
BSOD Crashes and Debugging
BSOD When going into sleep. ntoskrnl.exe, 0x0000009f
I have had Windows 10 since the day it was released (upgrade from Windows 7 HP) and it has been great. However, I am having a very annoying and seemingly random problem when putting the computer into sleep mode. The computer appears to be going...
BSOD Crashes and Debugging
BSOD on sleep, DRIVER_POWER_STATE_FAILURE
This has been a problem even before upgrading to 10 from 8.1, but its getting worse. I reviewed my drivers in Device Manager and most look up to date. I realized I didn't have a chipset driver installed and that helped for a day or two, but its...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:01.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums