BSOD crashes after startup

[1ntegerByt3s]

Hello, hope you all are doing okay today. For the past week or so, I have been experiencing BSOD crashes, from sometimes crashing while a launching a game from Steam to now crashing after past the login screen. Afair, they were coded, CRITICAL_PROCESS_DIED. I ran Task Manager running on my second monitor and didn't notice anything usual, aside from the disk usage going high but that's normal from the startup apps. Sometimes it would crash after loading all startup apps and sometimes as soon as it reaches to the login screen. I have noticed slower loading times and I'm really trying to get some insight instead of pressing every button and hope it solves my problem.

 

The following lists the approaches I did to diagnose my PC...

- Disabled startup apps

- Ran chkdsk, sfc, and DISM

- Booted thru safe mode (it kept popping up ctfmon.exe about a stack buffer issue)

- Updated my chipset drivers and any drivers that required updating

- Did a in-place repair upgrade through the Windows installation media, hoping there were corrupt Windows files

- Looked through BIOS for any unexpected changes (for some reason, it was set in Mandarin lol?)

 

Sometimes I would get lucky and get no crashes and can play games with no issues or change in performance.

 

I hope I can get some feedback and cool my brain down. My parts are listed in my signature. Thanks for your time.

[ItTakes2ToMango]

Are you getting any additional errors/info from event viewer around the time of the crashes?

[1ntegerByt3s]

5 minutes ago, ItTakes2ToMango said:

Are you getting any additional errors/info from event viewer around the time of the crashes?

 

I only touched on it on the beginning of the crashes and all I saw was critical errors and stating it shutdown unexpectedly. Maybe I'm not too familiar with Event Viewer? 

[Bjoolz]

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

[1ntegerByt3s]

4 hours ago, Bjoolz said:

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

This dump folder was created prior to the Windows reinstall, but there was no dump folder in this current build.

Minidump.zip

[Bjoolz]

15 hours ago, 1ntegerByt3s said:

This dump folder was created prior to the Windows reinstall, but there was no dump folder in this current build.

Minidump.zip 341.1 kB · 0 downloads

This crash is from October 8th and was caused by BattlEye. We see anticheats causing BSODs all the time. Critical_Process_Died paired with no dump files makes me suspect a faulty storage drive. If you have lots of drives, open Disk Management and look under the size of each partition for "Page File". With the crash error being Critical Process Died it should be on the C: drive, just covering all bases.

 

And moving the page file should make it able to write dump files correctly again, the main suspect now is the drive crashing so it's not "available" during the dump write process. This process uses the page file to write the dump. Moving the page file to a different drive could make it able to write dump files, but with Critical Process Died it often just shows a Windows process. 

[1ntegerByt3s]

52 minutes ago, Bjoolz said:

This crash is from October 8th and was caused by BattlEye. We see anticheats causing BSODs all the time. Critical_Process_Died paired with no dump files makes me suspect a faulty storage drive. If you have lots of drives, open Disk Management and look under the size of each partition for "Page File". With the crash error being Critical Process Died it should be on the C: drive, just covering all bases.

 

And moving the page file should make it able to write dump files correctly again, the main suspect now is the drive crashing so it's not "available" during the dump write process. This process uses the page file to write the dump. Moving the page file to a different drive could make it able to write dump files, but with Critical Process Died it often just shows a Windows process. 

So I need a new storage device, eh? It's funny how sometimes I'm lucky it won't crash, like last night, I was able to play a couple of games fine.

[Robchil]

5 minutes ago, 1ntegerByt3s said:

So I need a new storage device, eh? It's funny how sometimes I'm lucky it won't crash, like last night, I was able to play a couple of games fine.

you can also run chkdsk on c: or drive the game is on, on C: it will do it after a reboot as it's the system drive. 

 

[1ntegerByt3s]

1 hour ago, Robchil said:

you can also run chkdsk on c: or drive the game is on, on C: it will do it after a reboot as it's the system drive. 

 

As I mentioned in the beginning of the thread, I already ran chkdsk on all drives and they all report no signs of bad sectors.

[Robchil]

1 minute ago, 1ntegerByt3s said:

As I mentioned in the beginning of the thread, I already ran chkdsk on all drives and they all report no signs of bad sectors.

 

yeah see it now. i would uninstall the above mentioned battleye and verify the game that installed it and maybe search google for battleye CRITICAL_PROCESS_DIED  for solutions, as you see you will find that it "protect" games for anything interfering with the game... also installing drivers.... 

check if you need to uninstall it and the game, and reinstall drivers then the game again. 

 

[1ntegerByt3s]

40 minutes ago, Robchil said:

 

yeah see it now. i would uninstall the above mentioned battleye and verify the game that installed it and maybe search google for battleye CRITICAL_PROCESS_DIED  for solutions, as you see you will find that it "protect" games for anything interfering with the game... also installing drivers.... 

check if you need to uninstall it and the game, and reinstall drivers then the game again. 

 

Is it worth the shot? Because I don't see BattleEye running in the background, not to mention it is not listed to the startup apps. Therefore, I don't see how BattleEye is related to the BSOD crashes past the login screen.

[Robchil]

4 minutes ago, 1ntegerByt3s said:

Is it worth the shot? Because I don't see BattleEye running in the background, not to mention it is not listed to the startup apps. Therefore, I don't see how BattleEye is related to the BSOD crashes past the login screen.

it's cheaper than a new drive

 

[1ntegerByt3s]

4 hours ago, Bjoolz said:

This crash is from October 8th and was caused by BattlEye. We see anticheats causing BSODs all the time. Critical_Process_Died paired with no dump files makes me suspect a faulty storage drive. If you have lots of drives, open Disk Management and look under the size of each partition for "Page File". With the crash error being Critical Process Died it should be on the C: drive, just covering all bases.

 

And moving the page file should make it able to write dump files correctly again, the main suspect now is the drive crashing so it's not "available" during the dump write process. This process uses the page file to write the dump. Moving the page file to a different drive could make it able to write dump files, but with Critical Process Died it often just shows a Windows process. 

 

Okay, so I uninstalled and installed BattleEye manually (it wasn't listed on Programs, so I had to go to Rainbow Six SIege's directory and do it there), but I will report back if I encounter any crashes because once my PC doesn't crash, it will behave normally. Also, here's a picture of my disk management...

[Robchil]

2 hours ago, 1ntegerByt3s said:

 

Okay, so I uninstalled and installed BattleEye manually (it wasn't listed on Programs, so I had to go to Rainbow Six SIege's directory and do it there), but I will report back if I encounter any crashes because once my PC doesn't crash, it will behave normally. Also, here's a picture of my disk management...

uhm.. what are those Fast Sexy drive devices?.. nvme's?.. what are your OS running on? 

nm.. but your boot drive is starting to get older..  consider getting a new one..  

smaller nvme's for boot has alot more use of all their data than larger drives.. 

i run 2 500gb nvme's in raid0  i'm considering upgrading to two 990 pro 2TB for a new biiig raid0

 

 

 

[Bjoolz]

5 hours ago, 1ntegerByt3s said:

 

Okay, so I uninstalled and installed BattleEye manually (it wasn't listed on Programs, so I had to go to Rainbow Six SIege's directory and do it there), but I will report back if I encounter any crashes because once my PC doesn't crash, it will behave normally. Also, here's a picture of my disk management...

You could try moving the page file location as you are not getting dump files from these crashes. Either of the other drives is fine. 

[1ntegerByt3s]

7 hours ago, Robchil said:

uhm.. what are those Fast Sexy drive devices?.. nvme's?.. what are your OS running on? 

nm.. but your boot drive is starting to get older..  consider getting a new one..  

smaller nvme's for boot has alot more use of all their data than larger drives.. 

i run 2 500gb nvme's in raid0  i'm considering upgrading to two 990 pro 2TB for a new biiig raid0

 

 

 

C: boot drive is an 2280 NVME M.2, while the other drives are 2.5" 1TB SSDs. And I am running Win11 Pro.
 

4 hours ago, Bjoolz said:

You could try moving the page file location as you are not getting dump files from these crashes. Either of the other drives is fine. 

Done. And luckily I got it to crash after I moved the page file location. Here's the new one...

Minidump2.zip

[Bjoolz]

37 minutes ago, 1ntegerByt3s said:

C: boot drive is an 2280 NVME M.2, while the other drives are 2.5" 1TB SSDs. And I am running Win11 Pro.
 

Done. And luckily I got it to crash after I moved the page file location. Here's the new one...

Minidump2.zip 228.71 kB · 0 downloads

It looks like the storage. 

[1ntegerByt3s]

34 minutes ago, Bjoolz said:

It looks like the storage. 

Well, I guess it's time to get myself a reputable brand: Samsung. Anyways, I really appreciate your help, @Bjoolz @Robchil!