About a week ago I made a thread on this forum regarding some virus stuff. It may ormay not be related. Google suggests that I may have possibly gotten a HaxDoor virus, but if I did I don't really have a way of getting rid of it without being able to boot my computer. I'm fairly sure that *isn't* the problem, however, due to never having the primary symptom of it: something about a log being created and to help Microsoft out by sending it, or something.
It can be found here:
This issue was not yet resolved at the time of crash, and has mostly been put on hold for now due to the whole not being able to boot thing.
Anyway. I am assuming while a virus may not help, that it is not the thing stopping me from being able to boot. That said, onto my situation:
Well the other day I was playing a game and my computer suddenly crashed with a bluescreen. Not entirely sure what all it said, in all honesty I didn't read much since it happens to other people sometimes and they usually come right back. From what I understood it was likely a memory dump, or something.
Anyway. As a reult I now get a stop error message 0x0000008E (0xC0000005, 0x04682DE, 0xF78BD85C, 0x00000000)
I've tried booting in safe mode, I always get this same stop error. I've tried last known good configuration, same thing, and of course normal mode is the same thing. I began to think I had a corrupt boot file, so I tried booting from a floppy. I used Command Prompt to use the following commands after formatting the floppy disk:
xcopy c:\boot.ini a: /h
xcopy c:\ntdetect.com a: /h
xcopy c:\ntldr a: /h
So I copied over boot.ini, ntdetect.com, and ntldr. When inserting this into my problematic machine, it told me it could not boot due to missing the file "hal.dll".
I then tried to use the XP CD (apparently setup CD does not equal a bootable CD) to boot, and it would not simply boot, but took me into setup. I decided to go with the flow and it told me that "it could not detect an installed hard drive", when I selected the option to try and repair the XP installation, as opposed to creating a new one, again with the goal of trying to keep information intact.
The strange part, to me, is that the setup menu still detects the drive and gives me all the basic information. 80 gigabytes, the code, specs etc
I've tried swapping SATA cables (I had a spare) and to no avail, it still tells me it cannot find a drive connected.
This is becoming sort of problematic. What I'm wanting to do is recover information from the drive that's rather important (and I didn't have the foresight to backup), make backups, and reformat the drive. Reformatting is easy enough (maybe? assuming I can get the drive recognized, but I believe that's the core of the problem), I'm just trying to get it "back to normal" so to speak, even if temporarily.
In setup i've tried turning the drive on and off, and nothing. I had a bluescreen problem about 18-24 months ago that was fixed via changing the SATA opertation from RAID/Autodetect otherwise AHCI, to Combination, and back, and it was fixed with all information intact (likely due to never having used RAID), and tried that this time, although this time it did not work.
But after all that that, and still having no results, one of the main things that puzzles me is tha my system setup menu detects it, but when running XP setup to repair, it does not detect the drive.
Does anyone recognize the problem/have any ideas that could help? I unfortunately don't have a lot of extra money to pay Geek Squad to just hand it to 'em and say "fix it", not to mention I'm not entirely ure if they offer refunds if I can't get the drive's information off of it.
An afterthought after all this - would it be possible to put the drive on a seperate computer (with the same operating system, XP home edition), and attempt to access it with aforementioned computer's primary drive still running? I wonder if it would help: One, to see if my drive is recognized by a computer that is working fine. and two, to see if any information is accessible. Would that be possible or would the fact both drives have an OS be a problem?