edit: on c:\windows\inf\setupapi.dev.log
you can directly look at this log and find the date and time that the usb wireless device was inserted into your machine.
(if you want to figure it when, why and who installed the driver)
Note: you had many bugchecks that indicated failures do a drivers data being corrupted. But only one bugcheck where windows caught a driver attempting to write on memory it did not own. (causing the corruption.) That driver was the wireless network adapter, It would not be loaded unless at sometime someone plugged it into a usb port on your machine.
It only take a second. From then on, it is loaded in case it gets plugged back in some time in the future.
so, make sure the driver is removed. delete all of your current memory dumps and run your system and see if the problem is resolved.
--------------------
usb drivers are kind of special, they can be plugged in/out ant any time so rather than remove them they are hidden in device manager. This means their drivers are still loaded and cause problems even after you remove the device.
What you want to do is have the device manager display hidden/removed devices so you can remove them
it is a registry setting:
http://support.microsoft.com/kb/315539
You may find that it is best to use the plug and play utility to remove the actual installation files for the OEM driver.
Windows will keep a copy of the driver and a backup copy of the driver in its driver store. You want to get rid of both. I looked at my network driver and I have 8 versions of the same driver on my machine.
what you want to do in this case is start the command shell (cmd.exe) as a admin (windows key+x + A)
then run
pnputil.exe -e (this will make a list of all oem drivers on your system)
look at the list, find the published name of the driver you want to remove, it will be something like "oem9.inf"
then remove it using
pnputil.exe -d oem9.inf
This is very helpful because it removes the copy from the driverstore. If you remove the driver directly, the windows plug and play will detect the uninstalled hardware and reinstall the old driver a few seconds after your just removed it. (The only symptom you get is people complaining that updating the driver did not help.) Often you want to go to control panel device manager and confirm what driver you have for your device and who made the driver.
Vendors will give Microsoft a basic driver for their device but they will keep working on the driver and make a enhanced version with special features that they will have on their own website. Some of these enhancements are bug fixes that they know about but don't want to go through the process required to give them to microsoft.
Vendors sell hardware, it is often not in their best interest to update drivers because that allows you not to buy a new piece of hardware from them. basically, no update to old driver = more sales for them, you buy new hardware to get new drivers.
look at the list, find the ones you want to remove and
Lanep82 :
johnbl :
95% of the time the term memory corruption does not mean that your RAM is broken. It means that the software had detected the wrong data stored at a particular place in the RAM on the machine. It is like a wallet, I put in a $50 bill, close it and later open it but it is now $3 one dollar bills. It can be a problem with the wallet but more likely something else happened and it is not the wallets fault (95% of the time)
anyway back to the problem: the file 021414-20997-01.dmp should have the answer to your problem, It is basically windows catching a hand in the wallet. Where the others are just complaining about the fact that the contents of the wallet have been changed.
give me a minute to look at it
Edit:
corruption caused by
\SystemRoot\system32\DRIVERS\athurx.sys
date Wed Apr 20 03:07:45 2011
I think this is just a old Atheros wireless driver connected to a USB device.
you will want to locate and install and activate a new driver. (usb drivers don't always get activated as the default when they are installed, so check in device manager that you do get a new one installed and activated.)
2: kd> lmvm athurx
start end module name
fffff880`0281c000 fffff880`029fa000 athurx T (no symbols)
Loaded symbol image file: athurx.sys
Image path: \SystemRoot\system32\DRIVERS\athurx.sys
Image name: athurx.sys
debug info
BugCheck C5, {fffffa80027c3018, 2, 0, fffff80002fc0127}
DRIVER_CORRUPTED_EXPOOL (c5)
notes:
ASUS P5N32-E SLI ACPI BIOS Revision 1903
BIOS Release Date 11/17/2009
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Manufacturer ASUSTeK Computer INC.
Product P5N32-E SLI
Max Speed 3800MHz
Current Speed 2400MHz
Note: you will want to update your BIOS if you can get a new one. It will have fixes that will work around errors in the various hardware in you machine. (incorrect memory settings, usb settings and fixes for microcode errors in the CPU.)
I mention this because that driver will depend on the correct function of the USB host controller, and that host controller depends on correct BIOS settings which is why you want to make sure you have the best one you can get for your machine.
Hi John and THANK you for your help. I appreciate the response.
I am having a little bity of a time following your instructions. I don't have the Atheros wireless adapter anymore (for several years) so I am a little confused on how it popped back up since I reformatted and all..... Do you know how I can properly remove the driver all together? I am not sure on that process.
Also, I uploaded a few more pieces of information that may help in determining the root cause for all of this.
Drivers List:
https://www.mediafire.com/?lvw2u9badlzbyya
System Information:
https://www.mediafire.com/?lvw2u9badlzbyya
None of these reports were obtained in safe mode.
Was there anything else in your post that was instructional to me? I read through it a few times and the only thing I could gather was regarding the Atheros driver and updating it.
THanks again for the help.
Lane
Facebook
Twitter
Instagram