Also see if there is a new C:\Windows \MEMORY.DMP file. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. You can try using Driver Verifier to see if that shows us any drivers with problems:ĭriver Verifier- tracking down a mis-behaving driver.įollowing the instructions in the above link will check for problems in all non-Microsoft drivers. 2004 build 19041.630ĬPU: Intel Core i5-3317U 1.70GHz, 1701 Mhz, 2 core, 4 CPUĪ driver has failed to complete a power IRP within a specific time.Īrg1: 0000000000000004, The power transition timed out waiting to synchronize with the PnpĪrg2: 000000000000012c, Timeout in seconds.Īrg3: ffffc20cd7222040, The thread currently holding on to the Pnp lock.Īrg4: fffffb00f5a29880, nt!TRIAGE_9F_PNP on Win7 and higher In order to do a deeper check I launched Bluescreenview to scan the dump file, and it found BSOD errors were caused by ntoskrnl.exe file, that as far as I know, it's just related to Windows kernel, and it just means there's a faulty driver, but I have no idea of what it is.Ĭan you please help to find the exact problem and solve this issue?īelow you can fine my pc specs, I can give you any other information needed: I've tried lots of solutions found around the web, like adding a registry key named "MSIServer" and starting msiserver, disabling sleep mode, run sfc command for integrity scan (that found nothing wrong), tried updating all drivers (that were found all updated), launch Windows updates, but none of them solved the problem.
I have an annoying problem with my pc, because almost everytime I shutdown or restart it gives BSOD screen with DRIVER_POWER_STATE_FAILURE error.
0 kommentar(er)
