-
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.
[b]ABIT SUCKS[/b]
- Thread starter 1EZduzit
- Start date
*user error*
Although your pain is understandable, I highly doubt that Abit is repsonsible for your mishaps. You updated your BIOS, for what reason, simply to overclock higher? Like the saying goes, "If it ain't broke, don't fix it." Perhaps there were other variables to it not posting anymore. Your pushing the voltage perhaps? Also, on the AMD board, the board will only change multipliers if your CPU is already unlocked.
Although your pain is understandable, I highly doubt that Abit is repsonsible for your mishaps. You updated your BIOS, for what reason, simply to overclock higher? Like the saying goes, "If it ain't broke, don't fix it." Perhaps there were other variables to it not posting anymore. Your pushing the voltage perhaps? Also, on the AMD board, the board will only change multipliers if your CPU is already unlocked.
Noid
Platinum Member
7 posts to yourself in 4 hours ...?
You need to give time for members like myself to help you.
(I have a Xp2600 running in mine)
1. the KX7-333 dosen't unlock chips. (you need to unlock the chip manually)
2. Clear CMOS and reset your setting to Chip defaults.
Post back after please.
You need to give time for members like myself to help you.
(I have a Xp2600 running in mine)
1. the KX7-333 dosen't unlock chips. (you need to unlock the chip manually)
2. Clear CMOS and reset your setting to Chip defaults.
Post back after please.
Corporate Thug
Lifer
you are blaming abit because YOU didnt have your info straight.
nforce 2 unlock multipler and some kt400 do as well NOT the original nforce
then u screw up your system by OCing and again its abit's fault?
nforce 2 unlock multipler and some kt400 do as well NOT the original nforce
then u screw up your system by OCing and again its abit's fault?
Noid
Platinum Member
well ,, I'm really confused now ...
I thought he was trying to change the Multi's on the KX7-333, and it locked up.
But now I see reference to a IT7 that's dead also ...
I have never had any mb die on me ...(all had some with problems thou)
_________________
I think he's probably up and running now .. after he cleared CMOS...
The KX7-333 are a hearty mb... I've oc'd the shiznitz outta mine...
I think he's just got some learning to do .....
If your still reading,,, but afraid to reply ....
My KX7-333 had very little thermal paste under the NB HSF unit. (which limited my fsb to 170ish if I remember right)
(yes,,, that means 3dmark2001 and other benchmarks fail,,, among other problems)
If you have some time and some extra cash...
Take out your mb and check under the HSF unit on the nb. (northbridge chip)
Get some Artic Silver thermal adheasive...( permanent glue,,, can only freeze mb to remove) ,,, and a cyrstal orb (I lapped it also)
(cheapest solution)
Or... get a cooper HSF unit that snaps/ bolts on and regular Artic Silver (more expensive usually)
That should improve your oc immensly ( I run 189.9fsb)
As for unlocking your chip ...
There are several methods to unlock chips ... choose your poison,,, some are easy ... some are hard.
Once the chip is manually unlocked ,,, you can change the mulitplier.
(unless you were unlucky enough to buy the new chips that are LOCKED permanently by AMD )
The BIOS only allows multi's 5.5 to 12.5 if I remember correctly
(that's just the way it is... until Abit changes BIOS to allow higher than 12.5)
There's a lot more stuff that can be done... but that's that best advice I can give for now.
I thought he was trying to change the Multi's on the KX7-333, and it locked up.
But now I see reference to a IT7 that's dead also ...
I have never had any mb die on me ...(all had some with problems thou)
_________________
I think he's probably up and running now .. after he cleared CMOS...
The KX7-333 are a hearty mb... I've oc'd the shiznitz outta mine...
I think he's just got some learning to do .....
If your still reading,,, but afraid to reply ....
My KX7-333 had very little thermal paste under the NB HSF unit. (which limited my fsb to 170ish if I remember right)
(yes,,, that means 3dmark2001 and other benchmarks fail,,, among other problems)
If you have some time and some extra cash...
Take out your mb and check under the HSF unit on the nb. (northbridge chip)
Get some Artic Silver thermal adheasive...( permanent glue,,, can only freeze mb to remove) ,,, and a cyrstal orb (I lapped it also)
(cheapest solution)
Or... get a cooper HSF unit that snaps/ bolts on and regular Artic Silver (more expensive usually)
That should improve your oc immensly ( I run 189.9fsb)
As for unlocking your chip ...
There are several methods to unlock chips ... choose your poison,,, some are easy ... some are hard.
Once the chip is manually unlocked ,,, you can change the mulitplier.
(unless you were unlucky enough to buy the new chips that are LOCKED permanently by AMD )
The BIOS only allows multi's 5.5 to 12.5 if I remember correctly
(that's just the way it is... until Abit changes BIOS to allow higher than 12.5)
There's a lot more stuff that can be done... but that's that best advice I can give for now.
SilverBack
Golden Member
Yeah I believe it's user error as well.
Well, what do you want to know? Do I know how to cear cmos? Yes, I even took the cmos battery completly out, unhooked the PSU, took out all the PCI cards except the video card and totally unhooked the hard drive. I still get no beeps and no video. I have no idea why it doesn't boot.
I had an unlocked xp1800 paly in this (that I wish I kept) that would run 10.5 x 172. I sold it because I had a XP2100 and I tried to unlock it, but it just wouldn't unlock. I sold that cpu with another system to my nephew and picked up a xp2000. I deceided to give the 2000 to my son and put in the 1600 he had because I was only going to use this system as a MP3/dvd player and hook it up to my stereo/TV. Somehow (despite being very careful) the 1600 died on me so I RMA'ed it and they sent me a XP2000 Tbred KIUHB. It booted fine, but it had an old bios and wasn't seen right, so I decied to put the new bios in. The CPU would run166 fsb (Alpha 8045 HS), but took 1.675 volts to do it and 3Dmark would lock up for some reason, even before I flashed the bios.
I deceided to try running 1 512 stick of Corsair XMS3200C2 instead of the 2 x 256 of AIB PC3500 in it to see if that mnade a difference. When I booted after making the switch, I went into bios because I had it set at 133 fsb. I changed it to 166 and then thought " I wonder what would happen if I set the multiplier to 12 instead of 12.5? I did and it booted up? Wierd?? It shouldn't do that. I have the bolt on HS and I didn't want to take it out to look at the CPU because you have to take the mobo completly out, so I deceided to play with the multi's.
I found that 11 (the lowest I tried), 11.5, 12, 1nd 12.5 all booted at 133 fsb. the 13 multiplier gave me the "unworkable cpu" error. I already knew it woule run 12 x 166 so I tried 11.5 x 166, thiniking that if I could get that to work, I would be able to run at default voltage. It locked up saying I had a bad config.sys file in windows/system?? and gave me a chance to fix it. I don't know enough to be messing around in those files, so I rebooted and set everything back to default. The system booted fine with no errors. To be safe I shut it down completley and let it sit for a few minutes. I then rebooted and everthing was fine so how was my config.sys file bad? I really wanted to run 11.5 x 166 so I tried it one more time to see what would happen. I got the exact same error, so I rebooted, but then it wouldn't reboot. No beeps, nothing. I have tried everthing I know and now I have no way of knowing if it is the mob or the cpu?
I had an unlocked xp1800 paly in this (that I wish I kept) that would run 10.5 x 172. I sold it because I had a XP2100 and I tried to unlock it, but it just wouldn't unlock. I sold that cpu with another system to my nephew and picked up a xp2000. I deceided to give the 2000 to my son and put in the 1600 he had because I was only going to use this system as a MP3/dvd player and hook it up to my stereo/TV. Somehow (despite being very careful) the 1600 died on me so I RMA'ed it and they sent me a XP2000 Tbred KIUHB. It booted fine, but it had an old bios and wasn't seen right, so I decied to put the new bios in. The CPU would run166 fsb (Alpha 8045 HS), but took 1.675 volts to do it and 3Dmark would lock up for some reason, even before I flashed the bios.
I deceided to try running 1 512 stick of Corsair XMS3200C2 instead of the 2 x 256 of AIB PC3500 in it to see if that mnade a difference. When I booted after making the switch, I went into bios because I had it set at 133 fsb. I changed it to 166 and then thought " I wonder what would happen if I set the multiplier to 12 instead of 12.5? I did and it booted up? Wierd?? It shouldn't do that. I have the bolt on HS and I didn't want to take it out to look at the CPU because you have to take the mobo completly out, so I deceided to play with the multi's.
I found that 11 (the lowest I tried), 11.5, 12, 1nd 12.5 all booted at 133 fsb. the 13 multiplier gave me the "unworkable cpu" error. I already knew it woule run 12 x 166 so I tried 11.5 x 166, thiniking that if I could get that to work, I would be able to run at default voltage. It locked up saying I had a bad config.sys file in windows/system?? and gave me a chance to fix it. I don't know enough to be messing around in those files, so I rebooted and set everything back to default. The system booted fine with no errors. To be safe I shut it down completley and let it sit for a few minutes. I then rebooted and everthing was fine so how was my config.sys file bad? I really wanted to run 11.5 x 166 so I tried it one more time to see what would happen. I got the exact same error, so I rebooted, but then it wouldn't reboot. No beeps, nothing. I have tried everthing I know and now I have no way of knowing if it is the mob or the cpu?
Originally posted by: shady06
you are blaming abit because YOU didnt have your info straight.
nforce 2 unlock multipler and some kt400 do as well NOT the original nforce
then u screw up your system by OCing and again its abit's fault?
It is supposed to do 333 mhz right? Or is that just marketing hype? I think I screwed up my system because the bios allowed me to change the multipliers, which it shouldn't let me do if it is going to WRECK the board or CPU!! What is up with that??
Now that I know Abits RMA policy there will be no more Abit parts for me EVER and anyone who buys used Abit parts is a SUCKER IMO!!!
Laugh all you want, I don't really care about that. If it wasn't such a pain in the butt for me to handle all these BS problems I'd be laughing with you.
Laugh all you want, I don't really care about that. If it wasn't such a pain in the butt for me to handle all these BS problems I'd be laughing with you.
Noid
Platinum Member
The BIOS cant stop your BIOS selections ,,, it has no way to stop your brain or your fingers from making errors.
another thing ... not all components work well together... Like one CPU compared to another CPU ...
They all have different characteristics... Esp when going to faster chips ...
(one usually has to make memory timing adjustments)
The config.sys error (or other window errors) is typical of memory errors or a severly misconfigured CPU.
I dont think I can help you.
(because I dont think you have the patience to understand what you are doing)
There are utilities to use before attempting a boot into windows when overclocking.
(to avoid the problems your having)
Oh .. and have fun abusing the RMA policies.
another thing ... not all components work well together... Like one CPU compared to another CPU ...
They all have different characteristics... Esp when going to faster chips ...
(one usually has to make memory timing adjustments)
The config.sys error (or other window errors) is typical of memory errors or a severly misconfigured CPU.
I dont think I can help you.
(because I dont think you have the patience to understand what you are doing)
There are utilities to use before attempting a boot into windows when overclocking.
(to avoid the problems your having)
Oh .. and have fun abusing the RMA policies.
No other suggestions? My guess is that either my CPU or my bios (or both) are trashed. I will try writing Abit tech support and see what they suggest. If i had another board or cpu handy I would try that. I do have another AMD system (my son's) but it also has a Alpha PAL 8045 HS on it and it is just too much trouble to take it off. I am going to try and purchase a cheapo xp1600 paly to try and see if the board still works. If it doesn't then I will have to try the XP200 Tbred in my son's mobo and see if it works. Major pain in the a$$!
I tried the monitor on another system and it is fine. I am going to try hooking a floppy up to the KX7-333 and booting from a boot disc, but I fear that it will only be a waste of time since it won't even post without a hard rive attached.
I tried the monitor on another system and it is fine. I am going to try hooking a floppy up to the KX7-333 and booting from a boot disc, but I fear that it will only be a waste of time since it won't even post without a hard rive attached.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 25K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 24K
-
-
