Constant BSOD on old rig

[nakedtons]

I know that my rig is old but it run without problems until now when I receive these BSOD every few hours or so. I tried updating all my drivers and also ran Windows Diagnostic to test my RAM. No problems indicated. I stress test every component without any glitch. A friend advised me to reset and then reinstall Windows but I researched that if does not really solve the problem if the driver causing it cannot be identified and not fixed by a fresh windows installation. I need this problem resolved as soon as possible as constant BSOD shutdowns sometimes boot my windows to Automatic repair upon startup which may corrupt system files. Thanks for your kind advice!


Crash Dump Analysis

---

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 4/11/2022 6:30:11 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041122-10515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F78A0)
Bugcheck code: 0xD1 (0x0, 0xD, 0x8, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 4/10/2022 5:45:57 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041122-12500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F78A0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80242AFB3DC, 0xFFFFB486DB241080, 0xFFFFF80242A84EC0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 4/10/2022 4:20:13 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041122-10828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F78A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8077DE87567, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 4/10/2022 5:26:24 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041022-10500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F78A0)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFA6806F495180, 0x4)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[NightRaven49]

A friend advised me to reset and then reinstall Windows but I researched that if does not really solve the problem if the driver causing it cannot be identified and not fixed by a fresh windows installation.

this is still the best course of action as u know that ur fresh installation should have no issues from the get go and also it will force u to download the latest drivers for ur devices. this should also help u to rule out a software problem if it persists, and can start seeing if hardware components other than ur ram are to blame; ur parts list looks pretty old (fx processor, rx 460 etc).

 

[Phen8210]

From the first impressions tell me you may have something related to CPU.

Please check that the temps are fine too.

Try a test like PCMark 10.

 

[nakedtons]

I figure out that it could be the RAM as a reinstallation of Windows did not help. Just RMA it anyway and waiting for it to be delivered from Taiwan. See if new RAM solve the problem. If it still doesn't, it could be the old GPU card. If it's the CPU, then the whole system is uplorry already and I may need to buy a new Ryzen system. Temp checks for CPU is ok as I am using an aftermarket cooler. Strange thing is that I stress tested every component without a single crash. But it crashed into BSOD when I opened multiple youtube videos at the same time. Really playing tikam now to see which is the culprit.

 

[tingsters]

1st fresh install your windows.. mean format everything..
then do fresh installation of windows
monitor it..
if still bS... then shd be hardware liao..

i guess is cpu give way liao..
if not change the mb and cpu..