Blue screen while using USB to serial adapter

Discussion in 'Parallels Desktop for Mac' started by plarusa, Sep 26, 2006.

  1. plarusa

    plarusa Member

    Messages:
    33
    Here is the MSFT debugger analysis for this error (a mem dump can be generated if needed). This is easily reproduced while using the MSFT debugger running in a VM. The debugger in the VM is used to debug a real machine through a USB to serial adapter attached to the VM. My goal is to use the MAC to develop Windows drivers. I would also like to debug one Windows VM from another connected through a virtual serial port, but that fails very badly also.


    MODULE_NAME: USBPORT

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

    BUGCHECK_STR: 0xC5_2

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt+74339
    8054b339 8913 mov dword ptr [ebx],edx

    CUSTOMER_CRASH_COUNT: 4

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    LAST_CONTROL_TRANSFER: from 8054b31e to 8054b339

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80550004 8054b31e 81fddcb8 821910ec 81f91008 nt+0x74339
    80550044 8054b0b9 81f91008 00000000 805500c0 nt+0x7431e
    80550054 f7dfbfb1 81f91008 82117c40 81f91008 nt+0x740b9
    805500c0 f7dfcb57 822bd458 00000000 821917d8 USBPORT+0x9fb1
    805500f0 f7dfd754 026e6f44 821910e0 821910e0 USBPORT+0xab57
    80550128 f7dfef6a 82191028 804e2eb4 82191230 USBPORT+0xb754
    80550154 f7e0cfb0 82191028 804e2eb4 82191028 USBPORT+0xcf6a
    80550190 f7e0d128 82191028 00000001 80558e80 USBPORT+0x1afb0
    805501ac 804dbbd4 8219164c 6b755044 00000000 USBPORT+0x1b128
    805501b0 8219164c 6b755044 00000000 821910ec nt+0x4bd4
    805501b4 6b755044 00000000 821910ec 00000000 0x8219164c
    805501b8 00000000 821910ec 00000000 806f372a 0x6b755044


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    USBPORT+9fb1
    f7dfbfb1 ?? ???

    SYMBOL_STACK_INDEX: 3

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: USBPORT.SYS

    SYMBOL_NAME: USBPORT+9fb1

    BUCKET_ID: WRONG_SYMBOLS

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

Share This Page