• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Weird Windows 2000 Problem - Anyone have suggestions?

G

Garet Jax

Diamond Member
Hello all,

I posted this in Overclocking, but didn't have any luck. 🙁

I have a machine with the following hardware:

Asus A7V133
Duron 750Mhz
GlobalWin CAK38 HSF
512 MB Crucial PC133 RAM
Maxtor 20.0 GB @ 5400 RPMS
Hercules 3D Prophet 4500 (Kyro II)
Turtle Beach Santa Cruz
48X Generic CD
HP 9100 Series CDRW
Digitial Doc5
Antec 1030 (with 4 case fans)

I have overclocked it to 6.0, 6.5 and 7.0 X 133 seemingly successfully. I have not pushed the OC to beyond a FSB of 133. It is running Windows 2000.

Two times in the last two weeks, the OS seems to have been corrupted. When the machine is starting it will hit the Windows 2000 window (the one with the blue progress bar). The progress bar will fill completely, the screen will blank (like it normally does) and then the machine will soft reboot. It looks like it displays the BSOD just before it reboots (unfortunately too quickly to know for certain and far too quickly to read any messages). It will do this repeatly until I turn the machine off. I have not found a way to get back into the OS.

Last time this happened, I tried to boot in Safe mode and a number of the other available options to no avail. I chalked it up to experience, re-installed the OS and forgot about it. It happened again last night. I have not yet tried other booting options for this occurence.

When I re-installed Windows 2000 3 weeks ago (before either of the corruptions), I had trouble finding the right drivers for 2000 for the promise controller. As a result, I just plugged the HD into the regular IDE channel on the A7V133. This is the first time in the year or so I have had this machine, that I ran the HD this way. Before the OS re-installation 3 weeks ago, it was always plugged into the promise controller.

I don't think this problem has anything to do with OCing (because the FSB is well within range) and because I have tried booting at the default 7.5 X 100.

Any ideas what to try next or how to solve it?
 
This sounds like a classic case of OC'ing corruption. Considering the fact that Duron's don't run @ 133 that's probably what started it. I accidently had the BIOS set on a K7S5A to 133 for a Duron 900 on a pc I was building for a friend and it killed that chip in an instant. In my limited OC'ing experiece once the OS has been corrupted by the OC'ing you need to go back and start from scrath, booting it to within specifications won't do any good as the corruption has already taken place. If you want a faster processor instead of OC'ing it, buy a better one they're cheap as hell and your board can handle it!
 
actually, durons can run at 133mhz because I have a 800mhz one running at 133mhz in my kt7e.
it's definitely your bios settings.
 
it can be a number of things. flaky hd, flaky ram, cpu gets flaky on high overclocks

have you tried stress testing your duron when overclocked yet?

true running rc5, seti, and prime 95 and see how well it fares.
 
Thanks for all replies.

Originally posted by: Adul
it can be a number of things. flaky hd, flaky ram, cpu gets flaky on high overclocks

have you tried stress testing your duron when overclocked yet?

true running rc5, seti, and prime 95 and see how well it fares.
Click to expand...

Adul,

When I originally OC'd this chip 8-10 months ago, I had it running at 133+ FSB and I did stress it with a lot of the tools I was able to find (including Prime and SETI). It seemed to be rock solid.

Originally posted by: WhoDeeny
This sounds like a classic case of OC'ing corruption. Considering the fact that Duron's don't run @ 133 that's probably what started it. I accidently had the BIOS set on a K7S5A to 133 for a Duron 900 on a pc I was building for a friend and it killed that chip in an instant. In my limited OC'ing experiece once the OS has been corrupted by the OC'ing you need to go back and start from scrath, booting it to within specifications won't do any good as the corruption has already taken place. If you want a faster processor instead of OC'ing it, buy a better one they're cheap as hell and your board can handle it!
Click to expand...

WhoDeeny,

Interesting point you made. It got me thinking and I have a theory. The only change between 8-10 months ago and today is the slot the HD is plugged into. 8-10 months ago it was plugged into the Promise controller. Today it is plugged into the native IDE channel on the A7V133 (because I couldn't find drivers that worked).

Is it possible that the Promise controller is more capable of being OC'd than the native IDE channels? If this is the case, then it could certainly account for the mysterious corruption on my HD.

In another thread, someone pointed me to a link for ASUS' version of the Promise drivers that allowed me to install 2000 with the HD plugged into the Promise controller last night. I will test this theory out over the next couple of weeks.
 
I had an A7V and had very similar problems. After several evenings of tinkering the only thing I could get to work was to move the drive back to the via controller. Apparently my promise controller went south and never came back. 😉

Try moving the drive back to the Via controller. Incidently I had to do a reinstall after moving it but didn't have any more problems after that.

Semper Fi
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top