![how to disable ff14 reshade how to disable ff14 reshade](https://www.mmogames.com/wp-content/uploads/2018/04/mxao-compare-ffxiv-reshade-guide-1-560x560.jpg)
- #How to disable ff14 reshade driver
- #How to disable ff14 reshade code
- #How to disable ff14 reshade windows
The second thing, and if the above doesn't help and despite Memtest running clean, I'd suggest you remove a stick of RAM and try running on just one stick for a few days. Give this a good try before moving on to the second thing to try. I don't know whether that's necessary but it's always a wise move when changes have been made. This will stop Defender applying these security features to ffxiv_dx11.exe. In the list of settings click the Override System Settings box for all settings and ensure that all settings are turned off. Click Add and then by program name and enter ffxiv_dx11.exe as the program name. I suspect they won't be there (if they are, make a note of the settings and then modify them as I'm going to suggest). Mostly these are added automatically at installation time, so scan down the list looking for ffxiv_dx11.exe and any other FFxiv entries too. The panel initially shows the System Settings, so click on Program Settings to see the program specific overrides. Now from the main Defender screen, click on App & Browser Control and under Exploit protection, click on Exploit protection settings. Click on Add an exclusion and then Folder, now navigate to the folder in which the game executable files are stored and add that to the Defender exclusions. Under Exclusions, click on Add or Remove exclusions. If you have Controlled Folder Access turned on then please turn it off (for now). Scroll down to Controlled Folder Access and click on Manage controlled folder access. Under Virus & Threat Protection Settings, click on Manage Settings. Open the Defender control panel and click on Virus & Threat Protection. There are two different troubleshooting steps I'd like you to take now and I'll describe them in the order I think you should try them.įirst let's try and ensure that Defender doesn't get in the way of the game.
#How to disable ff14 reshade windows
That has set me wondering whether Windows Defender is blocking some critical aspects of the way the game accesses the system services perhaps?
![how to disable ff14 reshade how to disable ff14 reshade](https://64.media.tumblr.com/9e160604ba8b65745fa3a49216b09316/tumblr_paht1m0qUY1vpmqjto5_1280.png)
#How to disable ff14 reshade driver
In addition there are two driver errors in the list of driver calls for the active thread our old favorite nvlddmkm.sys (the Nvidia graphics driver) and wdfilter.sys - which is a component of Windows Defender. That doesn't mean necessarily that you have a RAM issue nor a registry issue, though it is possible that the game writes registry entries (that were being searched here) and these are corrupt somehow?
![how to disable ff14 reshade how to disable ff14 reshade](https://staticdelivery.nexusmods.com/mods/3191/images/thumbnails/4/4-1584812224-1584682019.png)
#How to disable ff14 reshade code
Interestingly the exception code for the BSOD is 0xc0000005, which is a memory access violation. The registry hives are loaded into RAM at boot time, so all these registry function calls are RAM operations. The stack trace then appears to show a problem with the Windows registry. The final function call before the bug check is nt!CmpUnlockKcb and a KCB is a Key Control Block in the Windows registry. This is followed by several function calls opening a registry object followed by several doing a registry compare (checking some registry value perhaps?). They start with the normal nt!KiSystemServiceCopyEnd function call, which is how user mode code calls a kernel mode service and then we get the nt!NtOpenKeyEx call which is how the registry is accessed.
![how to disable ff14 reshade how to disable ff14 reshade](https://pbs.twimg.com/media/DsvvRaoU4AEUwcS.jpg)
The stack trace for the active thread contains system function calls that appear to have been related to accessing the registry. The process in control at the time of the bug check was ffxiv_dx11.exe and I don't need to tell you what that is. Your kernel dump does contain some possible new leads, although it still points very strongly at the game itself. Click to expand.Well this is disappointing.Ī SYSTEM_SERVICE_EXCEPTION stop code is also very common and also almost always driver related.