Signal drops during specific games, causing shutdowns. Requires force restart to resolve.
Signal drops during specific games, causing shutdowns. Requires force restart to resolve.
Executed the commands and received a repair message. Corrupted files detected and fixed. Online fixes are documented in the CBS log at windir\Logs\CBS\CBS.log. Offline repairs use the provided log file. I can share the CBS.log if needed. Will attempt to run Apex again to check for signal loss.
It shows improvement since the corrupt files were fixed. You don’t have to include the CBS log—what’s resolved is resolved. Consider reinstalling the nVidia drivers now. The installation process should no longer be blocked by issues with the operating system. If that doesn’t help, we’ll examine your Event Viewer log. I’ll guide you through that if driver reinstallation fails.
Reinstalled and attempted once more to check for the problem.
Review the logs in Event Viewer at Mavendow for any errors or warnings.
Launch the Event Viewer, go to Administrative Events, choose the relevant entry and upload the file as requested.
Included. Problems without internet occurred when removing the Ethernet during driver removal or reinstall. administrativeevents.evtx
01 AM the WHEA Logger logged an error code PCI\VEN_8086&DEV_4C01&SUBSYS_50001458&REV_01, which quickly followed by a crash in the nVidia driver. The operating system did issue a TDR (I mistakenly thought there was no TDR), and the driver managed to recover, suggesting the driver wasn’t at fault. As a result, KERNELBASE.DLL experienced crashes, and the system tried to fix it four times, but each time it hit permission issues from PerAppRuntimeBroker.
What I noted earlier is that DWM reported problems shortly after KERNELBASE.DLL, indicating DWM might be responsible for the crash. In reality, neither DWM nor the nVidia driver seems to be the cause. The root reason appears to be a hardware issue—specifically the PCI\VEN_8086&DEV_4C01 slot on the motherboard, which is likely the GPU card. This narrows it down to two possibilities: faulty Intel firmware or a genuine hardware fault in the motherboard/GPU.
If the latter was the case, the error would appear across all applications, not just a few. I suspect the earlier OS fix may have affected the Intel firmware as well. Regarding your nVidia installation, it’s showing errors during setup, and multiple accounts are being denied access to several DCOM apps. This could be the origin of the OS corruption we previously resolved, since DCOM plays a role in driver and firmware loading.
We’ll address those permissions issues by using a script that only works on your machine. Follow these steps: Extract C:\Downloads\DCOM.zip, right-click RunMe.cmd and select Run As Administrator. The output should display green text only—any red indicates a problem. Capture the red messages for review.
Second, download the utility from Intel’s site: https://www.intel.com/content/www/us/en/...kw=chipset inf utility. Save it to your computer (e.g., C:\Downloads). Open a command prompt as admin and run: setupchipset -OVERALL. This overwrites all chipset files, even if newer versions exist. Windows Update will handle any downgrades within hours. Reboot the PC after completion—this step is crucial.
Don’t delay; rebooting is necessary because chipset installation often requires it. I’ve tried this before and encountered numerous errors until a reboot resolved them.
Finally, EasyAntiCheat keeps crashing every five minutes. A session named "dc3a3596-71e1-45a3-b2ea-39ad5322fe51" failed to start with error code 0xC0000022. The GPU crashes seem unrelated to the EAC crash, which may cause in-game stuttering. I’m unsure how to fix this without interfering with kernel-level anti-cheat software.
If these steps help, please remove your AdministrativeEvents.evtx attachment for privacy.
You should proceed with the remaining steps. The initial output indicates the script functioned correctly, but you may want to verify its behavior further.