Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD playing multiplayer games, ntoskrnl and afd.sys


15 Jan 2012   #1

Windows 7 x64 Home edition
 
 
BSOD playing multiplayer games, ntoskrnl and afd.sys

I have recently built my own computer and I have been getting a lot of blue screens playing online. Starcraft 2 and League of legends.

I have tested my ram and done chkdsk.exe /f they came out clean.

I have attached a few minidumps for help.

My System SpecsSystem Spec
.

15 Jan 2012   #2

Windows 7 x64 Home edition
 
 

x86 Windows 7 home edition
Corsair 2x4 240pin ram
EVGA 580 classified edition
Intel i7-2600k@3.4
Western digital 500g 7200 rpm HDD

full retail parts, brand new
My System SpecsSystem Spec
16 Jan 2012   #3

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011312-36005-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c55670 Debug session time: Fri Jan 13 19:18:31.703 2012 (UTC - 7:00) System Uptime: 0 days 0:04:55.451 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {101, 2, 0, fffff80002ac7e1e} Probably caused by : ntkrnlmp.exe ( nt!KeContextFromKframes+11a ) Followup: MachineOwner --------- 1: 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: 0000000000000101, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff80002ac7e1e, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbf100 0000000000000101 CURRENT_IRQL: 2 FAULTING_IP: nt!KeContextFromKframes+11a fffff800`02ac7e1e 488b8200010000 mov rax,qword ptr [rdx+100h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff8800527aed0 -- (.trap 0xfffff8800527aed0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8800527b168 rbx=0000000000000000 rcx=fffffa800687fb60 rdx=fffff880009f50c0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a8f46f rsp=fffff8800527b068 rbp=fffffa800687fb60 r8=fffffa80065eb850 r9=0000000000000000 r10=0000000000000001 r11=fffff880009ea180 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac pe nc nt!KiSwapContext+0xf: fffff800`02a8f46f 0f29742430 movaps xmmword ptr [rsp+30h],xmm6 ss:0018:fffff880`0527b098=0000000000000001fffff80002a969e2 Resetting default scope EXCEPTION_RECORD: fffff8800527ae28 -- (.exr 0xfffff8800527ae28) ExceptionAddress: fffff80002a8f46f (nt!KiSwapContext+0x000000000000000f) ExceptionCode: 10000001 ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 LAST_CONTROL_TRANSFER: from fffff80002a8c1e9 to fffff80002a8cc40 STACK_TEXT: fffff880`0527a338 fffff800`02a8c1e9 : 00000000`0000000a 00000000`00000101 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0527a340 fffff800`02a8ae60 : fffffa80`0687fb60 fffffa80`0687fb60 ff00fa80`00000000 fffff880`0527a680 : nt!KiBugCheckDispatch+0x69 fffff880`0527a480 fffff800`02ac7e1e : 00000000`00000000 fffff800`02ab5055 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0527a610 fffff800`02ac82ff : fffff880`0527ae28 fffff880`0527ab80 fffff880`0527aed0 fffff880`009ea180 : nt!KeContextFromKframes+0x11a fffff880`0527a650 fffff800`02a8c2c2 : fffff880`0527ae28 fffffa80`0687fb60 fffff880`0527aed0 fffffa80`0687fc20 : nt!KiDispatchException+0xd3 fffff880`0527acf0 fffff800`02a8abca : 00000000`00000001 00000000`00000001 00000000`00002928 00000000`00000db8 : nt!KiExceptionDispatch+0xc2 fffff880`0527aed0 fffff800`02a8f46f : fffff880`0527b1d8 fffff900`c00bf010 00000000`00000000 00000000`00000002 : nt!KiGeneralProtectionFault+0x10a fffff880`0527b068 fffff800`02a91f32 : fffff960`0060a04e fffffa80`0687fb60 fffff880`00000000 00000000`000003e8 : nt!KiSwapContext+0xf fffff880`0527b1a8 fffff800`02a9474f : fffff900`c00c0fa0 fffffa80`0687fb60 00000000`00000000 fffff800`02a92fda : nt!KiCommitThreadWait+0x1d2 fffff880`0527b238 fffff800`02aaecef : 00000000`00000001 00000000`00000011 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x19f fffff880`0527b2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!AlpcpSignalAndWait+0x8f STACK_COMMAND: kb FOLLOWUP_IP: nt!KeContextFromKframes+11a fffff800`02ac7e1e 488b8200010000 mov rax,qword ptr [rdx+100h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KeContextFromKframes+11a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0xA_nt!KeContextFromKframes+11a BUCKET_ID: X64_0xA_nt!KeContextFromKframes+11a Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011312-16068-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`03099670 Debug session time: Fri Jan 13 22:49:47.897 2012 (UTC - 7:00) System Uptime: 0 days 0:24:13.756 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {1000c0103, 2, 1, fffff88005dce4e6} Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athrx.sys *** ERROR: Module load completed but symbols could not be loaded for athrx.sys Probably caused by : hardware ( nwifi!memcpy+66 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: 00000001000c0103, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff88005dce4e6, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003103100 00000001000c0103 CURRENT_IRQL: 2 FAULTING_IP: nwifi!memcpy+66 fffff880`05dce4e6 014883 add dword ptr [rax-7Dh],ecx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff80000b9baa0 -- (.trap 0xfffff80000b9baa0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000001000c0180 rbx=0000000000000000 rcx=fffff880029ccf50 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88005dce4e6 rsp=fffff80000b9bc38 rbp=0000000000000008 r8=0000000000000013 r9=0000000000000002 r10=0000000000000000 r11=fffff880029ccf50 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nwifi!memcpy+0x66: fffff880`05dce4e6 014883 add dword ptr [rax-7Dh],ecx ds:bd00:00000001`000c0103=???????? Resetting default scope MISALIGNED_IP: nwifi!memcpy+66 fffff880`05dce4e6 014883 add dword ptr [rax-7Dh],ecx LAST_CONTROL_TRANSFER: from fffff80002ed01e9 to fffff80002ed0c40 STACK_TEXT: fffff800`00b9b958 fffff800`02ed01e9 : 00000000`0000000a 00000001`000c0103 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff800`00b9b960 fffff800`02ecee60 : 00000000`00000000 fffff800`00b9c990 fffffa80`0aa8c000 fffff800`00b9bdb0 : nt!KiBugCheckDispatch+0x69 fffff800`00b9baa0 fffff880`05dce4e6 : fffff880`05da352d 00000000`00000000 00000000`00000020 00000006`00b9bd00 : nt!KiPageFault+0x260 fffff800`00b9bc38 fffff880`05da352d : 00000000`00000000 00000000`00000020 00000006`00b9bd00 00000000`00000000 : nwifi!memcpy+0x66 fffff800`00b9bc40 fffff880`05da2f10 : fffff800`030712b8 fffffa80`0b558980 00000000`00000013 fffffa80`0a3b8cd0 : nwifi!NwfUpcallMsg+0x689 fffff800`00b9bd20 fffff880`05dbd9fe : fffffa80`0b8e2660 fffffa80`00000000 00000000`00000000 00000000`4003000c : nwifi!NwfUpcallMsg+0x6c fffff800`00b9bd90 fffff880`05dbd4f7 : 00000000`00000000 fffffa80`0b8e2660 fffffa80`0a3b8d30 fffffa80`0a3988f0 : nwifi!ExtSTAIndicateNetworkChange+0x2ba fffff800`00b9bdf0 fffff880`05d98379 : fffffa80`0a3b7020 00000000`00000002 00000000`00000000 00000000`00000000 : nwifi!ExtSTADriverEntry+0x513 fffff800`00b9bf60 fffff880`05d9fb5e : fffffa80`0b17ed40 fffff880`018505e7 fffffa80`0a63d5d0 fffffa80`0a452030 : nwifi!Dot11ForwardStatusIndication+0x4d fffff800`00b9bf90 fffff880`0185b7e0 : fffffa80`0b17ec90 00000000`74617453 00000000`4003000c fffffa80`0b17ec90 : nwifi!Pt6Status+0x176 fffff800`00b9bfd0 fffff880`031d3e85 : fffffa80`0a44fa02 fffff880`00000013 fffff800`00b9c1d0 fffffa80`0b8e2660 : ndis!NdisFIndicateStatus+0x260 fffff800`00b9c070 fffff880`018d99cf : 00000000`03054c00 fffff800`00b9c1d0 fffffa80`0a63d5d0 00000000`4003000c : vwififlt!FilterStatus+0xb9 fffff800`00b9c0a0 fffff880`04c3737a : 00000000`00000101 fffff880`04d17002 fffff800`03054c00 00000000`00000000 : ndis!NdisMIndicateStatusEx+0x28f fffff800`00b9c150 00000000`00000101 : fffff880`04d17002 fffff800`03054c00 00000000`00000000 00000000`00162eae : athrx+0x537a fffff800`00b9c158 fffff880`04d17002 : fffff800`03054c00 00000000`00000000 00000000`00162eae 00000000`00000047 : 0x101 fffff800`00b9c160 fffff800`03054c00 : 00000000`00000000 00000000`00162eae 00000000`00000047 fffff800`03046e80 : athrx+0xe5002 fffff800`00b9c168 00000000`00000000 : 00000000`00162eae 00000000`00000047 fffff800`03046e80 fffff880`04c61369 : nt!KiNode0 STACK_COMMAND: kb FOLLOWUP_IP: nwifi!memcpy+66 fffff880`05dce4e6 014883 add dword ptr [rax-7Dh],ecx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nwifi!memcpy+66 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nwifi.sys BUCKET_ID: X64_IP_MISALIGNED_nwifi.sys Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011312-18829-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e4c000 PsLoadedModuleList = 0xfffff800`03091670 Debug session time: Fri Jan 13 22:53:38.436 2012 (UTC - 7:00) System Uptime: 0 days 0:03:08.295 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffffffb70f96d9, 0, fffff80002f1de6c, 5} Could not read faulting driver name Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+1c4c ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffffffb70f96d9, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002f1de6c, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fb100 ffffffffb70f96d9 FAULTING_IP: nt! ?? ::FNODOBFM::`string'+1c4c fffff800`02f1de6c ff9090900fb7 call qword ptr [rax-48F06F70h] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800af0ef30 -- (.trap 0xfffff8800af0ef30) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000649 rbx=0000000000000000 rcx=fffff8800af0f680 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002f1de6c rsp=fffff8800af0f0c0 rbp=fffff8800af0f790 r8=0000000000000000 r9=0000000000000000 r10=000000000010005f r11=fffff8800af0f120 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt! ?? ::FNODOBFM::`string'+0x1c4c: fffff800`02f1de6c ff9090900fb7 call qword ptr [rax-48F06F70h] ds:ffffffff`b70f96d9=???????????????? Resetting default scope EXCEPTION_RECORD: fffff8800af0fa38 -- (.exr 0xfffff8800af0fa38) ExceptionAddress: 00000000687cd3e4 ExceptionCode: 10000004 ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000000006a4 MISALIGNED_IP: nt! ?? ::FNODOBFM::`string'+1c4c fffff800`02f1de6c ff9090900fb7 call qword ptr [rax-48F06F70h] LAST_CONTROL_TRANSFER: from fffff80002e733bf to fffff80002ec8c40 STACK_TEXT: fffff880`0af0edc8 fffff800`02e733bf : 00000000`00000050 ffffffff`b70f96d9 00000000`00000000 fffff880`0af0ef30 : nt!KeBugCheckEx fffff880`0af0edd0 fffff800`02ec6d6e : 00000000`00000000 ffffffff`b70f96d9 fffff800`0303ee00 00000000`00000050 : nt! ?? ::FNODOBFM::`string'+0x44791 fffff880`0af0ef30 fffff800`02f1de6c : 00000000`04221000 fffff800`02ebe398 00000000`00000000 fffffa80`03949860 : nt!KiPageFault+0x16e fffff880`0af0f0c0 fffff800`02f042dc : fffff880`0af0fa38 fffff880`0af0fae0 00000000`0000167c fffff800`00000003 : nt! ?? ::FNODOBFM::`string'+0x1c4c fffff880`0af0f0f0 fffff800`02ec82c2 : fffff880`0af0fa38 00000000`00a35674 fffff880`0af0fae0 00000000`000006a0 : nt!KiDispatchException+0xb0 fffff880`0af0f900 fffff800`02ec6e3a : 00000000`00000000 00000000`000006a4 00000000`00773101 00000000`00a35674 : nt!KiExceptionDispatch+0xc2 fffff880`0af0fae0 00000000`687cd3e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a 00000000`0046ef4c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x687cd3e4 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+1c4c fffff800`02f1de6c ff9090900fb7 call qword ptr [rax-48F06F70h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1c4c FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011512-19843-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`030a0670 Debug session time: Sun Jan 15 15:36:23.859 2012 (UTC - 7:00) System Uptime: 0 days 1:36:19.718 Loading Kernel Symbols ............................................................... ....................................................... Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a039d89b68f689, b3b7465eede5c5df, fffff80002eafa00, 1} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a039d89b68f689, Reserved Arg2: b3b7465eede5c5df, Reserved Arg3: fffff80002eafa00, Failure type dependent information Arg4: 0000000000000001, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002ed7c40 STACK_TEXT: fffff880`03769498 00000000`00000000 : 00000000`00000109 a3a039d8`9b68f689 b3b7465e`ede5c5df fffff800`02eafa00 : nt!KeBugCheckEx STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: BAD_STACK Followup: MachineOwner ---------
  5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011512-16707-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03090670 Debug session time: Sun Jan 15 22:01:50.413 2012 (UTC - 7:00) System Uptime: 0 days 0:24:58.271 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {28, 2, 0, fffff80002f0ebd0} Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 ) Followup: MachineOwner --------- 7: 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: 0000000000000028, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff80002f0ebd0, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fa100 0000000000000028 CURRENT_IRQL: 2 FAULTING_IP: nt!MiFindNodeOrParent+0 fffff800`02f0ebd0 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: chrome.exe TRAP_FRAME: fffff8800928db10 -- (.trap 0xfffff8800928db10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002f0ebd0 rsp=fffff8800928dca8 rbp=0000000000000000 r8=fffff8800928dcf0 r9=0000000000000000 r10=fffffa800ae5ed20 r11=fffffa800ae59c90 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!MiFindNodeOrParent: fffff800`02f0ebd0 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h ds:1b90:00000000`00000028=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ec71e9 to fffff80002ec7c40 STACK_TEXT: fffff880`0928d9c8 fffff800`02ec71e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0928d9d0 fffff800`02ec5e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0ae5ed68 : nt!KiBugCheckDispatch+0x69 fffff880`0928db10 fffff800`02f0ebd0 : fffff800`02f10d67 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0928dca8 fffff800`02f10d67 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFindNodeOrParent fffff880`0928dcb0 fffff800`02f10e3d : 00000000`63416d4d 00000000`00000002 00000000`00000000 fffffa80`074adec8 : nt!MiLocateAddressInTree+0x17 fffff880`0928dce0 fffff800`02f10eb8 : 00000000`00000000 fffffa80`0b47f000 fffffa80`0a2585e0 fffffa80`0ae5edd8 : nt!MiGetSharedProtosAtDpcLevel+0xbd fffff880`0928dd30 fffff800`02e5f0cb : 00000000`00000000 fffff800`02fc8b2f 00000000`00000010 00000000`00000286 : nt!MiGetSharedProtos+0x18 fffff880`0928dd60 fffff800`02fc8bb0 : 00000000`00000000 fffffa80`0ae5ed60 fffffa80`06e6e001 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x938b fffff880`0928dd90 fffff800`02fc8d90 : fffffa80`074adb30 00000003`00000000 fffffa80`0ae5ed20 fffffa80`0ae5edd8 : nt!MiEmptyPageAccessLog+0x160 fffff880`0928de00 fffff800`02fc8f96 : fffffa80`06d23000 fffff680`0031a0c8 fffff680`0031a0c8 fffff800`02ee877d : nt!MiAllocateAccessLog+0x80 fffff880`0928de30 fffff800`02f371cd : 00000003`00000000 5a800001`4af88025 fffff700`010831c8 fffff680`0031a0c8 : nt!MiLogPageAccess+0x46 fffff880`0928de80 fffff800`02e99596 : fffffa80`074adb30 fffffa80`00000000 fffff880`0000014a fffff800`00000000 : nt! ?? ::FNODOBFM::`string'+0x3609d fffff880`0928e730 fffff800`0319db1a : fffff8a0`06dada70 fffff880`0928eae0 00000000`00000000 fffffa80`06e6e060 : nt!MmCleanProcessAddressSpace+0x96 fffff880`0928e780 fffff800`0318109d : 00000000`c0000005 00000000`00000001 00000000`7efd8000 fffffa80`06b83b60 : nt!PspExitThread+0x56a fffff880`0928e880 fffff800`02ebb3fa : fffffa80`07476460 fffffa80`073ae670 00000000`00000000 fffffa80`07476390 : nt!PsExitSpecialApc+0x1d fffff880`0928e8b0 fffff800`02ebb740 : 00000000`00e80c00 fffff880`0928e930 fffff800`03181010 00000000`00000001 : nt!KiDeliverApc+0x2ca fffff880`0928e930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiFindNodeOrParent+0 fffff800`02f0ebd0 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiFindNodeOrParent+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiFindNodeOrParent+0 BUCKET_ID: X64_0xA_nt!MiFindNodeOrParent+0 Followup: MachineOwner ---------
  6. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011512-14164-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`0305e670 Debug session time: Sun Jan 15 22:05:06.152 2012 (UTC - 7:00) System Uptime: 0 days 0:02:08.011 Loading Kernel Symbols ............................................................... ................................................................ ......... Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 406f8, fffff80002ec1669} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000406f8 Arg4: fffff80002ec1669 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: WerFault.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002e951e9 to fffff80002e95c40 STACK_TEXT: fffff880`0336bde8 fffff800`02e951e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx fffff880`0336bdf0 fffff800`02e936b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0336bf30 fffff800`02ec1669 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeQueryCurrentStackInformation+0xd9 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`02e936b2 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner ---------
  7. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011512-17128-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`03095670 Debug session time: Sun Jan 15 22:12:33.681 2012 (UTC - 7:00) System Uptime: 0 days 0:06:12.540 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffab0062cda78, 2, 0, fffff80002e76fe7} Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athrx.sys *** ERROR: Module load completed but symbols could not be loaded for athrx.sys Probably caused by : athrx.sys ( athrx+38420 ) Followup: MachineOwner --------- 0: 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: fffffab0062cda78, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff80002e76fe7, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ff100 fffffab0062cda78 CURRENT_IRQL: 2 FAULTING_IP: nt! ?? ::FNODOBFM::`string'+44363 fffff800`02e76fe7 488b4128 mov rax,qword ptr [rcx+28h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: svchost.exe TRAP_FRAME: fffff80000ba1df0 -- (.trap 0xfffff80000ba1df0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa800a3ad030 rbx=0000000000000000 rcx=fffffa800a3ad030 rdx=fffffa800a596e28 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88004e58420 rsp=fffff80000ba1f88 rbp=0000000000000000 r8=fffff80000ba2118 r9=0000000000000080 r10=fffff88004f8d098 r11=00000000000000ff r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc athrx+0x38420: fffff880`04e58420 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ecc1e9 to fffff80002eccc40 STACK_TEXT: fffff800`00ba19b8 fffff800`02ecc1e9 : 00000000`0000000a fffffab0`062cda78 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff800`00ba19c0 fffff800`02ecae60 : 00000000`00000000 fffff880`054f2045 00000000`00000001 fffff6fb`7dbf1000 : nt!KiBugCheckDispatch+0x69 fffff800`00ba1b00 fffff800`02e76fe7 : 00000000`00000000 fffff800`02e0a6e5 00000000`00000000 00000000`00000f00 : nt!KiPageFault+0x260 fffff800`00ba1c90 fffff800`02ecad6e : fffff880`04e219c0 fffffa80`0a5a45d8 00000000`00000000 fffffa80`0a2b91a0 : nt! ?? ::FNODOBFM::`string'+0x44363 fffff800`00ba1df0 fffff880`04e58420 : fffff880`04e57628 fffffa80`0a3ad030 fffff880`04e41e33 fffffa80`0a3fb8d0 : nt!KiPageFault+0x16e fffff800`00ba1f88 fffff880`04e57628 : fffffa80`0a3ad030 fffff880`04e41e33 fffffa80`0a3fb8d0 fffffa80`0a3aa650 : athrx+0x38420 fffff800`00ba1f90 fffffa80`0a3ad030 : fffff880`04e41e33 fffffa80`0a3fb8d0 fffffa80`0a3aa650 fffffa80`0a3ad030 : athrx+0x37628 fffff800`00ba1f98 fffff880`04e41e33 : fffffa80`0a3fb8d0 fffffa80`0a3aa650 fffffa80`0a3ad030 fffffa80`0a3aa470 : 0xfffffa80`0a3ad030 fffff800`00ba1fa0 fffffa80`0a3fb8d0 : fffffa80`0a3aa650 fffffa80`0a3ad030 fffffa80`0a3aa470 fffff800`00000000 : athrx+0x21e33 fffff800`00ba1fa8 fffffa80`0a3aa650 : fffffa80`0a3ad030 fffffa80`0a3aa470 fffff800`00000000 fffff880`04e41891 : 0xfffffa80`0a3fb8d0 fffff800`00ba1fb0 fffffa80`0a3ad030 : fffffa80`0a3aa470 fffff800`00000000 fffff880`04e41891 fffffa80`0a3ad030 : 0xfffffa80`0a3aa650 fffff800`00ba1fb8 fffffa80`0a3aa470 : fffff800`00000000 fffff880`04e41891 fffffa80`0a3ad030 fffffa80`0a596e28 : 0xfffffa80`0a3ad030 fffff800`00ba1fc0 fffff800`00000000 : fffff880`04e41891 fffffa80`0a3ad030 fffffa80`0a596e28 00000000`00000008 : 0xfffffa80`0a3aa470 fffff800`00ba1fc8 fffff880`04e41891 : fffffa80`0a3ad030 fffffa80`0a596e28 00000000`00000008 00000000`00000080 : 0xfffff800`00000000 fffff800`00ba1fd0 fffffa80`0a3ad030 : fffffa80`0a596e28 00000000`00000008 00000000`00000080 fffff800`00ba2118 : athrx+0x21891 fffff800`00ba1fd8 fffffa80`0a596e28 : 00000000`00000008 00000000`00000080 fffff800`00ba2118 fffff880`0312d095 : 0xfffffa80`0a3ad030 fffff800`00ba1fe0 00000000`00000008 : 00000000`00000080 fffff800`00ba2118 fffff880`0312d095 fffffa80`0a3ad030 : 0xfffffa80`0a596e28 fffff800`00ba1fe8 00000000`00000080 : fffff800`00ba2118 fffff880`0312d095 fffffa80`0a3ad030 fffffa80`00000000 : 0x8 fffff800`00ba1ff0 fffff800`00ba2118 : fffff880`0312d095 fffffa80`0a3ad030 fffffa80`00000000 00000000`00000000 : 0x80 fffff800`00ba1ff8 fffff880`0312d095 : fffffa80`0a3ad030 fffffa80`00000000 00000000`00000000 fffff880`04ea59f2 : 0xfffff800`00ba2118 fffff800`00ba2000 fffff880`03130080 : fffff800`00ba2118 fffffa80`09a28f80 fffffa80`0715c800 fffff880`05503000 : afd!AfdReturnBuffer+0x85 fffff800`00ba2040 fffffa80`0a2b91a0 : fffffa80`0715c620 fffff880`01af37b0 00000000`00000000 fffff800`03057348 : afd!AfdBCommonChainedReceiveEventHandler+0x150 fffff800`00ba2180 fffffa80`0715c620 : fffff880`01af37b0 00000000`00000000 fffff800`03057348 00000000`00000000 : 0xfffffa80`0a2b91a0 fffff800`00ba2188 fffff880`01af37af : 00000000`00000000 fffff800`03057348 00000000`00000000 00000000`00000000 : 0xfffffa80`0715c620 fffff800`00ba2190 00000053`7dd5ba78 : bb00001b`29001a1a 00006978`00008101 00000000`000000c8 fffff880`00000000 : tcpip!UdpTlProviderSendMessages+0x10f fffff800`00ba2210 bb00001b`29001a1a : 00006978`00008101 00000000`000000c8 fffff880`00000000 fffff800`00ba2430 : 0x53`7dd5ba78 fffff800`00ba2218 00006978`00008101 : 00000000`000000c8 fffff880`00000000 fffff800`00ba2430 fffff800`00ba2430 : 0xbb00001b`29001a1a fffff800`00ba2220 00000000`000000c8 : fffff880`00000000 fffff800`00ba2430 fffff800`00ba2430 00000000`00000000 : 0x6978`00008101 fffff800`00ba2228 fffff880`00000000 : fffff800`00ba2430 fffff800`00ba2430 00000000`00000000 fffff880`04eda5ec : 0xc8 fffff800`00ba2230 fffff800`00ba2430 : fffff800`00ba2430 00000000`00000000 fffff880`04eda5ec fffffa80`0a395030 : 0xfffff880`00000000 fffff800`00ba2238 fffff800`00ba2430 : 00000000`00000000 fffff880`04eda5ec fffffa80`0a395030 fffffa80`0b93c030 : 0xfffff800`00ba2430 fffff800`00ba2240 00000000`00000000 : fffff880`04eda5ec fffffa80`0a395030 fffffa80`0b93c030 fffffa80`0a596e28 : 0xfffff800`00ba2430 STACK_COMMAND: kb FOLLOWUP_IP: athrx+38420 fffff880`04e58420 ?? ??? SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: athrx+38420 FOLLOWUP_NAME: MachineOwner MODULE_NAME: athrx IMAGE_NAME: athrx.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4af48d62 FAILURE_BUCKET_ID: X64_0xA_athrx+38420 BUCKET_ID: X64_0xA_athrx+38420 Followup: MachineOwner ---------
  8. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011512-17550-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e5f000 PsLoadedModuleList = 0xfffff800`030a4670 Debug session time: Sun Jan 15 22:13:43.752 2012 (UTC - 7:00) System Uptime: 0 days 0:00:27.611 Loading Kernel Symbols ............................................................... ................................................................ ............... Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff880016489e6, fffff88009845a80, 0} Probably caused by : hardware ( afd!AfdFastDatagramSend+3d6 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff880016489e6, Address of the instruction which caused the bugcheck Arg3: fffff88009845a80, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: afd!AfdFastDatagramSend+3d6 fffff880`016489e6 46a1fbff488b5728498b mov eax,dword ptr [8B4928578B48FFFBh] CONTEXT: fffff88009845a80 -- (.cxr 0xfffff88009845a80) rax=fffffa800b7c91b8 rbx=00000000000003dd rcx=0000000000000001 rdx=0000000000000c82 rsi=fffff88009846690 rdi=fffffa800b80cd00 rip=fffff880016489e6 rsp=fffff88009846460 rbp=fffff88009846b60 r8=fffffa800b80cd00 r9=0000000000000001 r10=fffffa800b80ce50 r11=0000000000000000 r12=0000000000000000 r13=fffffa800b7c97e0 r14=fffffa800b7c97e0 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 afd!AfdFastDatagramSend+0x3d6: fffff880`016489e6 46a1fbff488b5728498b mov eax,dword ptr [8B4928578B48FFFBh] ds:002b:8b492857`8b48fffb=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 MISALIGNED_IP: afd!AfdFastDatagramSend+3d6 fffff880`016489e6 46a1fbff488b5728498b mov eax,dword ptr [8B4928578B48FFFBh] LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880016489e6 STACK_TEXT: fffff880`09846460 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : afd!AfdFastDatagramSend+0x3d6 FOLLOWUP_IP: afd!AfdFastDatagramSend+3d6 fffff880`016489e6 46a1fbff488b5728498b mov eax,dword ptr [8B4928578B48FFFBh] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: afd!AfdFastDatagramSend+3d6 FOLLOWUP_NAME: MachineOwner DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .cxr 0xfffff88009845a80 ; kb MODULE_NAME: hardware IMAGE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner ---------
  9. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011512-14102-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03058670 Debug session time: Sun Jan 15 22:54:12.091 2012 (UTC - 7:00) System Uptime: 0 days 0:02:08.950 Loading Kernel Symbols ............................................................... ................................................................ ............... Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff80013007f10, 1, fffff80002eaecde, 2} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MiCompleteProtoPteFault+15e ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff80013007f10, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff80002eaecde, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c2100 fffff80013007f10 FAULTING_IP: nt!MiCompleteProtoPteFault+15e fffff800`02eaecde 65ff042510220000 inc dword ptr gs:[2210h] MM_INTERNAL_CODE: 2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: Steam.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800b097530 -- (.trap 0xfffff8800b097530) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff800030c2680 rbx=0000000000000000 rcx=0000000000000003 rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002eaecde rsp=fffff8800b0976c0 rbp=0000000000000000 r8=0000000000000046 r9=0000000186cd4000 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac po nc nt!MiCompleteProtoPteFault+0x15e: fffff800`02eaecde 65ff042510220000 inc dword ptr gs:[2210h] gs:00000000`00002210=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e3a3f0 to fffff80002e8fc40 STACK_TEXT: fffff880`0b0973c8 fffff800`02e3a3f0 : 00000000`00000050 fffff800`13007f10 00000000`00000001 fffff880`0b097530 : nt!KeBugCheckEx fffff880`0b0973d0 fffff800`02e8dd6e : 00000000`00000001 fffff800`13007f10 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x447c6 fffff880`0b097530 fffff800`02eaecde : fffff880`0000006a fffff800`02e928a4 fffff900`0000006a 00000000`00000000 : nt!KiPageFault+0x16e fffff880`0b0976c0 fffff800`02ec0faf : 00000001`86cd4860 00000001`86cd4121 fffffa80`049467c0 fffffa80`0bc64ec8 : nt!MiCompleteProtoPteFault+0x15e fffff880`0b097750 fffff800`02eae695 : 00000000`00000000 00000001`86cd4860 fffffa80`0bc5f060 fffffa80`0bc64ec8 : nt!MiResolveTransitionFault+0x32f fffff880`0b0977e0 fffff800`02ead053 : 00000000`00193d2a 00000000`3a045690 fffff680`001d0228 fffffa80`0bc64ec8 : nt!MiResolveProtoPteFault+0x325 fffff880`0b097870 fffff800`02e9cf19 : 00000000`00200200 00000000`3a045690 fffff880`0b097ab8 00000000`00000000 : nt!MiDispatchFault+0x1c3 fffff880`0b097980 fffff800`02e8dd6e : 00000000`00000008 00000000`3a045690 fffff880`0b097a01 00000000`0018df58 : nt!MmAccessFault+0x359 fffff880`0b097ae0 00000000`3a045690 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0018df0c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3a045690 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiCompleteProtoPteFault+15e fffff800`02eaecde 65ff042510220000 inc dword ptr gs:[2210h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiCompleteProtoPteFault+15e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MiCompleteProtoPteFault+15e BUCKET_ID: X64_0x50_nt!MiCompleteProtoPteFault+15e Followup: MachineOwner ---------
  10. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\skipfire15\011512-15256-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Mini Kernel Dump does not have process information Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address 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`02e10000 PsLoadedModuleList = 0xfffff800`03055670 Debug session time: Sun Jan 15 23:05:59.133 2012 (UTC - 7:00) System Uptime: 0 days 0:11:03.992 Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address Loading Kernel Symbols .Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff80002e8ae7b, 1, 0} ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002e8ae7b, The address that the exception occurred at Arg3: 0000000000000001, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: +3939393562626339 fffff800`02e8ae7b 0000 add byte ptr [rax],al EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 0000000000000000 WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 0000000000000000 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0x1E_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from fffff80002ed8588 to fffff80002e8cc40 STACK_TEXT: fffff880`0be7f0c8 fffff800`02ed8588 : 00000000`0000001e ffffffff`c0000005 fffff800`02e8ae7b 00000000`00000001 : 0xfffff800`02e8cc40 fffff880`0be7f0d0 00000000`0000001e : ffffffff`c0000005 fffff800`02e8ae7b 00000000`00000001 00000000`00000000 : 0xfffff800`02ed8588 fffff880`0be7f0d8 ffffffff`c0000005 : fffff800`02e8ae7b 00000000`00000001 00000000`00000000 00000000`3fff8001 : 0x1e fffff880`0be7f0e0 fffff800`02e8ae7b : 00000000`00000001 00000000`00000000 00000000`3fff8001 00004007`e50d0b00 : 0xffffffff`c0000005 fffff880`0be7f0e8 00000000`00000001 : 00000000`00000000 00000000`3fff8001 00004007`e50d0b00 400897f4`26000000 : 0xfffff800`02e8ae7b fffff880`0be7f0f0 00000000`00000000 : 00000000`3fff8001 00004007`e50d0b00 400897f4`26000000 96475a00`00000000 : 0x1 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: CORRUPT_MODULELIST Followup: MachineOwner ---------
Your crashes are pretty random, which usually points to a hardware, and many of your crashes do seem to be hardware related. The first set of hardware to check is memory modules. It may also be related to your wireless internet device, which should have its driver software updated to rule out driver problems.

Update your jswpslwfx.sys driver.

Also, update your athrx.sys driver.

Use Driver Reference Table - sysnative.com - MVP,
Drivers and Downloads,
Installing and updating drivers in 7,
Driver Install - Add Hardware Wizard,
and Driver Install - Device Manager
as references for finding drivers, driver manufacturers, updating driver procedures, installation procedures through the hardware wizard, and installation procedures through device manager respectively.

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

Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
My System SpecsSystem Spec
.


Reply

 BSOD playing multiplayer games, ntoskrnl and afd.sys




Thread Tools



Similar help and support threads for2: BSOD playing multiplayer games, ntoskrnl and afd.sys
Thread Forum
BSOD when playing games, ntoskrnl.exe BSOD Help and Support
Solved BSOD playing various games, ntoskrnl.exe BSOD Help and Support
BSOD Normally when playing Games but not always. (ntoskrnl.exe) BSOD Help and Support
BSOD NTOSKRNL.EXE while playing games etc BSOD Help and Support
BSOD: MOstly when playing online games, NTOSKRNL.EXE BSOD Help and Support
BSOD - BCC 124 while playing games - ntoskrnl.exe BSOD Help and Support
BSOD while playing games, ntoskrnl.exe BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:13 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33