Solved BSOD with error(s) 0x000000f4 and 0x0000007a while playing games.

[DylanRoberge]

Hello!

I've been looking and researching the BSOD errors in the title and in need of some assistance. The errors occur during playing graphically intensive games (The Witcher 3, Skyforge). And normally I would say it probably is a heating problem and would need to get some better cooling in my case. But I would love to make sure that it is just that and nothing else before I invest money into cooling systems and what not.
First things first, I need to know how to send you guys the minidump file in the correct format/file so you can properly view it without problems. And secondly how I can view the dump files later on so I can eventually figure it out myself, because I normally am a self-reliant individual and like to do things on my own.


Thank you.

 

[DylanRoberge]

Sorry, I just read instructions with the dump file and info you guys need. Here it is.

 

[derekimo]

Hi There,

These are both file system or HDD related,

BugCheck F4, {3, fffffa8008c731b0, fffffa8008c73490, fffff80003193940}

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

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

6: 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: fffffa8008c731b0, Terminating object
Arg3: fffffa8008c73490, Process image file name
Arg4: fffff80003193940, Explanatory message (ascii)

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

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

PROCESS_OBJECT: fffffa8008c731b0

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_[COLOR="Red"]IOERR
[/COLOR]
CUSTOMER_CRASH_COUNT:  1

BugCheck 7A, {fffff6fc4002a0c8, ffffffffc000000e, fdaebe0, fffff88005419000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3593a )

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc4002a0c8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000000fdaebe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88005419000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

[COLOR="red"]DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

Check your cables to make sure they are connected good.

Run a few tests,

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Please perform the following tests,

chkdsk /r

I see you have a WD, you can use their tool,

WD Support / Downloads / Other Products / Data Lifeguard Diagnostic for Windows

As for how to view the dump files, this is what we use,

http://www.sevenforums.com/tutorials/355137-windbg-install-configure-bsod-analysis.html

 

[DylanRoberge]

 

[DylanRoberge]

I did the WD Disk check. This quick smart diagnostic said it passed. I also tried doing the chkdsk /r but got this message, "Windows can't check the disk while it's in use."

 

[derekimo]

Try saving that as a jpeg instead, that one is messed up.

 

[DylanRoberge]

Ok, so I did the chkdsk /r and nothing popped up out of the norm. Doing the SFC /SCANNOW as we speak. I'm thinking its a bad file somewhere. Will keep you up to date.