Intermittant BSOD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by phcahill, Jun 3, 2011.

  1. phcahill

    phcahill New Member

    Joined:
    Jun 3, 2011
    Messages:
    4
    Likes Received:
    0
    Hi

    My PC is having the odd BSOD. It seems to happen sometime after waking up from hibernate to do a backup with Windows Home Server. I could be when is goes back in to hibernate (after 20 mins idle). If I manually hibernate a resume it's fine.

    ASUS V-P5G45 Intel G45 based board, onboard Intel grahics, CPU Intel E6300, 2GB DDR2 (memtests OK).
    Windows 7 x86 SP1.

    I hope I have attached the zip of the mini dump OK. Any help much appreciated.

    Regards
    Paul
     

    Attached Files:

  2. yowanvista

    yowanvista Well-Known Member

    Joined:
    Apr 10, 2011
    Messages:
    82
    Likes Received:
    0
    Your Microsoft LifeCam VX1000 Device Driver seems to be the cause, please update it
    Software Downloads | Microsoft Hardware
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {8fa6cdd8, 2, 1, 959e94c0}
    
    *** WARNING: Unable to verify timestamp for VX1000.sys
    *** ERROR: Module load completed but symbols could not be loaded for VX1000.sys
    Probably caused by : VX1000.sys ( VX1000+1d753 )
    
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 8fa6cdd8, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 959e94c0, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82fb8848
    Unable to read MiSystemVaType memory at 82f97e20
     8fa6cdd8 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    usbccgp!UsbcAcquireRemoveLock+8c
    959e94c0 8902            mov     dword ptr [edx],eax
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  8285cb90 -- (.trap 0xffffffff8285cb90)
    ErrCode = 00000002
    eax=8534316c ebx=87a6cd28 ecx=87a6cdd8 edx=8fa6cdd8 esi=85343168 edi=8534317c
    eip=959e94c0 esp=8285cc04 ebp=8285cc1c iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    usbccgp!UsbcAcquireRemoveLock+0x8c:
    959e94c0 8902            mov     dword ptr [edx],eax  ds:0023:8fa6cdd8=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 959e94c0 to 82e905cb
    
    STACK_TEXT:  
    8285cb90 959e94c0 badb0d00 8fa6cdd8 82f6f8c0 nt!KiTrap0E+0x2cf
    8285cc1c 959e54f0 00000000 44707249 85703550 usbccgp!UsbcAcquireRemoveLock+0x8c
    8285cc50 82e86593 87a67ae8 00703550 85703550 usbccgp!USBC_Dispatch+0x96
    8285cc68 8a637753 31314e53 856c5438 00000000 nt!IofCallDriver+0x63
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8285cc9c 8a637d0f 856c5438 87a95de4 87a95008 VX1000+0x1d753
    8285ccb8 8a633ba9 00000018 00000001 00000000 VX1000+0x1dd0f
    8285cce4 8a636af6 00000000 00000002 00000001 VX1000+0x19ba9
    8285cd48 8a63737f 8285cd90 83057f64 87a95008 VX1000+0x1caf6
    8285cd50 83057f64 87a95008 a6062972 00000000 VX1000+0x1d37f
    8285cd90 82f00219 8a63736e 87a95008 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    VX1000+1d753
    8a637753 ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  VX1000+1d753
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: VX1000
    
    IMAGE_NAME:  VX1000.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4acbf378
    
    FAILURE_BUCKET_ID:  0xD1_VX1000+1d753
    
    BUCKET_ID:  0xD1_VX1000+1d753
    
    Followup: MachineOwner
    ---------
    
    
     
  3. phcahill

    phcahill New Member

    Joined:
    Jun 3, 2011
    Messages:
    4
    Likes Received:
    0
    Hi

    Thanks for having a look at the dump.

    I have uninstalled the lifecam software and reinstalled the latest available from microsoft hardware. Unfortunately it is that same revision as I already had installed, Lifecam3.22 containing VX1000.SYS ver 1.3.11.0 dated 13 Mar 2010. Later versions of the lifecam package do not support the Microsoft VX1000 webcam. I have made sure I am using the lastest chipset driver package from Intel (USB etc).

    Ah well at least I now know there the problem lies. Does anyone know a way of reporting this to MS hardware support?

    Regards
    Paul
     

Share This Page

Loading...