Asus Aspire 1 BSOD

robmar0se

To be honext I haven't done it either (probably will go the route of a usb cd/dvd drive (around £200 as I have all os on disk already)

Have a look here, or google other sites etc:

http://www.techrepublic.com/downloads/illustrated-walk-through-creating-a-bootable-usb-flash-drive-for-windows-xp/283046

XP disk is less than 640mb, so any flash drive 1gb or larger would do.

To access the XP recovery console, this may help:

http://support.microsoft.com/kb/307654

waddler_8

Ubuntu on the memory stick should do it (replace the file, assuming it is infected).

rmg1

I know it's a bit of a cheat, but would a factory restore solve it?
I'm more than willing to try replacing the file (assuming I can get a good copy) but just wondering about last resorts.

robmar0se

rmg1 wrote: »

I know it's a bit of a cheat, but would a factory restore solve it?
I'm more than willing to try replacing the file (assuming I can get a good copy) but just wondering about last resorts.

I always remind myself with computers, never say never!

For example you may succesfully replace the file in question, only to find another, yet another, etc

The asnwer to yr question is it might. We don't know the cause. hence the reason for checking common causes such as checking RAM and the hdd.

rmg1

That sounds reasonable.
Will HBCD run off a flash-drive and can I run memtest off it as well?

waddler_8

If it is infected with TDSS then a factory reset will cure it. The driver loads as a boot service with the OS.

spud17

rmg1 wrote: »

That sounds reasonable.
Will HBCD run off a flash-drive and can I run memtest off it as well?

Look back at the thread from a week or so back, where myself, dcm and GunJack were helping/abusing each other.
All the details are there.
Install HBCD and also you *should* be able to add the memtest .iso.

waddler_8

robmar0se wrote: »

...you may succesfully replace the file in question, only to find another, yet another, etc

If it is that TDSS variant I linked too, it only infects volsnap.sys , so replacing that file with a good copy is pretty much a silver bullet. Once booted scan for the hidden TDLFS file system using TDSSKiller and it's gone.

The fact that it's BSOD'ing suggests that the viral code corrupted the host file rather than infecting it successfully.

robmar0se

waddler_8 wrote: »

If it is that TDSS variant I linked too, it only infects volsnap.sys , so replacing that file with a good copy is pretty much a silver bullet. Once booted scan for the hidden TDLFS file system using TDSSKiller and it's gone.

The fact that it's BSOD'ing suggests that the viral code corrupted the host file rather than infecting it successfully.

Waddler, I am sure you know what you're talking about, and I believe I suggested that the OP take your advice. Howeevr, both you and I know that the TDSS rootkit is not the only cause of this error.

In fact MS MVPs suggest the mentest should be run, and also say that the problems may be caused by out of date drivers, for example avgio.sys possibly a part of Avira antivirus, and NetMotCM.sys - Motorola USB Cable Modem driver, etc.

That was my point. I don't think we actually disagree, do we?

waddler_8

robmar0se wrote: »

I don't think we actually disagree, do we?

No, I don't disagree with you - Yes, there can be many causes - it may not be TDSS at all. It's all if's, but's, and maybe's at this point. I posted more for reference & clarification for if this topic was to be accessed later by someone with similar problems.