Help with Analysis of this blue screen (G73Sw)

Sometimes during gameplay, computer just auto shut down and restart, but this time bluescreen appears and I've no idea what this is. Could anyone here help me figure out the problem?

 

Please use Blue screen of death (STOP error) information in dump files.
and post what is in the dump file as an attachment.

 

Below is the information from BlueScreenView

==================================================
Dump File : 021712-16473-01.dmp
Crash Time : 2012/2/17 10:19:26 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa7f`fffffef8
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`0487cbf3
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021712-16473-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 292,936
==================================================
Here's the attachment of the dump file
View attachment 021712-16473-01.zip

 

A STOP 0xA IRQL_NOT_LESS_OR_EQUAL is a generic memory corruption BSOD. NTOSKRNL.EXE, the main Windows 7 process, is likely not the cause (unless you have a corrupt Windows 7 installation) but more likely a victim of memory corruption that occurred earlier from some other source.

Are you running the ASUS Factory OS installation or have you performed a clean Windows install? If the latter, did you encounter any problems during installation?

I would recommend:

1) If the shutdowns and BSOD are recent, restore your system to an earlier time (before you experienced these issues) with Windows System Restore OR restore the latest stable Windows System Image from your backups.

2) checking your memory 2 sticks at a time with 3 passes of memtest86.

3) Running CHKDSK C: /F /R from the Command Line started by right-clicking on the icon and choosing "Run as administrator" from the popup menu and restarting OR
right-clicking on C: in Windows Explorer and choosing "Properties" from the popup menu, select the "Tools" tab and click on the "Check now" button. Be sure BOTH check disk options checkboxes are checked and restart.

4) If these fail to resolve the problem, try uninstalling or disabling any 3rd party Antivirus, AntiMalware, Firewall or Remote Access software you've installed to troubleshoot possible driver conflicts leading to memory corruption on your system.

 

I will try to analyze this dumpfile for you, if I can. I don't think my symbols file but I'll get back to you IF I have something.

 

Okay. Managed to analyze it:

Code:

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


Loading Dump File [C:\Users\%%\Desktop\021712-16473-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0480a000 PsLoadedModuleList = 0xfffff800`04a4f670
Debug session time: Fri Feb 17 22:16:04.106 2012 (GMT-5)
System Uptime: 0 days 5:59:16.074
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa7ffffffef8, 2, 1, fffff8000487cbf3}

Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by : tdx.sys ( tdx! ?? ::FNODOBFM::`string'+3150 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa7ffffffef8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000487cbf3, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80004ab9100
 fffffa7ffffffef8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireSpinLockAtDpcLevel+43
fffff800`0487cbf3 f0480fba2900    lock bts qword ptr [rcx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88005569270 -- (.trap 0xfffff88005569270)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa7ffffffef8
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000487cbf3 rsp=fffff88005569400 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffffa80066f76d0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeAcquireSpinLockAtDpcLevel+0x43:
fffff800`0487cbf3 f0480fba2900    lock bts qword ptr [rcx],0 ds:fffffa7f`fffffef8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800048861e9 to fffff80004886c40

STACK_TEXT:  
fffff880`05569128 fffff800`048861e9 : 00000000`0000000a fffffa7f`fffffef8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`05569130 fffff800`04884e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`009b3180 : nt!KiBugCheckDispatch+0x69
fffff880`05569270 fffff800`0487cbf3 : fffffa80`0a5db1a0 fffffa80`0706d001 fffff880`05569650 fffff800`048d285c : nt!KiPageFault+0x260
fffff880`05569400 fffff880`06439530 : fffffa80`0dc12798 00000000`00000000 fffffa7f`fffffef0 fffffa80`0de83910 : nt!KeAcquireSpinLockAtDpcLevel+0x43
fffff880`05569450 fffff880`06434283 : fffffa80`0de83910 fffffa80`0de83910 fffffa80`0de83910 fffffa80`0de83910 : tdx! ?? ::FNODOBFM::`string'+0x3150
fffff880`05569520 fffff880`06434b2d : 00000000`00000000 fffff880`055695c0 00000000`00000000 fffffa80`0a5c0848 : tdx!TdxDeleteTransportAddress+0x63
fffff880`05569560 fffff880`01fe9bbb : 00000000`00000000 fffff800`04898a61 fffa8007`72e85000 fffffa80`075e9aff : tdx!TdxTdiDispatchCleanup+0x4bd
fffff880`05569600 00000000`00000000 : fffff800`04898a61 fffa8007`72e85000 fffffa80`075e9aff fffffa80`0a5db101 : kl1+0x1babbb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tdx! ?? ::FNODOBFM::`string'+3150
fffff880`06439530 488d150963ffff  lea     rdx,[tdx! ?? ::FNODOBFM::`string' (fffff880`0642f840)]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  tdx! ?? ::FNODOBFM::`string'+3150

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79332

FAILURE_BUCKET_ID:  X64_0xA_tdx!_??_::FNODOBFM::_string_+3150

BUCKET_ID:  X64_0xA_tdx!_??_::FNODOBFM::_string_+3150

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

Judging by this, your problem is being caused by a tdx.sys driver. Based on very short and rushed research, this is linked to your WiFi drivers. Try updating those (get them from the official manufacturer sites).

 

If updating your WLAN driver fails to resolve the issue, tdx.sys causing BSOD - Fixed! - Windows 7 Forums indicates there may be conflicts between TDX.SYS and certain Antivirus products. It appears you are running Kapersky Antivirus. I would try Microsoft Security Essentials if I was in your situation.

 

Offtopic, isn't it nice how usefull a BSOD can actually be
Never underestimate this dump when having a BSOD!