System encountered file system issue (-1073740791) and unusual actions.
System encountered file system issue (-1073740791) and unusual actions.
Hello, you're using Windows 11 with a Ryzen 5600X, a 1TB Samsung 980 NVMe, and the MSI MPG B550 GAMING EDGE motherboard, paired with a 3070 GPU. This is the third instance this has occurred, roughly every five months or so, where a clean Windows 11 install resolves it. After leaving your PC idle for a few hours, you encounter a "file system error (-1073740791)" when trying to run as administrator. Continuing to use the machine leads to increasingly strange behavior—graphic issues or Explorer becoming unresponsive. While the PC is asleep, the monitor appears to flicker briefly. When attempting admin tasks and checking Event Viewer, this error keeps appearing: Faulting application name: consent.exe, version 10.0.22621.2070, timestamp 0x659cfa02; Faulting module name: Windows.UI.XamlHost.dll, version 10.0.22621.608, timestamp 0x6d3357a5; Exception code 0xc0000409, fault offset 0x0000000000005b63, process ID 0x0x56E0, application path C:\Windows\system32\consent.exe, module path C:\Windows\System32\Windows.UI.XamlHost.dll, Report ID 874ccc5b-3a7d-4b78-be97-8bf0eb9321c7, Faulting package. Suggestions: I attempted 'sfc /scannow' without issues, ran DISM and DSIM commands without success, performed two memtest86 runs with no RAM errors, and the SSD reports 95% usage. Only recent changes—like a registry tweak setting working hours from 8am to 8pm—have helped. Any advice on further checks or replacements? I’ve invested time and effort, and I don’t want another full reinstall in about five months. Appreciate your help!
Thank you for your message. Here are some alternative steps you could try:
- Check if your graphics drivers are up to date.
- Adjust display calibration settings manually.
- Test with a different monitor or input device.
- Ensure your system meets the minimum requirements for the game or app.
If these don’t help, let me know more details about the issue!
The issue persists even when MPO is disabled. Setting the screen to stay on continuously, along with the existing sleep settings, seems to resolve the problem. This suggests the root cause might lie elsewhere.