New
#11
A stop 0x10D BSOD causes mostly by any device driver or RAM.
We already have a failing device driver. So we need to fix it at first before any further attempt to troubleshoot.
A stop 0x10D BSOD causes mostly by any device driver or RAM.
We already have a failing device driver. So we need to fix it at first before any further attempt to troubleshoot.
So the problem is the TP-LINK Wireless USB Adapter? My adapter is this one: TL-WN721N - Welcome to TP-LINK
I simply downloaded the first one (TL-WN721N_V1_131113), is that ok?
Also, I have another question related to that. I have deleted every TP Link related file, but I still connect to the Internet whenever I "plug in" the USB. Is that actually what should happen?
It feels like the USB driver is completely useless and I have a connection regardless.
Deleting files will not uninstall the driver actually, until and unless the driver file (it is athrux.sys; that means it is developed by Atheros and marketed by TP Link) situated in C:\Windows\drivers. So connectivity will remain.
The driver that you have downloaded is a perfect one. Let us know how the computer is running after applying the update.
Is it better to delete that file as well? Because after I tried to install the "updated" one, it didn't really overwrite the old one but both "versions" were simultanously up.
I think I got that one wrong, I've installed the new one and played a game without BSOD (won't say a lot, obviously).
I'll test it for a longer period and tell you about the result.
So, everything was fine for a few hours, I even cleaned the dust on my pc that I hadn't seen before. But just ten minutes ago, another BSOD appeared, this time being IRQL_NOT_LESS_OR_EQUAL again.
Here's the file:
Attachment 294455
The problem seems to be the WLAN Driver again. So what went wrong? I didn't do anything extraordinary while downloading the driver. Or is the USB adapter the cause (I think it's the driver, though).
What kind of motherboard / power supply unit ( in watts ) ( modular or not ) ( 80 plus or not ) do you have?
Well, the latest crash dump is saying that the TP link driver is not updated.
And the BSOD is caused by it, again.Code:fffff880`03a3e000 fffff880`03bec000 athurx T (no symbols) Loaded symbol image file: athurx.sys Image path: \SystemRoot\system32\DRIVERS\athurx.sys Image name: athurx.sys Timestamp: Wed Apr 20 15:48:10 2011 (4DAEB2E2) CheckSum: 001B13DA ImageSize: 001AE000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:BugCheck A, {18, 2, 1, fffff80003290ce5} *** WARNING: Unable to verify timestamp for athurx.sys *** ERROR: Module load completed but symbols could not be loaded for athurx.sys Probably caused by : athurx.sys ( athurx+2f3a5 ) Followup: MachineOwner ---------
I suggest having the new driver on a usb drive if possible and on the desktop, going into safemode WITHOUT networking. Uninstalling the old driver, rebooting back into safemode, check to see if its gone, if so, install new driver in normal windows. Also make sure your USB drivers are up to date.
Here is safemode uninstall/install guide Uninstall and Remove Software in Safe Mode