Hey guys.
My PC has been going to BSOD lately while I've been playing WoW. Haven't changed any of my hardware configuration so I have no idea what's going on.
Attached is my minidump file from the last BSOD.
Any assistance as to the cause of the problem would be kindly appreciated!
Thanks!
Is Windows 7 . . .
- x64
- original OS
- MSDN version
- What is the age of system (hardware)? 1-3 years old
- What is the age of OS installation (have you re-installed the OS?) 4 months. Was running Vista Home Premium prior.
Edit: Sorry just saw the sticky.. Uploading the required files now.
Edit2: Have uploaded appropriate files.
BAsically three causes.
1- asacpi.sys
ASACPI.sys Sun Mar 27 22:30:36 2005
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
2-Your atheros ehternet driver. Re-install with newest version.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\Windows_NT6_BSOD_jcgriff2\122810-145392-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03010000 PsLoadedModuleList = 0xfffff800`0324de50
Debug session time: Mon Dec 27 08:49:55.720 2010 (GMT-5)
System Uptime: 0 days 11:02:12.500
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa80080d2ff8, 2, 0, fffff8000307771d}
Unable to load image \SystemRoot\system32\DRIVERS\L1E62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Unable to load image \SystemRoot\system32\DRIVERS\tmlwf.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tmlwf.sys
*** ERROR: Module load completed but symbols could not be loaded for tmlwf.sys
Probably caused by : L1E62x64.sys ( L1E62x64+6a10 )
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: fffffa80080d2ff8, 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: fffff8000307771d, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b80e0
fffffa80080d2ff8
CURRENT_IRQL: 2
FAULTING_IP:
nt!memmove+2ed
fffff800`0307771d 4c8b540ad0 mov r10,qword ptr [rdx+rcx-30h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: PBLauncher.exe
TRAP_FRAME: fffff880058c30b0 -- (.trap 0xfffff880058c30b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000013 rbx=0000000000000000 rcx=fffffa80092048f8
rdx=fffffffffeece730 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000307771d rsp=fffff880058c3248 rbp=0000000000605438
r8=0000000000605438 r9=6565724600f40000 r10=0000005c0070006d
r11=fffffa8008c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!memmove+0x2ed:
fffff800`0307771d 4c8b540ad0 mov r10,qword ptr [rdx+rcx-30h] ds:fffffa80`080d2ff8=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000307fca9 to fffff80003080740
STACK_TEXT:
fffff880`058c2f68 fffff800`0307fca9 : 00000000`0000000a fffffa80`080d2ff8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`058c2f70 fffff800`0307e920 : 00000000`00000002 fffffa80`07ace730 00000000`00000003 00000000`40452808 : nt!KiBugCheckDispatch+0x69
fffff880`058c30b0 fffff800`0307771d : fffff800`030ded17 00000000`00000000 fffffa80`07ace730 fffff800`00000000 : nt!KiPageFault+0x260
fffff880`058c3248 fffff800`030ded17 : 00000000`00000000 fffffa80`07ace730 fffff800`00000000 00000000`00000001 : nt!memmove+0x2ed
fffff880`058c3250 fffff800`030f4673 : fffff880`13000000 fffffa80`07ace730 00000000`000c0a81 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x13d87
fffff880`058c32f0 fffff800`035eecac : fffffa80`07ace730 fffffa80`00000000 00000000`00000001 fffffa80`04eec990 : nt! ?? ::FNODOBFM::`string'+0x34058
fffff880`058c33b0 fffff800`035ee593 : fffffa80`04eec990 fffffa80`04eec990 00000000`00000003 00000000`00000000 : hal!HalpDmaSyncMapBuffers+0x54
fffff880`058c3460 fffff800`035f14fb : fffffa80`05735848 fffffa80`04eec990 fffffa80`07ace730 00000000`40452808 : hal!HalpDmaMapScatterTransfer+0xa3
fffff880`058c34b0 fffff800`035f1472 : fffffa80`05735848 fffffa80`05735840 00000000`0000004c 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`058c3540 fffff800`035f094f : 00000000`00000000 fffff800`035edfb9 00000000`00000000 00000000`00000001 : hal!IoMapTransfer+0x8e
fffff880`058c3580 fffff800`035f113d : fffffa80`04df8050 fffffa80`04eec990 fffffa80`04eec901 00000000`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`058c3620 fffff800`035f071f : fffffa80`05735800 00000000`0000004c fffffa80`04eec990 fffffa80`07ace730 : hal!HalAllocateAdapterChannel+0x101
fffff880`058c3660 fffff880`01451831 : fffffa80`06d64540 fffffa80`0746fed0 fffff880`000000a0 fffff880`058c36e0 : hal!HalBuildScatterGatherList+0x2f3
fffff880`058c36d0 fffff880`04070a10 : fffffa80`04df81a0 fffff880`02d98d13 fffffa80`0572cc00 fffffa80`0746fed0 : ndis!NdisMAllocateNetBufferSGList+0x181
fffff880`058c3770 fffffa80`04df81a0 : fffff880`02d98d13 fffffa80`0572cc00 fffffa80`0746fed0 fffffa80`05735800 : L1E62x64+0x6a10
fffff880`058c3778 fffff880`02d98d13 : fffffa80`0572cc00 fffffa80`0746fed0 fffffa80`05735800 fffffa80`000001c0 : 0xfffffa80`04df81a0
fffff880`058c3780 fffffa80`0572cc00 : fffffa80`0746fed0 fffffa80`05735800 fffffa80`000001c0 00000000`00000000 : tmlwf+0x17d13
fffff880`058c3788 fffffa80`0746fed0 : fffffa80`05735800 fffffa80`000001c0 00000000`00000000 00000000`00000000 : 0xfffffa80`0572cc00
fffff880`058c3790 fffffa80`05735800 : fffffa80`000001c0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0746fed0
fffff880`058c3798 fffffa80`000001c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`05735800
fffff880`058c37a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0626f180 : 0xfffffa80`000001c0
STACK_COMMAND: kb
FOLLOWUP_IP:
L1E62x64+6a10
fffff880`04070a10 ?? ???
SYMBOL_STACK_INDEX: e
SYMBOL_NAME: L1E62x64+6a10
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: L1E62x64
IMAGE_NAME: L1E62x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a30a802
FAILURE_BUCKET_ID: X64_0xA_L1E62x64+6a10
BUCKET_ID: X64_0xA_L1E62x64+6a10
Followup: MachineOwner
---------
3-old drivers
Code:
ASACPI.sys 3/27/2005 21:30:36 0x42476c4c fffff880`041e8000 fffff880`041f0000 0x00008000
RTCore64.sys 5/25/2005 1:39:12 0x42941d90 fffff880`081d1000 fffff880`081d7000 0x00006000
spldr.sys 5/11/2009 11:56:27 0x4a0858bb fffff880`015dc000 fffff880`015e4000 0x00008000
GEARAspiWDM.sys 5/18/2009 7:17:04 0x4a1151c0 fffff880`03fe2000 fffff880`03fef000 0x0000d000
amdxata.sys 5/19/2009 12:56:59 0x4a12f2eb fffff880`00c2a000 fffff880`00c35000 0x0000b000
L1E62x64.sys 6/11/2009 1:45:22 0x4a30a802 fffff880`0406a000 fffff880`0407c000 0x00012000
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Ken J
Quote