BSOD always received when playing FFXIV

[hobotripin]

Not entirely sure what's causing this, i have received 3 so far 2 while playing ffxiv and one while attempting to post this.

 

[koolkat77]

Welcome to the forum hobotripin,

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\hobotripin\SF_22-07-2014\072214-14804-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0320e000 PsLoadedModuleList = 0xfffff800`03451890
Debug session time: Tue Jul 22 23:52:19.987 2014 (UTC + 6:00)
System Uptime: 0 days 9:41:52.001
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008f206d0, fffffa8008f209b0, fffff80003589270}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8008f206d0, Terminating object
Arg3: fffffa8008f209b0, Process image file name
Arg4: fffff80003589270, Explanatory message (ascii)

Debugging Details:
------------------

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa8008f206d0

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0b67c0e8 fffff800`03611ab2 : 00000000`000000f4 00000000`00000003 fffffa80`08f206d0 fffffa80`08f209b0 : nt!KeBugCheckEx
fffff880`0b67c0f0 fffff800`035bcabb : ffffffff`ffffffff fffffa80`0a985b50 fffffa80`08f206d0 fffffa80`08f206d0 : nt!PspCatchCriticalBreak+0x92
fffff880`0b67c130 fffff800`0353bf04 : ffffffff`ffffffff 00000000`00000001 fffffa80`08f206d0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`0b67c180 fffff800`03282e53 : fffffa80`08f206d0 fffff800`c0000006 fffffa80`0a985b50 00000000`02600c00 : nt!NtTerminateProcess+0xf4
fffff880`0b67c200 fffff800`0327f410 : fffff800`032ce82f fffff880`0b67cb78 fffff880`0b67c8d0 fffff880`0b67cc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0b67c398 fffff800`032ce82f : fffff880`0b67cb78 fffff880`0b67c8d0 fffff880`0b67cc20 00000000`026017a0 : nt!KiServiceLinkage
fffff880`0b67c3a0 fffff800`03283242 : fffff880`0b67cb78 00000000`00011b34 fffff880`0b67cc20 00000000`02601278 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`0b67ca40 fffff800`03281dba : 00000000`00000000 000007fe`fd75d8c0 00000000`779e1201 00000000`00011b34 : nt!KiExceptionDispatch+0xc2
fffff880`0b67cc20 00000000`779b9c42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`026011c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779b9c42


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

Followup: MachineOwner
---------

Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

Upload a screenshot of your hard disk using Crystal Disk Info:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Test your Hard Drive with SeaTools:

• How to Use SeaTools for DOS and Windows Disk Check Utility

 

[hobotripin]

I did the SeaTools and the Generic SD/MMC had a bunch of errors and the long generic and short generic test failed. The PATA-SATA short generic passed however long failed.

 

[hobotripin]

Here's the screenshot using crystal disk info

 

[koolkat77]

Follow this:

The caution indication can be converted to good using CrystalDiscInfo. Click on the caution Button, you will get another window ....

In the resulting window, there are three sliders in the left. Drag them to the ultimate left, and notice the values at the right side are converting to zeros.

Now click the apply button, and notice that the caution is gone.

 

[hobotripin]

Hmmm wow it changed it to good, wasn't expecting it to be such a simple fix, thank you very much!

 

[koolkat77]

I'd suggest you take a back up of all your important files though

 

[hobotripin]

So this fix didn't work , while I haven't BSOD(I restart my computer before it does), a BSOD would always follow after a brrrrr sound when talking to someone on teamspeak so anticipating that I restart my computer.

 

[koolkat77]

Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

• Speccy - System Information - Free Download
• HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.