Solved BSOD playing League of Legends, error 0x000000f4

KevinJV · Apr 14, 2012

Hi I am experienceing BSOD's everytime I enter a match in League of Legends. The game runs for a bit and then it becomes unresponsive and crashes. Sometimes it says BugSplatRc resource dll not found, crashing the game and then blue screening. My drivers for my graphics card as well as BIOS are up to date.

The Full Blue Screen Error is : *** STOP: 0x000000F4 (0X0000000000000003, 0XFFFFFA8007D5F060,0XFFFFFA80007D5F340,0XFFFFF800003385660)

I am currently running a custom computer I built myself. The specs are:

Windows 7 Home Premium - 64 bit (Installed myself)
Asus Motherboard P8Z68-V LX
NVIDIA GTX 570 Graphics Card
Intel I5 - 2500k Processor
8GB RAM
Age of hardware: All bought in december of 2011. However the HDD I bought 5 days ago.
Due to the new hard drive I reinstalled everything 5 days ago.

Also I thought it might be important to mention when I first built the computer and installed everything (last December) I was experiencing the same BSOD problems. I thought it was a audio driver failure because I heard strange noises sometimes before it would blue screen. It used to only crash for League of Legends and Skyrim, but other games worked. I began to use a wireless headset and the Blue Screens stopped. Now I do not know if the problem has to do with audio, or what and I hope I can get help. Thanks!

writhziden · Apr 15, 2012

Possible out of date driver:

Code:

nx6000	fffff880`038f7000	fffff880`03904000	Fri Jun 26 11:13:21 2009 (4a4501b1)	00012312		nx6000.sys

This is your Microsoft Lifecam, and webcam drivers are usually outdated and work fine. Probably nothing to be concerned with.

Problem drivers:

Code:

AiCharger	fffff880`0fddc000	fffff880`0fddde80	Wed Oct 20 06:00:33 2010 (4cbed9e1)	00005a64		AiCharger.sys
AiChargerPlus	fffff880`00ed0000	fffff880`00ed1e00	Sun Nov 07 23:48:26 2010 (4cd79d3a)	00005a96		AiChargerPlus.sys

ASUS AI Apple Charger. Recommend removing the software. It may be part of the software bundled in AI Suite, or it may just be ASUS AI Charger in Start Menu -> Control Panel -> Uninstall a program. Remove whichever one you have after you create a restore point

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\KevinJV\041412-11060-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03003000 PsLoadedModuleList = 0xfffff800`03247650
Debug session time: Sat Apr 14 12:14:40.335 2012 (UTC - 6:00)
System Uptime: 0 days 0:13:54.193
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008eeeb30, fffffa8008eeee10, fffff80003382660}

Probably caused by : csrss.exe

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

1: 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: fffffa8008eeeb30, Terminating object
Arg3: fffffa8008eeee10, Process image file name
Arg4: fffff80003382660, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8008eeeb30

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:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`08483e38 fffff800`03409772 : 00000000`000000f4 00000000`00000003 fffffa80`08eeeb30 fffffa80`08eeee10 : nt!KeBugCheckEx
fffff880`08483e40 fffff800`033b6f7b : ffffffff`ffffffff fffffa80`0b4f4060 fffffa80`08eeeb30 fffffa80`08eeeb30 : nt!PspCatchCriticalBreak+0x92
fffff880`08483e80 fffff800`033360f4 : ffffffff`ffffffff 00000000`00000001 fffffa80`08eeeb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`08483ed0 fffff800`0307ef13 : fffffa80`08eeeb30 fffff800`c0000006 fffffa80`0b4f4060 00000000`045a0f00 : nt!NtTerminateProcess+0xf4
fffff880`08483f50 fffff800`0307b4d0 : fffff800`030ca9df fffff880`08484a38 fffff880`08484790 fffff880`08484ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`084840e8 fffff800`030ca9df : fffff880`08484a38 fffff880`08484790 fffff880`08484ae0 00000000`76f25c44 : nt!KiServiceLinkage
fffff880`084840f0 fffff800`0307f302 : fffff880`08484a38 00000000`045e0000 fffff880`08484ae0 00000000`76f31658 : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`08484900 fffff800`0307de7a : 00000000`00000000 00000000`76f25c47 00000000`772c7301 00000000`045e0000 : nt!KiExceptionDispatch+0xc2
fffff880`08484ae0 00000000`771a8f36 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`045a1620 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771a8f36


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
---------

The above crash occurred because a Windows system process was terminated unexpectedly. Possible causes are hard disk errors... System file corruption... Viruses... Lack of Windows updates... Drivers...

Let's start by looking for data corruption.

If you are overclocking any hardware, please stop.
Run Disk Check with Automatically fix file system errors checked. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

KevinJV · Apr 15, 2012

All right I removed ASUS AI Charger and ran Check Disk. My hard drive is partitioned into two disks.
On disk D:

Chkdsk was executed in read/write mode.

Checking file system on D:
Volume label is Data.

CHKDSK is verifying files (stage 1 of 3)...
1280 file records processed. File verification completed.
19 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
1506 index entries processed. Index verification completed.

CHKDSK is verifying security descriptors (stage 3 of 3)...
1280 file SDs/SIDs processed. Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
113 data files processed.
Windows has checked the file system and found no problems.

464759807 KB total disk space.
2761108 KB in 894 files.
340 KB in 115 indexes.
81419 KB in use by the system.
65536 KB occupied by the log file.
461916940 KB available on disk.

4096 bytes in each allocation unit.
116189951 total allocation units on disk.
115479235 allocation units available on disk.

On Disk C: (First check)

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
100096 file records processed. File verification completed.
115 large file records processed. 0 bad file records processed. 0 EA records processed. 92 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
141924 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
100096 file SDs/SIDs processed. Cleaning up 250 unused index entries from index $SII of file 0x9.
Cleaning up 250 unused index entries from index $SDH of file 0x9.
Cleaning up 250 unused security descriptors.
Security descriptor verification completed.
20915 data files processed. CHKDSK is verifying Usn Journal...
35148872 USN bytes processed. Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

511896575 KB total disk space.
41407988 KB in 77054 files.
56912 KB in 20916 indexes.
0 KB in bad sectors.
216643 KB in use by the system.
65536 KB occupied by the log file.
470215032 KB available on disk.

4096 bytes in each allocation unit.
127974143 total allocation units on disk.
117553758 allocation units available on disk.

Internal Info:
00 87 01 00 be 7e 01 00 74 de 02 00 00 00 00 00 .....~..t.......
ab 00 00 00 5c 00 00 00 00 00 00 00 00 00 00 00 ....\...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
Chkdsk of C: (Second Check):
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
100096 file records processed. File verification completed.
114 large file records processed. 0 bad file records processed. 0 EA records processed. 92 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
141938 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
100096 file SDs/SIDs processed. Cleaning up 11 unused index entries from index $SII of file 0x9.
Cleaning up 11 unused index entries from index $SDH of file 0x9.
Cleaning up 11 unused security descriptors.
Security descriptor verification completed.
20922 data files processed. CHKDSK is verifying Usn Journal...
37290248 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

511896575 KB total disk space.
41873304 KB in 77158 files.
56956 KB in 20923 indexes.
0 KB in bad sectors.
218563 KB in use by the system.
65536 KB occupied by the log file.
469747752 KB available on disk.

4096 bytes in each allocation unit.
127974143 total allocation units on disk.
117436938 allocation units available on disk.

Internal Info:
00 87 01 00 2d 7f 01 00 32 df 02 00 00 00 00 00 ....-...2.......
ac 00 00 00 5c 00 00 00 00 00 00 00 00 00 00 00 ....\...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

writhziden · Apr 15, 2012

Looks good. See how the SFC /SCANNOW goes and let us know how the system is responding.

KevinJV · Apr 15, 2012

The first sfc /scannow test reported no errors.
"Windows Resource Protection did not find any integrity violations."

writhziden · Apr 15, 2012

Good news! See how the system responds for a while. Let us know if you need further help.

KevinJV · Apr 15, 2012

Ok thanks!

KevinJV · Apr 15, 2012

Unfortunately the problem still persists. Only a few seconds into the game, it BSOD. I am uploading the dmp file.

writhziden · Apr 15, 2012

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\KevinJV\041512-11980-01\041512-11980-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`0329f650
Debug session time: Sun Apr 15 11:22:36.941 2012 (UTC - 6:00)
System Uptime: 0 days 1:16:49.800
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc400098a0, ffffffffc000000e, 29a24860, fffff88001314844}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
GetPointerFromAddress: unable to read from fffff80003309278
Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: 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: fffff6fc400098a0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000029a24860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88001314844, 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.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  League of Lege

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800475a260 -- (.trap 0xfffff8800475a260)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=00000000000b1e01
rdx=fffff8800475be50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001314844 rsp=fffff8800475a3f8 rbp=fffff8800475a560
 r8=fffff88001314844  r9=fffff8800475a560 r10=0000000000000002
r11=fffff8800475a468 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
Ntfs! ?? ::NNGAKEGL::`string'+0x165b:
fffff880`01314844 0000            add     byte ptr [rax],al ds:cb00:00000000`00000001=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003147f12 to fffff800030d7c80

STACK_TEXT:  
fffff880`04759f48 fffff800`03147f12 : 00000000`0000007a fffff6fc`400098a0 ffffffff`c000000e 00000000`29a24860 : nt!KeBugCheckEx
fffff880`04759f50 fffff800`030feb0f : fffffa80`0bce1630 fffff880`0475a0c0 fffff800`0330c540 fffffa80`0bce1630 : nt! ?? ::FNODOBFM::`string'+0x3716a
fffff880`0475a030 fffff800`030e52a9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff8a0`1b5a20d0 : nt!MiIssueHardFault+0x28b
fffff880`0475a100 fffff800`030d5dae : 00000000`00000008 fffff880`01314844 fffff8a0`1688d000 fffff880`01276180 : nt!MmAccessFault+0x1399
fffff880`0475a260 fffff880`01314844 : fffff800`03102f7f 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0475a3f8 fffff800`03102f7f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs! ?? ::NNGAKEGL::`string'+0x165b
fffff880`0475a400 fffff880`0123f5c5 : fffff880`0127618c fffff880`0475be50 fffff880`0475bac8 fffff880`0475be50 : nt!_C_specific_handler+0x13f
fffff880`0475a470 fffff800`031029cd : fffff880`0475be50 00000000`00000000 fffff880`01226000 fffff880`01276178 : Ntfs!_GSHandlerCheck_SEH+0x75
fffff880`0475a4a0 fffff800`03102418 : fffff880`0475be50 fffff880`0475a520 fffff880`0123f550 fffff880`01226000 : nt!RtlpExecuteHandlerForUnwind+0xd
fffff880`0475a4d0 fffff800`03102f0c : fffff880`0475c0a0 fffff880`01234a42 fffff880`0475bac8 ffffffff`c0000006 : nt!RtlUnwindEx+0x472
fffff880`0475ab70 fffff800`0310294d : fffff880`012723b0 fffff880`0475c0a0 00000000`00000000 fffff880`01226000 : nt!_C_specific_handler+0xcc
fffff880`0475abe0 fffff800`03101725 : fffff880`012723b0 fffff880`0475ac58 fffff880`0475bac8 fffff880`01226000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0475ac10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlDispatchException+0x415


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    fffff88001314000-fffff88001314031  50 bytes - Ntfs! ?? ::NNGAKEGL::`string'+d61
	[ 48 2b d7 48 8b 75 70 48:00 00 00 00 00 00 00 00 ]
    fffff88001314035-fffff88001314037  3 bytes - Ntfs! ?? ::NNGAKEGL::`string'+d96 (+0x35)
	[ 4c 8b 83:00 00 00 ]
    fffff88001314039 - Ntfs! ?? ::NNGAKEGL::`string'+d9a (+0x04)
	[ 01:00 ]
    fffff8800131403c-fffff88001314068  45 bytes - Ntfs! ?? ::NNGAKEGL::`string'+d9d (+0x03)
	[ 49 8b c0 48 2b c7 41 8d:00 00 00 00 00 00 00 00 ]
    fffff8800131406c-fffff88001314072  7 bytes - Ntfs! ?? ::NNGAKEGL::`string'+dcd (+0x30)
	[ 48 29 7e 30 48 29 bb:00 00 00 00 00 00 00 ]
    fffff88001314074 - Ntfs! ?? ::NNGAKEGL::`string'+dd5 (+0x08)
	[ 01:00 ]
    fffff88001314077-fffff8800131407c  6 bytes - Ntfs! ?? ::NNGAKEGL::`string'+dd8 (+0x03)
	[ eb 07 48 8b 9d f8:00 00 00 00 00 00 ]
    fffff88001314080-fffff8800131408b  12 bytes - Ntfs! ?? ::NNGAKEGL::`string'+de1 (+0x09)
	[ 48 8b 53 40 48 8b 52 70:00 00 00 00 00 00 00 00 ]
    fffff8800131408f-fffff88001314094  6 bytes - Ntfs! ?? ::NNGAKEGL::`string'+df0 (+0x0f)
	[ e8 dc 18 f2 ff eb:00 00 00 00 00 00 ]
    fffff88001314096-fffff880013140b2  29 bytes - Ntfs! ?? ::NNGAKEGL::`string'+df7 (+0x07)
	[ 48 83 c4 40 41 5d 5f 5e:00 00 00 00 00 00 00 00 ]
    fffff880013140b6-fffff880013140bb  6 bytes - Ntfs! ?? ::NNGAKEGL::`string'+e1b (+0x20)
	[ e8 6d b3 f2 ff eb:00 00 00 00 00 00 ]
    fffff880013140bd-fffff880013140f8  60 bytes - Ntfs! ?? ::NNGAKEGL::`string'+e22 (+0x07)
	[ 48 83 c4 70 5d c3 90 55:00 00 00 00 00 00 00 00 ]
    fffff880013140fa-fffff88001314119  32 bytes - Ntfs! ?? ::NNGAKEGL::`string'+e65 (+0x3d)
	[ 48 83 c4 28 5e 5d c3 90:00 00 00 00 00 00 00 00 ]
    fffff8800131411c-fffff88001314126  11 bytes - Ntfs! ?? ::NNGAKEGL::`string'+e8b (+0x22)
	[ ff 15 4e 7a f5 ff 4c 8b:00 00 00 00 00 00 00 00 ]
    fffff88001314129-fffff88001314130  8 bytes - Ntfs! ?? ::NNGAKEGL::`string'+e98 (+0x0d)
	[ 4d 85 db 74 10 80 7d 60:00 00 00 00 00 00 00 00 ]
    fffff88001314132-fffff88001314137  6 bytes - Ntfs! ?? ::NNGAKEGL::`string'+ea1 (+0x09)
	[ 75 0a 41 83 8b 80:00 00 00 00 00 00 ]
    fffff8800131413b-fffff8800131413c  2 bytes - Ntfs! ?? ::NNGAKEGL::`string'+eaa (+0x09)
	[ 01 eb:00 00 ]
    fffff8800131413e-fffff88001314154  23 bytes - Ntfs! ?? ::NNGAKEGL::`string'+ead (+0x03)
	[ 48 83 c4 28 5d 5b c3 90:00 00 00 00 00 00 00 00 ]
    fffff88001314157-fffff88001314160  10 bytes - Ntfs! ?? ::NNGAKEGL::`string'+eca (+0x19)
	[ 0f ba 71 04 11 48 8b 85:00 00 00 00 00 00 00 00 ]
    fffff88001314163-fffff8800131416b  9 bytes - Ntfs! ?? ::NNGAKEGL::`string'+ed6 (+0x0c)
	[ 48 8b 50 40 48 8b 52 70:00 00 00 00 00 00 00 00 ]
    fffff8800131416d-fffff88001314170  4 bytes - Ntfs! ?? ::NNGAKEGL::`string'+ee0 (+0x0a)
	[ 18 f2 ff eb:00 00 00 00 ]
    fffff88001314172-fffff8800131418d  28 bytes - Ntfs! ?? ::NNGAKEGL::`string'+ee5 (+0x05)
	[ 48 83 c4 40 5d c3 53 55:00 00 00 00 00 00 00 00 ]
    fffff8800131418f-fffff880013141be  48 bytes - Ntfs! ?? ::NNGAKEGL::`string'+f09 (+0x1d)
	[ 74 1e 48 8b 4b 18 48 83:00 00 00 00 00 00 00 00 ]
    fffff880013141c0-fffff880013141d3  20 bytes - Ntfs! ?? ::NNGAKEGL::`string'+f3a (+0x31)
	[ 48 83 c4 28 5d 5b c3 90:00 00 00 00 00 00 00 00 ]
    fffff880013141d5-fffff880013141df  11 bytes - Ntfs! ?? ::NNGAKEGL::`string'+f5e (+0x15)
	[ 74 31 48 8b 5d 58 48 8b:00 00 00 00 00 00 00 00 ]
    fffff880013141e2-fffff880013141fb  26 bytes - Ntfs! ?? ::NNGAKEGL::`string'+f6b (+0x0d)
	[ 48 8b 50 70 48 85 d2 74:00 00 00 00 00 00 00 00 ]
    fffff880013141fe-fffff88001314201  4 bytes - Ntfs! ?? ::NNGAKEGL::`string'+f87 (+0x1c)
	[ 49 c7 43 70:00 00 00 00 ]
    fffff88001314206-fffff88001314210  11 bytes - Ntfs! ?? ::NNGAKEGL::`string'+f8f (+0x08)
	[ eb 04 48 8b 5d 58 48 8b:00 00 00 00 00 00 00 00 ]
    fffff88001314213-fffff8800131421a  8 bytes - Ntfs! ?? ::NNGAKEGL::`string'+f9c (+0x0d)
	[ 48 8b 48 40 48 8b 89 88:00 00 00 00 00 00 00 00 ]
    fffff8800131421e-fffff88001314224  7 bytes - Ntfs! ?? ::NNGAKEGL::`string'+fa7 (+0x0b)
	[ ff 15 7c 7a f5 ff eb:00 00 00 00 00 00 00 ]
    fffff88001314226-fffff88001314248  35 bytes - Ntfs! ?? ::NNGAKEGL::`string'+faf (+0x08)
	[ 48 83 c4 28 5d 5b c3 90:00 00 00 00 00 00 00 00 ]
    fffff8800131424c-fffff88001314251  6 bytes - Ntfs! ?? ::NNGAKEGL::`string'+fd9 (+0x26)
	[ e8 3f c6 fc ff eb:00 00 00 00 00 00 ]
    fffff88001314253-fffff8800131427f  45 bytes - Ntfs! ?? ::NNGAKEGL::`string'+fe0 (+0x07)
	[ 48 83 c4 58 5f 5d c3 90:00 00 00 00 00 00 00 00 ]
    fffff88001314282-fffff88001314288  7 bytes - Ntfs! ?? ::NNGAKEGL::`string'+1014 (+0x2f)
	[ 74 33 48 8b 83 08 01:00 00 00 00 00 00 00 ]
    fffff8800131428b-fffff88001314294  10 bytes - Ntfs! ?? ::NNGAKEGL::`string'+101d (+0x09)
	[ f0 83 40 24 ff 48 8b 8b:00 00 00 00 00 00 00 00 ]
    fffff88001314297-fffff880013142a8  18 bytes - Ntfs! ?? ::NNGAKEGL::`string'+1029 (+0x0c)
	[ 83 c8 ff f0 0f c1 41 40:00 00 00 00 00 00 00 00 ]
    fffff880013142ab-fffff880013142b4  10 bytes - Ntfs! ?? ::NNGAKEGL::`string'+103d (+0x14)
	[ e8 c0 cc fd ff 48 89 bb:00 00 00 00 00 00 00 00 ]
    fffff880013142b7-fffff880013142c3  13 bytes - Ntfs! ?? ::NNGAKEGL::`string'+1049 (+0x0c)
	[ 48 8b 4d 38 48 3b cf 74:00 00 00 00 00 00 00 00 ]
    fffff880013142c5-fffff880013142d6  18 bytes - Ntfs! ?? ::NNGAKEGL::`string'+1057 (+0x0e)
	[ 48 8b 4d 28 48 3b cf 74:00 00 00 00 00 00 00 00 ]
    fffff880013142d8-fffff880013142ee  23 bytes - Ntfs! ?? ::NNGAKEGL::`string'+106a (+0x13)
	[ 48 83 c4 20 5f 5d 5b c3:00 00 00 00 00 00 00 00 ]
    fffff880013142f2-fffff88001314306  21 bytes - Ntfs! ?? ::NNGAKEGL::`string'+108b (+0x1a)
	[ 74 0e 48 8b 4d 70 48 8b:00 00 00 00 00 00 00 00 ]
    fffff88001314309-fffff8800131431d  21 bytes - Ntfs! ?? ::NNGAKEGL::`string'+10a2 (+0x17)
	[ 74 14 48 8b 45 50 48 8b:00 00 00 00 00 00 00 00 ]
    fffff8800131431f-fffff88001314339  27 bytes - Ntfs! ?? ::NNGAKEGL::`string'+10b8 (+0x16)
	[ 48 83 c4 58 5f 5d c3 90:00 00 00 00 00 00 00 00 ]
    fffff8800131433d-fffff8800131434f  19 bytes - Ntfs! ?? ::NNGAKEGL::`string'+10e6 (+0x1e)
	[ 48 8b 48 58 48 83 c1 08:00 00 00 00 00 00 00 00 ]
    fffff88001314353-fffff88001314360  14 bytes - Ntfs! ?? ::NNGAKEGL::`string'+10fc (+0x16)
	[ 48 8b 5d 38 48 85 db 74:00 00 00 00 00 00 00 00 ]
    fffff88001314364-fffff8800131436c  9 bytes - Ntfs! ?? ::NNGAKEGL::`string'+110d (+0x11)
	[ 74 0e 33 d2 48 8b 8b b0:00 00 00 00 00 00 00 00 ]
    fffff8800131436f-fffff8800131439a  44 bytes - Ntfs! ?? ::NNGAKEGL::`string'+1118 (+0x0b)
	[ e8 7c 25 f8 ff f6 45 20:00 00 00 00 00 00 00 00 ]
    fffff8800131439e-fffff8800131442d  144 bytes - Ntfs! ?? ::NNGAKEGL::`string'+1147 (+0x2f)
	[ 48 85 c9 74 06 ff 15 8f:00 00 00 00 00 00 00 00 ]
    fffff8800131442f-fffff88001314444  22 bytes - Ntfs! ?? ::NNGAKEGL::`string'+11d8 (+0x91)
	[ 48 83 c4 20 41 5c 5d 5b:00 00 00 00 00 00 00 00 ]
    fffff88001314448-fffff88001314455  14 bytes - Ntfs! ?? ::NNGAKEGL::`string'+11f8 (+0x19)
	[ 33 db 48 3b cb 74 08 ff:00 00 00 00 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3610 errors : !Ntfs (fffff88001314000-fffff88001314ffe)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------

This indicates a possible bad cable between the hard disk and motherboard. Make sure all connections are secure. If they are, you may want to consider replacing the cable.

KevinJV · Apr 16, 2012

Alright, I don't think that is the problem. Could you check this dmp file for me?

writhziden · Apr 16, 2012

If only the shortcut took me all the way to your system... Unfortunately, the file provide is not an actual .dmp file but a shortcut to one on your system and only works if executed on your system. Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the full crash report.

If you do not think the last crash was hard disk cable related, I would recommend checking your memory for errors.

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.

KevinJV · Apr 17, 2012

I tried changing the cable and it still didn't make a difference. I have two more dmp files (I think) I would like you to check. This time it occurred while playing a different game. I will try those tests as well.

James7679 · Apr 17, 2012

Kevin, you need to run memtest as Writhziden already stated. He can check dmps for you all day, but if you want it fixed, you need to do what he asked. Run memtest and post results please.

KevinJV · Apr 17, 2012

Okay I have tried to run memtest. I downloaded it to a USB, ran the program, formatted it, etc and it does not run. Instead, it boots regularly and starts Windows, goes to the log in screen, etc. I have set the boot priority in the BIOS to the USB stick. Any thoughts as to why it does not run?

Trying a CD instead.

writhziden · Apr 17, 2012

Some systems have a hard time reading the boot information from a Memtest86+ USB device. Good idea to try the CD. Let us know how it goes.

You continue to have hard disk related crashes... Test to see if the hard disk itself is faulty.

I also suggest going through the steps in HD Diagnostic

If your hard disk manufacturer does not have a diagnostic utility or you are unable to use the diagnostic utility for any reason, run the short and long tests with SeaTools from Seagate. The link for SeaTools can be found in that link, as well.

KevinJV · Apr 18, 2012

I ran memtest86 from a CD last night and it worked. It ran 8 times and reported no errors. Seems like my memory is fine. Starting the HD Diagnostic now.

KevinJV · Apr 18, 2012

I just ran the HD Diagnostic test from Seagate (my hard drive manufacturer) and it came back clean with no issues. Could we test for driver interference next? Or maybe the settings of a program or device that could be causing it? Possibly even the BIOS version because one of the other BIOS updates from ASUS caused my computer to Blue screen.

writhziden · Apr 18, 2012

You could try flashing to a different BIOS. If you do, I recommend you use the DOS based version outside Windows or through the BIOS itself if you have that feature. That way, Windows will not be a factor. You do not want Windows to crash during a BIOS flash because any interruption to the flash can render the system completely useless.

To check if it is a service/application conflicting with your system: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

KevinJV · Apr 19, 2012

I tried the clean startup and still no success. I will try to flash a previous version of the BIOS that I used and I know is stable. I will let you know how it goes.

James7679 · Apr 19, 2012

Kevin, what devices do you have plugged in to your pc?

Solved BSOD playing League of Legends, error 0x000000f4

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Lurking

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Lurking

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer