Im running xp pro on one of my machines, it always worked fine until the other day I transferred a 9gig folder onto it of mp3s. It rebooted to a blue screen that stated I needed to try one of 3 things, I tried all those things to no avail. So I shut it off, the next day I booted it and it booted up to windows, I deleted the 9gig folder (thinking it may have clogged up the drive)and soon after it froze, I try to reboot and it makes a weird sound over and over , I think its the hard drive. If I let it sit turned off for an hour or so it'll boot again but within minutes freeze again. Is this a hardware or software problem?
It sounds like you have some sort of file corruption. You might want to try to run the chkdsk c:/f command from the dos window. You probably need the windows xp installation cd to get into the dos screen. If you got system file corruption, you will get similar symptoms as you describe, usually happens with improper shutdows. Chkdsk can usually fix these problems. http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315265
I wasnt into computers much during the dos days, I assume when you say run chkdsk from dos window you mean the command prompt , am I right? when I open command prompt it defaults to C:\Documents and settings\user, what command is it that I use to make it just C:\? cd.. ? or something? and how do I type the chkdsk command , because I typed just that and it was in read only mode , but it did detect a couple errors , so I might be on the right track, thanks for the help
I just read the link you put in your msg, think I answered my questions, Ill try again and keep you posted on my progress, thanks again
well Im still working on running chkdsk. Since Im only able to boot the comp every 3 hours or so (otherwise it wont boot, just makes weird sounds). Goign to try in the next couple hours. I got fed up today and tried to format and got this error msg "File \i386\ntkrnlmp.ese could not be loaded. The error code is 7." So if the chkdsk doesnt work Ill be trying what this link suggest. Hopefully its not my RAM I dont want to pay to replace it. Again Ill keep you posted http://support.microsoft.com/kb/318729
well, I finally found the time to mess with this computer again, there was 2 sticks of ram in it, I swapped them out and found that one of them was bad, but unfortunately I still boot up to the blue screen, Im going to try and reformat it right now and see if I get that missing file msg again, sorry I took so long to respond but Ive been busy with work, thanks again
