Solved BSOD after unplugging USB(TP link)

J

jons1122

New member
Local time
4:59 PM
Messages
7
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

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Coustum
OS
Windows 7 Ultimate x64
CPU
CORE I 7 4790K
Motherboard
H97M-HD3
Memory
8 GB RAM
Graphics Card(s)
EVGA GTX760 OVERCLOCKED
Hard Drives
1TB
Antivirus
NONE
Browser
CHROME
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 [B]athurx.sys[/B]
*** 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

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Dell XPS 420
OS
Windows 10, Home Clean Install
CPU
Intel Core2 processsor Q8200(2.33Ghz 1333FSB) Quad Core Tech
Motherboard
Dell
Memory
6 gb
Graphics Card(s)
ATI Radeon 256MB HD3650
Sound Card
Intergrated 7.1 Channel Audio
Monitor(s) Displays
Dell SP2009W 20"
Hard Drives
640 GB Serial ATA Hard drive
Cooling
Fan
Keyboard
Dell USB Keyboard
Mouse
Dell Premium Optical USB
Internet Speed
DSL 2.85
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 [B]athurx.sys[/B]
*** 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/
Click to expand...

Do i need the Atheros Drivers?
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Coustum
OS
Windows 7 Ultimate x64
CPU
CORE I 7 4790K
Motherboard
H97M-HD3
Memory
8 GB RAM
Graphics Card(s)
EVGA GTX760 OVERCLOCKED
Hard Drives
1TB
Antivirus
NONE
Browser
CHROME
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 [B]athurx.sys[/B]
*** 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/
Click to expand...

I tried both drivers for win 7, steel BSOD...
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Coustum
OS
Windows 7 Ultimate x64
CPU
CORE I 7 4790K
Motherboard
H97M-HD3
Memory
8 GB RAM
Graphics Card(s)
EVGA GTX760 OVERCLOCKED
Hard Drives
1TB
Antivirus
NONE
Browser
CHROME
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

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Dell XPS 420
OS
Windows 10, Home Clean Install
CPU
Intel Core2 processsor Q8200(2.33Ghz 1333FSB) Quad Core Tech
Motherboard
Dell
Memory
6 gb
Graphics Card(s)
ATI Radeon 256MB HD3650
Sound Card
Intergrated 7.1 Channel Audio
Monitor(s) Displays
Dell SP2009W 20"
Hard Drives
640 GB Serial ATA Hard drive
Cooling
Fan
Keyboard
Dell USB Keyboard
Mouse
Dell Premium Optical USB
Internet Speed
DSL 2.85
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?
Click to expand...

I am sure my TP LINK is tl-w821N.v3
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Coustum
OS
Windows 7 Ultimate x64
CPU
CORE I 7 4790K
Motherboard
H97M-HD3
Memory
8 GB RAM
Graphics Card(s)
EVGA GTX760 OVERCLOCKED
Hard Drives
1TB
Antivirus
NONE
Browser
CHROME
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?
http://www.sevenforums.com/tutorials/10169-safely-remove-hardware-eject-device.html

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:

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Dell XPS 420
OS
Windows 10, Home Clean Install
CPU
Intel Core2 processsor Q8200(2.33Ghz 1333FSB) Quad Core Tech
Motherboard
Dell
Memory
6 gb
Graphics Card(s)
ATI Radeon 256MB HD3650
Sound Card
Intergrated 7.1 Channel Audio
Monitor(s) Displays
Dell SP2009W 20"
Hard Drives
640 GB Serial ATA Hard drive
Cooling
Fan
Keyboard
Dell USB Keyboard
Mouse
Dell Premium Optical USB
Internet Speed
DSL 2.85
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?
http://www.sevenforums.com/tutorials/10169-safely-remove-hardware-eject-device.html

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
Click to expand...

Thank you very much for your help!
the Remove safely works, but i still want to solve the problem
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Coustum
OS
Windows 7 Ultimate x64
CPU
CORE I 7 4790K
Motherboard
H97M-HD3
Memory
8 GB RAM
Graphics Card(s)
EVGA GTX760 OVERCLOCKED
Hard Drives
1TB
Antivirus
NONE
Browser
CHROME
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

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Dell XPS 420
OS
Windows 10, Home Clean Install
CPU
Intel Core2 processsor Q8200(2.33Ghz 1333FSB) Quad Core Tech
Motherboard
Dell
Memory
6 gb
Graphics Card(s)
ATI Radeon 256MB HD3650
Sound Card
Intergrated 7.1 Channel Audio
Monitor(s) Displays
Dell SP2009W 20"
Hard Drives
640 GB Serial ATA Hard drive
Cooling
Fan
Keyboard
Dell USB Keyboard
Mouse
Dell Premium Optical USB
Internet Speed
DSL 2.85
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
Click to expand...

thanks for the solution, its just in other computers there is no BSOD with this TP LINK drive,
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Coustum
OS
Windows 7 Ultimate x64
CPU
CORE I 7 4790K
Motherboard
H97M-HD3
Memory
8 GB RAM
Graphics Card(s)
EVGA GTX760 OVERCLOCKED
Hard Drives
1TB
Antivirus
NONE
Browser
CHROME
MS does not know what effect if any there will be if hardware is not removed correctly. You can have loss of information, bsod, freezing or even hard drive damage. TY for the rep
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Dell XPS 420
OS
Windows 10, Home Clean Install
CPU
Intel Core2 processsor Q8200(2.33Ghz 1333FSB) Quad Core Tech
Motherboard
Dell
Memory
6 gb
Graphics Card(s)
ATI Radeon 256MB HD3650
Sound Card
Intergrated 7.1 Channel Audio
Monitor(s) Displays
Dell SP2009W 20"
Hard Drives
640 GB Serial ATA Hard drive
Cooling
Fan
Keyboard
Dell USB Keyboard
Mouse
Dell Premium Optical USB
Internet Speed
DSL 2.85
richc46 said:
MS does not know what effect if any there will be if hardware is not removed correctly. You can have loss of information, bsod, freezing or even hard drive damage. TY for the rep
Click to expand...

thank you!
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Coustum
OS
Windows 7 Ultimate x64
CPU
CORE I 7 4790K
Motherboard
H97M-HD3
Memory
8 GB RAM
Graphics Card(s)
EVGA GTX760 OVERCLOCKED
Hard Drives
1TB
Antivirus
NONE
Browser
CHROME
You must log in or register to reply here.

Similar threads

BSOD after unplugging HDMI-Cable from Intel NUC
Replies
4
Views
4K
Golden
Golden
Several BSOD after unplugging USB mouse.
Replies
1
Views
2K
Arc
Arc
Solved BSOD after unplugging power cable by mistake while playing Css.
Replies
13
Views
4K
koolkat77
koolkat77
BSOD 5-10 mins after unplugging eSata drive
Replies
8
Views
2K
supergahar
S
BSOD after unplugging ESATA external drive
Replies
9
Views
5K
Hopalong X
Hopalong X
Back
Top