I've had multiple people ask me about helping their computers in the past few months, all with the same issue. The results is that initially the computer will start to reboot by itself in admin mode if the trojan/virus strikes there, but if in the simple user account it may just hang. The next time one starts up, it will not be able to find the Hard Drive, giving the user that it's looking for the boot device and typically will be looking for a hard drive but calling it a USB device.
It seems whatever occurs first has attached itself via a bootsector (haven't been able to keep the computers alive long enough to actually do a good disection of what actually is occurring), and seems to hang up the computer upon starting Windows XP/Vista.
Eventually one will either get the BSOD or Driver_IRQL_NOT_Less_or_Equal message and normally a
Stop 0x000000D1 message. The most recent had a (0x00000000,,0x00000000,0x83d91395)
NVSTOR.sys-address 83d1395 base af 83d8d0000
Datestamp 46671a61
Now this wouldn't be a problem I would think, 0x000000D1 errors are typical and not unusual by themselves, but this one doesn't stay put.
After two or three restarts, and reseats of devices and such...the entire motherboard dies. Always, it seems, at least as far as I can tell.
I would be thinking it's actually a motherboard type virus/Bios virus (never heard of such a thing to tell the truth) which attacks the hard drive controller first and then moves onto the rest of the motherboard.
That would explain why it starts being unable to detect controllers or mislabeling the Hard Drive as a USB device. Eventually it starts not being able to recognize the harddrive at all.
I've dealt with 5 computers with this in the past two months. The only similarities that I can see is that they say that sometime before it struck they were all browsing and utilizing a flash movie of some sort. Three of the five admitted it was porn, I suspect the fourth was doing the same (from what I dissected of the hard drive, I have always been able to bring their hard drive info up via slave on my computer when trying to diagnose what went wrong, which further makes me think it's NOT actually something on their harddrive), and one was not.
I KNOW, I KNOW...you'll say, hey, it's a device error...but the commonalities of the coding, what occurs next, and how it happens all are too similar for me to pass it off as coincidence...especially since today when I wasn't browsing porn, it actually finally struck the computer I had been using to diagnose their hard drives (I've been using it for a couple months to do this, so it seems odd it would strike now). I WAS watching a movie via the Flash imbedding at the time however.
Same symptoms, same BSOD, same everything. Yes, I've always tried to restore the system, doesn't work, as I said the hard drive will be seen as a wrong device OR won't even be seen. I'm too the point that the motherboard is starting to freeze at this point so can't even get into the BIOS.
As I said, I think it's actually a virus of some sort and pretty bad one at that, probably would NOT be listed on Virus checkers since it takes down the computer via (my guess is motherboard) key components before anything even has a chance to react.
The only fix I've been able to give ANYONE thus far is to replace the motherboard...I'm not the technical wizard...but that's what I can tell thus far.
Any thoughts.
And...please, I've already tried the reseating of components on all of them, reinstall of OS's, reinstall of different components, reinstall of chipset drivers, setting Bios to vul checks and non-vul checks, open and close ports, and even trying to flash the Bios...whatever this thing is...it's EXTREMELY persistent and ALWAYS kills the motherboard within a few startups...
Thought I'd toss in the things I've already tried on all of them (before typically getting a new MB and putting it in, the ONLY surefire way I've found to get rid of this and overcome it after it hits these guys...and now me) before someone starts suggesting me to do them.