Functions are accessed unpredictably and only in part.
Functions are accessed unpredictably and only in part.
I reviewed it again and confirmed I experienced the issue multiple times daily, typically every 3 to 5 days. After the BIOS update on January 20th, my logs showed no further WHEA PCIE errors in the past 20 days. For prevention, I swapped my GPU slot and plan to try War Thunder soon. The game seems to trigger the error at times, though it usually resolves after a few hours. My storage setup includes one Crucial 1TB M.2 drive with the OS installed, plus two SanDisk 1TB SSDs. It might be related to Windows or read/write operations. When the system crashes, I can still use Windows features like CTRL-ALT-DEL, close open apps (except Firefox which loses its state), and Discord continues receiving audio. However, when I interact with Task Manager, metrics freeze completely while performance stays at 100%. If the crash recurs, I’ll record a video. I’m also noticing repeated spikes of this error—eight times in a row—especially during startup and shutdown. The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} failed to register with DCOM within the expected time, along with application-specific permission issues on my machine.
The issue persists. I reviewed a lecture video on Windows Media Player and it became unresponsive at some point. I shared a recording here: https://drive.google.com/file/d/1PV07ukn...sp=sharing. After rebooting the computer, it automatically applied a Windows update. Before the shutdown, the Event Manager logged 1.5 hours prior to the crash—a timezone verification and some problems updating the timezone were noted. The 'VMICTimeProvider' reported that its hardware and environment weren't supported, which is typical for non-HyperV guest setups. This might be the standard behavior for this provider in similar configurations. The NtpClient service is now aligning system time with the source at time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->40.119.148.38:123). The time service is synchronizing with that source using reference ID 647264040. The current local stratum is 4, and the time zone data was refreshed successfully. The bias is -60, and the system time updated to 2022-02-11T11:18:10.403476000Z. The change reason points to an application or component altering the clock. Process details indicate 'svchost.exe' was involved, followed by permission issues for a specific COM server. This setting can be adjusted via Component Services. This was the final log entry before I initiated a shutdown 1.5 hours ago.
To wrap up this discussion, I realized the (appearing) fix happened naturally. The performance drops diminished on their own over time. They remained active until about nine months ago when I upgraded my graphics card. After that, those freezing issues disappeared permanently and haven’t come back. It might have been a Windows update, a driver fix, or an isolated problem tied to the previous hardware. I’m hoping this helps someone else. Thread closed. Problem resolved.