BSOD with uTORRENT!!

abu46 said:

hello friends

i am facing a weierd problem with my system

i always get a BSOD in the morning when i leave my system on for downloading torrents via the utorrent client
other than that the system runs just fine when its connected to the internet, playing latest games, ps etc

i cannot imagine an app like utorrent causing BSODs

the only sw running during the BSOD are avast free antivirus, comodo free firewall and utorrent client version 2.2 (non beta)

heres my system specs

amd II x4 955be
asus m4a87td evo
asus eah 6850
2x2gb corsair ddr3 1333
corsair vx550w psu
win7 ultimate x64 with all the latest updates

the system is not overclocked in any way

also i recently formated my system

am using catalyst driver version 10.12(dont think i can downgrade to 10.11 with 6850)
also i have the latest chipset and LAN drivers (RealTekEthernet Controller Driver 7.21.531.2010)
was using virtual drive but have uinstalled it

kindly help me out here........

There are quite a few problems

1-asacpi.sys 2005 version A huge cause of bsods
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- Avast Antivirus remove and replace with Microsoft Security Essentials and the win 7 firewall

http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/


3-Your video driver remove using these instructions

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

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\010311-13962-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`02c07000 PsLoadedModuleList = 0xfffff800`02e44e50
Debug session time: Sun Jan  2 20:32:08.988 2011 (GMT-5)
System Uptime: 0 days 0:21:55.737
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 3B, {c0000005, fffff880048dc817, fffff88003811900, 0}

Probably caused by : atikmdag.sys ( atikmdag+90817 )

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

3: 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: fffff880048dc817, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003811900, 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: 
atikmdag+90817
fffff880`048dc817 8b4820          mov     ecx,dword ptr [rax+20h]

CONTEXT:  fffff88003811900 -- (.cxr 0xfffff88003811900)
rax=0000000000000000 rbx=fffffa8004ece7d0 rcx=fffffa8003b971b0
rdx=0000000000000000 rsi=0000000000000015 rdi=fffffa8003ba5340
rip=fffff880048dc817 rsp=fffff880038122d0 rbp=fffffa8003b971b0
 r8=0000000000000015  r9=fffff88004c9e970 r10=0000000000000000
r11=fffff88003812420 r12=0000000000000000 r13=fffffa8005e5e8c0
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0x90817:
fffff880`048dc817 8b4820          mov     ecx,dword ptr [rax+20h] ds:002b:00000000`00000020=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880048dc817

STACK_TEXT:  
fffff880`038122d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x90817


FOLLOWUP_IP: 
atikmdag+90817
fffff880`048dc817 8b4820          mov     ecx,dword ptr [rax+20h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+90817

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cef1f94

STACK_COMMAND:  .cxr 0xfffff88003811900 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+90817

BUCKET_ID:  X64_0x3B_atikmdag+90817

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

4- memory run memtest to verify yours

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

thankyou very much for the quick reply

i have some questions though

1.what is asacpi??

2.when i formatted the system i installed the 10.12 drivers only
do you recommend to reinstall them?
although i have the latest version of PhyX driver installed for MoH

3.will get rid of avast and install mse

4.i checked the ram with windows memory diagnostic and it reported no errors

BTW my system is barely 2 months old

@zigzag3143

thanks buddy the issue looks to be sorted
i installed the ATK driver and MSE
no BSODs from 2 days (fingers crossed)

could you explain what exactly is a ASACPI.sys