BSOD 06-12-11

#1
Here is a BSOD I got yesterday, been a long time since I got a BSOD
The only BSOD to look at should be the one dated 061211. I accidently attached other BSOD'S that I had in the past and had solved the problem
 


Attachments

Last edited by a moderator:

Captain Jack

Extraordinary Member
#2
Hello Mate,

Seems like the dump file wasn't very help since it didn't catch the culprit but only thing it mentions is USB Storage. If you had any additional BSOD then please upload the latest dump.

Code:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8012e97000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004da6a10, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cb100
 fffffa8012e97000 

FAULTING_IP: 
USBSTOR!memcpy+80
fffff880`04da6a10 8a040a          mov     al,byte ptr [rdx+rcx]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800357e330 -- (.trap 0xfffff8800357e330)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000010000000200 rbx=0000000000000000 rcx=fffffa800f3cb629
rdx=0000000003acb9d7 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004da6a10 rsp=fffff8800357e4c8 rbp=fffffa800deebb00
 r8=0000000000000003  r9=0000000000000000 r10=000001ffffffff00
r11=fffffa800f3cb52d r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
USBSTOR!memcpy+0x80:
fffff880`04da6a10 8a040a          mov     al,byte ptr [rdx+rcx] ds:2180:fffffa80`12e97000=??
Resetting default scope

LOCK_ADDRESS:  fffff80003297b60 -- (!locks fffff80003297b60)

Resource @ nt!PiEngineLock (0xfffff80003297b60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80003297b60
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80003047a0c to fffff8000309bd00

STACK_TEXT:  
fffff880`0357e1c8 fffff800`03047a0c : 00000000`00000050 fffffa80`12e97000 00000000`00000000 fffff880`0357e330 : nt!KeBugCheckEx
fffff880`0357e1d0 fffff800`03099e2e : 00000000`00000000 fffffa80`12e97000 fffffa80`0deeba00 fffffa80`12e96f00 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`0357e330 fffff880`04da6a10 : fffff880`04db2012 fffffa80`12e96f00 fffffa80`0deebb00 ffffd38d`00000001 : nt!KiPageFault+0x16e
fffff880`0357e4c8 fffff880`04db2012 : fffffa80`12e96f00 fffffa80`0deebb00 ffffd38d`00000001 fffffa80`12e96f00 : USBSTOR!memcpy+0x80
fffff880`0357e4d0 fffff880`04dad67c : fffffa80`0deebb60 fffffa80`0deebb60 fffffa80`0f3cb4c0 00000000`00000000 : USBSTOR!USBSTOR_GetDeviceSerialNumber+0x12e
fffff880`0357e540 fffff880`04dadc82 : fffffa80`0f3cb370 fffff880`04da9100 fffffa80`0deebb60 fffffa80`0deebf88 : USBSTOR!USBSTOR_CreateChildPDO+0x244
fffff880`0357e5b0 fffff880`04daca66 : 00000000`00000001 00000000`00000000 fffffa80`0deeba00 fffffa80`0deebb00 : USBSTOR!USBSTOR_EnumerateChildren+0x5aa
fffff880`0357e670 fffff880`04dac539 : fffffa80`0deeba10 fffffa80`0dcd5e10 00000000`00000000 fffffa80`0f8ad010 : USBSTOR!USBSTOR_FdoStartDevice+0x25a
fffff880`0357e750 fffff800`03451f5e : fffffa80`0f8ad010 fffffa80`0dcd5e10 fffffa80`0deeba10 fffff880`03386180 : USBSTOR!USBSTOR_Pnp+0xd9
fffff880`0357e790 fffff800`031898bd : fffffa80`12509060 fffffa80`0dcd5e10 fffff800`03192fe0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`0357e7d0 fffff800`034612a6 : fffff800`03297920 fffffa80`0eae7360 fffffa80`0dcd5e10 fffffa80`0eae7508 : nt!PnpStartDevice+0x11d
fffff880`0357e890 fffff800`03461544 : fffffa80`0eae7360 fffffa80`0a9c0027 fffffa80`0a9cd990 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`0357e920 fffff800`03484c76 : fffffa80`0eae7360 fffffa80`0a9cd990 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`0357e950 fffff800`03485208 : fffff800`032954e0 00000000`00000000 00000000`00000001 fffff800`03306248 : nt!PipProcessDevNodeTree+0x296
fffff880`0357ebc0 fffff800`03195927 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`0357ec10 fffff800`030a6021 : fffff800`03195600 fffff800`03239201 fffffa80`09d7f000 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`0357ecb0 fffff800`0333832e : 00000000`00000000 fffffa80`09d7f040 00000000`00000080 fffffa80`09d63b30 : nt!ExpWorkerThread+0x111
fffff880`0357ed40 fffff800`0308d666 : fffff880`03386180 fffffa80`09d7f040 fffff880`033910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0357ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBSTOR!memcpy+80
fffff880`04da6a10 8a040a          mov     al,byte ptr [rdx+rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBSTOR!memcpy+80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBSTOR

IMAGE_NAME:  USBSTOR.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79a6fc

FAILURE_BUCKET_ID:  X64_0x50_USBSTOR!memcpy+80

BUCKET_ID:  X64_0x50_USBSTOR!memcpy+80

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


#3
No it has nat failed again, I suspect it was a hiccup and is not really a problem. All my drivers are current and up to date
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#4
OK, since this is sort of "In the Family", I will make some observations.

I seems from the stack, information about a device is being gathered and problems are encountered during the PnP determination.

You have some older drivers, and at least two seem to be related to Sonic/Roxio, can't find the third one.

DRVEDDM.sys Sonic Roxio?
DLACDBHE.sys Sonic/Roxio?
wanatw64.sys ?

So, if it was my system, I would be suspicious of a USB Drive of some type, possibly a DVD.

Perhaps, it you wanted to track it down, the Drive Verifier might help.

Anyway good practice.... :)
 


#5
I know it is not a DVD because I have no USB Did drives. I suspect it was one of my numerous External drives
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.