Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after unplugging USB(TP link)

24 Dec 2014   #1
jons1122

Windows 7 Ultimate x64
 
 
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 System SpecsSystem Spec
.
24 Dec 2014   #2
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

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 System SpecsSystem Spec
25 Dec 2014   #3
jons1122

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by richc46 View Post
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 System SpecsSystem Spec
.

25 Dec 2014   #4
jons1122

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by richc46 View Post
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 System SpecsSystem Spec
25 Dec 2014   #5
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

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 System SpecsSystem Spec
25 Dec 2014   #6
jons1122

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by richc46 View Post
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 System SpecsSystem Spec
25 Dec 2014   #7
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

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
My System SpecsSystem Spec
25 Dec 2014   #8
jons1122

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by richc46 View Post
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 System SpecsSystem Spec
25 Dec 2014   #9
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

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 System SpecsSystem Spec
26 Dec 2014   #10
jons1122

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by richc46 View Post
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 System SpecsSystem Spec
Reply

 BSOD after unplugging USB(TP link)




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD unplugging USB mouse
Hi, I have been using my laptop with windows 7 installed for a while. Whenever I unplug my USB mouse, I receive a blue screen and windows says that it will restart. I have the dump file, and I can attach it to this post. Thanks for everyone's help.
BSOD Help and Support
Several BSOD after unplugging USB mouse.
EDIT:uploaded correct zip My problems all started a few days ago after inadvertently unplugging my mouse from the computer. Since then I have had a handful of bsod. I have run memtest and it came back negative. I have also run chkdsk. This is the result of that test Checking file system on C:...
BSOD Help and Support
Can only recover from BSOD by unplugging all USB devices
Been posting my problem in somebody's closed thread. My bad. So, here my problem in my very own new thread. PC slows down, then locks up, then does the BSOD thing. Sometimes with very few things open. (email and a magazine reader) Sometimes with lots of things open. (powerpoint, email, Bible...
BSOD Help and Support
BSOD when unplugging ethernet
It's the weirdest thing.. If I disconnect the ethernet plug from the computer, it will blue screen. Every time. Based on the blue screen info and the searches I have done on the error, it seems there is something wrong with the Nvidia drivers? I have went to every resource I could to make sure...
BSOD Help and Support
BSOD When unplugging xbox 360 accesories
Basically it just gives a BSOD every time i unplug the usb. I have the latest beta drivers downloaded from windows update. I have a wired control and the xplorer guitar (gh2), both works perfectly, the only trouble is when i unplug. The BSOD indicates something like irql less or equal...
Drivers


Our Sites

Site Links

About Us

Find 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 19:26.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App