Hello guys!
I get the BSOD crash memory dump after plug in a Sony Storage Media USB Device (4GB). Those are the stop info:
0×0000008E (0×60000005, 0×82CD02EE, 0×8A5976A0, 0×00000000)
After restarting (with the stick plugged in) all seams to be fine and I can normally use and work with the content on the stick.
If you please could look at the memory dump file and explain me why is that happening I will be thankful.
I've never heard of a USB drive causing BSOD, but its definately got something to do with the device driver or the USB drie itself is broken.
See if you can uninstall the driver, restart Windows and plug in the USB drive again.
To be honest these things are so chep these days, if I was you I'd just bin it and get something else (not Sony).
Thanks for reply:)
Here are the Event Viewer info:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 8.4.2010. 11:13:31
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: BORIS-DESKTOP
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0x82cd02ee, 0x8a5976a0, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 040810-14898-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-04-08T09:13:31.000000000Z" />
<EventRecordID>51554</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>BORIS-DESKTOP</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000008e (0xc0000005, 0x82cd02ee, 0x8a5976a0, 0x00000000)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">040810-14898-01</Data>
</EventData>
</Event>
I will change the memory stick to the new one but I'm still curios what was the problem. What kind of bugcheck was it? The content is clean (ESET 32, Malwarebytes, Spybot).
For now I' disabled Autoplay in gpedit.msc.
Thanks again!
It looks like part of your Acronis is causing the problems. Here's a very informative article I found: Interesting Issue with Acronis True Image Home 2010 - Windows Enterprise Desktop
I suggest following the advice in that link, and if it doesn't work, uninstall Acronis.
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\Temp1_040810-14898-01.zip\040810-14898-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 = 0x82a53000 PsLoadedModuleList = 0x82b9b810 Debug session time: Thu Apr 8 05:04:36.335 2010 (GMT-4) System Uptime: 0 days 0:33:30.067 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 82cd02ee, 8a5976a0, 0} *** WARNING: Unable to verify timestamp for tdrpm251.sys *** ERROR: Module load completed but symbols could not be loaded for tdrpm251.sys Probably caused by : tdrpm251.sys ( tdrpm251+2b5cf ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: 82cd02ee, The address that the exception occurred at Arg3: 8a5976a0, Trap Frame Arg4: 00000000 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+2b 82cd02ee 0fb6460c movzx eax,byte ptr [esi+0Ch] TRAP_FRAME: 8a5976a0 -- (.trap 0xffffffff8a5976a0) ErrCode = 00000000 eax=8a597768 ebx=00000000 ecx=00000000 edx=8a5977c0 esi=0000101b edi=00001033 eip=82cd02ee esp=8a597714 ebp=8a597778 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!ObpQueryNameString+0x2b: 82cd02ee 0fb6460c movzx eax,byte ptr [esi+0Ch] ds:0023:00001027=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 82cd0a7a to 82cd02ee STACK_TEXT: 8a597778 82cd0a7a 00001033 84e3ab70 00000080 nt!ObpQueryNameString+0x2b 8a597794 892465cf 00001033 84e3ab70 00000080 nt!ObQueryNameString+0x18 WARNING: Stack unwind information not available. Following frames may be wrong. 8a597798 00000000 84e3ab70 00000080 8a5977c0 tdrpm251+0x2b5cf STACK_COMMAND: kb FOLLOWUP_IP: tdrpm251+2b5cf 892465cf ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: tdrpm251+2b5cf FOLLOWUP_NAME: MachineOwner MODULE_NAME: tdrpm251 IMAGE_NAME: tdrpm251.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a72f8eb FAILURE_BUCKET_ID: 0x8E_tdrpm251+2b5cf BUCKET_ID: 0x8E_tdrpm251+2b5cf Followup: MachineOwner ---------
Jonathan_King thanks for reply and detailed report .
Acronis is working flawlessly regardless what USB device I plug in, only these older memory stick is the reason for confusion. Strange, on my Asus Eee PC 1201N is the same Acronis version and the "atrocious" stick is working normally with AutoPlay enabled. I hope the reason is the older stick and maybe other settings, just not (please God) Acronis, so I'll move all files to the new external drive.
Quote