The issue arises when the user sees Event ID 65 in the event viewer of his system. Some users encounter the issue with a system crash/hang-up (having failed with 0x57 description), whereas for others, it is just creating entries in the event viewer without any notable system issue. In some cases, the issue was triggered when the user used Alt + Tab keys while playing a game on the full screen (some users reported the issue with just one game only). Before moving on with the solutions, make sure to create a restore point of your system. Moreover, make sure you are not overclocking your system (try to lower the speed of your system/GPU to the lowest possible). Furthermore, check if using just one (or two) ram sticks in the system solves the issue. Additionally, check if clean booting the system resolves the issue. If so, then enable applications/services one by one till you find the problematic one. Last but not least, make sure the Windows of your system is updated to the latest build.
Solution 1: Disable Full-Screen Optimization for the Problematic Game/Application
Windows automatically tries to optimize an application that is operating on the full screen. You may encounter the Event ID 65 if the full-screen optimization of Windows is hindering the operation of the problematic game/application. In this case, disabling the full-screen optimization for the problematic game/application may solve the problem.
Solution 2: Disable Variable Refresh Rate of Your Display
Variable Refresh Rate (VRR) is used to change the refresh rate of a display unit (where supported) to prevent screen tearing during the game’s play in full-screen. But this feature may hinder the operation of the display modules and thus cause the error under discussion. In this case, disabling the Variable Refresh Rate may solve the problem. But this option may not be available to all the users.
Solution 3: Disable Focus Assist and Notifications
Focus Assist helps users in using the system without interception or playing the game without notifications. But this feature may hinder the operation of full-screen applications/games and thus trigger the Event ID 65. In this context, disabling the Focus Assist may solve the problem.
Solution 4: Remove/Disable the Tasks from the Task Scheduler
You may get the Event ID 65 error if a task defined in the Task Scheduler is triggering the behavior. In this case, removing/disabling the tasks from the Task Scheduler may solve the problem.
Solution 5: Perform SFC and DISM Scan
You may encounter the event ID 65 if the files essential for your OS are corrupt. In this context, performing SFC and DISM scans may clear the corruption and thus solve the problem.
Solution 6: Reinstall the Visual C++ Redistributable
Many applications/games use the Visual C++ Redistributable to complete their runtime. You may encounter the AppModel-Runtime error at hand if the installation of Visual C++ Redistributable is corrupt. In this context, reinstallation of the Visual C++ may solve the problem.
Solution 7: Remove the Windows 10 Update
If the issue started after a Windows 10 update (reported by many users), then uninstalling the Windows 10 buggy updates or reverting to an older version of Windows may solve the problem. If so, then you may try to update again but after trying the following steps:
Solution 8: Revert, Update or Reinstall the Graphics Driver
You may encounter the error under discussion if the graphics driver of your system is outdated, corrupt, or incompatible (after a driver update). In this context, updating, reinstalling, or reverting to the older version of the graphics driver may solve the problem. If reverting or updating the graphics driver did not solve your issue, then you may have to reinstall the graphics driver.
Solution 9: Edit the BIOS Options
You may get the Event ID 65 if the BIOS of your system is outdated or not properly configured. In this context, updating or properly configuring the BIOS options may solve the problem. Warning: Proceed at your own risk and with extreme caution as updating/editing the system’s BIOS requires a certain level of proficiency and if done wrong, you may brick your system and cause everlasting damage to your data. If the issue is still there, then check if performing a clean install of Windows solves the issue. If not, then you may have to live with it (if it is not causing serious issues for you) or get your system checked for any hardware issues (like a faulty graphics card or processor).
How to Fix ‘AppModel Runtime Error 0x490’ on Windows 10How to Fix Runtime Error 429 on Windows 10 and Earlier VersionsFix Error Could not find Java SE Runtime Environment[FIX] Runtime Error when Installing Malwarebytes (Could not Install Proc)
