Need to do my earlier post since it won’t let me respond.
I am unable to play WoW from my home network (wifi or LAN). Other computers on home network can connect without issue to WoW.
All other online games, internet, youtube, etc works without issue. I go to log into wow and it takes forever to either maybe get to the char select screen where I try and log to a character there only to give me a WOW51900319 error or BLIZ51901016 error.
I’ve done every trouble shooting step I could find so far but have yet to fix this issue. I’ve also reinstalled Windows and WoW, ran WoW with and without addons and still am not able to play. I also made sure my drivers were update as well.
I have no issue connecting to WoW from my hotspot on my phone, or from other networks when I traveled for work this week.
A few memory leaks, check your sticks. Not sure if you added a 8 gig stick, amazon shows the laptop comes with 8Gb.
Event Name: RADAR_PRE_LEAK_64
On events 0-4
MacAfee, seeing a few update errors, mentions it is also not connecting.
Also Windows Updater might be having connection issues.
Spoilers provided by Gemini.
You have a variety of errors reported, which can be categorized as follows:
Memory Leaks (RADAR_PRE_LEAK_64): WER0, WER1, WER2, WER3, WER4 all report RADAR_PRE_LEAK_64. This indicates that these applications (Firefox, Discord, foundation.exe, ManorLords, and Wow.exe) are suspected of leaking memory. This doesn’t necessarily mean they’re crashing, but they’re not releasing allocated memory as they should, which can eventually lead to performance issues or system instability if left unchecked.
McAfee Issues (mfevtps.exe/CRYPT32.dll): WER5 and WER6 show crashes related to mfevtps.exe (McAfee VirusScan Enterprise) and CRYPT32.dll (Windows cryptography library). This strongly suggests a problem with the McAfee installation or a conflict with the system. The error code c0000005 (Access Violation) indicates the McAfee process is trying to access memory it doesn’t have permission to.
McAfee MOVE AntiVirus Issues (rundll32.exe/mcmscins.dll): WER7 and WER8 show crashes involving rundll32.exe and mcmscins.dll (McAfee MOVE AntiVirus). Again, the c0000005 error code points to an access violation.
Windows Store Update Failure (StoreAgentScanForUpdatesFailure0): WER9 reports a failure to scan for updates in the Windows Store, with error code 80240438. This often indicates network connectivity problems or issues with the Windows Update service.
Analysis and Recommended Actions:
Memory Leaks (RADAR_PRE_LEAK_64):
These are warnings, not immediate crashes. However, they should be addressed.
Update the applications: Ensure Firefox, Discord, and WoW are updated to their latest versions. Developers often fix memory leaks in updates.
Monitor memory usage: Use Task Manager to monitor the memory usage of these applications over time. If you see memory usage constantly increasing, it’s a strong indication of a leak.
Consider alternatives (if the problem persists): If a specific application consistently leaks memory even after updates, you might consider looking for alternative software.
McAfee Issues (mfevtps.exe/CRYPT32.dll and rundll32.exe/mcmscins.dll):
These are the most critical errors as they are causing crashes.
Focus on McAfee: The common thread is McAfee. The issues with both VirusScan Enterprise and MOVE AntiVirus point to a problem with the McAfee installation, configuration, or compatibility.
Prioritize McAfee Troubleshooting:
Update McAfee: Ensure both VirusScan Enterprise and any MOVE AntiVirus components are updated to the latest versions.
Repair McAfee: Try repairing the McAfee installations.
Reinstall McAfee: If repairing doesn’t work, uninstall and reinstall McAfee completely.
Check for Conflicts: See if any other security software is installed or if there have been recent system changes that could be conflicting with McAfee.
Check for Compatibility: Make sure your McAfee version is compatible with your Windows version.
Contact McAfee Support: If the problem persists after reinstalling, contact McAfee support.
Windows Store Update Failure (StoreAgentScanForUpdatesFailure0):
This is less critical than the McAfee crashes but should still be addressed.
Troubleshoot Windows Update: Follow the troubleshooting steps outlined in my previous response regarding error 80240438. Focus on network connectivity, the Windows Update troubleshooter, and restarting the relevant services.
Key Takeaway:
The McAfee-related crashes are the most pressing issue. Address those first. Once you’ve resolved the McAfee problems, then focus on the Windows Store update issue. The memory leak warnings are less urgent but should be monitored and addressed by updating the affected applications.
Since you’re seeing multiple McAfee-related crashes, it is highly recommended you focus your efforts on troubleshooting, repairing, or reinstalling McAfee software. This will most likely resolve the most critical issues you are experiencing.
Those are killer branded cards and the killer software has been an issue at various times. You may want to look for software to completely remove it if the driver updates don’t help.