5/19/2023 0 Comments Directx 11 error ffxiv![]() 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? 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. 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.
0 Comments
Leave a Reply. |