Atriox Aug 27, 2024 @ 2:05pm
CRITICAL_PROCESS_DIED BSOD Error
Can I please have some help identifying what caused my BSOD error?

It started with the audio cutting off - I went to desktop and then videos plus audio wouldn't work too.

I posted the WinDbg dump on reddit because it's too big to post on steam - https://www.reddit.com/r/pcmasterrace/comments/1f2s3ee/critical_process_died_bsod_error/
< >
Showing 1-15 of 19 comments
You mentioned in a reply to that Reddit post that you changed CPUs. Did this BSOD start after that change?

With that error, the first thing I'd be doing is testing the storage/Windows installation. Doing disks checks, running file checker, etc. Reinstalling Windows would be the "nuclear" option, but I'm not suggesting you need to try that out the gate.

With a high SKU Raptor Lake CPU, the problems with them is also a probably cause, since you went from one to another.

Besides that, rule number 1 when you have stability issues is set everything to stock. Namely, disable XMP if it is active before proceeding with testing.

I would also ensure the BIOS is updated (with whatever the "Intel default" is these days), and consider any updates to Windows, drivers, etc.
Last edited by Illusion of Progress; Aug 27, 2024 @ 4:52pm
Azza ☠ Aug 27, 2024 @ 7:44pm 
Can you boot into a Safe Mode (with Command Prompt)?

If so run the following commands under an admin command prompt:

sfc /scannow

(that will check your Windows critical files and attempt to repair them)

Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth

(that will update your OS image to the latest online version to check against and then run again)

sfc /scannow

You want the message: "Windows Resource Protection did not find any integrity violations" or "Windows Resource Protection found corrupt files and successfully repaired them"

What motherboard are you using? You might need to update/reinstall your motherboard drivers under the official website > support > drivers

Note that the crashing "Rpcrt4.dll" file is associated with the Remote Procedure Call program. If you are using a remote access app / software, uninstall it to check. If you aren't expecting any remote access connection, then scan for malware - with MalwareBytes, BitDefender or a free version of SpyBot.

Note that "Rpcrt4.dll" is for internet and networking connections, not just remote access, but also could be called for when Windows is searching for updates, etc. It's just ideal is ensure it's not some remote access malware attempt.

Another reason "Rpcrt4.dll" could commonly be crashing is the .NET framework usage. Check if you have installed any .NET framework lately, these sometimes are bundled with installing games/apps. Under Start > Settings > Programs and Features > look for "Microsoft .NET Framework". Either uninstall and download a new copy of the same version .NET to reinstall. Or use the .NET Framework Repair tool from Microsoft: https://www.microsoft.com/en-in/download/details.aspx?id=30135

You will likely find the audio cutting/hanging is just a side-effect of the actual crash.

Your Win 10 OS build appears to be stuck upon an older version (19041.4597) or hasn't fully updated yet? The latest version is 19045.4780.

After Start > Settings > Windows Update > Check for Updates / Install

Under your search/run box on the taskbar, to check type: winver

Are you on Version 22H2 / 19045.4780? There might just of been some updates pending.

If your Windows Update isn't working, try using the Windows Update Assistant > Update Now:
https://www.microsoft.com/en-us/software-download/windows10
Last edited by Azza ☠; Aug 27, 2024 @ 7:54pm
Atriox Aug 27, 2024 @ 10:25pm 
Originally posted by Illusion of Progress:
You mentioned in a reply to that Reddit post that you changed CPUs. Did this BSOD start after that change?

With that error, the first thing I'd be doing is testing the storage/Windows installation. Doing disks checks, running file checker, etc. Reinstalling Windows would be the "nuclear" option, but I'm not suggesting you need to try that out the gate.

With a high SKU Raptor Lake CPU, the problems with them is also a probably cause, since you went from one to another.

Besides that, rule number 1 when you have stability issues is set everything to stock. Namely, disable XMP if it is active before proceeding with testing.

I would also ensure the BIOS is updated (with whatever the "Intel default" is these days), and consider any updates to Windows, drivers, etc.
Started about 4 days after I changed CPU.

When I first installed it, I noticed that my audio driver wasn’t working so I reinstalled SteelseriesGG which fixed it. I’m wondering if it could be something related to that program being corrupt?

Right before the crash happened, the audio cut out whilst I was playing a game. Videos also wouldn’t load because it said that the audio driver wasn’t working, and then I got a BSOD.
Atriox Aug 27, 2024 @ 10:35pm 
Originally posted by Azza ☠:
Can you boot into a Safe Mode (with Command Prompt)?

If so run the following commands under an admin command prompt:

sfc /scannow

(that will check your Windows critical files and attempt to repair them)

Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth

(that will update your OS image to the latest online version to check against and then run again)

sfc /scannow

You want the message: "Windows Resource Protection did not find any integrity violations" or "Windows Resource Protection found corrupt files and successfully repaired them"

What motherboard are you using? You might need to update/reinstall your motherboard drivers under the official website > support > drivers

Note that the crashing "Rpcrt4.dll" file is associated with the Remote Procedure Call program. If you are using a remote access app / software, uninstall it to check. If you aren't expecting any remote access connection, then scan for malware - with MalwareBytes, BitDefender or a free version of SpyBot.

Note that "Rpcrt4.dll" is for internet and networking connections, not just remote access, but also could be called for when Windows is searching for updates, etc. It's just ideal is ensure it's not some remote access malware attempt.

Another reason "Rpcrt4.dll" could commonly be crashing is the .NET framework usage. Check if you have installed any .NET framework lately, these sometimes are bundled with installing games/apps. Under Start > Settings > Programs and Features > look for "Microsoft .NET Framework". Either uninstall and download a new copy of the same version .NET to reinstall. Or use the .NET Framework Repair tool from Microsoft: https://www.microsoft.com/en-in/download/details.aspx?id=30135

You will likely find the audio cutting/hanging is just a side-effect of the actual crash.

Your Win 10 OS build appears to be stuck upon an older version (19041.4597) or hasn't fully updated yet? The latest version is 19045.4780.

After Start > Settings > Windows Update > Check for Updates / Install

Under your search/run box on the taskbar, to check type: winver

Are you on Version 22H2 / 19045.4780? There might just of been some updates pending.

If your Windows Update isn't working, try using the Windows Update Assistant > Update Now:
https://www.microsoft.com/en-us/software-download/windows10
I tried sfc and DISM last night, but I don’t think they found anything to be wrong.

I’ll check for everything else tonight.

It’s worth me saying that before closing my computer off last night, both Intel and my Steelseries program wanted to do updates when I looked at windows update, and I installed both of those updates. I’m not sure if that could’ve fixed it yet because I haven’t been able to use the PC again since.

The Intel update was supposed to be related to graphics - I guess this is because I went from a 13900KF to a 13900K.
Atriox Aug 28, 2024 @ 5:16am 
I just did a sfc /scannow after doing the DISM last night and it didn't find anything.

I checked for windows updates but it says I'm up to date.

I tried looking for .NET Framework under that location but couldn't find anything.
skOsH♥ Aug 28, 2024 @ 5:25am 
Critical processes being interrupted is a surefire sign of an outdated BIOS

leave a BIOS and not updating it, over time, things like clicking on icons or launching programs not even working.

You can also check your hard disks for corrupted files

That's all I can think of right now. Perhaps there is also something that has been changed in the registry that is messing something up.

Or there could be a conflict with programs or drivers
Atriox Aug 28, 2024 @ 5:51am 
Originally posted by skOsH:
Critical processes being interrupted is a surefire sign of an outdated BIOS

leave a BIOS and not updating it, over time, things like clicking on icons or launching programs not even working.

You can also check your hard disks for corrupted files

That's all I can think of right now. Perhaps there is also something that has been changed in the registry that is messing something up.

Or there could be a conflict with programs or drivers
I think it’s possibly SteelseriesGG which caused it, because when I replaced the CPU in my computer the audio on my headset wouldn’t work.

I reinstalled GG which got it working again, but I guess something could’ve corrupted in the process.

I’ll try reinstalling it yet again and see if the issues go away, if not then I’ll update the BIOS.

I’ve been trying to hold off from doing that because people say the microcode patch is bricking some people’s motherboards.
skOsH♥ Aug 28, 2024 @ 6:45am 
Originally posted by Atriox:
Originally posted by skOsH:
Critical processes being interrupted is a surefire sign of an outdated BIOS

leave a BIOS and not updating it, over time, things like clicking on icons or launching programs not even working.

You can also check your hard disks for corrupted files

That's all I can think of right now. Perhaps there is also something that has been changed in the registry that is messing something up.

Or there could be a conflict with programs or drivers
I think it’s possibly SteelseriesGG which caused it, because when I replaced the CPU in my computer the audio on my headset wouldn’t work.

I reinstalled GG which got it working again, but I guess something could’ve corrupted in the process.

I’ll try reinstalling it yet again and see if the issues go away, if not then I’ll update the BIOS.

I’ve been trying to hold off from doing that because people say the microcode patch is bricking some people’s motherboards.

Oh yikes on that last part! Is there a stable version that is newer than the one you have right now but isnt the one with issues? I think my motherboard is on the 5th bios by now
Crashed Aug 28, 2024 @ 7:01am 
Originally posted by Atriox:
Originally posted by skOsH:
Critical processes being interrupted is a surefire sign of an outdated BIOS

leave a BIOS and not updating it, over time, things like clicking on icons or launching programs not even working.

You can also check your hard disks for corrupted files

That's all I can think of right now. Perhaps there is also something that has been changed in the registry that is messing something up.

Or there could be a conflict with programs or drivers
I think it’s possibly SteelseriesGG which caused it, because when I replaced the CPU in my computer the audio on my headset wouldn’t work.

I reinstalled GG which got it working again, but I guess something could’ve corrupted in the process.

I’ll try reinstalling it yet again and see if the issues go away, if not then I’ll update the BIOS.

I’ve been trying to hold off from doing that because people say the microcode patch is bricking some people’s motherboards.
I've only heard that from rumors. Did they perhaps not reset their BIOS to default when upgrading? Or they didn't wait a minute or so for the initial RAM testing and training?
r.linder Aug 28, 2024 @ 8:03am 
CRITICAL_PROCESS_DIED is just another one of those vague errors that appears when you have at least one of the following happen:

1) Faulty hardware or peripherals
2) Outdated or bad drivers
3) System infected with malware
4) System file corruption

So for troubleshooting based on what you've already tried:

1) Unplug all unnecessary devices from your system before and after boot
2) Run an anti-virus and/or malware scanners to check for malicious software
3) Try booting a completely fresh copy of Windows with only the drivers installed to see if the issue can be replicated, don't install anything like SteelSeriesGG until you want to see if it's the root cause

If all else fails then it might be possible that you have really bad luck and ended up with a bad 13900K that's just the source of precipitating issues
Last edited by r.linder; Aug 28, 2024 @ 8:05am
Atriox Aug 28, 2024 @ 8:47am 
Originally posted by skOsH:
Originally posted by Atriox:
I think it’s possibly SteelseriesGG which caused it, because when I replaced the CPU in my computer the audio on my headset wouldn’t work.

I reinstalled GG which got it working again, but I guess something could’ve corrupted in the process.

I’ll try reinstalling it yet again and see if the issues go away, if not then I’ll update the BIOS.

I’ve been trying to hold off from doing that because people say the microcode patch is bricking some people’s motherboards.

Oh yikes on that last part! Is there a stable version that is newer than the one you have right now but isnt the one with issues? I think my motherboard is on the 5th bios by now
Yeah I think there is. I'll look to update to that one instead if it does turn out to be caused by the BIOS - that's a good idea.
Azza ☠ Aug 28, 2024 @ 11:28am 
Updating the BIOS adds the default Intel CPU settings, as an option to pick rather than the motherboard's overclocked settings.

It should be marked as the Intel microcode 0x129 by now and by setting it as the default Intel CPU settings, improves the stability of Intel Core 13th and 14th gen CPUs.

1. Intel default settings to avoid elevated power delivery impact to the processor (May 2024)
2. Microcode 0x125 to fix the eTVB issue in i9 processors (June 2024)
3. Microcode 0x129 to address elevated voltages (August 2024)

It's the elevated voltages given my some motherboards to the CPU causing most of the issue. The latest microcode update (0x129) will limit voltage requests above 1.55V. This will give you the normal standard speed out of your CPU with stability, just slightly slower than an unstable and possibly damaging overclocked speed from the motherboard (depending on the motherboard brand).

You want that version (Microcode 0x129) and to set the default CPU settings. You can pick and toggle between them however anyways, so it doesn't actually force it upon you. It's the BETA versions before that you might of wished to avoid (they slowed it down more, but wasn't really addressing the real root cause of instability). Just note you need to update the Intel ME as well, if it's not already included and pushed in the BIOS update too.

NOTE: From the date you had purchased the Intel 13th or 14th Gen CPU, you have an extension on it's warranty from Intel of an additional 2 years (so 5 years in total now, you can claim on it), if it ever does come down to that, it's still under Intel's warranty. However, you are getting a different error message.
Last edited by Azza ☠; Aug 28, 2024 @ 11:36am
Atriox Aug 28, 2024 @ 12:08pm 
Originally posted by Azza ☠:
Updating the BIOS adds the default Intel CPU settings, as an option to pick rather than the motherboard's overclocked settings.

It should be marked as the Intel microcode 0x129 by now and by setting it as the default Intel CPU settings, improves the stability of Intel Core 13th and 14th gen CPUs.

1. Intel default settings to avoid elevated power delivery impact to the processor (May 2024)
2. Microcode 0x125 to fix the eTVB issue in i9 processors (June 2024)
3. Microcode 0x129 to address elevated voltages (August 2024)

It's the elevated voltages given my some motherboards to the CPU causing most of the issue. The latest microcode update (0x129) will limit voltage requests above 1.55V. This will give you the normal standard speed out of your CPU with stability, just slightly slower than an unstable and possibly damaging overclocked speed from the motherboard (depending on the motherboard brand).

You want that version (Microcode 0x129) and to set the default CPU settings. You can pick and toggle between them however anyways, so it doesn't actually force it upon you. It's the BETA versions before that you might of wished to avoid (they slowed it down more, but wasn't really addressing the real root cause of instability). Just note you need to update the Intel ME as well, if it's not already included and pushed in the BIOS update too.

NOTE: From the date you had purchased the Intel 13th or 14th Gen CPU, you have an extension on it's warranty from Intel of an additional 2 years (so 5 years in total now, you can claim on it), if it ever does come down to that, it's still under Intel's warranty. However, you are getting a different error message.
Luckily on my z790 maximus hero bios I am able to already disable ASUS Multi-Core enhancement which stops the main issue. If these BSOD crashes continue even after the fixes I have already tried, I will update the BIOS to rule that out.
Elucidator Aug 28, 2024 @ 12:12pm 
Originally posted by Atriox:
https://www.reddit.com/r/pcmasterrace/comments/1f2s3ee/critical_process_died_bsod_error/
It's an error when running multithreated tasks, concerning the clock. It's directly related to the CPU and its driver.

Start windows in savemode, remove the driver completely and reinstall the cpu driver
Atriox Aug 28, 2024 @ 12:15pm 
Originally posted by Elucidator:
Originally posted by Atriox:
https://www.reddit.com/r/pcmasterrace/comments/1f2s3ee/critical_process_died_bsod_error/
It's an error when running multithreated tasks, concerning the clock. It's directly related to the CPU and its driver.

Start windows in savemode, remove the driver completely and reinstall the cpu driver
I think that may have already happened thanks to windows recommending a cpu update? When I checked last night after the BSOD, it asked for an Intel CPU graphics update. Do you think that might have fixed it already?

Also if not, how do I uninstall the CPU driver and which specific driver is it?

Thanks.
< >
Showing 1-15 of 19 comments
Per page: 1530 50

Date Posted: Aug 27, 2024 @ 2:05pm
Posts: 19