Speedstep is working for me, drops down to 1600MHz at idle. Also my CPU fan speed is ramping up and down with temperature. I'm on the 1003 bios at the moment, on a non-pro board. I'm running my RAM at stock (1333MHz) though, perhaps that makes a difference.
ASUS P8P67 PRO owners - what BIOS version did yours come with
- Thread starter coneypark
- Start date
Speedstep is working for me, drops down to 1600MHz at idle. Also my CPU fan speed is ramping up and down with temperature. I'm on the 1003 bios at the moment, on a non-pro board. I'm running my RAM at stock (1333MHz) though, perhaps that makes a difference.
Associate
Speedstep is working for me too under stock settings. It's when you o/c that it sometimes goes wild. Having said that, I think rev. 1053 was to blame. I'll see how overcloking goes on rev. 1003.
I'm on a Pro board and cpu fan speed stuck on max, both power and cpu fans.
Any good utility for software control of fans? FanSpeed doesn't work on P67.
I don't think these issues will be unique to Asus boards. I think most people who managed to purchase early went for an Asus board. I think you will see similar posts for the other makes showing up next week.
You never know, Gigabyte sticking to the traditional BIOS may have been a smart move.
I'm sure a future BIOS update will solve any issues.
Associate
Well I've never had a bad Asus board in 18 years of pc building. Had plenty of duff Gigabyte ones & 1 MSI. Abit ones have been very good too. Just my experience. As has been mentioned, it's the price to pay for the technology echelon.
mee tooo
Associate
Thought I'd chime in on this with my experience with the P8P67 PRO.
To start with my part are:
Intel Core i5-2500K 3.30GHz (Sandybridge) Socket LGA1155 Processor (with stock fan)
Patriot Viper Xtreme 8GB (2x4GB) PC3-16000C9 2000MHz Dual Channel Kit
Asus P8P67 PRO Intel P67 (Socket 1155) DDR3 Motherboard
The rest is from my old system. So there’s the antec 300 case, Corsair 620 PSU, a velociraptor 300GB and a simple 750gig samsung drive. And am using window 7 64bit.
Set it all up all fine on friday night with all stock setting (BIOS 0402 and optimal setting in BIOS). Installed windows and started installing drivers. I had all my drives via the Marvell sata controller, started to copy over the BB:BC2 patch (you know the 2.5gig one) and it just BSOD on me… rebooted, tired again to copy it and it BOSD again. So I move all the drives to the Intel Chip sata ones and tried again, worked fine. So has anyone had Marvell sata controller problems, or it just me?
Next up I tried some overclocking with BOIS 0402 and 1053. I am not the most techy person when it comes to overclocking, but I’ll have go!
First up my RAM. Set the XMP profile for the RAM and it just did a red DRAM LED and never booted. I know XMP profiles aren’t the best, but wanted to see if there was an easy way to overclock the lot. i.e. load XMP profile and use OC tuner and TPU, done!…. It’s not that simple now I’ve tried!
Just to be lazy I did first try the OC Tuner in the BOIS, that worked fine. But at a poor 3.6ghz, not worth it really after all the reviews saying 4.5ghz!!! Ran prime95 and about 15min it froze and crashed. Rebooted and set optimal setting in BOIS.
Now for manual overclock following bit-tech.net, but leaving all CPU voltages and stuff to auto. I set it to 40 so 4.0ghz. Rebooted all fine and run prime95 for an hour… all fine but temps where 50 idle and 71 load… so I think that’s too much heat there. This is with stock cooler. Rebooted and set optimal setting in BOIS.
I tried my RAM again and this time manually. Worked ok, all booted fine and got to windows… for about 10min then froze! Set ram back to auto and all is fine. I’ve ran memtest and its passed so can’t see it being the RAM.
So for now I’ll leave it all on optimal setting in BOIS and not change a thing till I get a new cooler (might get a H50) and try again. Since idle at 50 is toasty… or once there a new BOIS after the beta 1053. To me it’s the first lot with new chips and BOIS, so if it works all on stock and not overclocked, then leave it till some bugs are sorted out then in 2/4 months time update everything and try again. Anything is better than my old E6600!
One question to you guys with this board what’s your boot up like from cold? I press the power button and it starts some mobo checks (VGA LED, DRAM LED, BOOT Device LED), then it powers down, then 1sec later it boots up…. Is this right?
To start with my part are:
Intel Core i5-2500K 3.30GHz (Sandybridge) Socket LGA1155 Processor (with stock fan)
Patriot Viper Xtreme 8GB (2x4GB) PC3-16000C9 2000MHz Dual Channel Kit
Asus P8P67 PRO Intel P67 (Socket 1155) DDR3 Motherboard
The rest is from my old system. So there’s the antec 300 case, Corsair 620 PSU, a velociraptor 300GB and a simple 750gig samsung drive. And am using window 7 64bit.
Set it all up all fine on friday night with all stock setting (BIOS 0402 and optimal setting in BIOS). Installed windows and started installing drivers. I had all my drives via the Marvell sata controller, started to copy over the BB:BC2 patch (you know the 2.5gig one) and it just BSOD on me… rebooted, tired again to copy it and it BOSD again. So I move all the drives to the Intel Chip sata ones and tried again, worked fine. So has anyone had Marvell sata controller problems, or it just me?
Next up I tried some overclocking with BOIS 0402 and 1053. I am not the most techy person when it comes to overclocking, but I’ll have go!
First up my RAM. Set the XMP profile for the RAM and it just did a red DRAM LED and never booted. I know XMP profiles aren’t the best, but wanted to see if there was an easy way to overclock the lot. i.e. load XMP profile and use OC tuner and TPU, done!…. It’s not that simple now I’ve tried!
Just to be lazy I did first try the OC Tuner in the BOIS, that worked fine. But at a poor 3.6ghz, not worth it really after all the reviews saying 4.5ghz!!! Ran prime95 and about 15min it froze and crashed. Rebooted and set optimal setting in BOIS.
Now for manual overclock following bit-tech.net, but leaving all CPU voltages and stuff to auto. I set it to 40 so 4.0ghz. Rebooted all fine and run prime95 for an hour… all fine but temps where 50 idle and 71 load… so I think that’s too much heat there. This is with stock cooler. Rebooted and set optimal setting in BOIS.
I tried my RAM again and this time manually. Worked ok, all booted fine and got to windows… for about 10min then froze! Set ram back to auto and all is fine. I’ve ran memtest and its passed so can’t see it being the RAM.
So for now I’ll leave it all on optimal setting in BOIS and not change a thing till I get a new cooler (might get a H50) and try again. Since idle at 50 is toasty… or once there a new BOIS after the beta 1053. To me it’s the first lot with new chips and BOIS, so if it works all on stock and not overclocked, then leave it till some bugs are sorted out then in 2/4 months time update everything and try again. Anything is better than my old E6600!
One question to you guys with this board what’s your boot up like from cold? I press the power button and it starts some mobo checks (VGA LED, DRAM LED, BOOT Device LED), then it powers down, then 1sec later it boots up…. Is this right?
Associate
Copey, sounds like we are barking up the same tree.
Interestingly, the old HDD RAID 0 lock ups I mentioned happened whilst patching BFBC2. Ended up downloading stand alone client to patch.
Mine is currently running Sandra 2011 burn in, will see how it coped when I get home later. Stock it's been fine with rev. 1003.
I managed 4.6GHz part stable while I had the other issues so once we get a more solid BIOS we may do better.
Yes my booting is the same, brief self test then power down & power up fully. Post is quite slow on this board. Once cleared W7 x64 loads in 8 secs or so
Edit: by the way i've got SS RAID 0 & the optical drive on the Intel controller. I also had the HDD RAID 0 on that too before I unplugged it.
Interestingly, the old HDD RAID 0 lock ups I mentioned happened whilst patching BFBC2. Ended up downloading stand alone client to patch.
Mine is currently running Sandra 2011 burn in, will see how it coped when I get home later. Stock it's been fine with rev. 1003.
I managed 4.6GHz part stable while I had the other issues so once we get a more solid BIOS we may do better.
Yes my booting is the same, brief self test then power down & power up fully. Post is quite slow on this board. Once cleared W7 x64 loads in 8 secs or so
Edit: by the way i've got SS RAID 0 & the optical drive on the Intel controller. I also had the HDD RAID 0 on that too before I unplugged it.
Last edited:
Sorry if this is offtopic but I have this board coming to me for Tuesday, and what I'm wondering is after reading a few topics about the board and the problems people are having if it would be wise to change my order and get the http://overclockers.co.uk/showproduct.php?prodid=MB-154-MS MSI P67A-GD65 Intel P67 instead? Or is this just a temporary BIOS problem that will be fixed soon?
Last edited:
Soldato
My personal thoughts here are indeed that this is just a temporary problem, which Asus will quickly resolve, although it will almost certainly take a few BIOS updates to sort out completely.
Asus didn't get where they are by not looking after their customers, and my first Sandy Bridge board will still definately be an Asus... a micro ATX one though, although I am now seriously considering waiting for a few weeks to give time for some more BIOS updates to filter through... and hopefully for prices to drop a bit also!
Asus didn't get where they are by not looking after their customers, and my first Sandy Bridge board will still definately be an Asus... a micro ATX one though, although I am now seriously considering waiting for a few weeks to give time for some more BIOS updates to filter through... and hopefully for prices to drop a bit also!
Associate
Ok, I've had a chance to do more tinkering. I'm playing with overcloking after establishing that for me rev. 1003 seems ok and stable at stock settings, though testing is on going.
I've put that on the back hob for a wee while, whilst I tinker with some overclocking after being relatively happy with having root causes for the hang ups.
So here is my quick effort, 4.8GHz. I'm not going for any records, just wanted to see how it went and also try to put people's mind at ease with regards to this Asus board.
Uploaded with ImageShack.us
I've run a series of benches for around 30mins and seems stable. Just going to jump online into BFBC2 to see how it runs there.
Lots more tinkering required, but I think it will turn out to be a good board once the BIOS gets polished.
I've put that on the back hob for a wee while, whilst I tinker with some overclocking after being relatively happy with having root causes for the hang ups.
So here is my quick effort, 4.8GHz. I'm not going for any records, just wanted to see how it went and also try to put people's mind at ease with regards to this Asus board.
Uploaded with ImageShack.us
I've run a series of benches for around 30mins and seems stable. Just going to jump online into BFBC2 to see how it runs there.
Lots more tinkering required, but I think it will turn out to be a good board once the BIOS gets polished.
Associate
Quick update, been playing Crysis for 30mins at 4.8GHz.
Running solid at 55fps, GPUs and RAM stock. Max CPU temps recorded were 55deg C.
There's no real point in running at this speed day in day out I don't think. I'm at 1.34v which is not silly but we're yet to see what the long term implications are for Sandy. First impression of peeps is that they are somewhat more delicate.
Running solid at 55fps, GPUs and RAM stock. Max CPU temps recorded were 55deg C.
There's no real point in running at this speed day in day out I don't think. I'm at 1.34v which is not silly but we're yet to see what the long term implications are for Sandy. First impression of peeps is that they are somewhat more delicate.
Last edited:
Associate
It appears from what a few of us here have found that under stock settings things are ok, once you get your RAM at the right speed and voltage. If you choose a kit which is on their QVL you should be ok.
I have the ongoing issue of CPU and PWR fans stuck at max speed, they don't cycle with temp.
Overall things are a little touch and go due to BIOS. My personal experience is that rev. 1003 is the best at the mo.
Loko, just wanted to check if your are having any problems with cold boot? If I switch my machine off it never comes back on first time when switched back on.
What I see is the system comes on, then switches off. Comes back on but just sits there. Monitor goes into Power Save and fans spin but it never posts. No matter how long I leave it, it never posts.
I have to hold down the power button until it powers off as reset doesn't work. Then switch it back on. At this point it does post but get a screen saying your over clock failed and to press F1 to enter set up.
Once I've done that I can finally boot up.
I've tried both BIOS updates and neither make any difference to this.
Just to say, I only tries the auto over clock once which caused a blue screen so when this message says failed overclock I wasn't actually trying to over clock anything.
Only changes I made was to select correct options and voltage for my RAM.
coney, can I ask what speed and voltage your memory was running at to start with?
According to Corsair, the SPD on the memory should default it to 1333Mhz at 1.5v, if you want the full 1600Mhz then you have to set it to 1.65v manually.
Are you saying that it initially set it to 1333Mhz at 1.5v yet this was unstable?
You might want to have a look at this thread btw: http://forums.overclockers.co.uk/showthread.php?t=18227516
According to Corsair, the SPD on the memory should default it to 1333Mhz at 1.5v, if you want the full 1600Mhz then you have to set it to 1.65v manually.
Are you saying that it initially set it to 1333Mhz at 1.5v yet this was unstable?
You might want to have a look at this thread btw: http://forums.overclockers.co.uk/showthread.php?t=18227516
Associate
The issue you have I believe is related with the board not believing it has been shut down in a controlled manner. I don't have this cold boot problem, but I have had the ocerclocking failed message under all stock settings after system crash. The board thinks you're overclocking because you're running higher RAM voltage & non auto RAM speed, so technically it's right.
The issue is to do with the standard RAM not being recognised right. I believe yours is actually in the QVL list though!
The issue is to do with the standard RAM not being recognised right. I believe yours is actually in the QVL list though!
Last edited:
Hi,
Your right. The memory is detected as 1333Mhz at 1.5v - at this setting the system boots ok.
If you select the XML profile it is detected as 1600Mhz at 1.65v and the voltage is automatically set at 1.65v - at these settings I encounter the cold boot problem described above.
I have currently left the RAM at 1333Mhz at 1.5v.
My other problem is that I am randomly experiencing what I can only describe as freezing.
I have experienced this with the memory set at 1600 and 1333 and on all versions of BIOS available.
I don't know if this is down to the motherboard or some other component.
I've experienced this freezing in WOW and in Windows. Basically, the screen either freezes or a particular process freezes, hard drive stays on and any sound continues as normal.
Sometimes, if you leave it, it will unfreeze and work as normal. Other times I need to restart the system. It never results in a blue screen.
I think I can rule out the graphics card and PSU as these worked fine in my previous build. I don't think it's the hard drive as WOW and Windows are installed on the SSD. So that only leaves:- Motherboard, Memory, SSD or Processor.
I had a look at the other thread you linked to, interesting stuff from Gibbo. Begs the question why Asus have my memory on the approved list in the manual at 1.65v and why they overclock the BCLK as well!
Yip, my memory is on the QVL list in the manual and problem occurs when trying to run it at XML profile with everything else at default settings.
To be honest, it's the random freezing i described above that is my main issue. Just happened why typing this!
Think I'm going to flash back to the beta 1053 bios as I don't think I got these freezes as much on that one.