InquiryError code: 0xc0000005 - Persistent Application/Installer Failures
InquiryError code: 0xc0000005 - Persistent Application/Installer Failures
I assembled a largely new system in December 2022. I utilize it for remote work and engage in a significant amount of gaming during my leisure time. I observed in January that applications would sporadically crash, but since it occurred infrequently (1-2 times weekly), I did not think much of it. The crashes escalated to the extent that the computer became unusable for gaming (WoW would crash 6+ times within a 1-hour session, Discord can't remain open for more than 5 minutes without crashing) so I opted for a complete Windows 11 reset and cleaned all files using the reset PC feature around 4 weeks ago.
This is when the more serious issues emerged. After the fresh installation, I struggled to even get my drivers installed. The installers would either not appear, crash during installation, or freeze completely. After hours of rebooting, attempting again, using motherboard manufacturer tools (Asus Armoury Crate etc.) and third-party driver installers (Drivereasy), I managed to get all my drivers installed. Installing applications was equally challenging - Chrome required 3+ attempts, GeForce Experience needed 3+ attempts, Discord cannot install at all, and whenever I manage to get something to install, it still crashes repeatedly. Chrome and games (WoW, Hearthstone, League) crashes all display Exception code: 0xc0000005 in the event viewer. I've been attempting to troubleshoot for a few months now but am genuinely out of solutions.
My troubleshooting steps and additional notes:
- No blue screens
- 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 current
- Flashed the BIOS to the latest version
- Memory diagnostic tool on both RAM sets, both returned 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 were only ever connected one at a time. Same driver/other application installation problems.
- Reinstalled Windows 10 from a bootable flash drive that my friend created for me on all 3 drives, one at a time. All faced the same issues still.
- Replaced the motherboard 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 version 7D25v1D, still encountering 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 version 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 components from swapping pieces in and out:
CPU cooler: Lian Li GALAHAD 360 ARGB WHITE
Motherboard: ASUS TUF GAMING Z690-PLUS WIFI D4 BIOS version 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 assist, thank you.
Avoid using any third-party installers.
Download all drivers manually directly from the relevant manufacturer's website. [Ensure that the website is the authentic manufacturer's site. Just because the manufacturer's name might appear in the URL does not guarantee that the site is truly the manufacturer.]
Download, install, and configure all drivers as necessary.
= = = =
You mentioned Event Viewer - that is one tool.
Check Reliability History/Monitor. Much more user-friendly and the timeline format may uncover some patterns.
Look for error codes, warnings, or informational events that are documented just before or at the time of the crashes.
Any entry can be clicked for more details. The details may or may not be useful.
= = = =
Reduce to the simplest configuration possible. "Basic" means 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 a time.
Gradually reintroduce components etc. and monitor for what changes when the crashes begin to recur.
Take your time, be methodical. Change only one element at a time.
Thank you for your response!
Point 1 - I always default to installing the drivers from the manufacturer's website; however, this is the first time I've encountered drivers that simply do not install. I'll download the driver, extract it, run it, and nothing occurs. What should I do at this point? Just restart and try again? I plan to reinstall the OS in a basic setup and see what the reliability monitor reveals.
Point 2 - I appreciate you informing me about Reliability History. I will use it to gather more information. It generally appears normal - all the informational events are successful installations, and the 3 warnings were failed Windows updates on the initial 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 two critical events from my attempt at installing the chipset driver alone, followed by 5 critical events of the MSI tool trying to do the same thing, but it seems that it was successfully installed at 12:14 PM.
What I find strange is that I cannot identify the chipset driver in the device manager:
Point 3 - I have never been able to return to a crash-free state. I am going to attempt a fresh OS installation with only one drive, using the onboard graphics, one monitor, and a single RAM stick with XMP off, and then gradually switch RAM sticks/drives, but if none of that works, I am uncertain where to proceed from there.
I will share the results here during my subsequent installations.
Investigate what all is happening via Process Explorer (Microsoft, free).
For your information:
https://learn.microsoft.com/en-us/sysint...s-explorer
Any references to Terminal Server?
For your information:
https://learn.microsoft.com/en-us/t...er...pplication
Noted that you executed sfc ("sfc /scannow"). Did you try "dism"?
Examine Process Explorer prior to reinstalling the OS. Capture some screenshots for future reference.
Consider that some game or other application may have introduced something else that is now operating in the background. Possibly buggy or corrupt.
RAM: double-check the motherboard's User Guide/Manual. Some motherboards require that the first physically installed RAM be placed in a specific slot.
The objective is to gather 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".
I wish I had seen this before I chose to reinstall. Currently stuck in the same situation as all the other installations, the chipset driver fails to do anything when I execute the application.
PRO Z690-A DDR4
PRO series motherboards, optimized for superior 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
Win10 64 -> System & Chipset Drivers -> Intel Chipset Driver
Obtained the LAN driver from here, and it functioned fine.
Here is where I would prefer to use MCI Center or ASUS Armoury Crate to get the remaining drivers to install. What is the optimal way to proceed from here?
I am currently running Process Explorer and do not see any references to Terminal Server. I reviewed the Terminal Server article, but I did not comprehend most of it.
I did execute sfc but have not tried dism. I am reviewing the article now and will give it a shot.
Both boards' manuals indicated that the RAM should be installed in slots 2 and 4 for dual-channel, which is where I had them placed.
"This is where I would prefer to use MCI Center or ASUS Armoury Crate to get the remaining drivers installed. What is the optimal way to proceed from here?"
Neither. Perform 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 particular slot must be the first.
DISM check health and DISM scan health indicated everything was fine.
I cannot get the driver to install. The chipset driver installer won't open after I run the application. I've attempted restarting the PC, running as administrator, and redownloading the driver.
The manual suggests DIMMA2 before DIMMB2, which is what I've been doing, though I currently only have DIMMA2 installed.
Edit: I do not have MSI installed at all right now.
Finally managed to get an error to display for the chipset installer:
Source
Intel® 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 holds any significance.
This exception code?
https://learn.microsoft.com/en-us/a...pp...ectly-(0xc
I receive no prompts from the installer or application; literally nothing occurs after I execute the SetupChipset application and confirm on the prompt.
I posted the only error that appears in the Reliability Monitor above.