DEVICE_POWER_STATE_FAILURE around login

Ok. I ran SFC and there were no integrity violations. Here's the dump files if you need them.

I will try disconnecting the DVD drives tomorrow, it's already 10pm where I live and I'm pretty tired. That's a pretty interesting discovery there, the DVD drive would have been the last place I looked. But since it's caused by atapi.sys I can see why that would have been the case.

essenbe said:

It is saying pretty much the same thing.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe000963f8060, fffff8015ea4bce0, ffffe0009815bb40}
Unable to load image \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
Probably caused by : atapi.sys

Code:

0: kd> 
Device object (ffffe000963f8060) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\atapi DriverObject ffffe000963f5890
Current Irp 00000000 RefCount 0 Type 00000002 Flags 00005050
DevExt ffffe000963f81b0 DevObjExt ffffe000963f89f0 Dope ffffe00097de30e0 DevNode ffffe000963fc8a0 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000101)  FILE_REMOVABLE_MEDIA, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe00096211b50 \Driver\ACPI
Device queue is not busy.

Code:

ffffe000963fc8a0
DevNode 0xffffe000963fc8a0 for PDO 0xffffe000963f8060
  Parent 0xffffe000962103e0   Sibling 0xffffe000961ce540   Child 0000000000   
  InstancePath is "IDE\CdRomTSSTcorp_CD/DVDW_TS-H652D_______________GA01____\5&3f9cfc3&0&0.0.0"
  ServiceName is "cdrom"
  TargetDeviceNotify List - f 0xffffc0010302d740  b 0xffffc001040c5e20
  State = DeviceNodeStarted (0x308)
  Previous State = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[08] = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[07] = DeviceNodeEnumeratePending (0x30c)
  StateHistory[06] = DeviceNodeStarted (0x308)
  StateHistory[05] = DeviceNodeStartPostWork (0x307)
  StateHistory[04] = DeviceNodeStartCompletion (0x306)
  StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
  StateHistory[02] = DeviceNodeDriversAdded (0x303)
  StateHistory[01] = DeviceNodeInitialized (0x302)
  StateHistory[00] = DeviceNodeUninitialized (0x301)
  StateHistory[19] = Unknown State (0x0)
  StateHistory[18] = Unknown State (0x0)
  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  StateHistory[15] = Unknown State (0x0)
  StateHistory[14] = Unknown State (0x0)
  StateHistory[13] = Unknown State (0x0)
  StateHistory[12] = Unknown State (0x0)
  StateHistory[11] = Unknown State (0x0)
  StateHistory[10] = Unknown State (0x0)
  StateHistory[09] = Unknown State (0x0)
  Flags (0x2c000138)  DNF_REENUMERATE, DNF_ENUMERATED, 
                      DNF_IDS_QUERIED, DNF_NO_RESOURCE_REQUIRED, 
                      DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS, 
                      DNF_NO_UPPER_DEVICE_FILTERS

I think you solved it! I haven't experienced another BSOD after unplugging that drive. Thanks man!