Windows 10: Having frequent BSOD's. at least 4 today, need help identifying the cause

PC wil just randomly stop working, mostly it just freezes, and sometimes just randomly reboots. would like help identifying what I need to do in order to fix it.system info, will prepare one drive file for the minidumps.these are the 3 minidumps from today in dropbox.https://www.dropbox.com/scl/fo/c2koipy79iswz6jt35l74/APti8nnk6RbgJtul5cNrRcM?rlkey=1fhfnr9pj96v5y417bmfad5cj&st=549r9qs0&dl=0OS Name Microsoft Windows 11 Pro Version 10.0.22631 Build 22631 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name RYZEN-2022 System Manufacturer ASUS System Model

:)

 

Identifying driver causing BSOD

My laptop suddenly went into BSOD with the error IRQL_NOTLESS_OR_EQUAL. I tried using a bsod viewer to identify the driver but it just states ntoskrnl.exe. I have the dump files available, will it be helpful in identifying the driver that is causing this
issue?

 

Frequent Crashes/BSODs With No Identifiable Pattern or Cause

The computer I'm using now is the first one I ever built - I completed it about two years ago. For many months now I've had frequent crashes with no identifiable cause. There doesn't seem to be a correlation between RAM-intensive activities and crashes.
Sometimes I'll only have a couple crashes in a whole day, sometimes I have four within 15 minutes. About half the time I'll get a BSOD and my computer will restart itself. The BSOD error messages are inconsistent, I've listed the most common ones below:

SYSTEM_SERVICE_EXCEPTION

IRQL_NOT_LESS_OR_EQUAL

MEMORY_MANAGEMENT

The other half of the time my computer will just freeze and become unresponsive. Sometimes it'll restart itself, but most of the time I have to manually shut down the computer with the power button on the tower. If I have my speakers turned on when the computer
freezes they make a horrible screeching noise.


About a month ago a friend suggested I test my RAM, so I ran MemTest86 for a full 24 hours. It returned with no errors. I cleaned the inside of my computer with compressed air and re-seated the RAM sticks. I have confirmed they're in the correct slots. I've
also suspected a failing power supply, but I don't know how to confirm it before I attempt a lengthy return process. I've also checked many times to confirm that all of my drivers are up to date.

I'm fully aware that I'll need to try to multiple things to diagnose my crashing problem, but I don't know how to go about this methodically. Any help this forum can offer would be greatly appreciated. Thank you.

Specs:

http://speccy.piriform.com/results/S2XKHhSwt1K6v6oJ1zsi62k

 

Frequent BSoD: IRQL_NOT_LESS_OR_EQUAL 0x0A. Is it possible to identify the cause?

Last weekend, I visited a family member who built my PC in an attempt to resolve a frequent bluescreen error. Previously, I had moved house and therefore had to reconnect all of my devices, however no other changes had been made to my PC.

The crash was IRQL_NOT_LESS_OR_EQUAL, STOP: 0x0000000A, which I have discovered is most likely a driver issue. However, using NirSoft's BlueScreenView to identify the driver causing the issue only came up with ntoskrnl.exe, which after looking up I found
out is a integral part of Windows itself and it's most likely that a different driver is causing the problem. This crash occurred about 4 times with no particular pattern.

Here's whats happened since then:

• We discovered System Restore was disabled, meaning I can't simply use a restore point.
• We tried using the Windows Memory Diagnostic. No problems were discovered.
• We tried using sfc /scannow. No problems either.
• We increased the page file size to be more appropriate for the amount of RAM I have (16GB). Page file size has never been a problem for me before.
• It did not crash the entire weekend and has not done since.

I have tried researching if this problem can be connected to page file size but have found nothing. Therefore, in case it happens again and for the sake of closure, I would like to know if uploading my minidump files would allow for the cause of the crash
to be identified.

Thank you!