Question blue screen of death (BSOD)- KMODE_EXCEPTION_NOT_HANDLED / IRQL_NOT_LESS_OR_EQUAL : ntoskrnl.exe

[Mauricio21]

Hello good morning, afternoons or nights. A little over a week ago I bought a computer assembled online. The store that sold it to me is official and has good reviews but as I say, the purchase was online. A few days ago suddenly (after about a week of use) the pc that has factory components, began to show strange signs.
For example, the first error I had was that the screen froze while I was doing some task or something not very demanding, which was solved with a forced restart. That problem no longer appears to me, but I think it is a worse one now and it is the blue screen of death (BSOD).
The first time it (BSOD) appeared to me was when I wanted to open a low-resource game from steam (after having previously installed it) and I was quite surprised because I didn't finish creating a new game and this problem appeared. Then after having been approximately 4 or 5 hours with the computer in use (doing tasks) the BSOD jumped again.
what I came to notice is that after a long (or short) time of use, I am doomed to BSOD appear.
In BlueScreenView I get the following data: kmode_exception_not_handled (I guess this is the one that appeared to me last time) with cause ntoskrnl.exe.
and another irql_not_less_or_equal with the same cause, ntoskrnl.exe.
My pc specs are:
Ryzen 5 4600g with radeon vega 7
2x8gb Ram
ASROCK A520-HDV motherboard
480gb SSD
Windows 11 (reinstall it from scratch but the error persists)

I attach some screenshots that I took from BlueScreenView.
Thanks for your time.

 

[Mauricio21]

Hello good morning, afternoons or nights. A little over a week ago I bought a computer assembled online. The store that sold it to me is official and has good reviews but as I say, the purchase was online. A few days ago suddenly (after about a week of use) the pc that has factory components, began to show strange signs.
For example, the first error I had was that the screen froze while I was doing some task or something not very demanding, which was solved with a forced restart. That problem no longer appears to me, but I think it is a worse one now and it is the blue screen of death (BSOD).
The first time it (BSOD) appeared to me was when I wanted to open a low-resource game from steam (after having previously installed it) and I was quite surprised because I didn't finish creating a new game and this problem appeared. Then after having been approximately 4 or 5 hours with the computer in use (doing tasks) the BSOD jumped again.
what I came to notice is that after a long (or short) time of use, I am doomed to BSOD appear.
In BlueScreenView I get the following data: kmode_exception_not_handled (I guess this is the one that appeared to me last time) with cause ntoskrnl.exe.
and another irql_not_less_or_equal with the same cause, ntoskrnl.exe.
My pc specs are:
Ryzen 5 4600g with radeon vega 7
2x8gb Ram
ASROCK A520-HDV motherboard
480gb SSD
Windows 11 (reinstall it from scratch but the error persists)

I attach some screenshots that I took from BlueScreenView.
Thanks for your time.

 

[johnbl]

3 bugchecks
1 due to a access violation (bad memory address)
1 due to a breakpoint set without a debugger
1 due to a driver trying to access memory address that was paged out.

for this I would update the various drivers from your motherboard vendor. Mainly the cpu chipset driver, and any special driver for your drive storage. You might run crystaldiskinfo.exe and check the health of your drive(s) also check the firmware version and see if there is a upgrade.

since all of the errors involved a bad memory address being used. I would update the bios to get the best default memory timings, then boot and run memtest86 to confirm your memory timings are correct.
update of the chipset drivers should help if there is a bug in how the pagefile.sys is being saved.

otherwise you have to have someone look at the actual minidump file with a debugger. I would delete the old memory dumps and do the bios and driver updates and testing. Then provide a new memory dump if you still have issues.