BSOD after unplugging USB(TP link)

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Ultimate x64
       #1

    BSOD after unplugging USB(TP link)


    Hello
    I am using windows 7 64bit system.
    for some reason, after im unpluging my TP-LINK usb device, a BSOD appears
    it happens every time im doing it.
    (TP LINK WN821N v3)

    i have to say it happens only with the TP LINK device, if im unplugging the mouse/keyboard USB
    everything is ok...

    *added dm log collector info

    thanks!
      My Computer


  2. Posts : 17,796
    Windows 10, Home Clean Install
       #2

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
     
    Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_YONI-PC-Wed_12_24_2014_181604_53.zip\122114-33602-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e96890
    Debug session time: Sun Dec 21 12:38:21.238 2014 (UTC - 5:00)
    System Uptime: 0 days 0:22:05.051
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols
    Loading unloaded module list
    ......
    Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athurx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athurx.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000007E, {ffffffffc0000005, fffff88008808e26, fffff8800333f808, fffff8800333f060}
    Probably caused by : athurx.sys ( athurx+8e26 )
    Followup: MachineOwner
    ---------
    4: 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: fffff88008808e26, The address that the exception occurred at
    Arg3: fffff8800333f808, Exception Record Address
    Arg4: fffff8800333f060, 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: 
    athurx+8e26
    fffff880`08808e26 488b8098260000  mov     rax,qword ptr [rax+2698h]
    EXCEPTION_RECORD:  fffff8800333f808 -- (.exr 0xfffff8800333f808)
    ExceptionAddress: fffff88008808e26 (athurx+0x0000000000008e26)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000002698
    Attempt to read from address 0000000000002698
    CONTEXT:  fffff8800333f060 -- (.cxr 0xfffff8800333f060)
    rax=0000000000000000 rbx=fffffa800809e050 rcx=fffffa8008f9b030
    rdx=0000000000000002 rsi=fffffa800673a040 rdi=fffffa800724f580
    rip=fffff88008808e26 rsp=fffff8800333fa40 rbp=fffff80002e6e280
     r8=0000000000000000  r9=0000000000000f44 r10=fffff80002c53000
    r11=0000000000000000 r12=fffffa800724f580 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    athurx+0x8e26:
    fffff880`08808e26 488b8098260000  mov     rax,qword ptr [rax+2698h] ds:002b:00000000`00002698=????????????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_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:  0000000000002698
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f00100
     0000000000002698 
    FOLLOWUP_IP: 
    athurx+8e26
    fffff880`08808e26 488b8098260000  mov     rax,qword ptr [rax+2698h]
    BUGCHECK_STR:  0x7E
    LAST_CONTROL_TRANSFER:  from fffffa800809e050 to fffff88008808e26
    STACK_TEXT:  
    fffff880`0333fa40 fffffa80`0809e050 : fffff880`08808dc5 fffff880`0894c740 fffff880`0894c6f0 00000000`000015d7 : athurx+0x8e26
    fffff880`0333fa48 fffff880`08808dc5 : fffff880`0894c740 fffff880`0894c6f0 00000000`000015d7 00000000`00000002 : 0xfffffa80`0809e050
    fffff880`0333fa50 fffff880`0894c740 : fffff880`0894c6f0 00000000`000015d7 00000000`00000002 00000000`00000000 : athurx+0x8dc5
    fffff880`0333fa58 fffff880`0894c6f0 : 00000000`000015d7 00000000`00000002 00000000`00000000 00000000`c0000184 : athurx+0x14c740
    fffff880`0333fa60 00000000`000015d7 : 00000000`00000002 00000000`00000000 00000000`c0000184 00000000`00000000 : athurx+0x14c6f0
    fffff880`0333fa68 00000000`00000002 : 00000000`00000000 00000000`c0000184 00000000`00000000 0000057f`00000000 : 0x15d7
    fffff880`0333fa70 00000000`00000000 : 00000000`c0000184 00000000`00000000 0000057f`00000000 fffffa80`08f9baf8 : 0x2
     
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  athurx+8e26
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: athurx
    IMAGE_NAME:  athurx.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4daeb071
    STACK_COMMAND:  .cxr 0xfffff8800333f060 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_athurx+8e26
    BUCKET_ID:  X64_0x7E_athurx+8e26
    Followup: MachineOwner
    ---------
    The problem seems to be caused by your wireless driver. Go to website and update


    Driver Description: Atheros AR9271 Wireless Network Adapter

    Atheros driver also written for - TP-LINK 150Mbps Wireless Lite N Adapter
    Driver Update Site: http://www.atheros.cz/

    TP-LINK drivers - http://www.tp-link.com/en/support/download/
      My Computer


  3. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #3

    richc46 said:
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
     
    Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_YONI-PC-Wed_12_24_2014_181604_53.zip\122114-33602-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e96890
    Debug session time: Sun Dec 21 12:38:21.238 2014 (UTC - 5:00)
    System Uptime: 0 days 0:22:05.051
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols
    Loading unloaded module list
    ......
    Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athurx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athurx.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000007E, {ffffffffc0000005, fffff88008808e26, fffff8800333f808, fffff8800333f060}
    Probably caused by : athurx.sys ( athurx+8e26 )
    Followup: MachineOwner
    ---------
    4: 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: fffff88008808e26, The address that the exception occurred at
    Arg3: fffff8800333f808, Exception Record Address
    Arg4: fffff8800333f060, 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: 
    athurx+8e26
    fffff880`08808e26 488b8098260000  mov     rax,qword ptr [rax+2698h]
    EXCEPTION_RECORD:  fffff8800333f808 -- (.exr 0xfffff8800333f808)
    ExceptionAddress: fffff88008808e26 (athurx+0x0000000000008e26)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000002698
    Attempt to read from address 0000000000002698
    CONTEXT:  fffff8800333f060 -- (.cxr 0xfffff8800333f060)
    rax=0000000000000000 rbx=fffffa800809e050 rcx=fffffa8008f9b030
    rdx=0000000000000002 rsi=fffffa800673a040 rdi=fffffa800724f580
    rip=fffff88008808e26 rsp=fffff8800333fa40 rbp=fffff80002e6e280
     r8=0000000000000000  r9=0000000000000f44 r10=fffff80002c53000
    r11=0000000000000000 r12=fffffa800724f580 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    athurx+0x8e26:
    fffff880`08808e26 488b8098260000  mov     rax,qword ptr [rax+2698h] ds:002b:00000000`00002698=????????????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_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:  0000000000002698
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f00100
     0000000000002698 
    FOLLOWUP_IP: 
    athurx+8e26
    fffff880`08808e26 488b8098260000  mov     rax,qword ptr [rax+2698h]
    BUGCHECK_STR:  0x7E
    LAST_CONTROL_TRANSFER:  from fffffa800809e050 to fffff88008808e26
    STACK_TEXT:  
    fffff880`0333fa40 fffffa80`0809e050 : fffff880`08808dc5 fffff880`0894c740 fffff880`0894c6f0 00000000`000015d7 : athurx+0x8e26
    fffff880`0333fa48 fffff880`08808dc5 : fffff880`0894c740 fffff880`0894c6f0 00000000`000015d7 00000000`00000002 : 0xfffffa80`0809e050
    fffff880`0333fa50 fffff880`0894c740 : fffff880`0894c6f0 00000000`000015d7 00000000`00000002 00000000`00000000 : athurx+0x8dc5
    fffff880`0333fa58 fffff880`0894c6f0 : 00000000`000015d7 00000000`00000002 00000000`00000000 00000000`c0000184 : athurx+0x14c740
    fffff880`0333fa60 00000000`000015d7 : 00000000`00000002 00000000`00000000 00000000`c0000184 00000000`00000000 : athurx+0x14c6f0
    fffff880`0333fa68 00000000`00000002 : 00000000`00000000 00000000`c0000184 00000000`00000000 0000057f`00000000 : 0x15d7
    fffff880`0333fa70 00000000`00000000 : 00000000`c0000184 00000000`00000000 0000057f`00000000 fffffa80`08f9baf8 : 0x2
     
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  athurx+8e26
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: athurx
    IMAGE_NAME:  athurx.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4daeb071
    STACK_COMMAND:  .cxr 0xfffff8800333f060 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_athurx+8e26
    BUCKET_ID:  X64_0x7E_athurx+8e26
    Followup: MachineOwner
    ---------
    The problem seems to be caused by your wireless driver. Go to website and update


    Driver Description: Atheros AR9271 Wireless Network Adapter

    Atheros driver also written for - TP-LINK 150Mbps Wireless Lite N Adapter
    Driver Update Site: http://www.atheros.cz/

    TP-LINK drivers - http://www.tp-link.com/en/support/download/
    Do i need the Atheros Drivers?
      My Computer


  4. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #4

    richc46 said:
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
     
    Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_YONI-PC-Wed_12_24_2014_181604_53.zip\122114-33602-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e96890
    Debug session time: Sun Dec 21 12:38:21.238 2014 (UTC - 5:00)
    System Uptime: 0 days 0:22:05.051
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols
    Loading unloaded module list
    ......
    Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athurx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athurx.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000007E, {ffffffffc0000005, fffff88008808e26, fffff8800333f808, fffff8800333f060}
    Probably caused by : athurx.sys ( athurx+8e26 )
    Followup: MachineOwner
    ---------
    4: 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: fffff88008808e26, The address that the exception occurred at
    Arg3: fffff8800333f808, Exception Record Address
    Arg4: fffff8800333f060, 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: 
    athurx+8e26
    fffff880`08808e26 488b8098260000  mov     rax,qword ptr [rax+2698h]
    EXCEPTION_RECORD:  fffff8800333f808 -- (.exr 0xfffff8800333f808)
    ExceptionAddress: fffff88008808e26 (athurx+0x0000000000008e26)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000002698
    Attempt to read from address 0000000000002698
    CONTEXT:  fffff8800333f060 -- (.cxr 0xfffff8800333f060)
    rax=0000000000000000 rbx=fffffa800809e050 rcx=fffffa8008f9b030
    rdx=0000000000000002 rsi=fffffa800673a040 rdi=fffffa800724f580
    rip=fffff88008808e26 rsp=fffff8800333fa40 rbp=fffff80002e6e280
     r8=0000000000000000  r9=0000000000000f44 r10=fffff80002c53000
    r11=0000000000000000 r12=fffffa800724f580 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    athurx+0x8e26:
    fffff880`08808e26 488b8098260000  mov     rax,qword ptr [rax+2698h] ds:002b:00000000`00002698=????????????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_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:  0000000000002698
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f00100
     0000000000002698 
    FOLLOWUP_IP: 
    athurx+8e26
    fffff880`08808e26 488b8098260000  mov     rax,qword ptr [rax+2698h]
    BUGCHECK_STR:  0x7E
    LAST_CONTROL_TRANSFER:  from fffffa800809e050 to fffff88008808e26
    STACK_TEXT:  
    fffff880`0333fa40 fffffa80`0809e050 : fffff880`08808dc5 fffff880`0894c740 fffff880`0894c6f0 00000000`000015d7 : athurx+0x8e26
    fffff880`0333fa48 fffff880`08808dc5 : fffff880`0894c740 fffff880`0894c6f0 00000000`000015d7 00000000`00000002 : 0xfffffa80`0809e050
    fffff880`0333fa50 fffff880`0894c740 : fffff880`0894c6f0 00000000`000015d7 00000000`00000002 00000000`00000000 : athurx+0x8dc5
    fffff880`0333fa58 fffff880`0894c6f0 : 00000000`000015d7 00000000`00000002 00000000`00000000 00000000`c0000184 : athurx+0x14c740
    fffff880`0333fa60 00000000`000015d7 : 00000000`00000002 00000000`00000000 00000000`c0000184 00000000`00000000 : athurx+0x14c6f0
    fffff880`0333fa68 00000000`00000002 : 00000000`00000000 00000000`c0000184 00000000`00000000 0000057f`00000000 : 0x15d7
    fffff880`0333fa70 00000000`00000000 : 00000000`c0000184 00000000`00000000 0000057f`00000000 fffffa80`08f9baf8 : 0x2
     
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  athurx+8e26
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: athurx
    IMAGE_NAME:  athurx.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4daeb071
    STACK_COMMAND:  .cxr 0xfffff8800333f060 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_athurx+8e26
    BUCKET_ID:  X64_0x7E_athurx+8e26
    Followup: MachineOwner
    ---------
    The problem seems to be caused by your wireless driver. Go to website and update


    Driver Description: Atheros AR9271 Wireless Network Adapter

    Atheros driver also written for - TP-LINK 150Mbps Wireless Lite N Adapter
    Driver Update Site: http://www.atheros.cz/

    TP-LINK drivers - http://www.tp-link.com/en/support/download/
    I tried both drivers for win 7, steel BSOD...
      My Computer


  5. Posts : 17,796
    Windows 10, Home Clean Install
       #5

    The report indicated that the problem was either the driver or TP Link. Are you using the correct TP Link? Can you change it and see if problem persists?
      My Computer


  6. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #6

    richc46 said:
    The report indicated that the problem was either the driver or TP Link. Are you using the correct TP Link? Can you change it and see if problem persists?
    I am sure my TP LINK is tl-w821N.v3
      My Computer


  7. Posts : 17,796
    Windows 10, Home Clean Install
       #7

    So lets assume for now that everything is correct
    The next most likely cause is the method used to unplug the device.
    Do you use the remove hardware icon, lower right of your monitor near the clock?
    Safely Remove Hardware - Eject Device

    If it is not the link and not the driver and you remove correctly, the next likely cause is registry errors

    I am calling it a night. I do not know if I will be on tomorrow. If I am not and no one helps, I will be back ASAP
    Last edited by richc46; 25 Dec 2014 at 01:40.
      My Computer


  8. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #8

    richc46 said:
    So lets assume for now that everything is correct
    The next most likely cause is the method used to unplug the device.
    Do you use the remove hardware icon, lower right of your monitor near the clock?
    Safely Remove Hardware - Eject Device

    If it is not the link and not the driver and you remove correctly, the next likely cause is registry errors

    I am calling it a night. I do not know if I will be on tomorrow. If I am not and no one helps, I will be back ASAP
    Thank you very much for your help!
    the Remove safely works, but i still want to solve the problem
      My Computer


  9. Posts : 17,796
    Windows 10, Home Clean Install
       #9

    There is no problem if using the correct procedure works. The remove safely icon is not a work around it is the procedure everyone is suppose to use; it is the correct way to remove hardware

    I am marking this thread as solved
      My Computer


  10. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #10

    richc46 said:
    There is no problem if using the correct procedure works. The remove safely icon is not a work around it is the procedure everyone is suppose to use; it is the correct way to remove hardware

    I am marking this thread as solved
    thanks for the solution, its just in other computers there is no BSOD with this TP LINK drive,
      My Computer


 
Page 1 of 2 12 LastLast

  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 11:32.
Find Us