Hi! I've got a BSOD problem with my pc. After changing the CPU and graphic card, i have sometimes a BSOD with a reboot. Need help.
My windows 7:
- x64
- full pro version
- Age of system - 2 year
- Age of OS installation - 5 months
You have several problems
1-ASACPI.SYS (5 years old +) is a huge BSOD cause.
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-Old drivers
Code:
ASACPI.sys fffff880`049fe000 0x00008000 3/27/2005 21:30:36 0x42476c4c fffff880`049f6000
IntcHdmi.sys fffff880`04f20000 0x00024000 6/6/2007 18:23:23 0x466741eb fffff880`04efc000
yk60x64.sys fffff880`02dec000 0x00065000 12/6/2007 08:50:34 0x4757fe2a fffff880`02d87000
tap0901.sys fffff880`02c93000 0x0000d000 10/8/2008 00:15:10 0x48ec41de fffff880`02c86000
dump_iaStorV.sys fffff880`03bda000 0x0011e000 4/8/2009 11:57:17 0x49dcd76d fffff880`03abc000
iaStorV.sys fffff880`011f1000 0x0011e000 4/8/2009 11:57:17 0x49dcd76d fffff880`010d3000
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 manufacturer links are on this page: Drivers and Downloads
3-Lavasoft ADaware the cause of these was Lbd.sys part of adaware. Iwould remove it
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\112110-21372-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a16000 PsLoadedModuleList = 0xfffff800`02c53e50
Debug session time: Sun Nov 21 04:54:50.486 2010 (GMT-5)
System Uptime: 20 days 15:05:20.172
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {20, 2, 1, fffff80002a8d203}
*** WARNING: Unable to verify timestamp for Lbd.sys
*** ERROR: Module load completed but symbols could not be loaded for Lbd.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnection+255 )
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: 0000000000000020, 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: fffff80002a8d203, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbe0e0
0000000000000020
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeAcquireSpinLockAtDpcLevel+43
fffff800`02a8d203 f0480fba2900 lock bts qword ptr [rcx],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: emule.exe
TRAP_FRAME: fffff880046a0ec0 -- (.trap 0xfffff880046a0ec0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000020
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a8d203 rsp=fffff880046a1050 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffffa800600e020
r11=fffff88001945db0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeAcquireSpinLockAtDpcLevel+0x43:
fffff800`02a8d203 f0480fba2900 lock bts qword ptr [rcx],0 ds:00000000`00000020=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a85ca9 to fffff80002a86740
STACK_TEXT:
fffff880`046a0d78 fffff800`02a85ca9 : 00000000`0000000a 00000000`00000020 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`046a0d80 fffff800`02a84920 : 00000000`000f01ff fffff800`02c00e80 fffffa80`02440840 fffffa80`02f1c260 : nt!KiBugCheckDispatch+0x69
fffff880`046a0ec0 fffff800`02a8d203 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`046a1050 fffff880`0190e54d : fffffa80`076ad010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAcquireSpinLockAtDpcLevel+0x43
fffff880`046a10a0 fffff880`0193332c : fffffa80`076ad010 00000000`00000000 fffffa80`076ad2f8 00000000`00000000 : tcpip!NeedToOffloadConnection+0x2d
fffff880`046a10e0 fffff880`0187f313 : fffffa80`076ad010 00000000`00000024 00000000`00000000 fffff800`02d9c196 : tcpip!DoStateBasedProcessing+0x8c
fffff880`046a1110 fffff880`0187f347 : fffffa80`076ad010 00000000`00000000 fffff880`046a11c0 fffff800`02bba4d3 : tcpip!OlmNotifyRequest+0xd3
fffff880`046a1140 fffff880`01875de7 : fffff880`046a1420 fffffa80`076ad010 00000000`00000000 00000000`00000000 : tcpip!OlmNotifySend+0x17
fffff880`046a1180 fffff880`01875e7b : 00000000`000000e8 fffffa80`05e02f20 fffffa80`04b3cb60 fffff880`010ac090 : tcpip!TcpEnqueueTcbSend+0x3f7
fffff880`046a1220 fffff800`02a95e5a : fffffa80`09953920 00000000`00000011 00000000`00000000 fffffa80`09953a38 : tcpip!TcpTlConnectionSendCalloutRoutine+0x1b
fffff880`046a1250 fffff880`0187bdaa : fffff880`01875e60 fffff880`046a1360 fffffa80`04d59300 fffff880`010b0f9f : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`046a1330 fffff880`010badf5 : fffffa80`04d59360 fffffa80`095ffad0 00000000`00000024 00000000`00000000 : tcpip!TcpTlConnectionSend+0x7a
fffff880`046a13a0 fffff880`010ad77f : fffffa80`095ffad0 fffff880`046a1ca0 00000000`00000024 fffffa80`095ffad0 : tdx!TdxSendConnection+0x255
fffff880`046a1480 fffff880`01097ebd : fffffa80`04b6b490 00000000`11aba4e8 fffff880`046a18b0 fffffa80`0c23a8c0 : tdx! ?? ::FNODOBFM::`string'+0x8a5
fffff880`046a14b0 fffffa80`04b6b490 : 00000000`11aba4e8 fffff880`046a18b0 fffffa80`0c23a8c0 fffffa80`095ffd40 : Lbd+0x2ebd
fffff880`046a14b8 00000000`11aba4e8 : fffff880`046a18b0 fffffa80`0c23a8c0 fffffa80`095ffd40 fffff880`03d28d55 : 0xfffffa80`04b6b490
fffff880`046a14c0 fffff880`046a18b0 : fffffa80`0c23a8c0 fffffa80`095ffd40 fffff880`03d28d55 fffffa80`08066360 : 0x11aba4e8
fffff880`046a14c8 fffffa80`0c23a8c0 : fffffa80`095ffd40 fffff880`03d28d55 fffffa80`08066360 fffff880`046a1ca0 : 0xfffff880`046a18b0
fffff880`046a14d0 fffffa80`095ffd40 : fffff880`03d28d55 fffffa80`08066360 fffff880`046a1ca0 00000000`00000024 : 0xfffffa80`0c23a8c0
fffff880`046a14d8 fffff880`03d28d55 : fffffa80`08066360 fffff880`046a1ca0 00000000`00000024 00000000`00000000 : 0xfffffa80`095ffd40
fffff880`046a14e0 fffff880`03cfc423 : fffff880`046a1a88 fffffa80`02b4df20 fffffa80`0612c9a0 fffffa80`086ba010 : afd! ?? ::GFJBLGFE::`string'+0x708e
fffff880`046a16a0 fffff800`02da1473 : 00000000`00000024 fffffa80`02b4df20 00000000`0039d370 fffff800`02ff9b01 : afd!AfdFastIoDeviceControl+0x413
fffff880`046a1a10 fffff800`02da1f66 : 00000000`00000000 00000000`00000240 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x373
fffff880`046a1b40 fffff800`02a85993 : fffffa80`04b3cb60 fffff880`046a1ca0 00000000`000be218 00000000`72da2450 : nt!NtDeviceIoControlFile+0x56
fffff880`046a1bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
STACK_COMMAND: kb
FOLLOWUP_IP:
tdx!TdxSendConnection+255
fffff880`010badf5 bf03010000 mov edi,103h
SYMBOL_STACK_INDEX: c
SYMBOL_NAME: tdx!TdxSendConnection+255
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tdx
IMAGE_NAME: tdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc16b
FAILURE_BUCKET_ID: X64_0xA_tdx!TdxSendConnection+255
BUCKET_ID: X64_0xA_tdx!TdxSendConnection+255
Followup: MachineOwner
---------
Quote