BSOD when gaming.

Toggle sidebar Toggle sidebar
N

Nargrull

Reputable
Aug 30, 2014
9
0
4,510
Hi guys,

I built a brand new PC a couple of years ago and everything seemed fine with it. However, when playing specific games I would get a BSOD. It would be very rare so I basically ignored it. I ended up getting into xbox gaming and only using the PC for work etc.

I'm now trying to get back into PC gaming but I keep getting BSOD regularly when playing. I seems like the more demanding the game the faster the BSOD will occur. When playing some games I wont get a BSOD at all yet others I can't play for more than 15 minutes.

Can anyone give me some help on how to identify the problem or what it could be?

Thanks,

Nathan
 
Solution
J
yep, update your wireless card driver. if the device is a usb device you also need to update your cpu chipset drivers and if you have a special USB 3.0 chip on your motherboard you need to update that driver as well.

older version of athurx.sys corrupt memory of other device drivers that later bugcheck because their data is corrupted.

you don't get these updates from microsoft windows, you have to get it from the vendor because the vendor did not give microsoft a updated copy of the driver so microsoft will not push it out via windows update.

also note: the driver will corrupt other drivers data even if you are not using the device currently. Windows will load the drivers in a different order on each boot to confound hackers...
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,182
230
67,290
first thing to check would be to update your graphics driver directly from the graphics card vendor.
if it is a online game, often they will crash because of bugs in the ethernet driver and you just have to install the update.
(from your motherboard vendor website or directly from the vendor)

you can also have problems that are cause by overheating because of dust build up in the fans. just blow the dust out with a can of air.

best to check these before looking too hard at other potential causes
 
Upvote 0 Downvote
N

Nargrull

Reputable
Aug 30, 2014
9
0
4,510
My specs are;

Processor - AMD FX-8150 Eight Core Processor 3.87 GHz
RAM - 8.00 GB
Windows 7 64-bit Operating System

The 'WhoCrashed' program reports the following:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 13/06/2013 11:33:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061313-124020-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x101104)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003908104, 0xFFFFF880021061A8, 0xFFFFF88002105A00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\athurx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Thu 13/06/2013 11:33:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athurx.sys (athurx+0x101104)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88003908104, 0xFFFFF880021061A8, 0xFFFFF88002105A00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\athurx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Mon 03/06/2013 19:54:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060313-24445-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF8000360C7D0)
Bugcheck code: 0x50 (0xFFFFF80004627598, 0x0, 0xFFFFF8000360C7D0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 23/05/2013 21:03:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052313-24882-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF800036107D0)
Bugcheck code: 0x50 (0xFFFFF8000462B598, 0x0, 0xFFFFF800036107D0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 10/05/2013 21:30:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051013-30217-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF800030177D0)
Bugcheck code: 0x50 (0xFFFFF80004032598, 0x0, 0xFFFFF800030177D0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 01/05/2013 21:14:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050113-25864-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF8000302D7D0)
Bugcheck code: 0x50 (0xFFFFF80004048598, 0x0, 0xFFFFF8000302D7D0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 24/04/2013 22:12:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042413-26286-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF800030CAC00)
Bugcheck code: 0x50 (0xFFFFF80004036598, 0x0, 0xFFFFF8000301B7D0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: PAGE_FAULT_IN_NONPAGED_AREA



On Tue 16/04/2013 00:20:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041613-30451-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF800036147D0)
Bugcheck code: 0x50 (0xFFFFF8000462F598, 0x0, 0xFFFFF800036147D0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 06/04/2013 00:34:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040613-29499-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF800030177D0)
Bugcheck code: 0x50 (0xFFFFF80004032598, 0x0, 0xFFFFF800030177D0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 18/03/2013 18:01:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031813-19578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0xA (0x4, 0x2, 0x0, 0xFFFFF800030922A3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

It says that 'Atheros Extensible Wireless LAN device driver' was mainly responsible but that only caused one of the BSODs.
 
Upvote 0 Downvote
N

Nargrull

Reputable
Aug 30, 2014
9
0
4,510
I have checked for updates on my drivers and windows is saying that there aren't any that need installing.

I don't use wireless anymore, I use a wired connection using TP Link powerlines.

I am using AMD Radeon HD 7800 Series and my PSU is 600W Corsair Builder Series 600CX V2 80PLUS power supply.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,182
230
67,290
yep, update your wireless card driver. if the device is a usb device you also need to update your cpu chipset drivers and if you have a special USB 3.0 chip on your motherboard you need to update that driver as well.

older version of athurx.sys corrupt memory of other device drivers that later bugcheck because their data is corrupted.

you don't get these updates from microsoft windows, you have to get it from the vendor because the vendor did not give microsoft a updated copy of the driver so microsoft will not push it out via windows update.

also note: the driver will corrupt other drivers data even if you are not using the device currently. Windows will load the drivers in a different order on each boot to confound hackers. Problem is that driver will corrupt the data belonging to another driver that is stored in memory next to it. End effect is various different bugcheck in different drivers.

Also note: the other drivers are windows core drivers, windows will update them when problems are detected. After all this time they are pretty good and most failures are due to the drivers that windows can not update. IE the third party drivers. When a microsoft core driver fails they get 100's of thousands of automatic bug reports the next day via the automatic reporting. They tend to fix them pretty fast. For third party drivers microsoft gives the report and help to the vendor, the vendor might fix it and put a fix on their website if they feel it is worth while for them. (many vendors will not provide a fix unless they still currently sell the product)


Atheros AR9271 Wireless Network Adapter maybe here: https://www.atheros.cz/
or
TP-LINK 150Mbps Wireless Lite N Adapter maybe here: http://www.tp-link.com/en/support/download/

also note that usb device have the added fun of being associated with each USB port and when the device is unpluged it becomes hidden in device manager but the driver still gets loaded and corrupts memory.

you have to make device manager show the hidden devices, turn off the automatic install of drivers, delete the hidden devices and associated drivers, install the updated USB driver and re enable the automatic install of the drivers. Otherwise you delete the driver and the plug and play system re installs it a few seconds later and you are back at where you started.

You can also also have many different device drivers installed for one device but have to force certain ones to be used and windows put the place to do that in a obscure location in its UI so people never actually find it.
(my ethernet card had 6 different versions of drivers for the one card, 3 intel versions and 3 microsoft versions)

in the end, always check the version and date of the driver and make sure it changed after you update it

 
Upvote 0 Downvote
Solution
N

Nargrull

Reputable
Aug 30, 2014
9
0
4,510
Thanks for the help.

I have downloaded and installed drivers for Atheros here :https://www.atheros.cz/atheros-wireless-download.php?chipset=64&system=5
I have downloaded and installed drivers for TP-Link here: http://www.tp-link.com/en/support/download/?model=TL-WN822N&version=V2

However, can't I just remove the TP-Link driver as I do not use the device anymore?

My motherboard is a MSI MS-7640 and I am not sure if it has a special USB 3.0 chip on it.

I am going to restart my computer now and see whether I can a BSOD when playing.
 
Upvote 0 Downvote
N

Nargrull

Reputable
Aug 30, 2014
9
0
4,510
Looks like this didn't work as I got a BSOD when watching something on Twitch. Got the error PAGE FOUND IN NON_PAGED AREA and a STOP: 0x00000050 error code.

Any ideas?
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,182
230
67,290
Renesas Electronics USB 3.0 Host Controller is on that motherboard. The copy windows has may be ok.



 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,182
230
67,290
you would have to put a current bugcheck memory .dmp file on a cloud server so it can be looked at.
and run memtest86 and confirm you don't have a memory problem.



 
Upvote 0 Downvote
N

Nargrull

Reputable
Aug 30, 2014
9
0
4,510


I have run memtest86 and it has found nothing wrong with my RAM.

I then did the bugcheck on the memory.dmp file and found the below.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`0328e670
Debug session time: Thu Jun 13 12:33:56.478 2013 (UTC + 1:00)
System Uptime: 0 days 0:06:31.649
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff88003908104, fffff880021061a8, fffff88002105a00}

*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
Probably caused by : athurx.sys ( athurx+101104 )

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

5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003908104, The address that the exception occurred at
Arg3: fffff880021061a8, Exception Record Address
Arg4: fffff88002105a00, 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+101104
fffff880`03908104 8b1490 mov edx,dword ptr [rax+rdx*4]

EXCEPTION_RECORD: fffff880021061a8 -- (.exr 0xfffff880021061a8)
ExceptionAddress: fffff88003908104 (athurx+0x0000000000101104)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000060
Attempt to read from address 0000000000000060

CONTEXT: fffff88002105a00 -- (.cxr 0xfffff88002105a00)
rax=0000000000000000 rbx=fffffa800a13cb50 rcx=00000000ffffff8f
rdx=0000000000000018 rsi=0000000000000028 rdi=0000000000000000
rip=fffff88003908104 rsp=fffff880021063e0 rbp=0000000000000080
r8=0000000000000003 r9=00000000000000c5 r10=0000000000017603
r11=fffff88003090100 r12=fffffa800a038030 r13=fffff8800380e750
r14=0000000000000000 r15=fffff800077d6080
iopl=0 nv up ei pl zr ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010256
athurx+0x101104:
fffff880`03908104 8b1490 mov edx,dword ptr [rax+rdx*4] ds:002b:00000000`00000060=????????
Resetting default scope

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: 0000000000000060

READ_ADDRESS: 0000000000000060

FOLLOWUP_IP:
athurx+101104
fffff880`03908104 8b1490 mov edx,dword ptr [rax+rdx*4]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffff88003944a6f to fffff88003908104

STACK_TEXT:
fffff880`021063e0 fffff880`03944a6f : 00000000`00000000 fffff880`00000000 ffff0000`00000003 fffffa80`000000c5 : athurx+0x101104
fffff880`02106430 fffff880`0392d48c : fffffa80`0a2fd030 fffffa80`0a2fe9c8 fffffa80`0a2f0002 06000000`00000032 : athurx+0x13da6f
fffff880`021064c0 fffff880`039273ce : fffffa80`0a2fd030 fffff880`021067b0 fffffa80`0a2fe9c8 d9000000`00000000 : athurx+0x12648c
fffff880`021065a0 fffff880`038c76d5 : fffffa80`0a2fd030 fffff880`00000001 fffff880`021067b0 fffff800`00000000 : athurx+0x1203ce
fffff880`02106630 fffff880`038c8c45 : fffffa80`0a2bc030 fffff880`021067b0 fffffa80`0a2bfe00 fffffa80`00000000 : athurx+0xc06d5
fffff880`02106700 fffff880`038ad09e : fffffa80`0a2bc030 fffff880`021067b0 fffffa80`09b72030 ffff0000`018c725b : athurx+0xc1c45
fffff880`02106780 fffff880`03856e53 : fffffa80`09b72030 fffffa80`09b73778 00000000`00000000 fffffa80`09b72030 : athurx+0xa609e
fffff880`021067e0 fffff880`0387d12c : fffffa80`09b72030 fffffa80`09b72880 00000000`00000034 fffff880`02106938 : athurx+0x4fe53
fffff880`02106820 fffff880`0384309f : fffffa80`09b6d310 fffffa80`07ca4a30 fffffa80`00000001 fffffa80`00000005 : athurx+0x7612c
fffff880`021068e0 fffff880`03842ad1 : fffffa80`0a324030 fffffa80`07ca4a30 fffffa80`00000005 fffffa80`0a13cb50 : athurx+0x3c09f
fffff880`02106930 fffff880`03843bf5 : fffffa80`0a324030 fffffa80`07ca4a30 fffffa80`0a324287 fffffa80`0a13cb50 : athurx+0x3bad1
fffff880`02106980 fffff880`03843cc1 : fffffa80`0a324030 fffff880`03845801 fffffa80`0a324030 fffff880`038451d6 : athurx+0x3cbf5
fffff880`02106a70 fffff880`03846160 : fffffa80`0a324030 fffff880`039b2720 00000020`00000026 00000020`00000001 : athurx+0x3ccc1
fffff880`02106aa0 fffff880`03846351 : fffffa80`0a324030 fffffa80`00000000 fffffa80`09b74f90 fffffa80`0a13cb50 : athurx+0x3f160
fffff880`02106ad0 fffff880`0380d7f3 : 00000000`00000000 fffffa80`0a324030 00000000`00000000 00000000`00000000 : athurx+0x3f351
fffff880`02106b40 fffff880`0380e8c1 : 00000000`00000000 fffffa80`09b74f50 00000000`00000000 00000000`00000000 : athurx+0x67f3
fffff880`02106b90 fffff800`0335eede : fffffa80`0a038030 fffff800`0323be80 fffff880`02106c70 fffffa80`0a13cb50 : athurx+0x78c1
fffff880`02106c00 fffff800`030b1906 : fffff800`0323be80 fffffa80`0a13cb50 fffff800`03249cc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`02106c40 00000000`00000000 : fffff880`02107000 fffff880`02101000 fffff880`02105f90 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: athurx+101104

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: athurx

IMAGE_NAME: athurx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4daeb071

STACK_COMMAND: .cxr 0xfffff88002105a00 ; kb

FAILURE_BUCKET_ID: X64_0x7E_athurx+101104

BUCKET_ID: X64_0x7E_athurx+101104

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


It looks like its the same issue that someone picked up earlier in the thread but does anyone know how I can fix the issue as I believed I had updated the driver.

Thanks.

 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,182
230
67,290
in the windows debugger you can use the
lmiftsm command to list the drivers and dates and check the date to the driver to make sure it got updated.

it is very common for USB drivers not to get updated, they tend to get installed but you might have to go another step to select the driver as the one loaded.



 
Upvote 0 Downvote
N

Nargrull

Reputable
Aug 30, 2014
9
0
4,510


When I run that command I get the list below. As you can see it says Wed Apr 20 11:07:45 2011 for the athurx.sys driver. I thought I had updated it with the link earlier on in the thread. How do I update it?


5: kd> lmiftsm
start end module name
fffff880`00f01000 fffff880`00f58000 ACPI \SystemRoot\system32\drivers\ACPI.sys Sat Nov 20 09:19:16 2010 (4CE79294)
fffff880`03c4e000 fffff880`03cd7000 afd \SystemRoot\system32\drivers\afd.sys Wed Dec 28 03:59:20 2011 (4EFA9418)
fffff880`04c00000 fffff880`04c16000 AgileVpn \SystemRoot\system32\DRIVERS\AgileVpn.sys Tue Jul 14 01:10:24 2009 (4A5BCCF0)
fffff880`049de000 fffff880`049f2000 amdiox64 \SystemRoot\system32\DRIVERS\amdiox64.sys Thu Feb 18 15:17:53 2010 (4B7D5A21)
fffff880`04dcb000 fffff880`04de0000 amdppm \SystemRoot\system32\DRIVERS\amdppm.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD)
fffff880`0119d000 fffff880`011a8000 amdxata \SystemRoot\system32\drivers\amdxata.sys Fri Mar 19 16:18:18 2010 (4BA3A3CA)
fffff880`07e72000 fffff880`07ea4000 AODDriver2 \??\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Thu Apr 05 10:23:37 2012 (4F7D6499)
fffff880`0116a000 fffff880`01173000 atapi \SystemRoot\system32\drivers\atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`01173000 fffff880`0119d000 ataport \SystemRoot\system32\drivers\ataport.SYS Sat Nov 20 09:19:15 2010 (4CE79293)
fffff880`03807000 fffff880`039e5000 athurx \SystemRoot\system32\DRIVERS\athurx.sys Wed Apr 20 11:07:45 2011 (4DAEB071)
fffff880`0910b000 fffff880`09127000 AtihdW76 \SystemRoot\system32\drivers\AtihdW76.sys Tue Nov 06 21:41:51 2012 (5099841F)
fffff880`056c4000 fffff880`061da000 atikmdag \SystemRoot\system32\DRIVERS\atikmdag.sys Wed Dec 19 20:38:55 2012 (50D225DF)
fffff880`048f4000 fffff880`04981000 atikmpag \SystemRoot\system32\DRIVERS\atikmpag.sys Wed Dec 19 19:32:55 2012 (50D21667)
fffff880`0125b000 fffff880`01262000 Beep \SystemRoot\System32\Drivers\Beep.SYS Tue Jul 14 01:00:13 2009 (4A5BCA8D)
fffff880`04583000 fffff880`04594000 blbdrive \SystemRoot\system32\DRIVERS\blbdrive.sys Tue Jul 14 00:35:59 2009 (4A5BC4DF)
fffff880`07f90000 fffff880`07fae000 bowser \SystemRoot\system32\DRIVERS\bowser.sys Wed Feb 23 04:55:04 2011 (4D649328)
fffff960`00660000 fffff960`00687000 cdd \SystemRoot\System32\cdd.dll Thu Feb 03 11:25:25 2011 (4D4A90A5)
fffff880`01228000 fffff880`01252000 cdrom \SystemRoot\system32\drivers\cdrom.sys Sat Nov 20 09:19:20 2010 (4CE79298)
fffff880`00c00000 fffff880`00cc0000 CI \SystemRoot\system32\CI.dll Sat Nov 20 13:12:36 2010 (4CE7C944)
fffff880`010ea000 fffff880`0111a000 CLASSPNP \SystemRoot\system32\drivers\CLASSPNP.SYS Sat Nov 20 09:19:23 2010 (4CE7929B)
fffff880`00cfd000 fffff880`00d5b000 CLFS \SystemRoot\system32\CLFS.SYS Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`01400000 fffff880`01472000 cng \SystemRoot\System32\Drivers\cng.sys Sat Jun 02 04:25:51 2012 (4FC987BF)
fffff880`04de0000 fffff880`04df0000 CompositeBus \SystemRoot\system32\drivers\CompositeBus.sys Sat Nov 20 10:33:17 2010 (4CE7A3ED)
fffff880`0a1e9000 fffff880`0a1f7000 crashdmp \SystemRoot\System32\Drivers\crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD)
fffff880`044e2000 fffff880`04565000 csc \SystemRoot\system32\drivers\csc.sys Sat Nov 20 09:27:12 2010 (4CE79470)
fffff880`04565000 fffff880`04583000 dfsc \SystemRoot\System32\Drivers\dfsc.sys Sat Nov 20 09:26:31 2010 (4CE79447)
fffff880`044d3000 fffff880`044e2000 discache \SystemRoot\System32\drivers\discache.sys Tue Jul 14 00:37:18 2009 (4A5BC52E)
fffff880`013e4000 fffff880`013fa000 disk \SystemRoot\system32\DRIVERS\disk.sys Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`09164000 fffff880`09186000 drmk \SystemRoot\system32\drivers\drmk.sys Tue Jul 14 02:01:25 2009 (4A5BD8E5)
fffff880`03c00000 fffff880`03c49000 dtsoftbus01 \SystemRoot\system32\DRIVERS\dtsoftbus01.sys Fri Jan 13 13:45:46 2012 (4F10358A)
fffff880`09c0c000 fffff880`09c15000 dump_atapi \SystemRoot\System32\Drivers\dump_atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`09c00000 fffff880`09c0c000 dump_dumpata \SystemRoot\System32\Drivers\dump_dumpata.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`09c15000 fffff880`09c28000 dump_dumpfve \SystemRoot\System32\Drivers\dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
fffff880`0a15d000 fffff880`0a169000 Dxapi \SystemRoot\System32\drivers\Dxapi.sys Tue Jul 14 00:38:28 2009 (4A5BC574)
fffff880`04800000 fffff880`048f4000 dxgkrnl \SystemRoot\System32\drivers\dxgkrnl.sys Wed Apr 10 04:28:09 2013 (5164DC49)
fffff880`05600000 fffff880`05646000 dxgmms1 \SystemRoot\System32\drivers\dxgmms1.sys Wed Apr 10 04:27:15 2013 (5164DC13)
fffff880`01000000 fffff880`01014000 fileinfo \SystemRoot\system32\drivers\fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481)
fffff880`011a8000 fffff880`011f4000 fltmgr \SystemRoot\system32\drivers\fltmgr.sys Sat Nov 20 09:19:24 2010 (4CE7929C)
fffff880`0162c000 fffff880`01636000 Fs_Rec \SystemRoot\System32\Drivers\Fs_Rec.sys Thu Mar 01 03:41:06 2012 (4F4EEFD2)
fffff880`013aa000 fffff880`013e4000 fvevol \SystemRoot\System32\DRIVERS\fvevol.sys Thu Jan 24 03:11:24 2013 (5100A65C)
fffff880`01315000 fffff880`0135e000 fwpkclnt \SystemRoot\System32\drivers\fwpkclnt.sys Thu Jan 03 03:06:48 2013 (50E4F5C8)
fffff880`04d3d000 fffff880`04d43c00 GEARAspiWDM \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys Thu May 03 20:56:17 2012 (4FA2E2E1)
fffff800`03002000 fffff800`0304b000 hal hal.dll Sat Nov 20 13:00:25 2010 (4CE7C669)
fffff880`05646000 fffff880`0566a000 HDAudBus \SystemRoot\system32\drivers\HDAudBus.sys Sat Nov 20 10:43:42 2010 (4CE7A65E)
fffff880`09c28000 fffff880`09c41000 HIDCLASS \SystemRoot\system32\drivers\HIDCLASS.SYS Sat Nov 20 10:43:49 2010 (4CE7A665)
fffff880`09c41000 fffff880`09c49080 HIDPARSE \SystemRoot\system32\drivers\HIDPARSE.SYS Tue Jul 14 01:06:17 2009 (4A5BCBF9)
fffff880`039f2000 fffff880`03a00000 hidusb \SystemRoot\system32\drivers\hidusb.sys Sat Nov 20 10:43:49 2010 (4CE7A665)
fffff880`07ec7000 fffff880`07f90000 HTTP \SystemRoot\system32\drivers\HTTP.sys Sat Nov 20 09:24:30 2010 (4CE793CE)
fffff880`01636000 fffff880`0163f000 hwpolicy \SystemRoot\System32\drivers\hwpolicy.sys Sat Nov 20 09:18:54 2010 (4CE7927E)
fffff880`04df0000 fffff880`04dff000 kbdclass \SystemRoot\system32\drivers\kbdclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116)
fffff880`09c4a000 fffff880`09c58000 kbdhid \SystemRoot\system32\drivers\kbdhid.sys Sat Nov 20 10:33:25 2010 (4CE7A3F5)
fffff800`00ba8000 fffff800`00bb2000 kdcom kdcom.dll Sat Feb 05 16:52:49 2011 (4D4D8061)
fffff880`0499b000 fffff880`049de000 ks \SystemRoot\system32\drivers\ks.sys Sat Nov 20 10:33:23 2010 (4CE7A3F3)
fffff880`01600000 fffff880`0161b000 ksecdd \SystemRoot\System32\Drivers\ksecdd.sys Sat Jun 02 03:50:23 2012 (4FC97F6F)
fffff880`01472000 fffff880`0149c000 ksecpkg \SystemRoot\System32\Drivers\ksecpkg.sys Sat Jun 02 04:27:11 2012 (4FC9880F)
fffff880`09186000 fffff880`0918b200 ksthunk \SystemRoot\system32\drivers\ksthunk.sys Tue Jul 14 01:00:19 2009 (4A5BCA93)
fffff880`09c88000 fffff880`09c9d000 lltdio \SystemRoot\system32\DRIVERS\lltdio.sys Tue Jul 14 01:08:50 2009 (4A5BCC92)
fffff880`09c65000 fffff880`09c88000 luafv \SystemRoot\system32\drivers\luafv.sys Tue Jul 14 00:26:13 2009 (4A5BC295)
fffff880`0a14f000 fffff880`0a15d000 MBfilt64 \SystemRoot\system32\drivers\MBfilt64.sys Fri Jul 31 04:40:32 2009 (4A7267B0)
fffff880`00cdc000 fffff880`00ce9000 mcupdate_AuthenticAMD \SystemRoot\system32\mcupdate_AuthenticAMD.dll Tue Jul 14 02:29:09 2009 (4A5BDF65)
fffff880`0a1be000 fffff880`0a1cc000 monitor \SystemRoot\system32\DRIVERS\monitor.sys Tue Jul 14 00:38:52 2009 (4A5BC58C)
fffff880`056b4000 fffff880`056c3000 mouclass \SystemRoot\system32\drivers\mouclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116)
fffff880`09c58000 fffff880`09c65000 mouhid \SystemRoot\system32\DRIVERS\mouhid.sys Tue Jul 14 01:00:20 2009 (4A5BCA94)
fffff880`00e00000 fffff880`00e1a000 mountmgr \SystemRoot\System32\drivers\mountmgr.sys Sat Nov 20 09:19:21 2010 (4CE79299)
fffff880`07fae000 fffff880`07fc6000 mpsdrv \SystemRoot\System32\drivers\mpsdrv.sys Tue Jul 14 01:08:25 2009 (4A5BCC79)
fffff880`07fc6000 fffff880`07ff3000 mrxsmb \SystemRoot\system32\DRIVERS\mrxsmb.sys Wed Apr 27 03:40:38 2011 (4DB78226)
fffff880`07e00000 fffff880`07e4e000 mrxsmb10 \SystemRoot\system32\DRIVERS\mrxsmb10.sys Sat Jul 09 03:46:28 2011 (4E17C104)
fffff880`07e4e000 fffff880`07e72000 mrxsmb20 \SystemRoot\system32\DRIVERS\mrxsmb20.sys Wed Apr 27 03:39:37 2011 (4DB781E9)
fffff880`010a2000 fffff880`010ad000 Msfs \SystemRoot\System32\Drivers\Msfs.SYS Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`00f61000 fffff880`00f6b000 msisadrv \SystemRoot\system32\drivers\msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE)
fffff880`01032000 fffff880`01090000 msrpc \SystemRoot\System32\drivers\msrpc.sys Sat Nov 20 09:21:56 2010 (4CE79334)
fffff880`044c8000 fffff880`044d3000 mssmbios \SystemRoot\system32\drivers\mssmbios.sys Tue Jul 14 00:31:10 2009 (4A5BC3BE)
fffff880`015da000 fffff880`015ec000 mup \SystemRoot\System32\Drivers\mup.sys Tue Jul 14 00:23:45 2009 (4A5BC201)
fffff880`014db000 fffff880`015cd000 NDIS \SystemRoot\System32\drivers\NDIS.SYS Wed Aug 22 16:11:46 2012 (5034F6B2)
fffff880`04c3a000 fffff880`04c46000 ndistapi \SystemRoot\system32\DRIVERS\ndistapi.sys Tue Jul 14 01:10:00 2009 (4A5BCCD8)
fffff880`09c9d000 fffff880`09cb0000 ndisuio \SystemRoot\system32\DRIVERS\ndisuio.sys Sat Nov 20 10:50:08 2010 (4CE7A7E0)
fffff880`0566a000 fffff880`05699000 ndiswan \SystemRoot\system32\DRIVERS\ndiswan.sys Sat Nov 20 10:52:32 2010 (4CE7A870)
fffff880`090f6000 fffff880`0910b000 NDProxy \SystemRoot\System32\Drivers\NDProxy.SYS Sat Nov 20 10:52:20 2010 (4CE7A864)
fffff880`03d76000 fffff880`03d85000 netbios \SystemRoot\system32\DRIVERS\netbios.sys Tue Jul 14 01:09:26 2009 (4A5BCCB6)
fffff880`03cd7000 fffff880`03d1c000 netbt \SystemRoot\System32\DRIVERS\netbt.sys Sat Nov 20 09:23:18 2010 (4CE79386)
fffff880`012b5000 fffff880`01315000 NETIO \SystemRoot\System32\drivers\NETIO.SYS Wed Aug 22 16:11:28 2012 (5034F6A0)
fffff880`010ad000 fffff880`010be000 Npfs \SystemRoot\System32\Drivers\Npfs.SYS Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`044bc000 fffff880`044c8000 nsiproxy \SystemRoot\system32\drivers\nsiproxy.sys Tue Jul 14 00:21:02 2009 (4A5BC15E)
fffff800`0304b000 fffff800`03631000 nt ntkrnlmp.exe Tue Mar 19 03:21:42 2013 (5147D9C6)
fffff880`01645000 fffff880`017e7000 Ntfs \SystemRoot\System32\Drivers\Ntfs.sys Fri Apr 12 12:54:36 2013 (5167F5FC)
fffff880`0ad35000 fffff880`0ad3c000 NTIOLib_X64 \??\C:\Program Files (x86)\MSI\Super-Charger\NTIOLib_X64.sys Mon Jan 18 02:31:59 2010 (4B53C81F)
fffff880`01252000 fffff880`0125b000 Null \SystemRoot\System32\Drivers\Null.SYS Tue Jul 14 00:19:37 2009 (4A5BC109)
fffff880`00ddf000 fffff880`00df8000 nusb3hub \SystemRoot\system32\DRIVERS\nusb3hub.sys Thu Feb 10 05:52:32 2011 (4D537D20)
fffff880`04cfc000 fffff880`04d2d000 nusb3xhc \SystemRoot\system32\DRIVERS\nusb3xhc.sys Thu Feb 10 05:52:33 2011 (4D537D21)
fffff880`00db7000 fffff880`00ddf000 nvraid \SystemRoot\system32\drivers\nvraid.sys Fri Mar 19 20:59:20 2010 (4BA3E5A8)
fffff880`0918c000 fffff880`091df000 nwifi \SystemRoot\system32\DRIVERS\nwifi.sys Tue Jul 14 01:07:23 2009 (4A5BCC3B)
fffff880`03d25000 fffff880`03d4b000 pacer \SystemRoot\system32\DRIVERS\pacer.sys Sat Nov 20 10:52:18 2010 (4CE7A862)
fffff880`00fab000 fffff880`00fc0000 partmgr \SystemRoot\System32\drivers\partmgr.sys Sat Mar 17 05:06:09 2012 (4F641BC1)
fffff880`00f6b000 fffff880`00f9e000 pci \SystemRoot\system32\drivers\pci.sys Sat Nov 20 09:19:11 2010 (4CE7928F)
fffff880`00fd5000 fffff880`00fdc000 pciide \SystemRoot\system32\drivers\pciide.sys Tue Jul 14 00:19:49 2009 (4A5BC115)
fffff880`00fdc000 fffff880`00fec000 PCIIDEX \SystemRoot\system32\drivers\PCIIDEX.SYS Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`0161b000 fffff880`0162c000 pcw \SystemRoot\System32\drivers\pcw.sys Tue Jul 14 00:19:27 2009 (4A5BC0FF)
fffff880`0a4d0000 fffff880`0a576000 peauth \SystemRoot\system32\drivers\peauth.sys Tue Jul 14 02:01:19 2009 (4A5BD8DF)
fffff880`09127000 fffff880`09164000 portcls \SystemRoot\system32\drivers\portcls.sys Tue Jul 14 01:06:27 2009 (4A5BCC03)
fffff880`00ce9000 fffff880`00cfd000 PSHED \SystemRoot\system32\PSHED.dll Tue Jul 14 02:32:23 2009 (4A5BE027)
fffff880`04c16000 fffff880`04c3a000 rasl2tp \SystemRoot\system32\DRIVERS\rasl2tp.sys Sat Nov 20 10:52:34 2010 (4CE7A872)
fffff880`05699000 fffff880`056b4000 raspppoe \SystemRoot\system32\DRIVERS\raspppoe.sys Tue Jul 14 01:10:17 2009 (4A5BCCE9)
fffff880`061da000 fffff880`061fb000 raspptp \SystemRoot\system32\DRIVERS\raspptp.sys Sat Nov 20 10:52:31 2010 (4CE7A86F)
fffff880`04981000 fffff880`0499b000 rassstp \SystemRoot\system32\DRIVERS\rassstp.sys Tue Jul 14 01:10:25 2009 (4A5BCCF1)
fffff880`0446b000 fffff880`044bc000 rdbss \SystemRoot\system32\DRIVERS\rdbss.sys Sat Nov 20 09:27:51 2010 (4CE79497)
fffff880`04c46000 fffff880`04c51000 rdpbus \SystemRoot\system32\DRIVERS\rdpbus.sys Tue Jul 14 01:17:46 2009 (4A5BCEAA)
fffff880`012a5000 fffff880`012ae000 RDPCDD \SystemRoot\System32\DRIVERS\RDPCDD.sys Tue Jul 14 01:16:34 2009 (4A5BCE62)
fffff880`01090000 fffff880`01099000 rdpencdd \SystemRoot\system32\drivers\rdpencdd.sys Tue Jul 14 01:16:34 2009 (4A5BCE62)
fffff880`01099000 fffff880`010a2000 rdprefmp \SystemRoot\system32\drivers\rdprefmp.sys Tue Jul 14 01:16:35 2009 (4A5BCE63)
fffff880`0149c000 fffff880`014d6000 rdyboost \SystemRoot\System32\drivers\rdyboost.sys Sat Nov 20 09:43:10 2010 (4CE7982E)
fffff880`09cb0000 fffff880`09cc8000 rspndr \SystemRoot\system32\DRIVERS\rspndr.sys Tue Jul 14 01:08:50 2009 (4A5BCC92)
fffff880`04c5c000 fffff880`04cfc000 Rt64win7 \SystemRoot\system32\DRIVERS\Rt64win7.sys Tue Sep 27 15:50:33 2011 (4E81E2B9)
fffff880`09cd0000 fffff880`0a14e700 RTKVHD64 \SystemRoot\system32\drivers\RTKVHD64.sys Tue Dec 13 10:24:54 2011 (4EE727F6)
fffff880`0a576000 fffff880`0a581000 secdrv \SystemRoot\System32\Drivers\secdrv.SYS Wed Sep 13 14:18:38 2006 (4508052E)
fffff880`04db6000 fffff880`04dc2000 serenum \SystemRoot\system32\DRIVERS\serenum.sys Tue Jul 14 01:00:33 2009 (4A5BCAA1)
fffff880`03d85000 fffff880`03da2000 serial \SystemRoot\system32\DRIVERS\serial.sys Tue Jul 14 01:00:40 2009 (4A5BCAA8)
fffff880`017f7000 fffff880`017ff000 spldr \SystemRoot\System32\Drivers\spldr.sys Mon May 11 17:56:27 2009 (4A0858BB)
fffff880`09000000 fffff880`09098000 srv \SystemRoot\System32\DRIVERS\srv.sys Fri Apr 29 04:06:06 2011 (4DBA2B1E)
fffff880`0a400000 fffff880`0a469000 srv2 \SystemRoot\System32\DRIVERS\srv2.sys Fri Apr 29 04:05:46 2011 (4DBA2B0A)
fffff880`0a581000 fffff880`0a5b2000 srvnet \SystemRoot\System32\DRIVERS\srvnet.sys Fri Apr 29 04:05:35 2011 (4DBA2AFF)
fffff880`04c51000 fffff880`04c52480 swenum \SystemRoot\system32\drivers\swenum.sys Tue Jul 14 01:00:18 2009 (4A5BCA92)
fffff880`01800000 fffff880`01a00000 tcpip \SystemRoot\System32\drivers\tcpip.sys Thu Jan 03 03:11:48 2013 (50E4F6F4)
fffff880`0a5b2000 fffff880`0a5c4000 tcpipreg \SystemRoot\System32\drivers\tcpipreg.sys Wed Oct 03 17:07:26 2012 (506C62BE)
fffff880`015cd000 fffff880`015da000 TDI \SystemRoot\System32\drivers\TDI.SYS Sat Nov 20 09:22:06 2010 (4CE7933E)
fffff880`010be000 fffff880`010e0000 tdx \SystemRoot\system32\DRIVERS\tdx.sys Sat Nov 20 09:21:54 2010 (4CE79332)
fffff880`04457000 fffff880`0446b000 termdd \SystemRoot\system32\drivers\termdd.sys Sat Nov 20 11:03:40 2010 (4CE7AB0C)
fffff960`00420000 fffff960`0042a000 TSDDD \SystemRoot\System32\TSDDD.dll Tue Jul 14 01:16:34 2009 (4A5BCE62)
fffff880`04594000 fffff880`045ba000 tunnel \SystemRoot\system32\DRIVERS\tunnel.sys Sat Nov 20 10:51:50 2010 (4CE7A846)
fffff880`0a169000 fffff880`0a1be000 udfs \SystemRoot\system32\DRIVERS\udfs.sys Sat Nov 20 09:26:11 2010 (4CE79433)
fffff880`045ba000 fffff880`045cc000 umbus \SystemRoot\system32\drivers\umbus.sys Sat Nov 20 10:44:37 2010 (4CE7A695)
fffff880`0a1cc000 fffff880`0a1e9000 usbccgp \SystemRoot\system32\DRIVERS\usbccgp.sys Fri Mar 25 03:29:14 2011 (4D8C0C0A)
fffff880`04d2d000 fffff880`04d2ef00 USBD \SystemRoot\system32\DRIVERS\USBD.SYS Fri Mar 25 03:28:59 2011 (4D8C0BFB)
fffff880`04da5000 fffff880`04db6000 usbehci \SystemRoot\system32\DRIVERS\usbehci.sys Fri Mar 25 03:29:04 2011 (4D8C0C00)
fffff880`04d2f000 fffff880`04d3d000 usbfilter \SystemRoot\system32\DRIVERS\usbfilter.sys Mon Nov 29 09:50:21 2010 (4CF3775D)
fffff880`0909c000 fffff880`090f6000 usbhub \SystemRoot\system32\DRIVERS\usbhub.sys Fri Mar 25 03:29:25 2011 (4D8C0C15)
fffff880`04d44000 fffff880`04d4f000 usbohci \SystemRoot\system32\DRIVERS\usbohci.sys Fri Mar 25 03:29:03 2011 (4D8C0BFF)
fffff880`04d4f000 fffff880`04da5000 USBPORT \SystemRoot\system32\DRIVERS\USBPORT.SYS Fri Mar 25 03:29:12 2011 (4D8C0C08)
fffff880`045e9000 fffff880`045f8000 usbrpm \SystemRoot\system32\DRIVERS\usbrpm.sys Sat Nov 20 11:37:19 2010 (4CE7B2EF)
fffff880`00f9e000 fffff880`00fab000 vdrvroot \SystemRoot\system32\drivers\vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB)
fffff880`01262000 fffff880`01270000 vga \SystemRoot\System32\drivers\vga.sys Tue Jul 14 00:38:47 2009 (4A5BC587)
fffff880`01270000 fffff880`01295000 VIDEOPRT \SystemRoot\System32\drivers\VIDEOPRT.SYS Tue Jul 14 00:38:51 2009 (4A5BC58B)
fffff880`0111a000 fffff880`01156000 vmbus \SystemRoot\system32\drivers\vmbus.sys Sat Nov 20 09:57:29 2010 (4CE79B89)
fffff880`017e7000 fffff880`017f7000 vmstorfl \SystemRoot\system32\drivers\vmstorfl.sys Sat Nov 20 09:57:30 2010 (4CE79B8A)
fffff880`00fc0000 fffff880`00fd5000 volmgr \SystemRoot\system32\drivers\volmgr.sys Sat Nov 20 09:19:28 2010 (4CE792A0)
fffff880`00d5b000 fffff880`00db7000 volmgrx \SystemRoot\System32\drivers\volmgrx.sys Sat Nov 20 09:20:43 2010 (4CE792EB)
fffff880`0135e000 fffff880`013aa000 volsnap \SystemRoot\system32\drivers\volsnap.sys Sat Nov 20 09:20:08 2010 (4CE792C8)
fffff880`03dbd000 fffff880`03df9000 vpchbus \SystemRoot\system32\DRIVERS\vpchbus.sys Wed Apr 15 06:49:20 2009 (49E57560)
fffff880`03d4b000 fffff880`03d60000 vpcnfltr \SystemRoot\system32\DRIVERS\vpcnfltr.sys Wed Apr 15 06:49:17 2009 (49E5755D)
fffff880`045cc000 fffff880`045e9000 vpcusb \SystemRoot\system32\DRIVERS\vpcusb.sys Wed Apr 15 06:49:20 2009 (49E57560)
fffff880`04400000 fffff880`04456f00 vpcvmm \SystemRoot\system32\drivers\vpcvmm.sys Wed Apr 15 06:49:22 2009 (49E57562)
fffff880`039e5000 fffff880`039f2000 vwifibus \SystemRoot\system32\DRIVERS\vwifibus.sys Tue Jul 14 01:07:21 2009 (4A5BCC39)
fffff880`03d60000 fffff880`03d76000 vwififlt \SystemRoot\system32\DRIVERS\vwififlt.sys Tue Jul 14 01:07:22 2009 (4A5BCC3A)
fffff880`091df000 fffff880`091e9000 vwifimp \SystemRoot\system32\DRIVERS\vwifimp.sys Tue Jul 14 01:07:28 2009 (4A5BCC40)
fffff880`03da2000 fffff880`03dbd000 wanarp \SystemRoot\system32\DRIVERS\wanarp.sys Sat Nov 20 10:52:36 2010 (4CE7A874)
fffff880`01295000 fffff880`012a5000 watchdog \SystemRoot\System32\drivers\watchdog.sys Tue Jul 14 00:37:35 2009 (4A5BC53F)
fffff880`00e2f000 fffff880`00ef1000 Wdf01000 \SystemRoot\system32\drivers\Wdf01000.sys Thu Jul 26 03:25:13 2012 (5010AA89)
fffff880`00ef1000 fffff880`00f01000 WDFLDR \SystemRoot\system32\drivers\WDFLDR.SYS Thu Jul 26 03:29:04 2012 (5010AB70)
fffff880`03d1c000 fffff880`03d25000 wfplwf \SystemRoot\system32\DRIVERS\wfplwf.sys Tue Jul 14 01:09:26 2009 (4A5BCCB6)
fffff960`00000000 fffff960`00317000 win32k \SystemRoot\System32\win32k.sys Wed Apr 10 04:30:19 2013 (5164DCCB)
fffff880`01156000 fffff880`0116a000 winhv \SystemRoot\system32\drivers\winhv.sys Sat Nov 20 09:20:02 2010 (4CE792C2)
fffff880`04dc2000 fffff880`04dcb000 wmiacpi \SystemRoot\system32\drivers\wmiacpi.sys Tue Jul 14 00:31:02 2009 (4A5BC3B6)
fffff880`00f58000 fffff880`00f61000 WMILIB \SystemRoot\system32\drivers\WMILIB.SYS Tue Jul 14 00:19:51 2009 (4A5BC117)
fffff880`01014000 fffff880`01032000 WRkrn \SystemRoot\System32\drivers\WRkrn.sys Tue May 28 18:18:35 2013 (51A4E6EB)

Unloaded modules:
fffff880`0acc4000 fffff880`0ad35000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00071000
fffff880`015ec000 fffff880`015fa000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`01200000 fffff880`0120c000 dump_ataport.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000C000
fffff880`0120c000 fffff880`01215000 dump_atapi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00009000
fffff880`01215000 fffff880`01228000 dump_dumpfve.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00013000
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,182
230
67,290
basically, disconnect your usb wireless device, then you have to tell device manager to display disconnected devices, then delete each disconnected usb device. The device derive will be associated with each usb port you plugged the device into. you can also use the control panel device manager and go to update the device but slelect the have disk option. it is in a stupid hard to find menu subtree. Sorry, i don't have windows 7 installed anymore so I can not tell you where to look exactly. you can also use the cmd.exe as a admin and use pnputil.exe tool to remove the package.

you would use pnputil.exe -e to list all the packages installed, find the package name
then run pnputil.exe -d Oem#.inf (where the oem number it the package you want to remove)
http://technet.microsoft.com/en-us/library/cc730875.aspx




 
Upvote 0 Downvote
N

Nargrull

Reputable
Aug 30, 2014
9
0
4,510
When I use the cmd.exe & pnputil -e to find athurx.sys it isn't showing in my network adapters. I had showing an Apple one, two Realtek's and a RaLink driver.

Should I be removing those?



 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom