BSOD When plugging in Micro SD Card.

[tezlewis]

Ive had a few totally random BSOD's when plugging in my Micro SD 2GB card which doesnt normally happen.

Today is the first time it has happened but has happened about 4 times and cant get it to stay on with the card in.

Machine details should be in my profile and Mini dumpfile is attached.

Windows 7 Ultimate x64.

Thanks in advance for the help!

PS, any further info will be gladly provided if needed.

 

[zigzag3143]

Ive had a few totally random BSOD's when plugging in my Micro SD 2GB card which doesnt normally happen.

Today is the first time it has happened but has happened about 4 times and cant get it to stay on with the card in.

Machine details should be in my profile and Mini dumpfile is attached.

Windows 7 Ultimate x64.

Thanks in advance for the help!

PS, any further info will be gladly provided if needed.

This one was probably caused by AvastSvc.exe (avast AV). I would un-install it to test. then either install a fresh copy or a different product

let us know if you need help

Ken

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


Loading Dump File [C:\Users\K\Desktop\033110-29671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e89e50
Debug session time: Wed Mar 31 17:40:08.997 2010 (GMT-4)
System Uptime: 0 days 0:01:33.761
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fa0fb9, fffff880029ef640, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+51 )

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: fffff80002fa0fb9, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880029ef640, 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: 
nt!ObpQueryNameString+51
fffff800`02fa0fb9 410fb64718      movzx   eax,byte ptr [r15+18h]

CONTEXT:  fffff880029ef640 -- (.cxr 0xfffff880029ef640)
rax=fffff880029f0118 rbx=0000000000000000 rcx=7062737504050002
rdx=fffffa8002c46520 rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002fa0fb9 rsp=fffff880029f0020 rbp=7062737504050002
 r8=0000000000000080  r9=fffff880029f0180 r10=fffff80002e4b888
r11=fffff88001c0f3c0 r12=0000000000000000 r13=fffffa8003660800
r14=fffffa8002c46520 r15=706273750404ffd2
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
nt!ObpQueryNameString+0x51:
fffff800`02fa0fb9 410fb64718      movzx   eax,byte ptr [r15+18h] ds:002b:70627375`0404ffea=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002fa0fb9

STACK_TEXT:  
fffff880`029f0020 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpQueryNameString+0x51


FOLLOWUP_IP: 
nt!ObpQueryNameString+51
fffff800`02fa0fb9 410fb64718      movzx   eax,byte ptr [r15+18h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpQueryNameString+51

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff880029ef640 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpQueryNameString+51

BUCKET_ID:  X64_0x3B_nt!ObpQueryNameString+51

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

 

[tezlewis]

Nice one mate. I know quite abit about pc's but my debugger was blaming the ntkrnlmp.exe file but isnt fully setup to debug properly so blames this file for all BSOD. I do use Avast for my AV and have fopr ages. Like I say, this is totally random as have plugged this card in before. Strangly enough, its working fine with no BSOD's!! Thats computers for you!! Cheers again mate, Greatly appreciated and REP added!

 

[matt_0978]

I had a laptop that used to crash or not recognise that a card was inserted and more recently on my rig a usb port that caused my system to hang up, in both cases the root problem came down to a bent pin. with the laptop i convinced acer to change out the multicard reader port and just recently on my rig i removed the front usb/audio port, took it to maplin where they removed the offending pcb mounted usb socket and soldered on a new one for me. my pc has now been running for over 24 hrs solid and no bsods or crashes. happy days again!