BSOD - Driver Power State Failure - playing WoW (new PC)

[fearqq]

Hi there,


Was just shocked to see my computer get its first blue screen. This is a new build with entirely new parts including HDD and everything.

This blue screen was as the title suggests and I am running Windows 64 bit and I have only recently done the latest windows updates, and had no problems until now, so there may be some correlation there.

I have attached the zip folder.

Any help would be greatly appreciated!

Kind regards,
Daniel

 

[axe0]

Hi fearqq,

Do you still need help?

 

[fearqq]

Yes please.

 

[axe0]

Please check Logitech for driver updates for your device(s)

Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`11904e10 fffff800`00b9a3d8 fffffa80`10a88b20
Debug session time: Sun Oct 16 15:10:18.939 2016 (UTC + 2:00)
System Uptime: 2 days 3:54:02.326

0: kd> !irp fffffa80`10a88b20
Irp is active with 4 stacks 1 is current (= 0xfffffa8010a88bf0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  1 fffffa8011904e10 00000000 00000000-00000000    pending
	       \Driver\LEqdUsb
			Args: 00041100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e0 fffffa8010e10bb0 00000000 fffff880021ea2ec-fffffa8010e10d00 Success Error Cancel 
	      Unable to load image \SystemRoot\system32\DRIVERS\LHidEqd.Sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for LHidEqd.Sys
*** ERROR: Module load completed but symbols could not be loaded for LHidEqd.Sys
 \Driver\LHidEqd	HIDCLASS!HidpFdoPowerCompletion
			Args: 00041100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 fffffa8010e10bb0 00000000 00000000-00000000    pending
	       \Driver\LHidEqd
			Args: 00041100 00000001 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-fffffa801272d710    

			Args: 00000000 00000000 00000000 00000000

0: kd> !devobj fffffa8010e10bb0
Device object (fffffa8010e10bb0) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa8010e10b80
 \Driver\LHidEqd DriverObject fffffa8011934e70
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00002050
DevExt fffffa8010e10d00 DevObjExt fffffa8010e10f88 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0000000000)  
AttachedTo (Lower) fffffa8011904e10 \Driver\LEqdUsb
Device queue is not busy.

0: kd> lmvm LEqdUsb
Browse full module list
start             end                 module name
fffff880`01e09000 fffff880`01e20000   LEqdUsb  T (no symbols)           
    Loaded symbol image file: LEqdUsb.Sys
    Image path: \SystemRoot\system32\DRIVERS\LEqdUsb.Sys
    Image name: LEqdUsb.Sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jun 09 21:25:30 2015 (55773DAA)
    CheckSum:         00021EC5
    ImageSize:        00017000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> lmvm LHidEqd
Browse full module list
start             end                 module name
fffff880`01e3b000 fffff880`01e43000   LHidEqd  T (no symbols)           
    Loaded symbol image file: LHidEqd.Sys
    Image path: \SystemRoot\system32\DRIVERS\LHidEqd.Sys
    Image name: LHidEqd.Sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jun 09 21:25:30 2015 (55773DAA)
    CheckSum:         00009BAC
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[fearqq]

Thank you for the reply.

The only logitech product I have is:
Wireless Desktop MK710 - Logitech Support

And it says that there is, "no software or App needed to use this product."

Am I missing something? I had already downloaded setpoint, but that seems to just give more customization rather than driver updates.

 

[axe0]

Which download did you choose and what type? I see 3 downloads and 6 types total (3 types with 2 downloads)

 

[fearqq]

I chose the first one, SetPoint

I selected 64-bit from the drop down list and downloaded that.

The downloaded file is called: SetPoint6.67.83_64

Also, I had another blue screen last night and have attached the log.

Cheers

 

[axe0]

What error code was displayed? Any driver mentioned?

Unfortunately Windows hasn't saved any information about the crash.

 

[fearqq]

Driver power state failure.

Could it be an issue with power saving settings?

As per a recommendation from a friend, I have changed my power profile to "high performance" in the hope that this helps.

Is there anything else I can do?

I will update my computer specs tomorrow but every component was brand new so I'm unhappy seeing any BSOD

 

[axe0]

A 0x9F usually is caused by a driver improperly changing it's power state simultaneously with the system.
Quite often are the display driver, network drivers and USB device drivers causing this crash.

 

[fearqq]

Okay fair enough.

Is there any way to work out which component is causing the issue or a way to prevent them all?

I haven't had one since changing the power settings but haven't played that much.

Also should I be shutting my computer down each day or putting it to sleep?

 

[fearqq]

Just got another blue screen.

In the windows recovered from an unexpected shutdown it says:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 3081

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8011938E10
BCP3: FFFFF80000BA0748
BCP4: FFFFFA80151A9010
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\102616-7987-01.dmp
C:\Users\Dan\AppData\Local\Temp\WER-9048-0.sysdata.xml


I have attached the log file again also.

Thanks
Daniel

 

[axe0]

Please use another USB (if possible) or another keyboard on the same USB port for testing purpose.

 

[fearqq]

I have tried a different USB port for the wireless keyboard and mouse but am still getting the blue screen: driver state power failure.

I have attached another log.

Cheers,
Daniel

 

[axe0]

I don't assume that the same problem happens when the devices are connected to another pc?