BSOD playing Final Fantasy XIV: Heavensward bugcheck 0x0000004e

Was playing this game and my game crashed, unsure what the issue is, everything was fine until today.
Attachment 139548

Hi djseaghost,


These are some finding in the event logs:

The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled. Data corruption may occur.

Installation Failure: Windows failed to install the following update with error 0x80070103: NVIDIA - Display - 12/29/2016 12:00:00 AM - 21.21.13.7653.


Installation Failure: Windows failed to install the following update with error 0x80070103: NVIDIA - Display - 2/23/2017 12:00:00 AM - 21.21.13.7878.

File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T11:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy3'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor.

File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T11:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy5'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor.


The start type of the Service for NVIDIA High Definition Audio Driver service was changed from demand start to disabled.

Event[37317]:
Log Name: System
Source: Microsoft-Windows-WindowsUpdateClient
Date: 2017-06-12T20:28:03.581
Event ID: 20
Task: Windows Update Agent
Level: Error
Opcode: Installation
Keyword: Installation,Failure
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Logic-Bomb
Description:
Installation Failure: Windows failed to install the following update with error 0x80070103: NVIDIA - Display - 12/29/2016 12:00:00 AM - 21.21.13.7653.


Event[37319]:
Log Name: System
Source: Microsoft-Windows-WindowsUpdateClient
Date: 2017-06-12T20:28:16.872
Event ID: 20
Task: Windows Update Agent
Level: Error
Opcode: Installation
Keyword: Installation,Failure
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Logic-Bomb
Description:
Installation Failure: Windows failed to install the following update with error 0x80070103: NVIDIA - Display - 2/23/2017 12:00:00 AM - 21.21.13.7878.


The start type of the NVIDIA Display Container LS service was changed from auto start to disabled.

Code:

BugCheck 4E, {2, 119c3a, 41efff, 1}

***** Kernel symbols are WRONG. Please fix symbols to do analysis
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireSharedStarveExclusive+ad6 )

Open administrative command prompt and type or copy and paste:

1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)

2) sfc /scannow

3) dism /online /cleanup-image /restorehealth

4) chkdsk /scan

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread


5) Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.
Memtest86+ - Advanced Memory Diagnostic Tool

6) Uninstall all Nvidia drivers using Display Driver Uninstaller and install new drivers from the Asus web site. User your computers product or serial number and the operating system. Display Driver Uninstaller Download version 17.0.6.6
Display Driver Uninstaller Download version 17.0.6.6

Have you had any new bsod since your post?

The problem was clearly caused by ESET, which you have now removed. Disable Driver Verifier

daikin990 said:

The problem was clearly caused by ESET, which you have now removed. Disable Driver Verifier

daikin990 Where are you seeing ESET in this thread?

I can run those tonight when i go to bed, I did do a few things, I reinstalled the video driver via display driver uninstall, I reseated my ram and re-plugged in my hdd. The issue seems to have gone away, ran memtest+86 for 9 hours no errors. It did have errors then after I re-seated my ram I encountered 0 errors. I can do the other commands and post my findings by tomorrow morning most likely, thank you for the help.