:stick:Quote:
Originally Posted by ztop
Printable View
:stick:Quote:
Originally Posted by ztop
I have the same problem and no solution.has to be something I need to disable in vista itself.Quote:
Originally Posted by ztop
it is probably because of power saving. it decreases multiplier when cpu is not much loaded like laptops. try looking at the cpuz while runnig super pi or something like that. at that time if you see 7 multi then you can close this situation by power options in the control panel.
AW9D looooool :D
huh AW9D not AB9 QuadGT!Quote:
Originally Posted by fgw
someone delete that post before someone hoses his board!! :p:
sorry my fault! i own both boards. fingers were quicker than mind!Quote:
Originally Posted by eva2000
no new bios for the quad till now. somebody mentioned a final version should come out during this week. at least we know abit is not sleeping anymore. ;)
done!Quote:
Originally Posted by Revv23
i have tried, but still no goQuote:
Originally Posted by kromosto
are you running 1.39 version of cpuz?
#1. - This board is not a P5B-D take your settings from that board and forget them, take the time to learn a new board.Quote:
Originally Posted by Evanesco
#2. - Open CPU-Z and turn on orthos and watch your MHZ climb. You still have some sort of power saving on, shut everything off in the cpu page but except the the Execute Disable Bit.
Don't blame the board because you are to impatient to learn anything about it. No two boards are alike and you shouldn't expect them to be. This clocks differently then P5B with different timings and different voltages. Don't go ragging on the product because you are too dumb to use it.
Quote:
Originally Posted by ztop
under the cpu setting in bios, disable everything but the No Ex bit.
o yesQuote:
Originally Posted by kromosto
Don't use Vista... :)
Just built a box for a friend he is begging me to remove vista and put xp for him. He installed Alcohol 120$ and it BSOD. This is after 1 day of use.
Well who is dumb here! Abit! You got to admit, that it is really sloooow of abit not releasing a new final bios for this board.Quote:
Originally Posted by Revv23
How can a company put a product on the market, that does not work with USB keyboards, unless you digg deeper, and might get lucky to enter abits forum( that forum got serious problems ) and download the right beta bios.
On the box, it says Quad and future proof. Well it deffently isn't, and still isn't. The official bios is in its version 1.0
You can call me dumb just as much as you like! I know exactly what I'm working with.
#2. I did that, and if you look around, I'm not the only one with that specific problem. I did extactly that thing with orthos.. and the multi just don't change.
the whole building got hit by a power surge & it took out several servers incl. the one that hosts the forum.Quote:
Originally Posted by Evanesco
Normally the forum ticks along very nicely thank you.
Quote:
Originally Posted by Heidfirst
if that is true, lol makes you wonder should we buy mobos from a company that doesnt have surge protection for their Servers :stick: omg, not some worstation but Servers makes you wonder do they know what they are doing lol how do thay even make mobos is they dont have compentant IT staff for thir own computers.....lol i like abit but that is just too funny
ok, thats bad, ... for them..Quote:
Originally Posted by Heidfirst
but still.. How can abit release a product that doesnt support USB keyboards. That gives me some sort of indication, that abit does not test their products good enough before they release it.
if a real noob ( a person that does not visit forums like XS ), bought this board, he would have RMAed it right away, and would never ever look at or consider buying an abit product again.
Yes, I'm dissapointed!
Quote:
Originally Posted by Millyons
find me a surge protector that can stop a bolt of lightning and i will be impressed.
Quote:
Originally Posted by Evanesco
So how come mine works fine with 3 different usb keyboards now(after i looked in bios and found the switch t go from OS to BIOS control) and i had that multi issue then i looked in bios and fixed it in five minutes?
The board works fine, you just are too impatient. Most users that buy a product figure out how to use it before they send it back, even non XS people. The problem is you assume the issue is with the board and not yourself.
I dont think in all my years of building computers i have had a motherbaord exactly perfect right out of the box. Except perhaps my IC7-G. I always have to play with the options before everything works right...
Quote:
Originally Posted by Revv23
Quote:
Originally Posted by Heidfirst
I commented his post, and i dont see anywhere in it that a lightning hit the building
Delays on the last bios (the staff of Abit Taiwan and Europe is organized for the CEBIT) ; ABIT England said to me.
I hope to have more information before or during the CEBIT when I would see them has their stands (I believe that Fugger also comes?)
well, when I switched from OS to bios, the keyboard wasn't present, when I wanted to update the bios from a boot floppy. And if turned it back to OS, it just restarted, both on floppy(DOS) and vista.Quote:
Originally Posted by Revv23
I wanted to upgrade the bios.. so I had to search my house for the USB->PS2 adaptor, and that wasn't easy. ( not abits fault, but anyway )
I finally updated the bios to beta 02, and now I was able to use my USB keyboard.
I then started installing Vista, but it just hangs around during install, and doesn't go any further.
I then got the latest beta 06 bios, and updated the board. And now I was able to install Vista on my Quad Core QX6700. Everything went smoothly during install. And after installing various drivers and stuff like uGuru, I went for some basic OCing( that includes raising vcore and voltage on NB etc also ). During my way up to FSB400, at around FSB366 everthing seemed stabled. Ran a couple of Orthos to stress my QX6700 cores , and wow, what nice temps and stability I had. Fired up CPU-Z for some routine checking, and to my surprise the multiplier was set to 6x. I then rushed into bios and disabled all power related stuff. Went back into Vista, ran orthos, checked the multiplier in CPU-Z, and it was still on 6x.
The 6x multiplier was fixed no matter what I did, as soon as I raised the FSB speed. At standard settings there was no problems at all. By the way, I just come to think about, that I noticed the PWMs where around 85C and raised well beyon 100C when the CPU was under load. But uGuru didn't give me any warnings, so I didn't bother at the time, had other things to bother about, anyone ???
Please don't call me impatient again!!
humm thats odd i used the bios it shipped for a long time on a saiteik keyboard without ever having a problem
uGuru may not have been set up correctly for it to give you warnings. I had to set it at 120c and when one of the PWMs did go over 120, it promptly gave me a warning. Of course you will have to keep an eye on your screen to monitor the temps. It turned RED! So you will have to play with it like all softwares and hardwares. Also why not flash your bios in windows? Its so convenient. When everything is said and done, just flip the switch at the back and you're all good to go.Quote:
Originally Posted by Evanesco
Edit: Seems this issue is similar to the posts above. Checking with RM clock my multiplier is set to 6 on two of the cores. Checking in sandra it says that thermal throttling is enabled.
I know this has been posted before, but haven't a clue where.
Have my QX6700 installed.
Running 11x300. all features disabled except Ex Bit.
Ran the modded prime and noticed that 2 of the cores had hit test 6, where as the other 2 were still on test 3.
Then ran cpu-z with the -core parameter, and it seems two of my cores aren't overclocking.
Can't remember, but was there a solution to this problem. Is it the fact I am using an 11 multiplier?
I believe I am running the latest beta bios. Have USB, raid and ide all working as they should.
Thanks for any help.
RLM
I remember reading that there's a problem with vista possibly overriding c1e/eist settings, so you need to fiddle with power settings possibly. If rmclock works, you could always force itQuote:
Originally Posted by Ruslan