| Author | Message | ||
     Blake Luse (Muddyrover) Senior Member Username: Muddyrover Post Number: 673 Registered: 02-2002 |
I have a big problem......first off here's the computer setup: Asus A7V333 Mobo w\out RAID AMD Athlon XP1600+ cooled by Vantec Tornado fan Enermax 431w PSU Maxtor 40Gb HDD SB Audigy GF4 MX400 PCI graphics card Lite-On 40x CD-RW drive WinXP Pro I've asked this on another board but thought someone here might be able to help also, here's the problem: Yesterday all I did the whole day was burn a cd with Nero and then shut the computer down. No problem. Today, I go to turn the computer on, and after the asus mobo splash screen comes on, all I see is "windows cannot find the file C:\windows\system32\ntoskrnl.exe. Reinstall this file" or something along those lines. And I can do nothing from here.....everything is frozen until I restart. Its just telling me that that specific file is missing. Ok......no problem, I'll just reboot with a Windows98 boot disk that I have just to get into DOS and swap out the bad ntoskrnl.exe with a good one. Well, the computer won't recognize that there's a boot disk in there. It still just goes into that same screen telling me about the missing file. Ok......at this point I'm thinking I have the "boot up floppy seek" option turned off in BIOS for some strange reason. I reboot again, and when I press delete to go into BIOS I hear this awful clanking sound, coupled with "BEEPBEEPBEEPBEEPBEEPBEEPBEEPBEEPBEEP" that goes on forever at the rate of about 4-5 beeps per second. BIOS comes up as usual, but everything is frozen. I can't navigate around BIOS and everything is frozen. So I'm stuck and I can't do anything!!!!!!!!!! Can anyone help me out? Much much appreciation goes out to any help!!! here's some advice from others already. Whoa, all I can suggest is clear the CMOS by removing the battery on the mobo, placing the jumper on the bios reset for 3 sec, then removing the jumper and placing the battery back in. If I'm not mistaken, I belive the jumper is called CLR_RCT and is jumper number 16 in your manual. If this doesn't work, then try updating to the newest 1016 bios. Probably won't help, but its worth a shot. I get that ntoskernel.exe error when I try to push my overclock too high. Backing down my settings always works, and the restart is no problem. I'm now running the 1016 bios (and not noticing a difference from 1015). Listen to the beeps and try to decode them from the BIOS (the latest issue of maximum pc has an in-depth feature, listing the beep codes for all the latest bios manufacturers - or you can just look online). "MY REPLY" That's just it, I can't back down the settings because everything freezes the nanosecond I enter BIOS, then the beeping starts. And this is no correct beeping, its a beep code that just goes haywire beeping insanely fast because everything's frozen. I'll try to clear the CMOS and do the reset jumper thing today when I get back from class and see if that works. Also, I can't update my BIOS because boot disks won't work for some reason. The win98 boot disk did nothing, it still just went to the ntoskrnl error screen. And I don't understand the clanking sound, it's like a really fast clicking...the sound is coming out of the front of the computer so could it be originating from the hard drive? Could the hard drive be shot? But if the hard drive was shot, wouldn't I still be able to get into BIOS without everything freezing??? and another post. The reason a boot disk wont do anything for you is because you most likely used NTFS for the partition type. You cannot boot to an NTFS partiton with a DOS (FAT) disk. You can create a NTFS boot disk, but it will not get you to a command prompt. You need a proggie like NTFS-DOS (costs $$$) or you can use the XP Recovery Console which will give you limited access to the drive...only the \WINNT folder structure. Also getting into your BIOS has NOTHING to do with your hardrive. You can get into the BIOS without a HD attached. The NTOSKRNL error is usually corrupt data on your HD. It's rarely a problem with that file. Try performing a parallel install of XP. By a parallel install, I mean install XP to a DIFFERENT folder. Then you will have access to your data at least. You do have the option of trying a repair if you had an ERD, but I doubt you do...Most people don't think about backing anything up... this is driving me crazy ................. thanks | ||
| Jesse Lessard (Jlessard) New Member Username: Jlessard Post Number: 34 Registered: 10-2002 |
Try unplugging your Hard drive from the motherbord to see if it is causing the problem. I Know that if you put a IDE cable in backwords it can cause the bois to freeze, so mabey a bad hard drive could do the same. | ||
| Tommy Dougherty (Skydiver) Member Username: Skydiver Post Number: 118 Registered: 03-2002 |
Try this.. power off the computer. Unplug both the power cable and the ribbon cable from your hard drive and cdrom drive (if on the same channel). Then restart and see if you can go into CMOS. If so, turn on the floppy disk as the primary boot device. Try to boot just off the floppy now. If that works, power off & reconnect the hard drive (and cdrom), and see if that works. One of the posts mentioned that you might not be able to read the HD data if it's formatted as NTFS, which is true. There are some freeware apps which allow you to view/manipulate NTFS from DOS, but the names escape me now. One other thing - I had a similar thing happen to me (same error) when the boot.ini file got changed. If you only have one partition and one hard drive, see if your boot.ini looks like this: [boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT hope some of this helps/makes sense. -tommy | ||
| Christopher Boese (Christopher) New Member Username: Christopher Post Number: 18 Registered: 10-2002 |
That beeping might be a keyboard error, which would also explain your not being able to navigate around on the BIOS screens. Check your connections, make sure a key isn't stuck. | ||
| Blake Luse (Muddyrover) Senior Member Username: Muddyrover Post Number: 675 Registered: 02-2002 |
ahh its fixed, i took out the little battery in there and "dumped the cmos" or whatever its called and it works. Thanks guys | ||
| Prescottj (Prescottj) Senior Member Username: Prescottj Post Number: 302 Registered: 12-2002 |
blake are those new tires broken in yet? |
