F
FnPwnage
Guest
I have an issue where I get a BSOD consistently within the same time frame. Every time I get a BSOD, exactly two days afterward with around 3hrs of being on it the 2nd day, it will get a BSOD every single time. I have had this happen for about a month now with the same results each time. It seems to me the total time all together before another BSOD adds up to about 24hrs of on time before it gets one. Does anyone know why this would happen?
I get these errors:
On Tue 2/16/2021 9:54:19 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021621-8437-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8072F6FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 Sun 2/14/2021 6:28:50 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021421-7390-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF805686FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 Fri 2/12/2021 3:33:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021221-7578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xD1 (0xFFFFF80467DD61CD, 0x2, 0x8, 0xFFFFF80467DD61CD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Continue reading...
I get these errors:
On Tue 2/16/2021 9:54:19 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021621-8437-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8072F6FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 Sun 2/14/2021 6:28:50 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021421-7390-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF805686FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 Fri 2/12/2021 3:33:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021221-7578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xD1 (0xFFFFF80467DD61CD, 0x2, 0x8, 0xFFFFF80467DD61CD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Continue reading...