I didn't say FSB problems. I'm not having any fsb problems. I had a problem getting the cpu stable. I could dump 1.55volts on the cpu and it wasn't stable with 0311 but with 0501 it works fine at lower voltage.
Printable View
Anyone have a problem with their quadcore running 500mhz on FSB? Is it the boards problem where the POST restarts, or is that the chip? I cant seem to tell, it might be too much load on the chipset and everything. Anyone know if this sounds like a board limitation or FSB wall?
What voltages are people using to get 500+ FSB on a dual core for the following:
PLL
Northbridge
FSB Termination
Southbridge
Thanks
Heres what I ran on my Xeon 3060 (E6600 Equivalent)
PLL - 1.6-1.7v
NB - 1.55v
FSB Term - 1.4v
SB - Auto, but now for quad I leave it on 1.2v
Also set your NB to .67x or .61x depending on how much voltage your chip is eating, seems to of helped out my OC on my quad.
How are the actual voltages (measured reliably with a DMM
or something) the P5K Deluxe compared to the
settings in the BIOS?
Does VCORE actually match what's expected from the
BIOS settings for various versions of BIOS and
various VCORE values from 1.1 to 1.5x?
Does it droop a lot under load?
I notice that ASUS redesigned the RAM voltage regulation
on the P5K PREMIUM vs. the P5K deluxe and added several
more MOSFETS to their new board. Does the P5K DLX
generate a lot of instability / droop for RAM voltage
and so they found the need to change it radically?
I've heard lots of stories about many (most?) other ASUS
P5**** model boards having BIOS bugs or design
quirks where the actual VCORE is pretty different than
expected from the settings in BIOS.
I've also heard that their "x-phase" VCORE power on some
other models boards doesn't even do ANYTHING
unless you set the various VCORE options a certain way in
the BIOS AND tell it to give a 200mV Vboost.
Any reports on the P5K's voltages and power stability
under heavy load (Q6600 OC'd, 4 double sided RAM sticks) would be welcome, thanks in advance!
Is the stock ASUS P5K Deluxe cooling considered
trustworthy, or is one WELL advised to change it?
I remember hearing some comments by people about
things like NB / SB / MOS heatsinks with installations
that aren't actually even touching some of the chips
(e.g. the multiple FETs in a line), or with super-thick
gunky thermal tape so much that the overall cooling
is not so good, etc.
I also saw one article (which may have been biased)
that showed the back of the P5K PCB in the section near
the MOSFETs and CPU being VERY hot in the region of
100C under normal conditions.
I don't even know how well their heatpipes work in
practice whether the motherboard is vertical or horizontal
and whether there are mechanical/contact problems
with the NB/SB/FETS so much that it might not be doing
its job without reinstallation or replacement.
So I end up with some doubts about whether the
overall setup is "very pretty and theoretically impressive"
with the heatpipes, heatsinks, etc but maybe very
unreliable in the real world if the mechanical contact
and cooling is heat pipe action is not good.
Because of difficulty, risk, and not wanting to make things worse,
I would not want to tear off the existing heatsinks and
heat pipes if I can at all help doing it and they are
doing the job, but if they are actually blocking good
convection for the parts they supposedly cool I'd reinstall
them or replace them as needed/possible.
But probably wouldn't tear it ALL apart just for the heck
of it to replace their thermal tape with AS5 if there's no
well known major benefit to cooling of a large amount.
What can one do to cool the underside of the CPU area
of the PCB where there are bottom-mounted FETs and
the close confinement of the back side of the case
when you have no waterblock / heatsink designed for
that area, and your case hasn't got a back-side
fan opening? Any clever and cost effective ideas / products?
the stock cooling is OK better than the 680i motherboards. I'm watercooling my NB though. the motherboard temp sensor is at the top of the board so if you really want to know the temp of the board use your finger or get a temp probe and put it underneath the NB heatsink.
Jusrt got the P5K Premium to replace the P5K Deluxe that I erazed the EEPROM on with Asus flash. I booted straight up on delivery BIOS 0102 with 445x9 on 1.55v and memory at 1110 on air. I couldn't do that on the deluxe with the same CPU and memory so first impressions are that the different capacitors appear to make a difference. I will play with it a bit more and see what it takes to run orthos stable. Just wish I had more faith in the temp readings
If you want to remove and replace the thermal pads on the deluxe SB/NB with AS5 use the end of any click style pen barrel to compress the heatsink pins under the board. Its way better then trying to use long nose pliers as the end of the barrel fit neatly over the pins compressing them enough to allow easy release. That way you wont break any pins. You can also stick a 40mm fan on the NB to assist cooling . I did it on mine before I screwed the BIOS - I didnt bother with the mofsets. If you want to change the mofset on the side u could use a thermalright HR-09 mofset cooler. Check it will fit first. Overall changing the paste does help reduce MB temps and gives you confidence that the heatsinks are properly mounted with decent paste applied.
Never got to a P5K Deluxe, but am benching a P5K-Premium right now with the same X3060 cpu I ran in my P5B, and I can run SuperPi at quite a bit higher fsb in the new board.
Can't wait for the GO Q6600's to arrive here (New Zealand btw)
Anyone have resume issues? When my monitor goes into sleep mode, the computer will refuse to wake up. Anyone have a solution for this thing?
I've had that problem on a few different computers
in the past. I don't know if there's ever a totally
consistent solution.
One thing to help debug it is to make sure your
ACPI settings in Windows (assuming you use it)
and the BIOS are set to ONLY sleep the monitor
at that time, and not ALSO the HDDs, PC in
general, etc. Also change your screen saver to
something really basic like "none" or "starfield",
because sometimes it can be the screen saver
that crashes and not the monitor sleep itself.
Update your video drivers to the latest stable
thing, and look in their release notes for any
warnings about this issue.
Also set in the BIOS the ACPI monitor settings
for something like "DPMS enabled monitor" as
true (assuming it's so), and "All modes -> Off"
for the monitor power savings type of action.
Then in the BIOS power management settings
be sure to enable wake-up on several different
events like PS/2 keyboard, PS/2 mouse,
USB keyboard, USB mouse, etc.
Also try reprogramming your "power off" button
as functioning as a "shutdown" or "suspend"
function as opposed to "power off immediately"
or "power off in 4 seconds" because when all
else (keyboard, mouse) fails to wake a
PC, sometimes a short tap on the soft-off case
power button will enable a graceful shutdown
when it's so configured.
Also enable the BIOS setting to
do something like re-post VGA BIOS or
issue VGA interrupt on resume from sleep
state. It's called something like that, I forget
the exact terminology used. Sometimes that's
necessary for video cards to resume working
properly when they come back from sleep.
Also try unplugging the USB KB/Mouse from
whatever hub or port they may be on and
(re)plug then directly into one of the motherboard
ports and see if they reset and help you wake
up from sleep state that way.
Other times physically powering off the monitor
and reapplying power to it can help wake up
the video card it's attached it.
Be careful of using things like DVI->VGA
dongle adapters too since sometimes they can
interfere with the communication of the DDC
link with the monitor that helps the PC manage
the monitor's power settings etc. Use the dongle
that's the latest one that matches your specific
video card or try a new VGA/DVI cable etc.
Also if you have a spare DPMS enabled monitor
then try hooking it up and see if the problem
persists with that one.
The only BIOS difference I can see from the deluxe is that CPU PLL offers voltage increments upto 2.2v. Presume that is for people with chilled cooling to make use of it. Overall seems a little bit more stable than deluxe.
From conversation at P5WDH thead about P5K DLX soldered BIOS chip
http://www.xtremesystems.org/forums/...postcount=5463
Hey guys, Since I get a thermalright ultra-120 Extr, Soon , I have to sacrifice 1 Side panel fan @ my CM stacker 830evo, so there wont be air blowing @ the NB area, can I run NBv. @ 1.55v for 24/7 ? I got like 2 fans @ intake front, 2 side intake/ right side of the sidepanel both( RAM/ HDD area). 1 side exhaust @ the lower left ( GFX area). 1 Rear Exhaust, 1 Top exhaust.
[QUOTE=bichi;2345031]From conversation at P5WDH thead about P5K DLX soldered BIOS chip
[url]http://www.xtremesystems.org/forums/showpost.php? QUOTE]
I notice that this is also refered to on the first post of this thread. It also mentions the following re Crash Free 3: -
'But it has Crash Free 3 bios feature see page 4-7 of manual. Shove the included driver dvd disk the system and boot it up and it should attempt to do a recovery bios flash.'
Please note that Crash Free 3 will not work if the BIOS flash has erased the EEPROM - your board will not post - end of story!
What is actually the best BIOS atm, I am still on 0311? I Try to get my E6420 higher , for 1.475vcore ( bios)/ windows :1.446 load =1.440/ CPU PLL volts: 1.5 /NBv 1.4 FSBv 1.3/ the rest on auto, It is stable. However for 3.5ghz prime would do @ 1.5125 however to get pass 3dmark05 cputest ( 3dmark06 cputest it can run all day). I need up to 1.5325 vcore @ bios. Also another note for 3.4ghz I needed 1.4625 to get 19hours+ primestable, however it would crash during 3dmark05 cputest first loop, so I find out 3dmark05 is a good test. But what I was wondering for 438 fsb= 3.5 / 450 fsb 3.6 , I try to achieve those clocks with reasonable volts, what do i need to change or different BIOS , or my chip just plainly cant got futher, I see @ different forums people with the same PFO: as mine getting 3.5 /3.6ghz within 1.5-1.55vcore , so thats makes me wonder maybe I got wrong settings or should try new bios.....? Btw My temps arent of a concern. 3.4ghz @1.4725vcore 44-45 with peaks to 47 during prime 9hours+ with coretemp..... Any help?
can someone tell me if the Sata problem has been fixed, the system hangs when trying to detect my raptor and samsung drive on sata ports 1 and 2 but runs fine on ports 5 & 6.
Thanks.
Well one thing I have found for my 6750 is it only takes 1.45 vcore to do 475 x 8 3.8Ghz and will boot windows at 490 x 8 with 1.5 vcore but orthos's failed after 3 hrs. I don't know if it is worth it to me to go over 1.5v actual just to gain 100-200Mhz. I would like to get 500 x 8 4Ghz stable but I am very happy with 3.8Ghz because I was only expecting 3.6......:)
Forgive the somewhat trivial question, but it's not
covered in the manual and I can't play with the
BIOS since I'm waiting for my Q6600.
At a given CPU multiplier, is there a way to make
the ram frequency SLOWER than 1:1 over the base
system clock?
I.e. at 1:1 you'd have 266 MHz for both base CPU clock
and also actual clock frequency input to the RAM.
The CPU would run (say) at 9x multi 9x266 = 2400,
and the RAM being DDR2 would run
266x2 rate internally = DDR2-533.
However if my CPU multiplier is locked at x9 maximum,
I'd like to be able to clock the CPU around 430x9,
but if the RAM can't do 430x2=DDR2-860, I'd want
the RAM to run at say DDR2-667 or DDR2-533 so
I'd need to use a RAM:FSB divider of something less than
1:1 which may not be documented as supported
according to the manual (which isn't very clear anyway).
I've heard about "hidden multipliers" in some of these
chipsets to give more flexibility thay the 4 or 5
"typical" choices they talk about in the manual.
What can I do with those on the P5K Deluxe / P35?
Can I actually get a good CPU overclock and still re-use
old slow DDR2-533 RAM by use of such multipliers?
If I change the timing from say 5-5-5-7 to something
slower like 8-8-8-10 or whatever would that usually
permit me to operate the RAM at MUCH higher
frequencies than it's designed for even with slower
access times? e.g DDR2-533 RAM at 450 MHz input?
^^I was looking for that option when I had slower PC2 6400 but I think 1:1 is lowest you can go.
These are awesome http://www.newegg.com/Product/Produc...82E16820148070
for the price these are great http://www.newegg.com/Product/Produc...82E16820231065
I have them both.
Is it just my rig, or the P5K Deluxe doesn't read the temps corectly ? I mean, i have like 17-20 Degrees Celsius (with almost every temp software, even in bios) in idle mode... while i have like 24 Degrees Celsius room ambient. As far as i know, there is no way the CPU temp should be lower than ambient, on AIR. So, it must be either the bios, either.... i don't know.
My rig is on a E6850 (1.5V) + SI128 + P5K Deluxe WiFi + OCZ 1000 4-4-4-15.
What else to do ? I'm now on 0404 bios. Thx in advance !
L.E.: Pls ignore the CoreTemp who shows 4410Mhz. It's actually 3430Mhz, like in AI Suite.
you need to add 15c to the temps on a G0 cpu.:D
HUH?...that makes absolutely no sense!...where do you think coretemp is reading from!..the board!...heck NO!
Even the latest coretemp indeed needs an update to display the correct GO CPU temps, even my 744G E6600 ran at 25°C idle at 3600Mhz, it's indeed in the CPU not the mobo and I hope they correct it as soon as possible as some users are really runnign their current CPU's at what they think a safe zone but in fact they are already in the red !!!
Coretemp 0.94 shows correct temps on e6400 + P5K-D
Ofcourse it's not a GO and an older variant of the Core2 duo (allendale)
Coretemp...as in the core of the CPU
I just read a good 30+ pages looking for this question. My question is can a G0 Q6600 work with BIOS 311? I see some people are reporting that there using BIOS 311 with there G0 E6750CPUs and all is fine, but nothing with the new G0 Q6600's using BIOS 311. Can someone please confirm that BIOS 311 WILL or WILL NOT work with this CPU, so you MUST FLASH TO 501 (or 404). Thanks
I understand from what I've heard from someone who
said they did it is that you CAN boot a Q6600 G0 with
BIOS 0202 or 0311. You MAY see some kind of
"ucode error" message somewhere, but evidentally
that does NOT prevent you from using the BIOS'
built in flash utility to reflash to a newer BIOS that
does support the Q6600 G0 -- which would be 0404 at
least.
That's what I'll be attempting in about 3-4 days since
my motherboard is likely 0202 BIOS and I have no
other compatible CPU to use to reflash the motherboard
to the newer version before using the G0.
I think ASUS MAY still have options enabled that
overclock / overvolt the CPU by default even on
"AUTO" configuration. So if you want to be safer,
I'd quickly hop into the BIOS, head straight to the
Health/Temperature screen, make sure your voltages
and temperatures are sane, head to the
"reset all settings to BIOS defaults" and execute that,
then go to the clock/voltage control stull and disable
automatic overclocking, change any timing/voltage
you NEED to for your RAMs, exit & save all that,
go into BIOS again, reflash to 0404 or newer,
and then go through the careful process of setting
up and checking things in more detail.
Let us know how it works. I'll post an update on this
attempt when I get my CPU installed in a few days.
EDIT:
Here's the thread where I saw it confirmed what some of the options and behavior to expect are:
http://forums.anandtech.com/messagev...keyword1=ucode
Quote:
Hello, I have a new machine I'm trying to put together.
Asus P5K Deluxe, Q6600 G0, patriot ddr2-800 4GB (2x2GB), evga 8800gts.
Had difficulty getting it to post, eventually did but got the message "Intel cpu uCode error."
I'm assuming a bios update would fix this but was unsure, checking with folks here.
Also, was not sure whether to use 4-pin or 8-pin power connector, mobo came with a cap on 4 of them, power supply supports both. Also, not sure where to put ram, yellow or black slots.
Thanks in advance.
...
Upgraded bios to version 404, no longer get that error, however the system will not post with both sticks of ram, will post with one but not the other stick. I think i have a faulty stick of ram. Anyone have any experience with Patriot RMAs? Do I have to send both back or can I keep the good one and send them the bad one?
...
relia85,
You're just the person I wanted to ask -- could you please explain
a little more about the problem you saw? I am worried that it will happen
to me also because I have a P5K and G0 stepping Q6600 CPU coming for it.
I'm pretty sure my current BIOS is older than 404 and I don't know what's
going to happen when I stick my G0 in there if it'll let me reflash to 404
safely at the right voltage/frequency/stability or not.
What BIOS version were you running BEFORE you reflashed to 404? You're sure
it was something earlier? Would that earlier BIOS let you use the G0 CPU at
all i.e. were you able to use the G0 to reflash TO 404 despite the error message
or other problems?
So where did you see that message, and what happened after you got it? Could
you just continue and ignore it, or would it stop dead or what? Was there a way
to get into the BIOS settings / BIOS based flash utility or whatever even with
the error?
Do you think the uCode error could have had anything to do with the possibly
bad RAM?
I don't know about your RAM problem, sorry, I've got two sticks of patriot here
that I'll be testing as soon as I get my CPU and put the system together.
Hopefully it'll work. I've never RMAed a Patriot stick before.
Maybe check the timings and go to manual override on all the voltages and timings
and put them at very very slow / conservative values to make sure it should work
if it's at all possible.
Some people say 0311 was a better BIOS, others seem to like 0404, others seem
to like 0501... so I guess there could be a BIOS problem that affects your ability
to have the MB be stable so maybe a different version would help. I wouldn't
load anything before 0404, though, if you think you'll go back to having a ucode error
or other CPU problems.
Originally posted by: relia85
Hello, I have a new machine I'm trying to put together.
Asus P5K Deluxe, Q6600 G0, patriot ddr2-800 4GB (2x2GB), evga 8800gts.
Had difficulty getting it to post, eventually did but got the message "Intel cpu uCode error."
I'm assuming a bios update would fix this but was unsure, checking with folks here.
Also, was not sure whether to use 4-pin or 8-pin power connector, mobo came with a cap on 4 of them, power supply supports both. Also, not sure where to put ram, yellow or black slots.
Thanks in advance.
...
The Asus P5K that I recieved had bios version 2.58 if I remember correctly, lets just say some 2.5x version. Using the G0 processor the system boots up just fine and posts, and you can get into the bios to make adjustments, and you can also flash the bios. I don't know if you can properly run the system and boot/install an OS because I didn't go that far but I doubt it. I downloaded bios version 404 to a USB flash drive and used the asus EZ flash utility (alt+F2 at the post screen) because I was way too lazy to break out a floppy drive. After that the error message disappears and I'm assuming you can load an OS just fine (haven't had time to do that yet). I'm just really angry right now that I have to RMA my ram because I have no spare ram to run the system on right now, so I have to wait. I highly doubt the ucode error was due to the ram and manually setting the ram timings and voltage had no effect. However, the mobo did not properly detect the 5-5-5-12 timings and instead posted 5-5-5-15 so I had to adjust that manually. I'm just relieved at least one stick of ram worked so I could confirm the cpu and mobo was fine (first lga 775 experience).
...
Hi, what bios settings are you guys using with quads and 4ghz + ?? I just got my SS and im having a hard time getting it stable. The cpu is @ -40 at all times, so thats not the issue
Can somebody pls tell me what would be a safe voltage for 24/7 run on a E6850 and P5K Deluxe ? It seems like it's super ok at 3600Mhz on 1.45V (everything else on Auto), but to be able to go over 3.7Ghz it requires 1.55V. I am now on SI128 cooler, AS5 thermal paste, and some 120 vents at 1500 RPM.
What is considered too much for air, even on SI128 ? 1.5V ? 1.6V ?
Thx in advance !
P.S. Somebody just told me that P5K Premium WiFi is much better for overclocking than my P5K Deluxe WiFi... Is this true ?
as long as you actual vcore is 1.55 or less you should be fine.
yes on your ps see here
http://www.xtremesystems.org/forums/...d.php?t=153598
Okay, can someone here tell me how long does it take ASUS to move from Beta to stable when it comes to their BIOS updates. Its been a month now and the 05xx BIOS is still in Beta. Is this normal? I haven't had an ASUS board since their AM2 CROSSHAIR 590 chipset, since then I have owned a DFI and EVGA and neither of them had such a long Beta stage for their BIOS's. Any idea?
my result with P5K Del and Q6600 B3 :)
max fsb
http://img413.imageshack.us/img413/5926/eeeevh3.th.jpg
max freq on air,i booted @4100 but not stable for high temp :cool:
http://img260.imageshack.us/img260/5723/cineqf7.th.jpg
The premium has more capacitors and no mofsets on the back of the board so it should offer more stability. You can also take the CPU PLL voltage upto 2.2v. Link to review http://forums.hardwarezone.com/showthread.php?t=1680376 That said I personally haven't noticed that much difference when I had a deluxe but as the review says it may be different when the BIOS matures. I didnt get to play with the deluxe too long as I had to RMA it when I deleted the EEPROM - I was in a hurry and used Asus update under vista x64 and it failed! I also had problems with CPU temp readings on the deluxe - the kept jumping about. Note that the temps you see with coretemp and speedfan are out by 15c by all accounts. Common sense tells you that your CPU cannot be running below ambient with air cooling!
You're quite welcome.
FYI to anyone who's going to use a Q6600 G0 with an
previously unused P5K deluxe:
a) I received a P5K DELUXE / WiFi board with factory
BIOS 0202 which is not advertised in ASUS' CPUSUPPORT
list as supporting Q6600 G0 revision.
b) I received a Q6600 G0 stepping.
c) I can CONFIRM that it is possible to use the
built in BIOS EZ-FLASH utility to flash FROM 0202 to
a newer BIOS (I flashed to 0501 beta) using the
Q6600 G0. I downloaded the new BIOS ZIP file,
unzipped it on another PC to get the .ROM image file
for the new BIOS, copied that on to a USB flash disk
which has FAT32 format on it, and hit ALT-F2 at the
BIOS POST screen to enter EZ-FLASH whereupon
my USB disk with the BIOS files showed up as 'C:\'
drive. I then used the keyboard to navigate to the new
BIOS filename in the list and initiated a reflash.
d) I can confirm you will see an error message about
"Error loading Intel CPU uCode" or similar from the
0202 BIOS due presumably to BIOS incompatibility
with the G0 Q6600 stepping, however it's quite possible
to ignore this error message, change anything you
may want / need to in BIOS setup using the old
BIOS version, then you can proceed to do your EZ-FLASH
update.
e) Having no spinning / connected CPU FAN is OK,
you'll get a diagnostic / error message, but it's nothing
that is impossible to proceed from. My TR120-U-X's
fans are plugged into a couple of the chassis fan
connectors. Oddly I only see the RPMs listed in the
BIOS hardware monitor screen for one
of the two, though they're both spinning, I'll have to
look into that later.
f) I can confirm the P5K Deluxe / WiFi AP board
with BIOS 0202 or 0501 does boot up and seem to
work with 8 GBY installed in the form of
4 DIMMS of 2GBY Super Talent DDR2-667 Micron D9HNL
memory.
g) I did have a problem at first when I used a really
old 15" LCD panel through a DVI->VGA dongle converter
attached to my 7800GT board. The monitor showed
no video and I'd get a beep error code from the
motherboard. I guess the scan rate wasn't compatible
between the graphics card and the monitor or something.
It's working now using DVI to my better LCD panel.
h) OOPS plug in the CPU 4-pin power connector
BEFORE putting the motherboard in the case.
i) OOPS you can't screw in a TR120-U-X when the
fans are attached to it.
j) OOPS you're far better off taking the
motherboard out of the case before even trying
to install a TR-120-U-X, and you'll possibly have
to remove case fans and whatever else may make it a
tight fit to get the M/B into the case easily.
(e.g. SONATA 1).
I'm getting started with memtest etc. and will report
back on any problems / tips / interesting results
over the days to come.
Q6600 G0 L723A841 pack date: 07/27/07
received from ClubIT.
ClubIT product ordered on 2007-07-30, received
2007-08-08.
I just checked the asus support page for a bios update for my gf's computer. The beta 1302 was from 2006/06/19, the 1303 final is from 2007/07/13. This is for the A8n-sli premium board by the way. It's an old one, but still.
Asus initially releases a lots of different bios, enhancing and optimizing performance. But when the mainstream settles for a good bios, even the beta won't go final. At least that's what I'm thinking. They have too many boards released recently..I guess they focus their resources where the money is...
Well 0501 beta bios for p5k deluxe sucks!
* It locks up during BIOS POST when you boot with various USB peripherals
attached e.g motherboard -> USB hub -> bunch of USB peripherals including
downstream hubs, keyboard, mouse, etc.
* It doesn't properly indicate memory it reserves and maps for
things like ACPI and peripherals is reserved so the OS can't use it,
so you get errors and ACPI failures and errors form LINUX saying
there is a BIOS bug that doesn't reserve the e840 region or
something to that effect.
* It obviously is screwing up ACPI because LINUX says the BIOS
isn't reporting power management capabilities for the Q6600 even
thouch ACPI, APM, SpeedStep, C1E, et.al. are all enabled in the BIOS.
etc etc.
How freaking hard is it to make a BIOS that works these days when you've
had what 20 years to practice getting it right over several dozens
of similar BIOS versions for similar chipsets?
Flash only beta's at your own risk, and give feedback...listing all your hardware could be nice and not just say on your rig it sucks doesn't help others ...
There can be issues on some combination of hardware, that's why they are beta's and some don't even make it into a final release, some are even withdrawn hours after release as they seem to bork some mobo's,....
And due to the abundance of hardware floating around it's kinda hard to release one bios that supports all...
Also the rule of thumb is : If it ain't broke don't fix it !!! so only flash if you really need it !!
It's at your own risk to flash and use a beta, some are good, some suck , some kill boards, some make your rig fly... only way to find out is to give them a try or let others do it for you... but you know you are taking a risk !!! If it ian't good flash back to the workign one... and share ya findings with the engineers.... and us....
no usb problems here I have two hubs, 2 mice, keyboard, usb drink cooler, SD/CF card reader, and an ipod. as for your ACPI troubles enable ACPI 2.0 in the power section of the bios. I get no such errors with several Linux install CDs. I don't have speedstep or C1e enabled. you might need to get a newer kernel and compile your kernel because it sounds to me like your running an old kernel.
QX6700 @ 3977 MHz @ P5K Deluxe
no 4.0 GHz so far !
http://img112.imageshack.us/img112/9805/1maib2.jpg
I'm going to ask this question again, could someone please respond: I'm currently using BIOS 311 with my Q6600 G0 processor, however according to asus's website, BIOS 311 isn't compatable with this stepping and I MUST use 404 or newer. I find 311 to be an xtremely good OCing BIOS and I really have no issues with this BIOS so I was trying to aviod flashing to any of those newer BIOSes. Everything seems great with this 311 BIOS, chip is recognized perfectly on POST, It OC's like a dream, etc..... So why does asus say I (we) need to run BIOS 404 or newer with the chip? Forgot to mention that I am using a P5K-DLX motherboard
Chessman... what vcore for that run? Thanks.
no idea why they insist on it... maybe at auto subtimings it provides general end users better performance due to tighter timings http://i4memory.com/showthread.php?t=4161 or not all G0 steppings are supported only some.. ??
Just use what works for you :)
K, I did some more research on Asus's website and for a fact, some G0 chips were coded into that BIOS, but just not the Q6600 (unless they forgot to mention it) Cause it seems to work great here!
http://aycu10.webshots.com/image/248...1949659_rs.jpg
Yes i did but my Q6600 ES was B3 not G0.
I'm no longer on Asus P5K Deluxe moved to Asus Blitz Formula/Extreme testing right now - threads coming later ;)
On Blitz Formula @8x450FSB 4:5
http://fileshosts.com/intel/Asus/Bli...3m11s766ms.png
http://fileshosts.com/intel/Asus/Bli..._validated.png
http://fileshosts.com/intel/Asus/Bli...m_15s734ms.png
http://fileshosts.com/intel/Asus/Bli...4m31s016ms.png
No problems with USB here either!
I'm using the 311 Bios on my P5K Dlx Q6600 G0, no issues here, works good for me, except for the mem dumps when the overclock isn't stable. Is that suppose to happen?
Yes, I understand that some people have it working in their setups, and
I've seen a couple of people indicating they've had similar problems
as I do with respect to USB devices locking up the BIOS boot phase.
ASUS seems to have no very attentively monitored way to submit
technical bug reports about their BIOS (general technical support = useless
as far as I can tell). Their web forums are (to me) beyond uselessly
screwed up -- 99.9% of the time I get an error page whenever I try to
access their 'product support' forum pages more than a hand full of times:
I didn't mean to imply these bugs were exclusicvelyQuote:
Due to vast number of connections online, the page that you requested cannot be displayed properly. Please re-connect using any of the following URL. Sorry for the inconvenience.
P5K Deluxe + WiFi 0501 Beta BIOS version problems, it's just that
this is all that I've personally experienced / used -- it would surprise me
if they weren't also present in all other preceding versions of their BIOS.
My motherboard came with 0202 BIOS and that didn't support the Q6600 G0
stepping according to the ASUS CPU SUPPORT table and according to
an error message in the BIOS, so I had to reflash to *something* and,
it being a new motherboard model, I picked the latest assuming it'd
probably be the "latest and greatest" and in some way(s) better than
the preceding versions it was meant to replace. I know sometimes there
are new and regression bugs that may make an older BIOS a better choice,
but lacking any information to the contrary, 0501 Beta is the only one I've
tried so far.
EDIT: UPDATE: I tested various USB configurations for about an hourQuote:
This is my current USB configuration, and it 'locks up' the BIOS POST
process 100% of the time whenever the switched USB chain is plugged in
while the BIOS POST is in control. I've never waited for more than a couple
of minutes to see if it'd eventually do something different, but to givel all
keyboard stimuli and available visual cues it seemed to just be locked up.
Motherboard USB Port A
-> SanDisk Corp. SDCZ2 Cruzer Mini Flash Drive (thin)
Motherboard USB Port B
*********** -> USB switch
****************** -> Keyspan USB 1.1 5-port HUB A -- AC powered and AC power connected.
********************* -> Link to Keyspan USB 1.1 5-port HUB B -- Physically Disconnected
********************* -> Microsoft Corp. Internet Keyboard Pro with built in 2 port USB hub (empty).
********************* -> Creative Technology, Ltd Fatality 1010 mouse
********************* -> DELL 2405 LCD Monitor with built in USB 1.x hub, and memory card reader.
*************************** -> Microsoft Corp. Wireless Intellimouse Explorer 2.0
*************************** -> Canon PIXMA IP 2000 printer
So that's one external hub branching out in "Y" parallel to two more
connected USB hubs. My 'full' configuration (involving the hub
I indicated as disconnected) would involve several other devices
and chained hubs, though it doesn't even take that to lock up the BIOS,
it crashes 100% with even the simple stripped down configuration.
I can hardly remove the built in hub/card reader in the keyboard and
the monitor, and of course I need the keyboard + monitor to boot, so,
other than having an extra mouse attached I'm pretty much down
to a very common sort of minimal setup already:
USB keyboard + 2 USB mice + card reader + printer + few incidental hubs.
and determined that the ASUS 0501 BETA BIOS locks up when
there's a mouse plugged in to one of the hub ports on the
DELL LCD 2405FPW's built in hub. When I remove a mouse from the DELL
hub port, the ASUS BIOS boots and stays functionally responsive. When
I attach peripherals OTHER THAN a mouse to the DELL LCD USB HUB
ports, everything works with no trouble from the ASUS BIOS -- I've attached
a Sandisk Cruzer USB Flash Drive, and a BELKIN USB Wireless NIC to the
DELL LCD USB HUB and those peripherals being attached there do not impair
the ASUS BIOS function.
I tested with three mice:
1) the Microsoft Wireless Intellimouse Explorer 2.0,
2) MEMOREX MX4210 optical wheel mouse.
3) Microsoft Basic Optical Mouse
and all three cause lock-ups of the ASUS BIOS when they're attached to
either of the two DELL USB ports.
When I attach them instead to OTHER USB HUB ports NOT connected
through the DELL LCD they work and do not interfere with the ASUS BIOS boot.
When I plug in one of these mice through the DELL LCD USB HUB AFTER
I'm ALREADY in the ASUS BIOS SETUP screen, I can navigate to the USB
screen in the BIOS setup and see that it indeed detected and is counting
the mouse in its peripheral list, so it is capable of functioning through
the DELL monitor USB HUB and with the ASUS BIOS, but the bug happens
during BIOS POS specifically.
When I plug in the USB stuff to the motherboard AFTER BIOS POST
is finished, the mice and anything else will work fine in LINUX even
through the DELL LCD USB HUB.
EDIT: UPDATE: Confirmed.Quote:
This is very probably the exact error message I get from LINUX about
the BIOS BUG about memory reservation it happens before logging
is enabled so I have only a visual record of it but it's quite
familiar and now that I've had a chance to search for the exact text
I recognize it. I've seen similar issues with
other known buggy BIOSes in the past (e.g. VIA EPIA M), as have the
kernel authors which is undoubtedly why they put that specific check and
bug error message in the code.
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
Here are the actual captured LINIX KERNEL BIOS bug related
error messages; it looks like there's one bug with the BIOS
making a bad ACPI data table checksum, another bug with the
BIOS not indicating its reserving of a certain memory block,
and another which relates to CPU power management's
absence [which might be actually due to either the bad checksum or
the non-reserved memory table].
EDIT: UPDATE: I got a chance to spend a few hoursQuote:
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMCONFIG.
PCI: Using configuration type 1
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
...
pnp: 00:0a: iomem range 0xfee00000-0xfee00fff could not be reserved
...
pnp: 00:0d: iomem range 0x0-0x9ffff could not be reserved
...
pnp: 00:0d: iomem range 0xe0000-0xfffff could not be reserved
pnp: 00:0d: iomem range 0x100000-0xcfffffff could not be reserved
...
ACPI Warning (tbutils-0158): Incorrect checksum in table [OEMB] - 7C, should be
7B [20070126]
ACPI: SSDT CFF8E0D0, 0190 (r1 AMI CPU1PM 1 INTL 20060113)
ACPI: SSDT CFF8E260, 0143 (r1 AMI CPU2PM 1 INTL 20060113)
ACPI: SSDT CFF8E3B0, 0143 (r1 AMI CPU3PM 1 INTL 20060113)
ACPI: SSDT CFF8E500, 0143 (r1 AMI CPU4PM 1 INTL 20060113)
hpet_resources: 0xfed00000 is busy
...
acpi-cpufreq: No P-States
cpufreq-core: initialization failed
researching how EIST works, reboot and go through the BIOS options
that might affect the CPU Power Management. It turns out that when
you set the CPU Multiplier in the BIOS setup away from AUTO to a given
number (e.g. X9) that causes the BIOS to delete the P-states in the ACPI
table corresponding to speed steps slower than the given speed.
That was unexpected (to me) since I'd assumed the BIOS would use
the manually set multiplier as the "normal" / "base" value (e.g. x9), but
still enable LOWER multipliers to be defined and used by the power
management (EIST/C1E/TM2) functions. Evidentally not.
The EIST/C1E/TM2 capabilities do work by changing the CPU
multiplier, so it's not unexpected that locking the CPU multiplier would
prevent the multiplier from changing in response to EIST/C1E; the only
unexpected part was the bit about it being a user set multiplier "lock"
that disabled the use of lower multipliers vs. it being just a specification
of the "desired maximum" multiplier. It doesn't necessarily make sense
in the BIOS for it to LET you change the CPU multiplier from AUTO
*and* have other distinctly usable options to enable/disable C1E etc.
but anyway now I understand what happened and have it working.
Anyway now that I changed the CPU multiplier to "AUTO" LINUX
is permitting two steps of power management for me:
* acpi-cpufreq: *P0: 2394 MHz, 88000 mW, 10 uS [1.15Vcore for my CPU]
* acpi-cpufreq: P1: 1596 MHz, 59048 mW, 10 uS [1.06Vcore for my CPU]
Where the P0 state = 266x9 and the P1 state is 266x6.
Presumably P1 would also be the speed and power/voltage that
is also used for TM2 and C1E, though I haven't tested that.
I'm still a little surprised that there aren't MORE EIST steps appearing
e.g. corresponding to each of the Q6600's possible CPU multipliers
of x9, x8, x7, x6, but I haven't seen any indication that that's actually
done in other peoples' BIOSes for the Q6600 so maybe that's "normal"
to just have the two speed steps (full and minumum frequency via
the CPU multiplier setting).
So now I'm getting happier since I have found a work-around for the
USB lock up bug, and also the EIST/C1E power management usage.
Unfortunately now it seems like I can't use the EIST power management
directly when I overclock the FSB a lot since it seems that it is not designed
to permit reducing the FSB AND the CPU multiplier AND the CPU voltage
when lower performance is acceptable, it only changes the CPU multiplier
and CPU Vcore. So maybe there is some utility I can find to change
FSB dynamically under LINUX/UNIX.
...
I think they must not make their BIOS authors actually test their releases
or use the products they apply to in 'real world' circumstances since
otherwise a lot of this stuff would NEVER make it to even a BETA
release (e.g. lockups due to USB, memory reservation errors,
broken ACPI, massively wrong indicated voltages / termperatures for several
other models I've read about etc. etc.).
Ah well I just wish there was an effective way to get more directly the
ear of the BIOS developers so we could get some of the long-absent
fixes and most desired features added in response to our feedback.
As it is it seems like we just wait and hope and maybe unplug our USB
hubs when we reboot.
DONE! See above.Quote:
I'll do more USB bug testing to see if I can narrow down the cause(s) of the
problem to certain peripherals or configurations further. I've been busy
programming and doing system burn-in to reboot / test much so far.
UPDATE EDIT: Looks like the BIOS 0501BETA in the HARDWARE screenQuote:
EDIT:
Oh, yeah, and neither the BIOS hardware monitor nor LINUX' sensors control
panel seems to be detecting the RPM of one of my two CPU fans. One is
showing up at the expected 1622 RPM on "FAN5" but "AUX FAN",
"CPU FAN", "CASE FAN" are all listed at 0 RPM and I think there may be
one or two fan connectors that actually exist on the motherboard that aren't
even mentioned in the BIOS health monitoring list or other programs I've seen.
I've got to track down what fan port the other fan is plugged into. I know
it is spinning since I've seen to that, but the absent or incorrect monitoring of
that fan port seems like a potential other BIOS bug to me so far.
monitors:
CPU FAN SPEED
CHASSIS FAN SPEED 1
CHASSIS FAN SPEED 2
CHASSIS FAN SPEED 3
...so it DOES NOT include either
CHASSIS FAN SPEED 4
or POWER FAN SPEED as it should do so since those are
available fan connectors on the motherboard.
UPDATE: EDIT: It looks like that might have been a problem withQuote:
EDIT2:
Oh yeah another BIOS problem I noticed. If I went right into the BIOS
setup by hitting DEL or whatever then I could select EZ flash from the
BIOS tools option there in the BIOS setup screens. However
at that place it did not recognize / show any files from my SanDisk USB
flash disk which had the new BIOS file on it.
However if I did NOT enter BIOS SETUP and used the ALT-F2 or whatever
sequence to go from the BIOS POST TEST screen to the EZ-FLASH, THEN
it would list the files from my USB flash disk. I think they must not actually
initialize the USB ports including your USB flash disks until a later time
in the BIOS boot process so if you try to go to BIOS SETUP or EZ FLASH
before such time as it has registered your USB disks, you cannot seemingly
use EZ flash from them.
BIOS 0202 more so than 0501 BETA.
Now with 0501 BETA BIOS if you enable LEGACY DEVICE SUPPORT
in the BIOS SETUP, you can see your USB flash disk files from either way
of entering EZ flash at least when I've recently tested it using my USB
keyboard as the means of getting into the BIOS setup (whereas in the
past I had used a PS/2 keyboard, but hopefully that's irrelevant).
Surprisingly, however, If I DO NOT enable LEGACY DEVICE SUPPORT
in the BIOS SETUP, it would not 'see' my USB SANDISK CRUZER flash disks
in EZ FLASH at all. In this case if you go to EZ FLASH you get the
nice error message:
"There Are No Any Existing Drives!"
I'm not sure how a modern USB flash disk is a 'legacy'
device whereas a mouse and keyboard isn't but whatever.
So FWIW in case it's helpful to anyone, that's what I now know about
BIOS 0501 BETA.
I've never seen than since I have yet to get to the point of OCing mine.
But I wouldn't be surprised if it was an understandable outcome of a crash
due to system instability.
It's pretty common to get 'blue screen' memory dumps or other dumps from
other situations whenever there's a serious instability.
I have no idea WHY Intel and ASUS say you must have a new BIOS for
Q6600 G0, but that is the official documentation from both sources.
In practice I know I was able to boot with P5K DELUXE BIOS 0202 with the
Q6600 G0 and go into BIOS setup and when it was booting use the reflash option
to upgrade the BIOS etc. So it can't be completely broken even with the old
BIOS versions.
However with BIOS 0202 I did get a message similar to
"Error loading ucode on Intel CPU" or somewhat similar phrasing. That error
message didn't seem to totally prevent the use of the PC, though.
The error message did go away when I flashed to the newer BIOS, though.
I don't know if there are (yet) any microcode updates for CPU stepping G0
that a newer BIOS could apply for better system stability. I know that
the older Q6600 steppings (B3 and previous) have ucode updates that
the BIOS or maybe also the OS could apply to help work-around
CPU bugs that could crash your system under certain circumstances.
Otherwise, "if it works for you, don't fix it".
any help?! my e6850 seems to have fsb wall @ 475 :down: i tryed with e6700 and fsb goed well over 500, maybe ther is some settings that wont let me past of 475 with e6850.
using asus p5k deluxe and adata ddr1066 memories.
Edit: it is a strap / divider problem... i need advice and sub timmings for p35
i have been having a problem with opening control panel in vista when my rig is over clocked :shakes:
P5K, e6750@3600
When i try to open it it just flashes up and then goes in a second, i know others have had this prob but unless i missed somethng no one has found the answer, well if you type (control ncpa.cpl users) into CMD it will open up netwok connections in control panel and you can then select anything in contorl panel you like, not ideal but the best work around i have found.
hope this help someone as this has been @*#xing me right off :)
Usually that means its unstable. Try giving it a little move volts or lowering your clocks a little. Sometimes that extra 50mhz will give u the biggest headaches.
Is that with Vista 32 or 64?
I had raise the core voltage to 1.525v and cpu pll to 1.7v before I could get 4 hours of of stability with my e6750@3600. I'm not sure this would be stable for say 24 hours. I'd bet your system isn't stable.
http://www.xtremesystems.org/forums/...16&postcount=4
Does Asus update this board anymore? lol
you expecting a bios update each month ? or after each user has an issue ...
I have not had a lot of time to do stability testing since i have put my 6750 in but it has passed 8hrs+ of orthos (450fsb x 8 @1.5v) this cpu will do 497fsb, but i am new to ocing so will try and drop back to 3500 to see if this helps
This is in vista 32
does anyone have a temperature difference between cores (Q6600)?
i'm getting 4 to 7C diff. from cores 0&1 against 2&3 cores.
core0-29
core1-28
core2-23
core3-24
are these normal? i'm reading them from speedfan 4.32
thanks for any reply
Yea I have temp differences on both cores on my E6420 too
Just looking for a bios that might eek out a little bit more performance, however I am only waiting on X38 and see how it does with quad, if thats a no go its P5K premium or blitz for me :)
I hear the premium board is the best overclocker even compared to the blitz but what does it give over the deluxe ?
Better cooling, due to better components around socket area and no more mosfets @ the back, which results in a even better stability ( for Quads) then a Deluxe would do, and some folks got some SATA RAID probs with this board, maybe they fixed in the Premium( I dunno for that part tho). its more like ( well it seems sofar) that Asus had put the Deluxe a side, and instead working on a new BIOS with improvements ( yes still waiting), they made a "bugfixed Deluxe" voila:
Asus P5K Premium..
Any issues with P5K Deluxe 0404 and eSATA? Picked up a eSATA enclosure today, plugged it in, it showed up fine on the first boot, after vista took a look at things, it wanted me to reboot to get things going, so I did, and after that the drive wouldn't show up at boot. The jmicron controller would sit there looking for a drive, but wouldn't see it. Tried powercycling the enclosure. It may just be a POS enclosure, I'll take it back to Frys and maybe pay more the next time, heh, but was just looking to see if there were any eSATA issues out there. Didn't find anything when I searched.
I can't even get the jmicron controller to see my Esata drive.
Same here. Though I KNOW my TRU120X is loose,
so I'm sure my temperatures could be better.
Right now :
Idle @ 1.06V / 1.60 GHz:
Core 0 34
Core 1 34
Core 2 28
Core 3 32
And the ~ 7C to ~ 8C difference maintains even
at higher loads and frequencies.
Oddly there's usually a several (4-5) degree temperature difference even between Core2 and Core 3 which
should be on the same die. I wonder if my heat sink
grease isn't spread well over that die or what.
I think the esata issue is with the system. In this OS, with the drive plugged into an internal connection, it was xfering around 40MB/s. I went and got an esata to sata cable and connected that to the drive, using just the enclosure for power. Enabled the esata controller, it saw the drive on boot. Vista told me to restart again to use it, restarted, drive still shows up, so I thought maybe it was the enclosure. But when I tried to transfer a 1.6GB file off the drive, it would only do it at 1-3MB/s, sheesh.
something like this is a good idea to try & even out the core temps on wc rgs.. Thermalright LGA775 Bolt-Thru-Kit reduces mobo warping across cpu area so that at least all cores are level & flush with heatsink.
Have seen many get more even temps by tweaking the tightness of their nuts:lol:
i dont really think it has something to do with the tighness or the thermal grease(though it should improve cooling)i had those readings with my stock hsf and still have them temp difference with the lapped tuniq.Quote:
something like this is a good idea to try & even out the core temps on wc rgs.. Thermalright LGA775 Bolt-Thru-Kit reduces mobo warping across cpu area so that at least all cores are level & flush with heatsink.
Have seen many get more even temps by tweaking the tightness of their nuts