BSOD out of nowhere

[SlasherIT]

Hi guys,

I left my laptop on then went to eat dinner and then watch a movie. After I came back to my laptop, I saw it was turned off. I turned it on, and logged in, and then it says the computer has recovered from a Blue Screen. First time in a while I get a BSOD on this laptop.

I'm using Windows 7 Home Premium 64 bit SP1, straight from the Windows 7 retail DVD. So yes, I installed Windows 7 myself over a HP OEM copy of Windows 7. Laptop was bought December 2009. If I can recall properly, I reinstalled the OS about during June or July, something like that. I can't really remember properly. Anyways, onto the info and logs.

Attached logs and perfmon zipped here: View attachment 179081

Help would be appreciated.

Thanks,
Slasher

 

[SlasherIT]

Sucks that noone responds to any of my threads lately...

 

[Jonathan_King]

Hi there,

Unfortunately, the zip archive seems to be corrupt. What did you use to create it? You might try creating a new zip archive out of the report files, using the Windows tool (send to > new compressed folder) if you used a 3rd-party tool.

 

[SlasherIT]

Hey, thanks for responding. I appreciate it.

The zip opens for me fine. Let me compress with something else then.

View attachment 179193

 

[Jonathan_King]

From the looks of things, your Atheros wireless adapter drivers were the cause of that BSOD. There may be an update available, seeing as the version you are running is from March 2010.

athrx.sys             Tue Mar 02 19:45:21 2010 (4B8DB121)

Unfortunately, Atheros does not release its drivers on its site; that is the job of the OEMs. Try installing HP's package: Atheros Wireless LAN Driver for Microsoft Windows 7 HP Pavilion dv6-2020ev Entertainment Notebook PC - HP Customer Care (United States - English)

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Oct 13 17:26:29.844 2011 (UTC - 4:00)
System Uptime: 0 days 10:21:23.890
Probably caused by : pci.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_athrx_IMAGE_pci.sys
BiosReleaseDate = 10/05/2010
SystemProductName = HP Pavilion dv6 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[SlasherIT]

I am using the driver that you linked...

Would this driver work? Drivers for Atheros AR5009 and Windows 7

I hate companies that don't give out generic drivers...

 

[Jonathan_King]

It sure is nice when chip manufacturers release their drivers to the public, but unfortunately that is not always the case.

I was unable to download any of the drivers from that site, but if you can, you might as well give them a shot. Be sure to use Device Manager to install them, rather than any EXE installer that might be included in the download. In case you don't know how, see: www.sevenforums.com/tutorials/97061-driver-install-device-manager.html

 

[SlasherIT]

I tried installing but I cannot select from the screen the AR5009. I can only select others such as the AR5008.

 

[Jonathan_King]

I ran a search on all my old processed dumps files, and I found I had run a dump from a Lenovo G575 that had a version more recent than anything else. That driver can be downloaded here (direct link): http://download.lenovo.com/UserFiles/Driver/en/Downloads and Drivers/G475G575/Win7/IN1WLN87WW5.exe

If that doesn't work for some reason, you can always download it manually now that you know it's from a Lenovo G575.

 

[SlasherIT]

Ok thanks I'll try it. Would it be ok though to select the AR5008 for example instead of the AR5009 for the driver I found for it though?

 

[Jonathan_King]

I suspect it's the same driver, go ahead. Use the Device Manager installation method; that will bypass any artificial compatibility checks installers may have. Keep in mind, either it's a different driver, in which case Device Manager will fail to detect it as an update, or it's the same driver, in which case it should install. If, for some reason, you started having worse problems with the new driver, you could always roll back the driver using that feature.

 

[SlasherIT]

It only comes as an .inf with some other files I can't be bothered to name, lol. So obviously has to be done on Device Manager.

So should I try the Lenovo driver you gave me or the one I chose thats for a different device?

 

[Jonathan_King]

Use the Lenovo driver. I downloaded it myself to confirm it was all good, and I can guarantee it will install.

 

[SlasherIT]

Ok then. Let me do it. One sec.

 

[SlasherIT]

Ok here are my results.

The driver I found does not list my AR5009 in the .inf file. So, when I go to install that driver from the .inf, naturally, there is no option to select the AR5009.

The Lenovo driver you found actually lists the AR5009 in the .inf file. Yet, when I go to install the driver from Device Manager, guess what? I get the exact same devices listed as I found in the driver I found. That means that I can't select the AR5009 device to install the right driver... I'm stumped. This is not making any sense.

Slasher

 

[Jonathan_King]

I'm not quite sure I follow. Download the ZIP file I've attached, extract it to a handy location, and then open Device Manager. Right-click on the Atheros wireless card and hit "Update driver software". Select "Browse my computer", and point it to the extracted "x64" file.

If it doesn't go without a hitch, just attach a screenshot of what you're seeing.

 

[SlasherIT]

Ya lol thats what I did already. I extracted the setup file you gave me and then accessed the inf that you provided as a zip. Let me give u a screenshot:

View attachment 179318

As you can see, there is no AR5009 available, even though the AR5009 is listed in the .inf.

 

[Jonathan_King]

Just start trying things. Start with the 5008 because it's probably the most similar, but in truth, most, if not all of them, should work.

Remember, at worst, you have to roll back the driver to an earlier version.

 

[SlasherIT]

Ok then. Wait a second.

 

[SlasherIT]

Well, it appears to work fine. How can I tell though that this driver won't give me a BSOD?