BSOD from a USB port


  1. tys
    Posts : 38
    Windows 7 Professional x64
       #1

    BSOD from a USB port


    Hi All,

    I have a problem, in which when I plug a USB stick in the USB port, the computer crashes with a BSOD.
    Obviously it's the USB ports... could it be driver related. Hopefully the .DMP files will give more of an insight.

    Please find attached files.

    Thanks
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

    Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

    Please go through this link:

    Do you have McAfee installed on your system by any chance?

    Upload a screenshot of your hard disk using CrystalDiskInfo:

    Make a hard drive test from the hard drive manufacturers website:

    Run Disk Check on your hard disk for file system errors and bad sectors on it:

    Perform a System File Check:
    1. Click on the start
    2. Type CMD on Search
    3. Left click and Run as Administrator
    4. Type SFC /scannow

    Full tutorial here:

    Reduce items at start-up. Nothing except anti-virus is required:

    See if enabling/disabling Selective Suspense helps:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9B, {14031c, fffff880033bc538, fffff880033bbd90, fffff88000fc7079}
    
    *** WARNING: Unable to verify timestamp for MfeEpePc.sys
    *** ERROR: Module load completed but symbols could not be loaded for MfeEpePc.sys
    Probably caused by : partmgr.sys ( partmgr!PmGlobalDispatch+69 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    UDFS_FILE_SYSTEM (9b)
        If you see UdfExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more helpful stack
        trace.
    Arguments:
    Arg1: 000000000014031c
    Arg2: fffff880033bc538
    Arg3: fffff880033bbd90
    Arg4: fffff88000fc7079
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff880033bc538 -- (.exr 0xfffff880033bc538)
    ExceptionAddress: fffff88000fc7079 (partmgr!PmGlobalDispatch+0x0000000000000069)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000000
    Attempt to read from address 0000000000000000
    
    CONTEXT:  fffff880033bbd90 -- (.cxr 0xfffff880033bbd90)
    rax=0000000000000000 rbx=fffffa8004403010 rcx=fffffa800cb85280
    rdx=fffffa8004403010 rsi=fffffa8004403440 rdi=fffffa800cb853d0
    rip=fffff88000fc7079 rsp=fffff880033bc770 rbp=fffffa8004b9e350
     r8=0000000000000003  r9=fffff88000fc9560 r10=fffff6fb7dbf5000
    r11=0000000000000000 r12=0000000000008001 r13=fffffa800cb85280
    r14=fffffa800cbbe000 r15=00000000c0000100
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    partmgr!PmGlobalDispatch+0x69:
    fffff880`00fc7079 48833800        cmp     qword ptr [rax],0 ds:002b:00000000`00000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
    
    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_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b7100
    GetUlongFromAddress: unable to read from fffff800032b71c0
     0000000000000000 Nonpaged pool
    
    FOLLOWUP_IP: 
    partmgr!PmGlobalDispatch+69
    fffff880`00fc7079 48833800        cmp     qword ptr [rax],0
    
    FAULTING_IP: 
    partmgr!PmGlobalDispatch+69
    fffff880`00fc7079 48833800        cmp     qword ptr [rax],0
    
    BUGCHECK_STR:  0x9B
    
    LAST_CONTROL_TRANSFER:  from fffff88007a2d775 to fffff88000fc7079
    
    STACK_TEXT:  
    fffff880`033bc770 fffff880`07a2d775 : fffffa80`0cbbe000 00000000`00000800 00000000`00000800 00000000`00008001 : partmgr!PmGlobalDispatch+0x69
    fffff880`033bc7a0 fffff880`07a3a5a7 : fffff880`07a21110 00000000`00008000 fffffa80`0cbbe000 fffff800`03284990 : udfs!UdfReadWriteSectors+0x27d
    fffff880`033bc830 fffff880`07a37cd5 : fffffa80`04b9e350 fffffa80`0cb85280 fffff800`00000800 fffff880`033bc94c : udfs!UdfRecognizeVolume+0x13f
    fffff880`033bc8e0 fffff880`07a368b2 : fffffa80`04b9e350 fffffa80`0bc8faf0 fffff880`033bca00 fffff880`012e1700 : udfs!UdfMountVolume+0x421
    fffff880`033bca40 fffff880`07a0c0a4 : fffff880`033be000 fffffa80`0bc8ff68 fffff880`033b8000 fffffa80`0bc8faf0 : udfs!UdfCommonFsControl+0x3e
    fffff880`033bca70 fffff880`012e050c : fffffa80`04f12010 fffffa80`0bc8faf0 fffffa80`0509ee30 00000000`00000000 : udfs!UdfFsdDispatch+0x37c
    fffff880`033bcae0 fffff880`012db971 : fffffa80`08082db0 00000000`00000000 fffffa80`0b66e040 fffffa80`0509ee30 : fltmgr!FltpFsControlMountVolume+0x28c
    fffff880`033bcbb0 fffff800`032edc8f : fffffa80`08082db0 00000000`00000000 fffffa80`08082db0 fffffa80`0bc8faf0 : fltmgr!FltpFsControl+0x101
    fffff880`033bcc10 fffff800`034743d6 : fffffa80`0b331790 fffffa80`06eca600 00000000`00000001 fffffa80`06eca600 : nt!IopMountVolume+0x28f
    fffff880`033bccd0 fffff880`0128e8af : 00000000`00000000 00000000`80000016 00000000`00000000 00000000`00000000 : nt!IoVerifyVolume+0x176
    fffff880`033bcd60 00000000`00000000 : 00000000`80000016 00000000`00000000 00000000`00000000 fffff880`033bcda0 : MfeEpePc+0x88af
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  partmgr!PmGlobalDispatch+69
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: partmgr
    
    IMAGE_NAME:  partmgr.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f641bc1
    
    STACK_COMMAND:  .cxr 0xfffff880033bbd90 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x9B_partmgr!PmGlobalDispatch+69
    
    BUCKET_ID:  X64_0x9B_partmgr!PmGlobalDispatch+69
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 24,479
    Windows 7 Ultimate X64 SP1
       #3

    Does this happen with any USB device and is it only with one or all USB ports?
    Your USB stick or the port may have a short/grounding problem. I had a port do this in the past.
      My Computer


  4. tys
    Posts : 38
    Windows 7 Professional x64
    Thread Starter
       #4

    Well, it's strange, as the USB device works for all other laptops/computers so I wouldn't think it was the USB stick. But it was plugged in another port and it BSOD. But other USB devices are plugged into that port and it doesn't BSOD. Then once after it BSODs then plug it in a different port, it works again....
      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 07:39.
Find Us