Win 10 Crash again (captured DMP file) - hw
-
I originally posted how my Win10 i7, 8GB laptop had crashed and restarted itself here at: Seriously Win10 What's With the Restart? - The Lounge[^] @randor had mentioned that I could take a look at the dump file to get more info. However, at the time the DMP file got delete so I was unable to go further. My machine rebooted and this time I still have the 997MB DMP file (which is crazy) and I opened it up with WinDbg. Here's what I see... I know it's a lot of info but just thought it might be interesting. You can see that it looks like it is the PCI.sys driver that failed. Reason I'm Mentioning This I mention this out of interest and to see if anyone else has had a situation with their Win10 PC rebooting itself like this while not in use. Just a discussion, not looking for an answer. I know better than to believe we would ever be able to run a cryptic thing like this down. This is the Way of Windows, a magical land where the magic often fails. :|
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem.Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe680b6184040, The thread currently holding on to the Pnp lock.
Arg4: ffff87012fc7d910, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
Implicit thread is now ffffe680`b6184040
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534SYSTEM_MANUFACTURER: TOSHIBA
SYSTEM_PRODUCT_NAME: Satellite S55t-B
SYSTEM_SKU: INVALID
SYSTEM_VERSION: PSPRDU-008004
BIOS_VENDOR: INSYDE Corp.
BIOS_VERSION: 1.40
BIOS_DATE: 05/13/2014
BASEBOARD_MANUFACTURER: Type2 - Board Vendor Name1
BASEBOARD_PRODUCT: Type2 - Board Product Name1
BASEBOARD_VERSION: Type2 - Board VersionDUMP_TYPE: 1
BUGCHECK_P1: 4
BUGCHECK_P2: 12c
BUGCHECK_P3: ffffe680b6184040
BUGCHECK_P4: ffff87012fc7d910DRVPOWERSTATE_SUBCODE: 4
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43ae
-
I originally posted how my Win10 i7, 8GB laptop had crashed and restarted itself here at: Seriously Win10 What's With the Restart? - The Lounge[^] @randor had mentioned that I could take a look at the dump file to get more info. However, at the time the DMP file got delete so I was unable to go further. My machine rebooted and this time I still have the 997MB DMP file (which is crazy) and I opened it up with WinDbg. Here's what I see... I know it's a lot of info but just thought it might be interesting. You can see that it looks like it is the PCI.sys driver that failed. Reason I'm Mentioning This I mention this out of interest and to see if anyone else has had a situation with their Win10 PC rebooting itself like this while not in use. Just a discussion, not looking for an answer. I know better than to believe we would ever be able to run a cryptic thing like this down. This is the Way of Windows, a magical land where the magic often fails. :|
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem.Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe680b6184040, The thread currently holding on to the Pnp lock.
Arg4: ffff87012fc7d910, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
Implicit thread is now ffffe680`b6184040
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534SYSTEM_MANUFACTURER: TOSHIBA
SYSTEM_PRODUCT_NAME: Satellite S55t-B
SYSTEM_SKU: INVALID
SYSTEM_VERSION: PSPRDU-008004
BIOS_VENDOR: INSYDE Corp.
BIOS_VERSION: 1.40
BIOS_DATE: 05/13/2014
BASEBOARD_MANUFACTURER: Type2 - Board Vendor Name1
BASEBOARD_PRODUCT: Type2 - Board Product Name1
BASEBOARD_VERSION: Type2 - Board VersionDUMP_TYPE: 1
BUGCHECK_P1: 4
BUGCHECK_P2: 12c
BUGCHECK_P3: ffffe680b6184040
BUGCHECK_P4: ffff87012fc7d910DRVPOWERSTATE_SUBCODE: 4
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43ae
You can set windbg to use microsoft public symbols by specifying srv*c:\Mylocalfolder*http://msdl.microsoft.com/download/symbols In the symbols dialog. This helps a lot with reading the stack. You can run !analyze -v in windbg command window (at the bottom) which will run a basic diagnostic. So, the bug itself happens when a PC does a power transition, so awake to suspend, awake to sleep, or awake to powered off, or vice versa. ( This is the only time windows sends power IRPs (IO request packet) to the driver stacks.) Is this what happened? If not then the dump file you have relates to the restart after the first crash. And the size is normal, it is the entire memory written to file. The system always overwrites memory.dmp with a new one if it crashes. However you can also get it to write a minidump. (system advanced start up and recovery). These files are much smaller, arent as useful of course, but are time stamped. But, I would be very surprised if pci.sys held on to a power IRP, so it is either a false positive, or some other driver in the stack thats making pci.sys fuck up. This is where the fun starts. Verifier.exe is a tool that can monitor drivers for bad behaviour. It can only manage two or three at a time. SO run it, select custom settings, select all the checks except code integrity, VM and low resource, and then select two or three non microsoft drivers. Hopefully verifier will point out the bad driver and you can get rid of it, or try to find an update. (And there are many bad third party drivers out there. A heck of a lot) The reason you often get false positives is that one driver can overwrite anothers memory. When the second driver runs, can be many hours later, it does something wrong because it is now using bad data, or a bad address, and it fails. But it isnt at fault, it is the first driver.
-
You can set windbg to use microsoft public symbols by specifying srv*c:\Mylocalfolder*http://msdl.microsoft.com/download/symbols In the symbols dialog. This helps a lot with reading the stack. You can run !analyze -v in windbg command window (at the bottom) which will run a basic diagnostic. So, the bug itself happens when a PC does a power transition, so awake to suspend, awake to sleep, or awake to powered off, or vice versa. ( This is the only time windows sends power IRPs (IO request packet) to the driver stacks.) Is this what happened? If not then the dump file you have relates to the restart after the first crash. And the size is normal, it is the entire memory written to file. The system always overwrites memory.dmp with a new one if it crashes. However you can also get it to write a minidump. (system advanced start up and recovery). These files are much smaller, arent as useful of course, but are time stamped. But, I would be very surprised if pci.sys held on to a power IRP, so it is either a false positive, or some other driver in the stack thats making pci.sys fuck up. This is where the fun starts. Verifier.exe is a tool that can monitor drivers for bad behaviour. It can only manage two or three at a time. SO run it, select custom settings, select all the checks except code integrity, VM and low resource, and then select two or three non microsoft drivers. Hopefully verifier will point out the bad driver and you can get rid of it, or try to find an update. (And there are many bad third party drivers out there. A heck of a lot) The reason you often get false positives is that one driver can overwrite anothers memory. When the second driver runs, can be many hours later, it does something wrong because it is now using bad data, or a bad address, and it fails. But it isnt at fault, it is the first driver.
-
I originally posted how my Win10 i7, 8GB laptop had crashed and restarted itself here at: Seriously Win10 What's With the Restart? - The Lounge[^] @randor had mentioned that I could take a look at the dump file to get more info. However, at the time the DMP file got delete so I was unable to go further. My machine rebooted and this time I still have the 997MB DMP file (which is crazy) and I opened it up with WinDbg. Here's what I see... I know it's a lot of info but just thought it might be interesting. You can see that it looks like it is the PCI.sys driver that failed. Reason I'm Mentioning This I mention this out of interest and to see if anyone else has had a situation with their Win10 PC rebooting itself like this while not in use. Just a discussion, not looking for an answer. I know better than to believe we would ever be able to run a cryptic thing like this down. This is the Way of Windows, a magical land where the magic often fails. :|
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem.Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe680b6184040, The thread currently holding on to the Pnp lock.
Arg4: ffff87012fc7d910, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
Implicit thread is now ffffe680`b6184040
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534SYSTEM_MANUFACTURER: TOSHIBA
SYSTEM_PRODUCT_NAME: Satellite S55t-B
SYSTEM_SKU: INVALID
SYSTEM_VERSION: PSPRDU-008004
BIOS_VENDOR: INSYDE Corp.
BIOS_VERSION: 1.40
BIOS_DATE: 05/13/2014
BASEBOARD_MANUFACTURER: Type2 - Board Vendor Name1
BASEBOARD_PRODUCT: Type2 - Board Product Name1
BASEBOARD_VERSION: Type2 - Board VersionDUMP_TYPE: 1
BUGCHECK_P1: 4
BUGCHECK_P2: 12c
BUGCHECK_P3: ffffe680b6184040
BUGCHECK_P4: ffff87012fc7d910DRVPOWERSTATE_SUBCODE: 4
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43ae
In cases like this, I clear all the logs and just wait for a pattern between work habits and events. (Deleting / disabling a lot of redundant apps / services / task scheduler tasks in the process). Solved a lot of issues in one case by not using the machine vendor's "program launcher".
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
I originally posted how my Win10 i7, 8GB laptop had crashed and restarted itself here at: Seriously Win10 What's With the Restart? - The Lounge[^] @randor had mentioned that I could take a look at the dump file to get more info. However, at the time the DMP file got delete so I was unable to go further. My machine rebooted and this time I still have the 997MB DMP file (which is crazy) and I opened it up with WinDbg. Here's what I see... I know it's a lot of info but just thought it might be interesting. You can see that it looks like it is the PCI.sys driver that failed. Reason I'm Mentioning This I mention this out of interest and to see if anyone else has had a situation with their Win10 PC rebooting itself like this while not in use. Just a discussion, not looking for an answer. I know better than to believe we would ever be able to run a cryptic thing like this down. This is the Way of Windows, a magical land where the magic often fails. :|
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem.Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe680b6184040, The thread currently holding on to the Pnp lock.
Arg4: ffff87012fc7d910, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
Implicit thread is now ffffe680`b6184040
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534SYSTEM_MANUFACTURER: TOSHIBA
SYSTEM_PRODUCT_NAME: Satellite S55t-B
SYSTEM_SKU: INVALID
SYSTEM_VERSION: PSPRDU-008004
BIOS_VENDOR: INSYDE Corp.
BIOS_VERSION: 1.40
BIOS_DATE: 05/13/2014
BASEBOARD_MANUFACTURER: Type2 - Board Vendor Name1
BASEBOARD_PRODUCT: Type2 - Board Product Name1
BASEBOARD_VERSION: Type2 - Board VersionDUMP_TYPE: 1
BUGCHECK_P1: 4
BUGCHECK_P2: 12c
BUGCHECK_P3: ffffe680b6184040
BUGCHECK_P4: ffff87012fc7d910DRVPOWERSTATE_SUBCODE: 4
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43ae
the reason for the crashing of windows 10 is the hardware which you are using in the system is not compatible with the operating system. visit Tenda router support to check the compatibility of the device if it is compatible then use windows 10 or else use another operating system.
