No boot after SuperStep use?

[Kentetsu]

Hello all. I've tried all types of different combinations for search, but never got even a single return on this so I'm kinda stumped.

I purchased my first ever board from Foxcon, and things started out pretty good with it. After I got XP loaded, along with the usual utilities and such, I started checking out the included utilities for the motherboard.

Everything was running great, until I played around with SuperStep. Short story, I think I did something very stupid. I assumed that the changes made were "real time", and was suprised to find that my system seemed to run fine at a fsb of even 145 (which is where I stopped). But I think I found out otherwise after I tried to reboot the system. It has not been able to boot since I did this. Not even using "last known good configuration" or safemode.

I assume this is because the changes made in Superstep are not effective until you reboot the system. Is this correct? I get the impression that everything is fine until superstep starts up with Windows, activating the unrealistic fsb setting that I put into it. But why would safemode not work either, unless this little program was still loading for some reason?

Anyway, am I going to have to reinstall windows to get around this problem? Am I barking up the wrong tree thinking that superstep is the problem? I'm really stumped on this one, so if anyone is more experienced with these boards and this program, please let me know how to save myself from my own stupidity. Thanks!

Here's the specs:

AMD 2000xp
1gb 400mhz memory
K7S741GXMG-6L motherboard
XP Proffesional SP2

If you need any more info, just let me know. Thanks again...

[timberwolf120]

Had a guess to what SuperStep was, but had to Google it just in case. I was correct...

I don't like to overclock or mess around in the BIOS through Windows based applications (i.e. SuperStep). Just go straight to the BIOS if you want to do stuff like that.

The reason why Safe Mode and Last Known Good Config doesn't work is because the BIOS loads first; before everything. You would want to reset your CMOS. The manual that came with your mobo should tell you how.

[Bio-Hazard]

I'll have to agree with you, the OC rpogram clocked the system to high. But it sounds like you can at least post, so either reset your Bios manually via the jumper/battery or boot the system and go into the system bios (Delete Key nonmally) and reset all the settings (load optimal setting or load fail safe settings).

[Kentetsu]

Thanks a lot for the info guys. I did try reverting to optimal settings in the bios, but no good. The bios itself does not allow for manual changes to the processor speeds, so I figured that the program was loading with windows and instituting the changes at that point. I never considered that superstep simply changed the bios for me. That will certainly make things simpler for me. I'll try clearing the cmos today and will post back tonight with the results.

Thanks again, I was about ready to wipe the hard drive and start over from scratch! :)

[timberwolf120]

I guess when you load optimal settings in the BIOS, it would work fine until Windows and SuperStep loads, which would override the optimal settings you just set. Is that how Windows based OC programs work Bio-Hazard?

[Bio-Hazard]

I've seen them work both ways, but don't quote me on that, I never really us Windows based OC'ing programs at all for OC'ing the complete system, just video cards. I'm 100% old school when it comes to system OC'ing, everything is done in the bios.

[Schwarz]

I would think they take effect when windows load.
If it doesn't work in Safe Mode and still loads those Overclocks then I would think you would have to reinstall windows.
Because even if you do change the settings manually or reset the CMOS as soon as windows will load then the changes will come back and your system will crash.
If this is the case here.
I haven't used any of them windows OC programs either.
Another thing though, maybe you could delete the program through DOS...

[Bio-Hazard]

Another thing though, maybe you could delete the program through DOS...

Now that's a thought and hopefully the OC program isn't one that actually changes the system Bios. But if it is one of the ones that modifies the Bios, clearing the CMOS and deleting the program will take care of the issue I would think.

[Kentetsu]

Thanks for the help guys. I cleared the cmos and all is good now (at least that part of my issues). Apparently the program does change the bios. I just had it stuck in my head that the program was loading with windows, and making the changes at that point. I'm glad it turned out to be otherwise...

I also normally use only the bios for clocking, but the thing is this piece of crap bios they're using has absolutely no settings for that. Its like they castrated it or something. The only option is to use the bundled software to make those types of adjustments.

This is my first ever Foxconn/Winfast mobo, and I have to say that despite the extremely low cost (like 35 bucks) I am not very happy with it. Need to sort out some video issues with the built-in, so far it won't run even the oldest/simplest video games or benchmarks.

Oh well, I'll keep tweaking at it and maybe I'll get something useful out of it yet. All I wanted was a system for my boys to play their games on, so they'd stay the heck off of my other systems. lol.

Thanks again though, you guys have been a great help...

[Bio-Hazard]

Glad to hear that you at least got it up and running. Good luck with the rest of the issues.