TP Link, Arthurx.sys driver causing BSOD

[Twinfire]

Hello Peoples of Seven Forums. First post here so you can guess i'm in a bind at the moment.

Bought a Wireless USB stick/WLAN/network adapter etc and ever since I have been having bluescreens, about 30-40 in 3 weeks. I use this machine for an hour or two a day so this bluescreen issue is getting ridiculous.

I have tried updating the driver from the manufacturer website and amusingly the update that Windows update provides is actually older than the one from the manufacturers website.

System specs are

CASE: Gigabyte Triton
MOBO: Gigabyte P55UD3
CPU: Intel Core i5 750
GPU: EVGA GTX570
PSU: 650W
RAM: 4gb
HDD: Samsung Spinpoint F3
ODD: Lite on DVD-R

 

[zigzag3143]

The three DMPS uploaded have 3 different appearent causes but really are a memory exception. Usually related to a driver. Please run memtest and driver verifier.

These need updating

tifsfilt.sys    8/29/2007 8:37:29 AM        fffff880`05d8e000    fffff300`05da5000    0xfffffa8000017000    0x46d56889                        
timntr.sys    8/29/2007 8:38:23 AM        fffff880`01af4000    fffff880`01ba4000    0x000b0000    0x46d568bf

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[JMH]

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[Twinfire]

Thank you for the help zigzag and JMH

Have tried Verifier with a predictable BlueScreen BUT the blue screen popped up and dissappeared before I could see what caused it.....is it meant to do this? Would a report have been made?

There is no Minidump for the event either.

Will attempt memtest when more.....awake

Twin

 

[writhziden]

The report probably was not made. How did memtest86+ go?

If you have had any new crashes, please provide us with the full logs with the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html