• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Help! FFXIV Won't Stop Crashing, Sometimes Takes Computer With It

Status
Not open for further replies.
Hi there. My partner and I have been experiencing a lot of issues playing FFXIV on Windows 10 in the past few months on my custom-built desktop, with the game crashing frequently and the computer sometimes crashing along with it. We tried a lot (which I will list below), including replacing the SSD and RAM, in order to try to fix this.

For a while, the computer crashed almost every time FFXIV did, until it eventually reached a point where it was stuck in an endless loop of BSODs that resulted in Windows being unable to actually start up. As I recall/have taken pictures, the consistent BSOD message was "PFN_LIST_CORRUPTED." We got on the phone with Microsoft Support, who took hours of our time and got us to wipe both of our drives, all while failing to do a clean install of Windows. We then took it to a repair place that got a clean install of Windows done successfully, though they could not save our data. We reinstalled FFXIV, seemed like we were good to go, and then the crashes came back after a week or two. Ever since the clean install, it has been mostly the game crashing on its own instead of the game crashing and then a BSOD coming with it, but BSODs have been becoming more common in the past few days. "PFN_LIST_CORRUPT" is even back with a vengeance.

Initially the problems seemed to have something to do with things were split between the C: and D: drives, now it seems it may have to do with memory errors. Below is a list of some of the error messages we have received from game crashes, followed by BSOD messages, followed by the steps we have taken to troubleshoot.

FFXIV errors:

1. The instruction at 0x00007FF94C0EDC30 referenced memory at 0x00007FF94C0EDC30. The memory could not be written.

2. An unexpected error has occurred. Exiting FINAL FANTASY XIV. 2020-12-14_11:31

nvwgf2umx.dll+2BDAEA
nvwgf2umx.dll+419469
nvwgf2umx.dll+4374EF
nvwgf2umx.dll+10B3FCF
nvwgf2umx.dll+10B3F4A
nvwgf2umx.dll+10A916D
nvwgf2umx.dll+67F25A
nvwgf2umx.dll+163552C

(We have gotten many errors like this one, filenames are not always the same, this is just the one for which I had a picture handy to copy from.)

BSOD stop codes:

1. PFN_LIST_CORRUPT

2. MEMORY MANAGEMENT

Steps taken:

1. Moved the .exe files for FFXIV out of the Steam folders so that Steam could be "tricked" into reinstalling it, in an attempt to replace the old .exe files
2. Replaced SSD
3. Replaced RAM
4. Clean install of Windows 10 (an unintentionally wiped both drives)
5. Renamed "Steam Library" file
6. Uninstalled game from C: drive and reinstalled on D: drive (and replicated step 6)
7. Turned off all overlays (Steam, Discord, GeForce)

Anything you folks can think of to help us stop the crashes would be greatly appreciated.

Edit: How could I forget specs?

CPU: Intel Core i5-6600K 3.5 GHz Quad-Core Processor (overclocked)
Motherboard: Asus Z170-A ATX LGA1151 Motherboard
RAM: Corsair Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600) C16 Desktop Memory
GPU: Zotac GeForce GTX 1080 8 GB AMP Video Card (factory and manually overclocked)
SSD: Samsung SSD 860 EVO 1TB 2.5 Inch SATA III Internal SSD (MZ-76E1T0B/AM)
HDD: Toshiba P300 3 TB 3.5" 7200RPM Internal Hard Drive
Monitor: Asus ROG SWIFT PG248Q 24.0" 1920x1080 180 Hz Monitor (uses Gsync)
OS: Windows 10 Home
 
Hello

I would try the fix at the other forum you listed your issue's on first.. This seems to be a driver issue according to microsoft page .

Cause​

This error is typically caused by a driver passing a bad memory descriptor list. For example, the driver might have called MmUnlockPages twice with the same list.

If a kernel debugger is available, examine the stack trace: the !analyze debug extension displays information about the bug check and can be helpful in determining the root cause, then enter one of the k (Display Stack Backtrace) commands to view the call stack.
 
Status
Not open for further replies.