BSOD last night. MacBook Pro running Bootcamp


  1. Posts : 2
    Windows 7 Home Premium 64 bit, Bootcamp
       #1

    BSOD last night. MacBook Pro running Bootcamp


    Hi

    I got 3 BSODs last night. I think it may have something to do with a missing Keyspan driver but am not sure.

    Could someone kindly take a look for me?:)

    Andy
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    The BSOD is caused by Keyspan USB Serial Adapter.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {68, 2, 1, fffff88005ab5a34}
    
    Unable to load image \SystemRoot\system32\DRIVERS\USA19Hx64p.SYS, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for USA19Hx64p.SYS
    Probably caused by : USA19Hx64p.SYS ( USA19Hx64p+a34 )
    
    Followup: MachineOwner
    ---------
    And the driver is extremely old.
    Code:
    fffff880`05ab5000 fffff880`05abdc00   USA19Hx64p   (no symbols)           
        Loaded symbol image file: USA19Hx64p.SYS
        Image path: \SystemRoot\system32\DRIVERS\USA19Hx64p.SYS
        Image name: USA19Hx64p.SYS
        Timestamp:        Wed Oct 24 02:49:44 2007 (471E6570)
        CheckSum:         0001274E
        ImageSize:        00008C00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Try to update it from the vendor's website. You may have a look here: http://www.macwise.com/Keyspan.html
      My Computer


  3. Posts : 2
    Windows 7 Home Premium 64 bit, Bootcamp
    Thread Starter
       #3

    I thought I'd updated the Keyspan driver but I got another BSOD.

    Can someone look please?
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    From the BSOD crash dump you uploaded, it appears that the said driver is not updated, and the BSOD is caused by the same driver.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {68, 2, 1, fffff88002318a34}
    
    Unable to load image \SystemRoot\system32\DRIVERS\USA19Hx64p.SYS, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for USA19Hx64p.SYS
    Probably caused by : USA19Hx64p.SYS ( USA19Hx64p+a34 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: 0000000000000068, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88002318a34, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f07100
    GetUlongFromAddress: unable to read from fffff80002f071c0
     0000000000000068 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    USA19Hx64p+a34
    fffff880`02318a34 48874768        xchg    rax,qword ptr [rdi+68h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  SRFeature.exe
    
    TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
    
    TRAP_FRAME:  fffff80000ba2990 -- (.trap 0xfffff80000ba2990)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004eca010
    rdx=fffffa8006e87780 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002318a34 rsp=fffff80000ba2b20 rbp=0000000000000002
     r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
    r11=fffff8800231a8e0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    USA19Hx64p+0xa34:
    fffff880`02318a34 48874768        xchg    rax,qword ptr [rdi+68h] ds:00000000`00000068=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ccf1a9 to fffff80002ccfc00
    
    STACK_TEXT:  
    fffff800`00ba2848 fffff800`02ccf1a9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff800`00ba2850 fffff800`02ccde20 : fffffa80`04d623e0 fffffa80`046c2050 fffffa80`04b9b430 fffffa80`06292a10 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba2990 fffff880`02318a34 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`06292a10 : nt!KiPageFault+0x260
    fffff800`00ba2b20 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`06292a10 fffffa80`05e116e0 : USA19Hx64p+0xa34
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    USA19Hx64p+a34
    fffff880`02318a34 48874768        xchg    rax,qword ptr [rdi+68h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  USA19Hx64p+a34
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: USA19Hx64p
    
    IMAGE_NAME:  USA19Hx64p.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  471e6570
    
    FAILURE_BUCKET_ID:  X64_0xD1_USA19Hx64p+a34
    
    BUCKET_ID:  X64_0xD1_USA19Hx64p+a34
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm USA19Hx64p
    start             end                 module name
    fffff880`02318000 fffff880`02320c00   USA19Hx64p   (no symbols)           
        Loaded symbol image file: USA19Hx64p.SYS
        Image path: \SystemRoot\system32\DRIVERS\USA19Hx64p.SYS
        Image name: USA19Hx64p.SYS
        Timestamp:        Wed Oct 24 02:49:44 2007 (471E6570)
        CheckSum:         0001274E
        ImageSize:        00008C00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:44.
Find Us