- Joined
- Feb 19, 2004
- Location
- NC
First post here, been reading for a while, but just registered. I need help.
I just got the following:
K7N2 Delta-L
AMD XP2500+
2x512 DDR400 Geil Golden Dragon
Maxtor 80GB 7200
Thermaltake Extreme 12 Volcano
Arctic Silver 5
Vid card is my old 4X ATi Radeon 64MB DDR w/VIVO. (7500 equivalent, I believe). I don't have the cash right now for the latest Radeon, so I'm going to live with this one until I can get the one I want.
I put the thing together last night, got Win2K installed on it, and burned it in with Prime95 overnight. No problems. Decided this morning to start seeing what she would do. Tried the "jump straight to 200Mhz FSB" trick, and while it would boot up, Prime95 would fail. I played with it a little, but couldn't get it stable, so I said, "Okay, let's go back to the start and start bumping it up a bit at a time and see how far it goes".
I started at 170Mhz, ran Prime95 TT for an hour, no problem. Bumped it to 175Mhz, ran Prime95 TT for an hour, no problem. Bumped it to 185Mhz, and it won't post. So, let's reset the CMOS and start again, right? WRONG. I've reset the CMOS at least 10 times, changed the jumpers to safe mode/100Mhz, won't post. D-Bracket shows halt at Memory check when in user mode/133Mhz. When changing it to 100Mhz/safe mode, D-bracket shows halt at floppy controller. I've pulled the memory, swapped it between slots, tried one stick, the other stick, both sticks, no sticks, no luck. I cannot get this board to post now. Disconnect floppy, doesn't matter. Heck, I even pulled the CMOS battery off the board, let it sit for 60 seconds, and put it back, and no luck.
So, I sent an e-mail to MSI support, and of course, the first thing out of their mouth is, "By overclocking the system, it will cause damage to the components installed and this also include the mb. Please confirm the cause of the problem with other components installed in another working system board to determine the cause of the problem."
I don't buy that. The fact that the thing ran fine overnight, and all this morning, and just started this not-posting thing when I made the last change to the FSB, tells me it's not that I damaged it with overclocking. My temps never went over 46C on the CPU and 40C in the system at any time, and I never had to crank the Tt fan over 4500RPM or so. She was running beautifully.
Help? WTF is going on here? Did I really mess up my stuff by trying to OC it? I've read SO many posts of people OCing this setup much higher than I tried to, I can't believe I damaged something. I never smelled smoke or anything bad like that. It just simply fails to post.
Thanks in advance for any help!
I just got the following:
K7N2 Delta-L
AMD XP2500+
2x512 DDR400 Geil Golden Dragon
Maxtor 80GB 7200
Thermaltake Extreme 12 Volcano
Arctic Silver 5
Vid card is my old 4X ATi Radeon 64MB DDR w/VIVO. (7500 equivalent, I believe). I don't have the cash right now for the latest Radeon, so I'm going to live with this one until I can get the one I want.
I put the thing together last night, got Win2K installed on it, and burned it in with Prime95 overnight. No problems. Decided this morning to start seeing what she would do. Tried the "jump straight to 200Mhz FSB" trick, and while it would boot up, Prime95 would fail. I played with it a little, but couldn't get it stable, so I said, "Okay, let's go back to the start and start bumping it up a bit at a time and see how far it goes".
I started at 170Mhz, ran Prime95 TT for an hour, no problem. Bumped it to 175Mhz, ran Prime95 TT for an hour, no problem. Bumped it to 185Mhz, and it won't post. So, let's reset the CMOS and start again, right? WRONG. I've reset the CMOS at least 10 times, changed the jumpers to safe mode/100Mhz, won't post. D-Bracket shows halt at Memory check when in user mode/133Mhz. When changing it to 100Mhz/safe mode, D-bracket shows halt at floppy controller. I've pulled the memory, swapped it between slots, tried one stick, the other stick, both sticks, no sticks, no luck. I cannot get this board to post now. Disconnect floppy, doesn't matter. Heck, I even pulled the CMOS battery off the board, let it sit for 60 seconds, and put it back, and no luck.
So, I sent an e-mail to MSI support, and of course, the first thing out of their mouth is, "By overclocking the system, it will cause damage to the components installed and this also include the mb. Please confirm the cause of the problem with other components installed in another working system board to determine the cause of the problem."
I don't buy that. The fact that the thing ran fine overnight, and all this morning, and just started this not-posting thing when I made the last change to the FSB, tells me it's not that I damaged it with overclocking. My temps never went over 46C on the CPU and 40C in the system at any time, and I never had to crank the Tt fan over 4500RPM or so. She was running beautifully.
Help? WTF is going on here? Did I really mess up my stuff by trying to OC it? I've read SO many posts of people OCing this setup much higher than I tried to, I can't believe I damaged something. I never smelled smoke or anything bad like that. It just simply fails to post.
Thanks in advance for any help!