W3J - Scandisk on restart loops forever?

Hi guys,

I've lurked the forums for a while, and because my W3J has not given me much trouble, I barely post here =) However, right now it's going a bit crazy, and I can't figure out what to do.

So, I took it on trip, and it worked fined after the plane, and 2 buses.

One day I was using it on battery to write a doc, nothing intense. I plugged it as the battery was gone, then turned it off after I was done. The next time I turned it on it came out saying that windows had not properly closed or something, and it started checking the disk. It did its thing and then windows started loading. Once the mouse came out for a second or two on black screen, rather than loading the user screen where you can type your account's password, it rebooted. After the reboot it said the same thing about the disk and repeated endlessly.

I went on safe mode and scanned the whole thing with Avast!, AVG, Spybot, and Adaware, and it mentioned a trojan and a few cookie trackers. I removed them, and that's that. Rebooted normally and did the same thing.

I left it alone and after a few tries the next day it loaded windows and worked perfectly. Then after a few reboots it did the same thing.

Now it works fine, except it seems that when it's turned on with just the battery the error is much more likely to occur. I now have to keep hibernating it so I don't have to reboot and test my luck.

Should I wipe the HDD assuming a virus is still around? Should I send it for a repair? Opinions are greatly appreciated =D

 

i would try a reinstall first, if it still doesn't work call support.

 

I would assume that the virus is still sitting somewhere on your HD if you still sometimes get errors. Even if it isn't, it clearly did something to your hard drive which greatly reduces its reliability. I'd say your best bet is to backup anything important and start fresh.

~ Brett

 

Or is it because of the VGA driver issue?

 

Well it's going into the checkdisk, not a regular restart, plus it's inconsistent while the driver issue was consistent and just caused a restart with no message/action so I suspect it's not a driver issue.

~ Brett