BSOD with Pandora Running

jastoneii · 04 Oct 2013

Over the past few months I have had several BSODs. To the best of my recollection, it always to happen when Pandora is active. Today's crash happened before Pandora completed playing the second song.

I have attached the zipped output from the SF Diagnostic Tool.

tia

Jeff

Arc · 04 Oct 2013

Hi jastoneii.

Do three things at first.

1. Update Intel® G41 Express Chipset display driver from Intel® Graphics Media Accelerator Driver, Windows 7* 64, Windows Vista* 64 (exe).

2. Remove Seagate Backup+ BK USB Device (1 TB External HDD).

3. Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Let us know how it is running after doing those.
____________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffe78005800395, 2, 0, fffff80003412173}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffe78005800395, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003412173, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
GetUlongFromAddress: unable to read from fffff800030bc1c0
 ffffe78005800395 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
hal!memcpy+223
fffff800`03412173 8a040a          mov     al,byte ptr [rdx+rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF88003192FB0

TRAP_FRAME:  fffff8800318b7a0 -- (.trap 0xfffff8800318b7a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000390 rbx=0000000000000000 rcx=fffffa800515a395
rdx=ffffed00006a6000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003412173 rsp=fffff8800318b938 rbp=0000000000000002
 r8=0000000000000006  r9=fffff8800318b978 r10=fffffa800570aa30
r11=fffffa800515a390 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
hal!memcpy+0x223:
fffff800`03412173 8a040a          mov     al,byte ptr [rdx+rcx] ds:ffffe780`05800395=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e84129 to fffff80002e84b80

STACK_TEXT:  
fffff880`0318b658 fffff800`02e84129 : 00000000`0000000a ffffe780`05800395 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0318b660 fffff800`02e82da0 : 00000000`00000000 fffffa80`05f25ba8 fffffa80`087717a0 fffffa80`0515a390 : nt!KiBugCheckDispatch+0x69
fffff880`0318b7a0 fffff800`03412173 : fffff800`033f7e15 fffffa80`0515a390 00000000`00000002 fffffa80`03e06360 : nt!KiPageFault+0x260
fffff880`0318b938 fffff800`033f7e15 : fffffa80`0515a390 00000000`00000002 fffffa80`03e06360 fffff880`0479d783 : hal!memcpy+0x223
fffff880`0318b940 fffff800`033f769a : fffffa80`0570aa30 fffffa80`0515a300 fffffa80`0572b000 00000000`00000006 : hal!HalpDmaSyncMapBuffers+0x1bd
fffff880`0318b9f0 fffff800`033fa83f : fffffa80`0570aa30 fffffa80`0515a390 fffffa80`0572b000 00000000`00000006 : hal!HalpDmaFlushScatterTransfer+0xae
fffff880`0318ba40 fffff800`033f97d5 : fffffa80`044b2910 fffffa80`0515a390 00000000`00000006 fffffa80`03e06360 : hal!IoFlushAdapterBuffers+0xaf
fffff880`0318ba80 fffff880`047ae07b : fffffa80`052571a0 fffffa80`08e26e60 fffffa80`05257050 fffffa80`052571a0 : hal!HalPutScatterGatherList+0x85
fffff880`0318bae0 fffff880`047aeb0f : fffffa80`08e26a02 fffffa80`0575c010 00000000`ffffffff fffffa80`05257eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x45f
fffff880`0318bbc0 fffff880`047ac66f : fffffa80`05257eb0 fffffa80`052571a0 fffffa80`05258050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`0318bc20 fffff880`0479df89 : fffffa80`05257050 00000000`00000000 fffffa80`05257e02 fffffa80`05257eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`0318bc60 fffff800`02e8f30c : fffff880`03163180 fffffa80`05257eb0 fffffa80`05257ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`0318bc90 fffff800`02e7c88a : fffff880`03163180 fffff880`0316dfc0 00000000`00000000 fffff880`0479ddb0 : nt!KiRetireDpcList+0x1bc
fffff880`0318bd40 00000000`00000000 : fffff880`0318c000 fffff880`03186000 fffff880`0318bd00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
fffff880`047ae07b 4533c0          xor     r8d,r8d

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c08

FAILURE_BUCKET_ID:  X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

BUCKET_ID:  X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

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

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880055cce07, fffff8800429b558, fffff8800429adb0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+7b )

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

2: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880055cce07, The address that the exception occurred at
Arg3: fffff8800429b558, Exception Record Address
Arg4: fffff8800429adb0, 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: 
dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+7b
fffff880`055cce07 488b09          mov     rcx,qword ptr [rcx]

EXCEPTION_RECORD:  fffff8800429b558 -- (.exr 0xfffff8800429b558)
ExceptionAddress: fffff880055cce07 (dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+0x000000000000007b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800429adb0 -- (.cxr 0xfffff8800429adb0)
rax=fffff8a0065534b0 rbx=fffff8a00db22350 rcx=ffff07a001bb2e80
rdx=fffff8800429b7b0 rsi=fffffa8005fe2c01 rdi=fffff8a00db22350
rip=fffff880055cce07 rsp=fffff8800429b790 rbp=0000000000000000
 r8=fffffa8005fe33d0  r9=0000000000000001 r10=fffffa8005d30000
r11=fffff8800429b7c0 r12=0000000000000001 r13=0000000000000000
r14=0000000000000000 r15=00000000000000ae
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+0x7b:
fffff880`055cce07 488b09          mov     rcx,qword ptr [rcx] ds:002b:ffff07a0`01bb2e80=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

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:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f6100
GetUlongFromAddress: unable to read from fffff800030f61c0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+7b
fffff880`055cce07 488b09          mov     rcx,qword ptr [rcx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880055c7a21 to fffff880055cce07

STACK_TEXT:  
fffff880`0429b790 fffff880`055c7a21 : fffff8a0`0db22350 fffff8a0`0db22350 fffffa80`05fe2c01 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+0x7b
fffff880`0429b7f0 fffff880`055bba3c : 00000000`00000000 fffffa80`05fe2c50 fffffa80`05fe2c50 fffff880`0429b870 : dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+0x159
fffff880`0429b840 fffff880`055bb909 : fffffa80`05fe2000 fffff880`055bb820 00000000`00000000 fffffa80`076e9400 : dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x40
fffff880`0429b880 fffff880`055b8831 : 00000000`000000ad 00000000`00000000 00000000`00000000 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x31
fffff880`0429b8d0 fffff880`055d27d9 : 00000000`00000000 fffff8a0`0309c4e0 fffffa80`00000000 fffffa80`076e9400 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xc79
fffff880`0429baa0 fffff880`055d2514 : fffff880`03167f40 fffff880`055d1f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0429bc90 fffff880`055d2012 : 00000000`00000000 fffffa80`05a27960 00000000`00000080 fffffa80`05fc1410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0429bcc0 fffff800`0315cbae : 00000000`0271bb03 fffffa80`059a5b50 fffffa80`03cd5040 fffffa80`059a5b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0429bd00 fffff800`02eaf8c6 : fffff880`03163180 fffffa80`059a5b50 fffff880`0316dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0429bd40 00000000`00000000 : fffff880`0429c000 fffff880`04296000 fffff880`0429b640 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+7b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

STACK_COMMAND:  .cxr 0xfffff8800429adb0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+7b

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::UnlockAllocationBackingStore+7b

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

2: kd> lmvm igdkmd64
start             end                 module name
fffff880`04a87000 fffff880`054a5b60   igdkmd64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Thu Aug 26 01:05:58 2010 (4C75709E)
    CheckSum:         00A23ACB
    ImageSize:        00A1EB60
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Next memtest & DV?