My pc is AMD Ryzen 7 3700x, AMD RX 5700, ASUS TUF Gaming X570 Plus,
2 X 8 GB Corsair CMK16GX4M2D3600C18 DDR4 3600MHz 18-22-22-42. ...
I have increasingly frequent BSOD errors which freezes the computer regardless of whether it is under load or not.
Never noticed any heating issues.
Prime95 crashes most of the times while cpu stress testing.
It mostly happens while idle or while browsing.
Never had any issues while playing graphic intense games. But faced issues sometimes while playing Windows Spider Solitaire(XP version)
I tried updating BIOS, Graphics Driver and Chipset Driver.
--------------------
Some of the Stop Codes are:-
KERNAL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
KERNAL_AUTO_BOOST_INVALID_LOCK_RELEASE
KERNAL_THREAD_PRIORITY_FLOOR_VIOLATION
KERNAL_SECURITY_CHECK_FAILURE
UNEXPECTED_KERNAL_MODE_TRAP
SYSTEM_SERVICE_EXCEPTION
DRIVER_IRQL_NOT_LESS_OR_EQUAL
IRQL_NOT_LESS_OR_EQUAL
APC_INDEX_MISMATCH
DPC_WATCHDOG_VIOLATION
INVALID_WORK_QUEUE_ITEM
--------------------
My Findings:-
Prime95 Data:-
FATAL ERROR: Rounding was 92.78491345, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 3.057664705e+12, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4999980044, expected less than 0.4
FATAL ERROR: Resulting sum was 4.801393168704695e+33, expected: 4.801393168704668e+33
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Resulting sum was 2.6833694435806e+34, expected: 2.683369443580598e+34
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4970703125, expected less than 0.4
Hardware failure detected, consult stress.txt file.
--------------------
WhoCrashed Output
Crash Dump Analysis:-
On Sat 29-05-2021 20:53:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052921-18640-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF8033AFAC025)
Bugcheck code: 0xD1 (0x2D, 0xFF, 0x5B, 0xFFFFF8033AFAC025)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 29-05-2021 20:53:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: amdppm.sys (0xFFFFF8033AFAC025)
Bugcheck code: 0xD1 (0x2D, 0xFF, 0x5B, 0xFFFFF8033AFAC025)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 25-05-2021 13:13:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052521-18906-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4b46)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8025ACFA320)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
2 X 8 GB Corsair CMK16GX4M2D3600C18 DDR4 3600MHz 18-22-22-42. ...
I have increasingly frequent BSOD errors which freezes the computer regardless of whether it is under load or not.
Never noticed any heating issues.
Prime95 crashes most of the times while cpu stress testing.
It mostly happens while idle or while browsing.
Never had any issues while playing graphic intense games. But faced issues sometimes while playing Windows Spider Solitaire(XP version)
I tried updating BIOS, Graphics Driver and Chipset Driver.
--------------------
Some of the Stop Codes are:-
KERNAL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
KERNAL_AUTO_BOOST_INVALID_LOCK_RELEASE
KERNAL_THREAD_PRIORITY_FLOOR_VIOLATION
KERNAL_SECURITY_CHECK_FAILURE
UNEXPECTED_KERNAL_MODE_TRAP
SYSTEM_SERVICE_EXCEPTION
DRIVER_IRQL_NOT_LESS_OR_EQUAL
IRQL_NOT_LESS_OR_EQUAL
APC_INDEX_MISMATCH
DPC_WATCHDOG_VIOLATION
INVALID_WORK_QUEUE_ITEM
--------------------
My Findings:-
- This doesn't relate to my SSD as I replaced it.
- Prime95 CPU Torture Test is throwing errors most of the times.
Prime95 Data:-
FATAL ERROR: Rounding was 92.78491345, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 3.057664705e+12, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4999980044, expected less than 0.4
FATAL ERROR: Resulting sum was 4.801393168704695e+33, expected: 4.801393168704668e+33
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Resulting sum was 2.6833694435806e+34, expected: 2.683369443580598e+34
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4970703125, expected less than 0.4
Hardware failure detected, consult stress.txt file.
--------------------
WhoCrashed Output
Crash Dump Analysis:-
On Sat 29-05-2021 20:53:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052921-18640-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF8033AFAC025)
Bugcheck code: 0xD1 (0x2D, 0xFF, 0x5B, 0xFFFFF8033AFAC025)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 29-05-2021 20:53:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: amdppm.sys (0xFFFFF8033AFAC025)
Bugcheck code: 0xD1 (0x2D, 0xFF, 0x5B, 0xFFFFF8033AFAC025)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 25-05-2021 13:13:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052521-18906-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4b46)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8025ACFA320)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
Last edited: