What's new

[8.1 Pro x64 Lenovo Yoga] BSOD driver_state_power_failure

Cascadiaelk

Contributor
Joined
Feb 20, 2018
Posts
5
Howdy. I have a new and regular BSOD occurrences resulting from a DRIVER_STATE_POWER_FAILURE. My company's IT support is limited for complex issues so I'm looking for assistance. Thank you much for taking a look!


Here is the requested information per instructions as far as I can ascertain (with attachment):


· OS: Windows 8.1
· x64
· What was original installed OS on system? Windows 8
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? I believe I updated it through MS without retail purchase.
· Age of system (hardware): 2013
· Age of OS installation - have you re-installed the OS? I believe the update occurred within months of original system purchase (2013).


· CPU: Intel Core i7-3537U CPU @ 2.00 GHz 2.50 GHz
· Video Card: Intel HD Graphics 4000


· System Manufacturer: Lenovo IdeaPad Yoga 13
· Exact model number (if laptop, check label on bottom): Model name 20175 | p/n 59386347


· Laptop
 

Attachments

HyperHenry

Active member
Joined
Feb 12, 2018
Posts
40
Location
Currently Texas
The dump files I've read so far all point to your Realtek LAN drivers. I'd go to the Lenobo website and update everything including teh chipset drivers.I will continue to check out the dump files.
 

Cascadiaelk

Contributor
Joined
Feb 20, 2018
Posts
5
Appreciate the help. I looked over the Lenovo website, and even checked Intel's available updates, and there were a couple chipset driver updates to install. However, the Realtek WLAN driver currently installed matches the recommended version. I'll see if these changes helped.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Posts
18,456
Location
Croatia
You can try an older version if the latest one is giving you trouble.
 

philc43

BSOD Academy Instructor, BSOD Kernel Dump Expert
Joined
Jul 7, 2017
Posts
123
Location
Cambridge, UK
I've just looked at your 3 most recent crash dumps and the blocked IRP is pointing towards the camera driver in each case.

Code:
1: kd> !irp ffffe000b70d4840
Irp is active with 14 stacks 12 is current (= 0xffffe000b70d4c28)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  0 ffffe000af915040 00000000 00000000-00000000    
          Unable to load image \SystemRoot\System32\Drivers\SPUVCbv_x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SPUVCbv_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for SPUVCbv_x64.sys
\Driver\SPUVCbv
            Args: 00000000 00000001 00000003 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe000b7012e40 00000000 fffff8032099a580-ffffe000adad3010 Success Error Cancel pending
\Driver\ksthunk    nt!PopRequestCompletion
            Args: 00000000 00000001 00000003 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe000adad3010    

            Args: 00000000 00000000 00000000 00000000

Code:
1: kd> lmvm SPUVCbv_x64
Browse full module list
start             end                 module name
fffff801`65c08000 fffff801`65d09400   SPUVCbv_x64 T (no symbols)           
    Loaded symbol image file: SPUVCbv_x64.sys
    Image path: \SystemRoot\System32\Drivers\SPUVCbv_x64.sys
    Image name: SPUVCbv_x64.sys
Browse all global symbolsfunctionsdata
    Timestamp:        Sat Aug 11 06:00:15 2012 (5026575F)
    CheckSum:         0010CED2
    ImageSize:        00101400
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
See if you can update the driver.
 

Cascadiaelk

Contributor
Joined
Feb 20, 2018
Posts
5
Thanks for looking and the suggestion. I updated as many drivers as I could find with available updates and still had recurring BSOD, making the PC unusable. I retreated to system restore and am functional for now. If the issues showed up due to software pushes from our IT team, hopefully the "proactive" driver updates will avoid it when the software comes back.
 
Top