Just got 1 fixed and another problem arrise

[Messerschmitt]

Hello

I am not sure if this should be at hardware or software since to be honest no idea if it is a hardware or software related. Most likely software tho.

My computer is: 1600+ XP Athlon, Sis chipset mobo, 512 ram, 2 HDD's WD, Gf4 Ti4400.

My problem:

My computer was playing Winamp and as far as I knew was pretty much idle since I had no idea what should I work/play with. It was conected over the internet since I was streaming on my Winamp. When all of the sudden a blue screen came up, and in less than a second computer went blank (HDD was still active).

I shut it down, waited a few minutes and powered it on. It loads fine the ram, bios, makes it checks, and at the time when Windows XP has to start up I get again the blue screen.

It said something like:

"Problem has occured and windows shut down to prevent damage"

Then it said something about:

Check adequate disk space [..] Try change your video adapter [..] Disable bios memory.

And

Technical info: ***Stop 0x000007E (0xc000005, 0xF84F101D, 0xF89514D0, 0xF895110C)

***ACPI.Sys Adress F84F101D base at F84c8000, Date Stamp 41107D27.

I restarted and then Windows told me if I want to start windows normaly or safemode.

I started normaly and I got a error message (on the normal black dos screen) that NTFS.SYS is missing or corrupted. I restarted again and started on Safe mode, then a bunch of files started to apear in lines and went up up til it reached NTFS.SYS angain and gave me the error.

Now after a few hours I try to open it again and I get again the blue error screen with the details I mentioned above. I restart, same blue screen.

I shut down the computer for about 5 minutes, and when I open it I got blue screen error but "another" message:

"Bios in this system is not fully ACPI configured. Turn off ACPI mode," etc. and some other numbers at Technical info.

After this I just shut it down and went to work.

Now can this just be windows problem? Maybe a virus? etc which destroyed my Windows XP? I have some mirrors made of Windows so I could try to mirror it.

Any sugestions before I would do this? Don't really keen to mirror my Windows, since the last copy of it I made it 3-4 months ago.

[puntoMX]

Well, Check your capasitors on your motherboard, clean out the CPU fan and other dust around the northbridge. If you need help to see how a capasitor looks like tell us that and we will help you. After all looks fine and the errors still pop up try to use an other IDE cable that has 80 wires.

EDIT: This is just a start, let´s do it step for step .

Edited May 29, 2007 by puntoMX

[nmX.Memnoch]

Boot from your XP CD into the Recovery Console. Run a CHKDSK on your drive.

[bonestonne]

not sure if you're up to this, but if you boot into linux, mount the drive, and then look around when you first open the drive, you may see the file. if you do, then all you can do is reinstall, if you can't see it, you need to replace it.

now, this is not the greatest of ideas, but it will work. i wouldn't suggest it if you've never used linux before.

chkdisk will most likely fix the problem though. i believe that once your in the recovery console, its "chkdisk -f" without the quotes, and it forces a check on the C: drive. not sure how to use check disk on a slave drive though.

[Messerschmitt]

Hey, as allways I want to update everything that is happening.

Right now I am writing from my computer, it seems it's fixed now.

From what I think the ntfs.sys file was somehow corrupted or some sort. When I booted from my winxp cd you know that it starts reading some files and loading them up prooly, down to bottom, well when it reached again ntfs.sys while booting from cd I again got blue screen. This was not good, I couldn't even perform a function from the CD.

Anyway I restarted and this time I just presed F-something, first one I seen when cd was loading, for mass storage something. Well, it worked, it asked me to insert additional drive with the diskete which I didn't but at least I did something. I canceld that and I let again windows cd load up all the files, but this time it passed the ntfs.sys and I could finaly pick an option. Pressed "r" from repair and I got into the console. Then I did a chkdsk check and all checked ok. After that I restarted and selected safe mode. Well it got it! Windows started. Afterwards restarted again and now I am normaly again operational.

Sincerely I have no idea what happened, nor if I will have futher problems. All I can ask now if you guys could identify the problem, what is happening/happened and hopefully this won't happen again.

[puntoMX]

All I can ask now if you guys could identify the problem, what is happening/happened and hopefully this won't happen again.

That´s hard to tell. I hope the problem stays away for you, if not read our first posts again .

[Messerschmitt]

Ye after 5 minutes I got blue screen again.

This time with a KMIXER.SYS file problem.

Now the thing is I think the blue screen where caused by the CMOS battery (small little battery a lot of problems it seems). Prooly the new one was already depleted so I again changed it. Now I no longer recive blue screens when I want to start windows but each time in normal or safe mode I get that "Could not start Systems32/Drivers/NTFS.SYS. Corrupt or missing".

Now the problem is I cannot run chkdsk again, my windows xp cd is frozen before all the files are loading. It fails loading "Kernel Debugger DLL", it just froze when it reaches that file, its about the 3rd file that windows is loading when booting after the CD. What can I do? I think that if I manage to repair again and do a chkdsk I might be ok this time since I no longer get the blue screens, now I just need to fix the NTFS.SYS file again. How can I do that if my windows XP CD is no longer booting? Why is the CD all of the sudden no longer booting?

Please help. I can't even format the disk if I need to now.

[puntoMX]

Did you do any thing like I posted?

[Messerschmitt]

Yes, motherboard is operational. The dust has been cleaned a bit early when i had a previous error. And I can't use 80 pin, I don't have one.

[puntoMX]

Then get one ASAP . I bet you already found your problem there... and you computer will run like never before...

[Messerschmitt]

Not really.

It became worse and worse.

I mean as I said my windows xp cd will no longer load (or it wasn't). I could twice boot from my image CD done with Norton Ghost and when I tried again it also no longer load.

At this moment I got to the stage where I have 2 HDD's both with windows XP and none of them will boot, when Windows should start loading I get another type of message this time on black screen saying something about kernel dll problem and i should contact my support whatever. Even when I boot from my Windows XP CD or from my image CD I get the exact same error. Nothing will read anymore.

So my conlcusion is it cannot be the HDD itself or the optical unit disk.

I have not switched the IDE wires between them (the one used for HDD and the one used for optical disks, CD-ROM, DVD-ROM), but I can't boot from any HDD or optical drive I don't think it's the wire.

Can it be that the motherboard just screwed up where you insert your IDE cable? Did something happened with the motherboard memory that won't allow now anything to be run?

I will switch the IDE Cables between them, but I doubt it will help, and it couldn't both IDE wires just faild at the same time so I would require to buy a new one.

Right now just absolutly nothing works. And I have no idea what's that error with the Kernel DLL thing.

[Messerschmitt]

I have got an older computer from a friend and I tried to do some switching around. On his HDD he has a Windows ME version so I plugged it in in my motherboard to see if my hardware will boot his HDD. Well it just restarts. When windows has to boot it restarts. What can I understand from this? Can the motherboard if broken impede booting?

I just ran out of ideas. I even used the IDE cable he had in his computer, same thing, it restarts.

[puntoMX]

Could be:

- Powersupply, try an other if you can...

- RAM, use MEMtest to check it out...

- Mobo, nothing to test here, replace it directly...

- ...

- Small chance the CPU, switch it with an other one if posible...

Looks like time for an upgrade ...