BSOD when using external hard drive

uncfer · 09 Apr 2010

Guys, my computer has just started giving me occasional BSODs within the past three weeks or so. The problems seem to come when my external hard drive is being accessed. That hard drive contains mostly media. The first couple of crashes happened while recording/capturing video to that hard drive from a game, and I assumed it was just something caused by the capturing mechanism in the game. Since then it has happened while browsing or listening to my MP3 collection in iTunes and Zune and other benign media-related activities like that.

I am running 32-bit Windows 7 Ultimate, completely up to date from Windows Update. The hard drive is a recertified Seagate 1.5TB drive I got from Woot in December. In my attempts to fix this, I have updated every driver I could think to update, including video card and sound card, all to no avail. I've scanned the hard drive with the built-in error-checking tool, and it came up completely clean.

I'm attaching my zipped up minidump folder so maybe someone smarter than me can interpret it. Just let me know anything else you need. Please help me!

YakSipper · 09 Apr 2010

Hey there. I noticed you're running AVG which is the worst bsod offender going. Completely uninstall that then give it a go. Enjoy.

That will fix things. If on the very slight chance it doesn't, look into updating this driver:

Code:

LUsbFilt LUsbFilt.Sys Fri Feb 29 05:08:14 2008

Jonathan_King · 09 Apr 2010

I agree with YakSipper, except I have noticed ZoneAlarm is slightly worse than AVG.

Anti-virus programs are a big cause of this sort of problem, as they try to scan everything that is plugged in.

uncfer · 09 Apr 2010

I'm not actually running AVG, I'm running Avira AntiVir, another free anti-virus. What anti-virus software is recommended to avoid crashes like this? Should I just go with a scanner with no active guard and schedule a weekly scan of my internal hard drives only or something?

Jonathan_King · 09 Apr 2010

I'll be honest I didn't look at your dmps, I just looked at the above user's post.

Most of them are corrupted, but one of them points to your display driver. I recommend updating it.

You may also want to run SFC and do a memory test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

As for anti-virus, I don't see any evidence of its failure, and Avira is not known to cause BSODs. My personal favorite is Microsoft Security Essentials, but I can't honestly say that's your problem.

Code:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp5_minidump.zip\minidump\032810-13650-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x81e00000 PsLoadedModuleList = 0x81f48810
Debug session time: Sun Mar 28 04:12:01.666 2010 (GMT-4)
System Uptime: 0 days 0:00:13.509
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 96b7188d, 961a2304, 961a1ee0}

Probably caused by : cdd.dll ( cdd!CopyBits+bd )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 96b7188d, The address that the exception occurred at
Arg3: 961a2304, Exception Record Address
Arg4: 961a1ee0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
cdd!CopyBits+bd
96b7188d 037024          add     esi,dword ptr [eax+24h]

EXCEPTION_RECORD:  961a2304 -- (.exr 0xffffffff961a2304)
ExceptionAddress: 96b7188d (cdd!CopyBits+0x000000bd)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0b851ca0
Attempt to read from address 0b851ca0

CONTEXT:  961a1ee0 -- (.cxr 0xffffffff961a1ee0)
eax=0b851c7c ebx=00001680 ecx=00000000 edx=00000000 esi=fdd1aa80 edi=850f3408
eip=96b7188d esp=961a23cc ebp=961823e4 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
cdd!CopyBits+0xbd:
96b7188d 037024          add     esi,dword ptr [eax+24h] ds:0023:0b851ca0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  0b851ca0

READ_ADDRESS: GetPointerFromAddress: unable to read from 81f68718
Unable to read MiSystemVaType memory at 81f48160
 0b851ca0 

FOLLOWUP_IP: 
cdd!CopyBits+bd
96b7188d 037024          add     esi,dword ptr [eax+24h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 96b745a9 to 96b7188d

STACK_TEXT:  
961a23e4 96b745a9 00850000 000002bb 00001680 cdd!CopyBits+0xbd
961a2ac4 96b7540f ffab62f8 00000000 00000000 cdd!CddPresentBlt+0x229
961a2d50 8200e66d ffb89010 ba781352 00000000 cdd!PresentWorkerThread+0xadb
961a2d90 81ec01d9 96b74934 ffb89010 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  cdd!CopyBits+bd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bd992

STACK_COMMAND:  .cxr 0xffffffff961a1ee0 ; kb

FAILURE_BUCKET_ID:  0x7E_cdd!CopyBits+bd

BUCKET_ID:  0x7E_cdd!CopyBits+bd

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