Problem with Windows explorer.exe during a bad restart
Problem with Windows explorer.exe during a bad restart
I was experiencing issues with an Xbox Game Pass and EA Sports game crashing. I attempted a reboot and the computer would freeze. Then I forced a reboot by cutting power, but a strange Bing Co-Pilot would appear on the taskbar. Now frequently, after shutting down or restarting, I encounter:
"Explorer.exe application error: the instruction at <memory address> referenced memory at <memory address> could not be written."
I've tried various fixes with different approaches, but the problem persists, especially when using Microsoft apps or games. It sometimes appears randomly during restarts.
I'm really hoping you can help me resolve this.
Full system specifications? Please include the brand and model of the PSU.
Malware scan results? Check the system for any threats.
What is the DNS server address?
PSU: TUF GAMING 750 W GOLD
Processor: AMD Ryzen 5 5600X3D 6-Core Processor, 3301 Mhz, 6 Core(s), 12 Logical Processor(s)
MPG B550 GAMING PLUS (MS-7C56)
Installed RAM: 32.0 GB
Total RAM: 31.9 GB
64-bit OS, x64 architecture
Windows 11
I ran these two steps and also a few times I have run sfc /scannow as many have suggested. I thought everything was fine, it shutdown and rebooted successfully without the error message.
Just now I rebooted and I got another of the error messages, so I am really not sure what is causing this.
I thought that those gaming apps crashing was responsible for the problem, and maybe it was, but now I am getting this error message seemingly at random.
What do you suggest? Do you think a windows restore would be helpful?
Microsoft recommends turning off "fast startup" or adjusting virtual memory settings, but these actions might not solve the actual problem.
I am not sure the answer to your questions, but this is a brand new computer, I can give you more specs, but this is just a Windows 11 issue, right?
I understand that Fast Startup could contribute to the issue, but does disabling it actually fix the memory issue, or just mask the problem? If I turned on Fast Startup again, would the problem just come back?
It appears that turning off Fast Startup doesn't even have anu effect on restarting, just powering on after shutdown, so I don't see how that helps anyhow since I'm getting the error on restarts.
Do you have any theories about why a bad shutdown would cause this particular error? And why does it happen seemingly at random?
Thank you for your help.
Just letting you know:
I attempted a System Restore from a restore point roughly three weeks ago, and it reported success, though the machine would not restart and became stuck in a loop. It tried Automatic Repair, but couldn't fix it; I selected 2/16 as a restore point, and that resolved the issue.
Is this suggesting there was an underlying problem?