- Thread Author
- #1
Hi forums,
Today, I had my very first BSOD encounter with my custom rig that I built back around mid September last year. According to the dump file, it was a DRIVER_POWER_STATE_FAILURE error and it was tied to ntoskrnl.exe. I ran memtest and it found no errors through 2 passes. I used the Driver Verifier built in to Windows and my computer would BSOD right after the "Starting Windows" screen. I've disabled it, but I'm typing this in safe mode right now. I've already taken the liberty of uploading the BSOD .dmp file to OneDrive, which will be posted below. I'm stumped and not sure what to do, but I don't think it's bad memory. I'm fairly certain it's a driver, I'm just not sure which one. Any help would be greatly appreciated.
BSOD dump file: 020216-12604-01.dmp
I guess I should mention that I'm running Windows 7 Ultimate 64-bit (but I guess that might be mostly obvious since I'm under the Windows 7 BSOD forums).
Today, I had my very first BSOD encounter with my custom rig that I built back around mid September last year. According to the dump file, it was a DRIVER_POWER_STATE_FAILURE error and it was tied to ntoskrnl.exe. I ran memtest and it found no errors through 2 passes. I used the Driver Verifier built in to Windows and my computer would BSOD right after the "Starting Windows" screen. I've disabled it, but I'm typing this in safe mode right now. I've already taken the liberty of uploading the BSOD .dmp file to OneDrive, which will be posted below. I'm stumped and not sure what to do, but I don't think it's bad memory. I'm fairly certain it's a driver, I'm just not sure which one. Any help would be greatly appreciated.
BSOD dump file: 020216-12604-01.dmp
I guess I should mention that I'm running Windows 7 Ultimate 64-bit (but I guess that might be mostly obvious since I'm under the Windows 7 BSOD forums).