Question Exception code: 0xc0000005 - Constant Program/Installer Crashes

Toggle sidebar Toggle sidebar
TheBigCheeselol

TheBigCheeselol

Jul 23, 2023
8
0
10
I put together a mostly new system back in Dec 2022. I use it to connect remotely for work and do a lot of gaming in my free time. I noticed back in January that programs would occasionally crash but as it was infrequent enough (1-2 times per week) that I made nothing of it. The crashes started increasing to the point where the computer was no longer useable as a gaming PC (WoW would crash 6+ times in a 1 hour session, discord can't be open for longer than 5 mins w.o crashing) so I decided to do a full Windows 11 reset and clean up all files using the reset pc feature about 4 weeks ago.

This is where the bigger issues began. After the fresh install, I struggled to even get my drivers to install. The installers would either not pop up, crash during installation or just freeze entirely. After hours of rebooting, trying again, using motherboard manufacturer tools (Asus Armoury Crate etc) and 3rd part driver installers (Drivereasy) I was able to get all my drivers installed. Installing programs was just as difficult - chrome took 3+ attempts, geforce experience took 3+ attempts, discord can't install period and when I do get anything to install, it still crashes constantly. Chrome and games (WoW, Hearthstone, League) crashes all show Exception code: 0xc0000005 in the event viewer. I've been trying to troubleshoot it for a few months now but am genuinely out of ideas.

My troubleshooting steps and other notes:
- No blue sceens
- Replaced my 2x16GB G.Skill Ripjaws V DDR4-3600 CL16 with 2x16GB Corsair Vengeance LPX DDR4 3600 C18
- Tried both sets of RAM with XMP on and off
- Replaced my Samsung 980 PRO 1TB with a Samsung 990 PRO 2TB
- Updated firmware on 980 PRO, 990 PRO was already up to date
- Flashed the BIOS to the most recent version
- Memory diagnostic tool on both RAM sets, both came back clean
- Offline virus scan, came back clean
- SFC scan, clean
- CHKDSK scan, clean
- Reinstalled Windows 11 using the Windows tool on my 860 EVO, 980PRO, 990PRO only ever had 1 plugged in at a time. Same driver/other program installation issues.
- Reinstalled Windows 10 from a bootable flash drive that I had my friend make for me on all 3 drives, one at time. All experienced the same issues still.
- Replaced the mobo from ASUS TUF GAMING Z690-PLUS WIFI D4 to MSI PRO A690-A DDR4, reinstalled Windows 10 from the flash drive, drivers had issues installing, flashed BIOS to vers. 7D25v1D, still experiencing issues.

Current system:
CPU: 13th Gen Intel Core i9-13900K 3.00 GHz
CPU cooler: Corsair iCUE H150i ELITE CAPPELIX XT
Motherboard: MSI PRO Z690-A DDR4, BIOS vers. 7D25v1D
Ram: 2x16GB Corsair Vengeance LPX DDR4 3600 C18
SSD/HDD: Samsung 990 PRO 2TB
GPU: Gigabyte AORUS GeForce RTX 4090 XTREME WATERFORCE 24G
PSU: Corsair RMe Series RM1000e Fully Modular 80PLUS Gold ATX (7 months old)
Chassis: Fractal Design Meshify S2 Black ATX
OS: Windows 10 Pro
Monitor 1: Dell S2716DG
Monitor 2: Gigabyte G24F 2
Monitor 3: Dell E2020H

Extra parts from swapping pieces in and out:
CPU cooler: Lian Li GALAHAD 360 ARGB WHITE
Motherboard: ASUS TUF GAMING Z690-PLUS WIFI D4 BIOS vers. 2602
Ram: 2x16GB G.Skill Ripjaws V DDR4-3600 CL16
SSD 1: Samsung 980 PRO 1TB
SSD 2: Samsung 860 EVO 1TB

Hoping someone can help out, thanks.
 
Do not use any third party installers.

Manually download all drivers directly from the applicable manufacturer's website. [Verify that the website is the real manufacturer's website. Just because the manufacturer's name may appear in the URL that does not mean that the site is really the manufacturer.]

Download, install, and configure all drivers as necessary.

= = = =

You mentioned Event Viewer - that is one tool.

Take a look in Reliability History/Monitor. Much more user friendly and the timeline format may reveal some pattern.

Look for error codes, warnings, or informational events that are captured just before or at the time of the crashes.

Any given entry can be clicked for more details. The details may or may not be helpful.

= = = =

Scale back to as basic a configuration as possible. "Basic" meaning no crashes. E.g. one monitor, one drive.

Then observe system performance using Task Manager, Resource Monitor, and Process Explorer. Use all three tools but again - only one tool at time.

Gradually add back components etc. and watch for what changes when the crashes start re-occuring.

Take your time, be methodical. Change only one thing at time.
 
Ralston18 said:
Do not use any third party installers.

Manually download all drivers directly from the applicable manufacturer's website. [Verify that the website is the real manufacturer's website. Just because the manufacturer's name may appear in the URL that does not mean that the site is really the manufacturer.]

Download, install, and configure all drivers as necessary.

= = = =

You mentioned Event Viewer - that is one tool.

Take a look in Reliability History/Monitor. Much more user friendly and the timeline format may reveal some pattern.

Look for error codes, warnings, or informational events that are captured just before or at the time of the crashes.

Any given entry can be clicked for more details. The details may or may not be helpful.

= = = =

Scale back to as basic a configuration as possible. "Basic" meaning no crashes. E.g. one monitor, one drive.

Then observe system performance using Task Manager, Resource Monitor, and Process Explorer. Use all three tools but again - only one tool at time.

Gradually add back components etc. and watch for what changes when the crashes start re-occuring.

Take your time, be methodical. Change only one thing at time.
Click to expand...
Thanks for the reply!

Point 1 - I always default to installing the drivers from the manufacturer's website however this is the first time I've seen the drivers just not install. I'll download the driver, extract, run and nothing will happen. What do I do at this point? Just restart and try again? I am going to reinstall the OS in a basic setup and see what the reliability monitor says.

Point 2 - Appreciate you letting me know about Reliability History. I'll use it to try and get some more information. It mostly looks normal - all the informational events are successful installs and the 3 warnings were failed windows updates on the first boot that reinstalled (and show up in informational events after the first reboot. The critical events are all games crashing with the same error code. At the top there are the two critical events of my attempt at installing the chipset driver alone, and then 5 critical events of the MSI tool trying to do the same thing but it looks like it got successfully installed at 12:14PM.

BJGd7Nb.png


LBNG7vE.png


What I find weird is I can't identify the chipset driver in the device manager:

HGwcyaN.png


Point 3 - I have never been able to get back to a crashless state. I am going to try reinstalling the OS from scratch with only one drive, with the onboard graphics and one monitor, one ram stick with XMP off and then slowly rotate RAM sticks/drives but if none of that works I am at a loss of where to go from there.

I'll post the results here during my next few installs.
 
Take a look at what all is going on via Process Explorer (Microsoft, free).

FYI:

https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

Any references to Terminal Server?

FYI:

https://learn.microsoft.com/en-us/t...erminal-server-startup-connection-application

Noted that you ran sfc ("sfc /scannow"). Did you try "dism"?

Look at Process Explorer before reinstalling the OS. Take some screenshots for future reference.

Consider that some game or other app may have slipped in something else that is now running in the background. Possibly buggy or corrupt.

RAM: doublecheck the motherboard's User Guide/Manual. Some motherboards require that the first physically installed RAM be placed in a specific slot.

Objective being to obtain as much information as possible before the reinstall if it comes to that.

Once the reinstall is completed you will be able to compare "before" and "after".
 
Ralston18 said:
Take a look at what all is going on via Process Explorer (Microsoft, free).

FYI:

https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

Any references to Terminal Server?

FYI:

https://learn.microsoft.com/en-us/t...erminal-server-startup-connection-application

Noted that you ran sfc ("sfc /scannow"). Did you try "dism"?

Look at Process Explorer before reinstalling the OS. Take some screenshots for future reference.

Consider that some game or other app may have slipped in something else that is now running in the background. Possibly buggy or corrupt.

RAM: doublecheck the motherboard's User Guide/Manual. Some motherboards require that the first physically installed RAM be placed in a specific slot.

Objective being to obtain as much information as possible before the reinstall if it comes to that.

Once the reinstall is completed you will be able to compare "before" and "after".
Click to expand...
Wish I saw this before I opted for the reinstall. Currently stuck in the same place as all the other installs, the chipset driver won't do anything when I run the application.

PRO Z690-A DDR4

PRO series motherboards, tuned for better performance by Core Boost, Memory Boost, Extended Heatsink Design, M.2 Shield Frozr, USB 3.2 Gen 2x2, Lightning Gen5, Front Type-C, 2.5G LAN
www.msi.com www.msi.com
Win10 64 -> System & Chipset Drivers -> Intel Chipset Driver

Got the LAN driver from here and it worked fine.

This is where I would opt to use MCI Center or ASUS Amoury Crate to get the remaining drivers to install. What's the best way to proceed from here?

I'm running process explorer right now and don't see any references to Terminal Server. I read over the Terminal Server article though I didn't understand most of it.

I did run sfc but have not tried dism. Reading over the article now and I'll give it a try.

Both boards manuals said the RAM needs to be installed in slots 2 and 4 for dual which is where I had them placed.
 
"This is where I would opt to use MCI Center or ASUS Amoury Crate to get the remaining drivers to install. What's the best way to proceed from here?"

Neither. Do all driver installations yourself. MSI may be buggy or corrupted. Uninstall if possible.

RAM: Slots 2 & 4. Okay provided the User Guide/Manual does not specifically state that one specific slot must be the first.
 
DISM check health and DISM scan health said everything was fine.

Ralston18 said:
"This is where I would opt to use MCI Center or ASUS Amoury Crate to get the remaining drivers to install. What's the best way to proceed from here?"

Neither. Do all driver installations yourself. MSI may be buggy or corrupted. Uninstall if possible.

RAM: Slots 2 & 4. Okay provided the User Guide/Manual does not specifically state that one specific slot must be the first.
Click to expand...
I can't get the driver to install. The chipset driver installer won't open after I run the application. I've tried restarting pc, running as admin and redownloading the driver.

The manual recommends DIMMA2 before DIMMB2 which is what I've been doing though I currently only have DIMMA2 slotted.

Edit: I don't have MSI installed at all right now.
 
Finally got an error to show for the chipset installer:

Source
Intel(R) Chipset Device Software

Summary
Stopped working

Date
‎7/‎23/‎2023 6:05 PM

Status
Report sent

Description
Faulting Application Path: C:\Windows\Temp\{095A423A-7A39-4CDD-9C67-7FB6388B08DE}\.cr\SetupChipset.exe

Problem signature
Problem Event Name: CLR20r3
Problem Signature 01: SetupChipset.exe
Problem Signature 02: 10.1.19199.8340
Problem Signature 03: 5fd0094e
Problem Signature 04: System
Problem Signature 05: 4.8.9166.0
Problem Signature 06: 64531ac9
Problem Signature 07: 3f3f
Problem Signature 08: 14e
Problem Signature 09: System.TypeInitialization
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 2beb
Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46
Additional Information 3: 0f5f
Additional Information 4: 0f5f347ec91b2c234974086c81e5c6fb

Extra information about the problem
Bucket ID: 256bd8493dfaecbcd0fa3da366aa0752 (1223358020795893586)

Not sure if this means anything.
 
I get no prompts from the installer or application, literally nothing happens after I run the SetupChipset application and press yes on the prompt.

I posted the only error that shows in the Reliability Monitor above.
 
Last edited:
Update: Even though my userbenchmarks and Intel XTU benchmarks were coming back fine I decided to run Cinebench R23. Single core came back perfect but as soon as I ran the multi-core bench it would crash, tried 2 or 3 times with no luck. Looking through the log it was giving me the same exception code (0xc0000005) as all my other program crashes which made me think .. are the programs only crashing when they attempt to use multiple cores in some way?

After some research I came accross these two threads:

Reddit - Dive into anything

www.reddit.com www.reddit.com

Reddit - Dive into anything

www.reddit.com www.reddit.com

Looks like after the Windows 22H2 Update a ton of people are having the same errors with high end intel chips, most noteably the 13900K and everyone's problem gets resolved after disabling Intel Turbo Boost in the BIOS.

I turned mine off as well and now the system is stable. On the one hand I want to rma my chip but on the other hand so many people are having this issue that I wonder is it's just another lottery.

Unfortunately now the package TDP doesn't exceed 50W and max core frequence won't go over 3.00GHz which entirely defeats the purpose of this chip. After work I'm going to test lowering the ratio multiplier on the P-cores and turning back on Intel Turbo Boost and see if I can get it to stabalize somewhere.

Wondering if anyone had any thoughts on this topic as a whole.

Thanks
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom