![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
-
Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
"ntkoskrnel damaged please replace it?"
- Thread starter oqvist
- Start date
Originally posted by oqvist
Was probably overclocking my fsb to high or ran to low voltage and got this message.
I don´t remember the exact filename but should I replace it or can windows XP self repair it? I was able to recover and boot again so...
If windows boots and runs fine now then there is no need to worry about it.
You got that error probably because (like you said) you o/c'd too high. When your computer read from the file, the data got corrupt in memory, and the error handling in windows generated that error for you. I assume it went "normal" again once you backed down the speeds???
This has happened to me a few times. I can't seem to get past 185fsb with my 2.4b. I'm stable all the way up to 183, 184 is a little shaky, and 185 is a definate bomb (boots into windows, but crashes every couple minutes). I've tried relaxing ram timings (shouldn't be an issue with the sticks I have. Geil pc4000 running at cas 2, 3-3-7. I can run lower 2-2-3-5 if I wanted, but would rather have gauranteed stability), better case cooling, new thermal paste, etc... haven't gone extreme with water cooling though.
Originally posted by nst6563
If windows boots and runs fine now then there is no need to worry about it.
You got that error probably because (like you said) you o/c'd too high. When your computer read from the file, the data got corrupt in memory, and the error handling in windows generated that error for you. I assume it went "normal" again once you backed down the speeds???
This has happened to me a few times. I can't seem to get past 185fsb with my 2.4b. I'm stable all the way up to 183, 184 is a little shaky, and 185 is a definate bomb (boots into windows, but crashes every couple minutes). I've tried relaxing ram timings (shouldn't be an issue with the sticks I have. Geil pc4000 running at cas 2, 3-3-7. I can run lower 2-2-3-5 if I wanted, but would rather have gauranteed stability), better case cooling, new thermal paste, etc... haven't gone extreme with water cooling though.
I was just afraid that it windows just stop loading that file and I may get problem with applications.
But it seem to run okay now.
I do guarantee watercooling though. As soon as I watercooled my chipset on my nforce 2 my whole computer came to life. Allowed me to overclock my CPU 100 Mhz more while 7-volting all my fans. And my FSB skyrocketed too.
Before I had to fight to get it stable at 193 FSB and 2230 Mhz which is quite poor with my setup especially. Seeing many with aircooling doing well 225 FSB and 2300 Mhz or above.
believe me...if windows stopped loading that file...windows wouldn't load period.
consider yourself lucky because many times an overclock too high will cause hdd corruption and then you're back to square one re-installing everything. Happened to me when I decided to try to boot at 198 fsb (even though my cpu is rated for 133, I soo wanted to hit 200...but I guess a 725Mhz fsb is close enough to 800 to make me happy.)
consider yourself lucky because many times an overclock too high will cause hdd corruption and then you're back to square one re-installing everything. Happened to me when I decided to try to boot at 198 fsb (even though my cpu is rated for 133, I soo wanted to hit 200...but I guess a 725Mhz fsb is close enough to 800 to make me happy.)
Originally posted by nst6563
believe me...if windows stopped loading that file...windows wouldn't load period.
consider yourself lucky because many times an overclock too high will cause hdd corruption and then you're back to square one re-installing everything. Happened to me when I decided to try to boot at 198 fsb (even though my cpu is rated for 133, I soo wanted to hit 200...but I guess a 725Mhz fsb is close enough to 800 to make me happy.)
Believe me I know what you mean. First I got a 8rda+ after hearing so many achieving 200 FSB with that one. I could never go above 185 stable. Then I get a 200 FSB rated mainboard and a 2500+ which everyone says do at least 11x200 stable.
Have to fight it like hell to get up to 193 FSB. But then I watercooled my northbridge and that was apparently what was holding me back all the time. Not my CPU or RAM.