need help laptop shuts off minidump uploaded.

[raptorddd]

am not sure if this is the right place to post this..

is there a place i can get help finding out why my laptop shut down.? or if someone that knows how to read minidump in here.?

it shuts down while am watching you tube. am using edge.

this happens once in a while..

 

 

050722-6156-01.dmp

[jaybee83]

when it shuts down, what is the behaviour like? is it an instant shut off? or does windows suddenly decide to initiate the shutdown procedure?

 

have u checked component temperatures (i.e. via HWInfo) when shutdowns happen? when was the last time u serviced your laptop (cleaning out dust, repaste, etc.)? do the shutdowns only happen on battery or on AC power? or both?

all this will help us dial down the range of potential culprits.

[raptorddd]

10 hours ago, jaybee83 said:

when it shuts down, what is the behaviour like? is it an instant shut off? or does windows suddenly decide to initiate the shutdown procedure?

 

have u checked component temperatures (i.e. via HWInfo) when shutdowns happen? when was the last time u serviced your laptop (cleaning out dust, repaste, etc.)? do the shutdowns only happen on battery or on AC power? or both?

all this will help us dial down the range of potential culprits.

instant shut off.  event viewer says 6008

i open minindump says 

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: ffffe703427a9040, The thread currently holding on to the Pnp lock.
Arg4: ffffbc010e637880, nt!TRIAGE_9F_PNP on Win7 and higher

 

yes i use realtemp and when it happens they are around 40-50-60c i use log and when it happens temps are fine.

clean service like 4 days ago.

i have no battery.

i can run stress test temps go upto 88c 

 

i also found this. i dont know how to read minidump

 

 

HARDWARE_ID:  {5d624f94-8850-40c3-a3fa-a4fd2080baf3}\vwifimp_wfd

IMAGE_NAME:  vwifibus.sys

MODULE_NAME: vwifibus

FAULTING_MODULE: fffff80546dd0000 vwifibus

[jaybee83]

7 hours ago, raptorddd said:

instant shut off.  event viewer says 6008

i open minindump says 

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: ffffe703427a9040, The thread currently holding on to the Pnp lock.
Arg4: ffffbc010e637880, nt!TRIAGE_9F_PNP on Win7 and higher

 

yes i use realtemp and when it happens they are around 40-50-60c i use log and when it happens temps are fine.

clean service like 4 days ago.

i have no battery.

i can run stress test temps go upto 88c 

 

i also found this. i dont know how to read minidump

 

 

HARDWARE_ID:  {5d624f94-8850-40c3-a3fa-a4fd2080baf3}\vwifimp_wfd

IMAGE_NAME:  vwifibus.sys

MODULE_NAME: vwifibus

FAULTING_MODULE: fffff80546dd0000 vwifibus

ok, so far so good.

 

this seems to be driver related, possibly a faulty driver or component hanging up the system. did you recently install any new components or drivers? when did this start happening? ideally we could fix this by returning your system to an earlier state via system restore.

[Eban]

Could try this. 

I installed it but have not had a crash so never tested.

 

https://www.resplendence.com/whocrashed

 

[jaybee83]

7 minutes ago, Eban said:

Could try this. 

I installed it but have not had a crash so never tested.

 

https://www.resplendence.com/whocrashed

 

sure, go ahead and lets see if we can get a bit more info 🙂

[raptorddd]

17 hours ago, jaybee83 said:

ok, so far so good.

 

this seems to be driver related, possibly a faulty driver or component hanging up the system. did you recently install any new components or drivers? when did this start happening? ideally we could fix this by returning your system to an earlier state via system restore.

ssd. like less than a month.

but it has happened before this.  i happens but like maybe in 1 week or more. not sure when it started. i just clean installed windows like 3 weeks ago,

16 hours ago, Eban said:

Could try this. 

I installed it but have not had a crash so never tested.

 

https://www.resplendence.com/whocrashed

 

thanks ill try this and will repot back if i get a shut off.

[raptorddd]

Crash Dump Analysis

---

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sat 5/7/2022 11:50:53 PM your computer crashed or a problem was reported
 

Crash dump file:	C:\Windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code:	0x9F(0x4, 0x12C, 0xFFFFE703427A9040, 0xFFFFBC010E637880)
Bugcheck name:	DRIVER_POWER_STATE_FAILURE
Driver or module in which error occurred:	intelppm.sys (intelppm+0x138f)
File path:	C:\Windows\System32\drivers\intelppm.sys
Description:	Processor Device Driver
Product:	Microsoft® Windows® Operating System
Company:	Microsoft Corporation
Bug check description:	This bug check indicates that the driver is in an inconsistent or invalid power state.
Analysis:	The power state transition timed out waiting to synchronize with the PnP subsystem. This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.

On Sat 5/7/2022 11:50:53 PM your computer crashed or a problem was reported
 

Crash dump file:	C:\Windows\Minidump\050722-6156-01.dmp (Minidump)
Bugcheck code:	0x1000009F(0x4, 0x12C, 0xFFFFE703427A9040, 0xFFFFBC010E637880)
Bugcheck name:	CUSTOM_ERROR
Analysis:

 

---

Conclusion

---

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

Read the suggestions displayed in the bugcheck analysis above.

The analysis process took 0:00:05 (h:mm:ss).

[jaybee83]

5 hours ago, raptorddd said:

Crash Dump Analysis

---

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sat 5/7/2022 11:50:53 PM your computer crashed or a problem was reported
 

Crash dump file:	C:\Windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code:	0x9F(0x4, 0x12C, 0xFFFFE703427A9040, 0xFFFFBC010E637880)
Bugcheck name:	DRIVER_POWER_STATE_FAILURE
Driver or module in which error occurred:	intelppm.sys (intelppm+0x138f)
File path:	C:\Windows\System32\drivers\intelppm.sys
Description:	Processor Device Driver
Product:	Microsoft® Windows® Operating System
Company:	Microsoft Corporation
Bug check description:	This bug check indicates that the driver is in an inconsistent or invalid power state.
Analysis:	The power state transition timed out waiting to synchronize with the PnP subsystem. This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.

On Sat 5/7/2022 11:50:53 PM your computer crashed or a problem was reported
 

Crash dump file:	C:\Windows\Minidump\050722-6156-01.dmp (Minidump)
Bugcheck code:	0x1000009F(0x4, 0x12C, 0xFFFFE703427A9040, 0xFFFFBC010E637880)
Bugcheck name:	CUSTOM_ERROR
Analysis:

 

---

Conclusion

---

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

Read the suggestions displayed in the bugcheck analysis above.

The analysis process took 0:00:05 (h:mm:ss).

 

Go ahead and try these steps here with regards to intelppm.sys: https://thegeekpage.com/fix-blue-screen-error-intelppm-sys-in-windows-10/

 

Sounds to me like some files might have been corrupted. Either that or its some kind of hardware failure causing the respective drivers to hiccup and timeout.

[Vasudev]

I'd suggest installing Intel chipset driver and uinstalling dptf driver if its present. Are you using any third party power plan optimizer that is interfering intel speedstep driver?

[raptorddd]

1 hour ago, Vasudev said:

I'd suggest installing Intel chipset driver and uinstalling dptf driver if its present. Are you using any third party power plan optimizer that is interfering intel speedstep driver?

hi. i did the other suggestion but the turbo boost was disaabled not sure. i checked frequencies and stayed at stock.

right now i havent faced any shut offs. maybe because while watching you tube i keep clicking on task bar with mouse button.

so you suggest to use the dell driver.... i dont know what is dptf.?

[Vasudev]

On 5/27/2022 at 1:25 AM, raptorddd said:

hi. i did the other suggestion but the turbo boost was disaabled not sure. i checked frequencies and stayed at stock.

right now i havent faced any shut offs. maybe because while watching you tube i keep clicking on task bar with mouse button.

so you suggest to use the dell driver.... i dont know what is dptf.?

DPTF allows configurable TDP, skin temp limit, acoustics etc.  But some OEMs choose to incorporate and some ignore it. If you don't see it listed the model/laptop doesn't support it.

[aldarxt]

You could also try these cmd (Admin) one line at a time it will refresh windows looking for corrupted files

1 line at a time and let it finish

Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

check disk chkdsk C: /f /r
chkdsk /r does the same thing as chkdsk /f only it also checks for bad sectors on the disk and recovers any readable information. Running chkdsk /r implies that also chkdsk /f is run.

chkdsk /f only checks for disk errors, not bad sectors.
________________________________________
Clean and Analyze the WinSXS folder

    DISM /Online /Cleanup-Image /StartComponentCleanup
    SFC /SCANNOW
    DISM /Online  /Cleanup-Image /AnalyzeComponentStore
    SFC /SCANNOW
Restart your computer
After the restart, open command prompt (as admin) again and run DISM.

    DISM /Online /Cleanup-Image /RestoreHealth

[raptorddd]

2 hours ago, aldarxt said:

You could also try these cmd (Admin) one line at a time it will refresh windows looking for corrupted files

1 line at a time and let it finish

Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

check disk chkdsk 😄 /f /r
chkdsk /r does the same thing as chkdsk /f only it also checks for bad sectors on the disk and recovers any readable information. Running chkdsk /r implies that also chkdsk /f is run.

chkdsk /f only checks for disk errors, not bad sectors.
________________________________________
Clean and Analyze the WinSXS folder

    DISM /Online /Cleanup-Image /StartComponentCleanup
    SFC /SCANNOW
    DISM /Online  /Cleanup-Image /AnalyzeComponentStore
    SFC /SCANNOW
Restart your computer
After the restart, open command prompt (as admin) again and run DISM.

    DISM /Online /Cleanup-Image /RestoreHealth

thanks i havent faced this again but if i do ill try this steps.

[raptorddd]

2 hours ago, aldarxt said:

You could also try these cmd (Admin) one line at a time it will refresh windows looking for corrupted files

1 line at a time and let it finish

Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

check disk chkdsk 😄 /f /r
chkdsk /r does the same thing as chkdsk /f only it also checks for bad sectors on the disk and recovers any readable information. Running chkdsk /r implies that also chkdsk /f is run.

chkdsk /f only checks for disk errors, not bad sectors.
________________________________________
Clean and Analyze the WinSXS folder

    DISM /Online /Cleanup-Image /StartComponentCleanup
    SFC /SCANNOW
    DISM /Online  /Cleanup-Image /AnalyzeComponentStore
    SFC /SCANNOW
Restart your computer
After the restart, open command prompt (as admin) again and run DISM.

    DISM /Online /Cleanup-Image /RestoreHealth

thanks i havent faced this again but if i do ill try this steps.