Win 10 Crash again (captured DMP file)
-
<EDIT> Moved to Hardware forum ==> Win 10 Crash again (captured DMP file) - hw - Hardware & Devices Discussion Boards[^] </EDIT> 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_VE -
<EDIT> Moved to Hardware forum ==> Win 10 Crash again (captured DMP file) - hw - Hardware & Devices Discussion Boards[^] </EDIT> 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_VEDid you try rebooting? :laugh: I have never had problems with Windows 10 crashing, but I am not running it on a laptop, so I don't have any power policies enabled - I am guessing that your crash is related to Power Management given the first line in your dump. BTW, I have worked with application crash dumps that were larger than 1GB, so I don't think 997MB for the OS crash dump is surprising.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
-
<EDIT> Moved to Hardware forum ==> Win 10 Crash again (captured DMP file) - hw - Hardware & Devices Discussion Boards[^] </EDIT> 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_VETake it to the hardware forum and I will answer you.
-
Did you try rebooting? :laugh: I have never had problems with Windows 10 crashing, but I am not running it on a laptop, so I don't have any power policies enabled - I am guessing that your crash is related to Power Management given the first line in your dump. BTW, I have worked with application crash dumps that were larger than 1GB, so I don't think 997MB for the OS crash dump is surprising.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
SoMad wrote:
am guessing that your crash is related to Power Management given the first line in your dump
Yeah, it does look like that. Just curious if this is a Win10 thing or related to my H/W. Of course this never happened in the past (only since recent updates) and never happened under Win8.1.
SoMad wrote:
I don't think 997MB for the OS crash dump is surprising
I agree, as a developer it is not surprising. As a consumer, it's a bit surprising. Also, with a dump with that much info I would think their might be an AI-type of process that Microsoft would provide that would give me a better idea of how to resolve. Such, as:
Microsoft Debug AI:
"PCI.sys has crashed due to conflict with Power settings driver. Please update power settings driver"
-
Take it to the hardware forum and I will answer you.
-
<EDIT> Moved to Hardware forum ==> Win 10 Crash again (captured DMP file) - hw - Hardware & Devices Discussion Boards[^] </EDIT> 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_VEMy wife's older all-in-one started doing this a while back. In her case, it would bring up the sad-face bsod which mentioned a power-state-failure error. I seem to have fixed it by changing the power plan from the default to a different setting. Good luck! :)
"Go forth into the source" - Neal Morse
-
<EDIT> Moved to Hardware forum ==> Win 10 Crash again (captured DMP file) - hw - Hardware & Devices Discussion Boards[^] </EDIT> 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_VE -
<EDIT> Moved to Hardware forum ==> Win 10 Crash again (captured DMP file) - hw - Hardware & Devices Discussion Boards[^] </EDIT> 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_VEWell,
raddevus wrote:
I know better than to believe we would ever be able to run a cryptic thing like this down.
Here is the Intel Wireless Networking[^] forum. Go over there with your ranting and tell them that your Intel® Dual Band Wireless-AC 3160[^] driver is crashing because NETwbw02.sys is holding a PNP lock causing a power IRP timeout... bugcheck 0x9f. Your Intel wireless driver appears to be failing during this process: Power IRPs for the System[^] Btw looks like Intel released a new version on 06-Feb-2018 so you might want to make sure you've got the latest device driver. Best Wishes, -David Delaune Edit: I'm going to start charging you for these debugging sessions. You owe me 2 beers. :beer::beer:
-
Well,
raddevus wrote:
I know better than to believe we would ever be able to run a cryptic thing like this down.
Here is the Intel Wireless Networking[^] forum. Go over there with your ranting and tell them that your Intel® Dual Band Wireless-AC 3160[^] driver is crashing because NETwbw02.sys is holding a PNP lock causing a power IRP timeout... bugcheck 0x9f. Your Intel wireless driver appears to be failing during this process: Power IRPs for the System[^] Btw looks like Intel released a new version on 06-Feb-2018 so you might want to make sure you've got the latest device driver. Best Wishes, -David Delaune Edit: I'm going to start charging you for these debugging sessions. You owe me 2 beers. :beer::beer:
-
Hi, You are welcome. Now you see why the DMP file is automatically cleaned up by a daily script. It's gigantic. :) Btw there are others complaining about similar blue screen bugs on the Intel wireless forum: Built-in Dual Band Wireless-AC 3168 causing Bluescreens on my Ryzen desktop?[^] Note that I see one of them point out a DPC_WATCHDOG_VIOLATION which is in the same class of bugs as your problem. This is why you should always go for the WHQL Microsoft signed device drivers. It means that the device driver has passed a huge series of tests[^] that confirm the driver is compatible with Windows. At least one of the following statements is true of any device driver not WHQL signed: 1.) The device driver was not submitted to WHQL[^]. or 2.) The driver was submitted and failed the test. Best Wishes, -David Delaune
-
Hi, You are welcome. Now you see why the DMP file is automatically cleaned up by a daily script. It's gigantic. :) Btw there are others complaining about similar blue screen bugs on the Intel wireless forum: Built-in Dual Band Wireless-AC 3168 causing Bluescreens on my Ryzen desktop?[^] Note that I see one of them point out a DPC_WATCHDOG_VIOLATION which is in the same class of bugs as your problem. This is why you should always go for the WHQL Microsoft signed device drivers. It means that the device driver has passed a huge series of tests[^] that confirm the driver is compatible with Windows. At least one of the following statements is true of any device driver not WHQL signed: 1.) The device driver was not submitted to WHQL[^]. or 2.) The driver was submitted and failed the test. Best Wishes, -David Delaune