Another BSOD problem 8-)

usasma · 20 Oct 2009

Go to Device Manager and locate the device there.
Right click on it and select "Properties"
Then select the "Details" tab
In the dropdown box, select Hardware ID

As it's a USB device you'll need to find the 4 characters immediately after the VID_ and the 4 characters immediately after the PID_
Then you can look up the device manufacturer and model at http://www.linux-usb.org/usb.ids

Once you find that, then go to the network device chipset manufacturer's website and locate the driver there.

I found this at the Belkin website (it's a Vista driver and it appears to be from 2009) Belkin : Support : F5D7050 Wireless G USB Network Adapter - Drivers

FWIW - there are known issues with some versions of the x64 RaLink drivers - so determining the maker of the chipset will help in determining where to get the driver from.

Xerse · 20 Oct 2009

just downloaded and installed that driver you posted for me, as i figured, it's the same one i have at the minute, (uninstalled the old driver first of course)
I downloaded it from the same site before also.
Going to try what you said about the Hardware ID now, thanks again :)

Xerse · 20 Oct 2009

Here's the answer,

050d Belkin Components
705c 802.11bg

So, obviously the belkin website, so i must have the most upto date driver, strange..considering it's from 2007.

Should i just skip the cause being the USB device now? and concentrate on the memtest?

Tews · 20 Oct 2009

Im not suggesting that you do this immediately, but you need to re-download the ISO for windows 7 in the event that you need to install once again.. The frequency and randomness of the occurrence of your crashes may be due to bad installation media... Just something to think about..

Xerse · 20 Oct 2009

Got you, i did however burn on the lowest speed (obviously, if it's a bad disk then it wouldn't matter how slow i burnt it on)

I'll be sure to make another copy now, just to be on the safe side, and try it if all else fails, that's for the input, Tews.

Tews · 20 Oct 2009

It is more important that you download a new copy rather than reburn the one that you currently have..it is possible that you had some data corruption during download...

usasma · 20 Oct 2009

Suspecting the USB device is based upon the USB drivers being old. That doesn't mean that they are bad, just that it's more likely for them to be causing problems. But we have to remember that that may not be the case.

I find that STOP 0x3B errors are normally caused by a misbehaving service (rather than a memory issue) - but running Memtest can't hurt.

More info on STOP 0x3B errors here: BSOD Index

This may respond to the old style method of fixing BSOD's:
- locate and download all the Win7 drivers that you can find.
- any drivers that you can't find Win7 drivers for - download Win Vista drivers
- uninstall the software related to each device (do these one at a time and start with the one that you've got Win7 drivers for) from Control Panel...Programs and features...Uninstall a program.
- install the downloaded drivers after uninstalling the devices.
For Vista drivers, install in Compatibility mode for ALL USERS to Run as Windows Vista and to Run as Adminstrator.

Xerse · 21 Oct 2009

Just to report back, i tried another image of windows 7, clean install, and did all as you said also John, so far so good, no BSOD at all :) earnt you both some rep right there :P

jcgriff2 · 21 Oct 2009

I agree - athrxusb.sys looks like a good candidate for this 0x3b BSOD. A re-install is always a good post-BSOD idea - fresh start. I suspect that when Windows Updates or installed program updates hit the fresh re-install, BSODs may again develop.

You specifically mentioned Live Messenger (was MSN). It is one of the very 1st apps to kick off post boot-up because of its login security procedures - using the Internet. Live Messenger also mandated recent updates. The newer Microsoft Live drivers may ave very well been the catalyst here.

Although you have a Belkin NIC device, the driver athrxusb is clearly Atheros. It along with its cousin athr.sys have been causing BSODs since the beginning of time. You should continue your search for a driver update. Try this Atheros Czech site -
some have had success -

ATHEROS drivers for Microsoft Windows

A 3rd party firewall would be a good candidate here as well because of the 0xc0000005 NTSTATUS exception code error.

Regards. . .

jcgriff2

.

Xerse · 21 Oct 2009

I think you're right jcgriff2.

I said it was all fine, and after i say that, i had CONSTANT steams of BSOD (I have the dumpfiles)

i thought enough is enough, disconnected my wireless adaptor, and took my pc downstairs, by the router and took another machine upstairs in its place, so far using the cable, no BSOD at all, and i've been doing everything (and a lot more) that used to cause BSOD's, i've been doing everything i usually do on my pc, and no problems, it seems to be the belkin adaptor, or as you say Atheros, since they make the driver.

So, another update here, SOLVED for now! by stopping using the device! lol

Just gonna have to buy a new one :P was on my list, since i got a new N router, so it's just speeding up that process for me, lol.

Thank you all, once more, for all of the help, you're a very friendly community :)