CRITICAL_PROCESS_DIED when gaming

Hello,

My pc crash on BSOD CRITICAL_PROCESS_DIED when gaming. It happens only when GPU is loaded, but strangly not in any benchmark (run OCCT, and bunch of other just fine). I tried almost everything, repair windows, DISM, sfc, stoping all non microsoft services, reinstalling drivers, downgrading drivers, nothing really helped.

Here is latest minidump:
110424-14875-01.dmp

And here is v2 log colletor output:

I figured out that turning out GPU limit to lower numbers can delay/stop BSOD
I have Hyper-V enabled, but no VM running.

Specs:
Ryzen 9 7900X
2*32GB DDR5 ram
RTX 3090
Samsung 980 PRO 2TB (boot drive)
Samsung 970 Plus 1TB

Are you overclocking?

Not that i know of, there some b***it in bios by default by asus, but i try to turn off everything, also i tried both mods on gpu itself (it has 2 bioses i guess, labeled Q and P mode) same results.

But sometimes previously before i tried to fix it, it would not even show BSOD, just black screen, some noise on the start and thats it, need to reboot because nothing can be done there. Now i just got BSOD and atleast minidump

EDIT:
Also it happens differently in different games. Examples:
LeagueOfLegends: 10-15mins into the game
LightyearFrontier: instantly on menu page
Deadlock: On the start of the match + 10 seconds or so.

EDIT2:
also, everything was running fine like a month ago, i have this pc for about a year. This started to happen suddenly

Well given the info posted, if you're overclocking try turning them down. Also look at the GPU and also graphics driver.

At this point given the info your issue can be from a myriad of things so it's going to be a step by step process in finding the issue. That said, suggest you provide the info stated above for further help - BSOD - Posting Instructions

Dru2 said:

Well given the info posted, if you're overclocking try turning them down. Also look at the GPU and also graphics driver.

At this point given the info your issue can be from a myriad of things so it's going to be a step by step process in finding the issue. That said, suggest you provide the info stated above for further help - BSOD - Posting Instructions

Click to expand...

i did include v2 log, its in the post

The logs indicated a new windows 11 installation with BSOD.

Was Windows Driver Verifier in use?





Some prior steps may be repeated.


Please perform the following steps:




1) Move the page file from D: > C:



2) Reboot



3) Run: Tuneup plus > post a share link






4) Run gather_additional_dump_files > post a share link





5) Run Sea Tools Long generic test (all drives) post share links




6) Download and install: Samsung Magician > test all applicable drives


Drive Details
Update software /firmware
Diagnostic Scan > full scan
Performance Benchmark
Over Provisioning
Performance Optimization



7) Run HD Sentinel > (all drives) post share links

Overview
Temperature
SMART

zbook said:

The logs indicated a new windows 11 installation with BSOD.

Was Windows Driver Verifier in use?





Some prior steps may be repeated.


Please perform the following steps:




1) Move the page file from D: > C:



2) Reboot



3) Run: Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

4) Run gather_additional_dump_files > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/358470d1643456903-batch-files-use-bsod-debugging-gather_additional_dump_files.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

5) Run Sea Tools Long generic test (all drives) post share links

SeaTools | Seagate US

SeaTools - Quick diagnostic tool that checks the health of your drive.

www.seagate.com

6) Download and install: Samsung Magician > test all applicable drives

Samsung Magician Software Download | Samsung Semiconductor Global

Samsung Magician software is designed to help you manage your Samsung SSD with a simple, intuitive user interface. Download files & find supported models.

semiconductor.samsung.com

Drive Details
Update software /firmware
Diagnostic Scan > full scan
Performance Benchmark
Over Provisioning
Performance Optimization



7) Run HD Sentinel > (all drives) post share links

Overview
Temperature
SMART

Click to expand...

Yes, i did tried to use driver verifier, but the issue seem to not catch within driver verifier as BSOD was not DRIVER_VERIFIER_ERROR

EDIT:
I will try to go through all items you mentioned. I already used samsung magician and no faulty blocks were detectet, but will try it again as i am not sure of coverage i was using