New
#11
Trying the zip again. No it will not attach anything in doc form. The doc is saved as an Office 2010 docx so I am really up the creek without a you know what.
Any suggestions on how to attach the msinfo please??
Trying the zip again. No it will not attach anything in doc form. The doc is saved as an Office 2010 docx so I am really up the creek without a you know what.
Any suggestions on how to attach the msinfo please??
Yes Brian it isn't the fastest although my Toshiba does not too poorly on it and is why I think the HP machine needs the driver for the wifi.
Thing is the link for Atheros is littered with links and a lot of them to Driver update software that is really quite annoying why the heck I cannot just Google for that driver and find it on the Qualcomm site is getting very tedious.
Sorry John, I was off watching a movie (self-indulgent, hyperbolic, demon hunting nonsense - can you guess what it was?!), I'll take a look in a minute mate.
It was The Devil Within, more Ralph Sarchie's self indulgence than mine but still...
John run the DM log collector in the BSOD instruction thread and post those logs up mate.
I think the Driver for the Atheros in the Link below might work ..
ASUSTeK Computer Inc. -Support- Drivers and Download G75VW
Ok Gav and Brian have got to dash out for a bit - tax time and woe betide me if I don't get it in in time.
These are usually good instructions for the msinfo John,
To suggest the right steps, we need to see some more files. Upload your MSINFO32.nfo file.
- Click on the start button
- Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
- File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
- Give the time for processing, it will save a .nfo file on your desktop.
- Zip it, and upload it following the instruction.
I don't think your atheros driver is that old,
You can try the one from maxie's link if you want, but it is a Version 9.Code:athrx.sys (10.0.0.67
I'm not convinced the driver is the problem here to be honest, I think something else is it at play. I could be completely wrong though.