Overheating components, erratic performance, AIO/RGB issues
Overheating components, erratic performance, AIO/RGB issues
Current logs show no specific details—just generic Windows events. We need to focus on the moments right before a shutdown, such as power loss indicators.
These initial two events appear distinct because they happened simultaneously and the error message relates to a dump file. Most other significant incidents over the past few days involved a "the computer has rebooted from a bugcheck" message roughly ten minutes earlier. Apart from the major power-off event that came before a bugcheck alert, there aren't many notable patterns. Besides the Malwarebytes-related issues and several warnings scattered, I recorded three distinct errors on 5/24.
There are several issues reported. System stability seems unaffected by dcom errors. Bug check problems likely stem from memory or storage issues. A volmgr error points to similar root causes. The Corsair icon service crash suggests RAM or SSD problems. Symptoms align with RAM concerns. Multiple factors are occurring, making it hard to pinpoint a single cause.
I’ve reviewed the critical incidents and mistakes, but nothing particularly noticeable has emerged. Even after lowering my RAM to the default, the problems persist. Recently, I attempted to play Hell Let Loose, which had previously worked, but after several failed launches it froze the whole system and required holding the power button. After restarting, it loads to the main menu but crashes immediately when I start a game. Here are the entries from the event viewer. I hope this provides some clarity? I’ve checked the nvwgf2umx.dll error in the viewer and tried various fixes, but nothing helped.
This graphics card issue appears to be linked to a crash. There seems to be a Windows component problem triggering the event viewer alert. Follow these steps:
1. Visit the provided guide: https://appuals.com/audit-events-have-be...transport/
2. Launch an elevated command prompt by searching for 'cmd' and opening it via shift + control + enter or right-click and select 'Run as administrator'.
3. Execute the following commands:
- sfc /scannow
- DISM /Online /Cleanup-Image /RestoreHealth
4. Download DDU, boot Windows in safe mode, then uninstall graphics drivers using DDU. Restart and reinstall.
If this resolves the matter, the problem might stem from hardware factors such as high CPU temperatures. Consider adjusting the CPU voltage settings in BIOS to a maximum of 1.25V for a slight performance reduction but lower temperatures.
I've already attempted steps 2 through 4 multiple times, but I'm proceeding with step 1 in sequence. Also worth mentioning is that Hell Let Loose and Predecessor don't function on the stock RAM profile, whereas they do with the XMP profile two. Essentially, "working" means I can run them for a short period before crashes happen, rather than being completely unable to play. I'm uncertain about the importance of this, but it might be useful to understand. I'll follow up tomorrow regarding the results of running all steps together!
Your RAM operates at a higher voltage when using XMP settings. If it exceeds the standard voltage, adjust it manually but keep the automatic timing and speed settings. This should improve stability, though it’s unusual and suggests a potential hardware issue.
This system has quite a few odd behaviors at first. It turned out the opposite of what I expected—it was actually an issue with my RAM settings. I had to turn off XMP because it was making games crash, not realizing it was linked to my old GPU. It seems the problem switched over time, so now XMP works better with my RAM. Have you encountered this before? What might have triggered it? I’ll test the voltage tomorrow when I go through more steps, but it’s getting late for me. Probably worth sending the RAM back to Corsair for replacement, just like with my AIO, which should arrive soon.