I should have waited on Sandy Bridge

[devilchrist]

All I can say now reading forums just about eveyrwhere, new sandy bridge boards are full of bugs and gremlins.

My own Gigabyte p67a-ud4 is full of problems as well

can't come out of sleep,
falls back to backup bio on reboot if OC'ed (unless it's drained completely of power) every time
rejects bios update, (says bios is corrupt and reflash with backup one)
In-bios flashing utility can't detect any drives.

Wow..

Asus seems to have it fair share of problems.

all I can say now.. if you're on the bridge about upgrading.. WAIT.. for all the bugs to be worked out.

 

[OCGuy]

I would blame the mobo, not the CPU.

Edit thread title to say "I should have bought a different mobo."

 

[Rifter]

This is why i ALWAYS wait till the second/third stepping CPU's to hit the market before i jump on a new platform.

It gives the mobo manufactorers time to work the bugs out of the new chipsets which there always are. I plan to go to LGA 2011 but not till mid to late next year which should be at least 6 months after release date.

Also title is good, these issues are not limited to his specific mobo, the forums are filled with SB issues right now with Asus, Gigabyte and MSI boards. The only ones i have seen with few issues are the Intel boards, which is what i would go with if i was buying at release.

 

[Diogenes2]

People with problems are the most vocal for whatever reason..
I suspect that satisfied users outnumber the ones with problems by a hefty margin ..

Other than a bit of a learning curve with the new BIOS, I have had no problems with my 2600K/Asus P8P67 Pro ( 1053 BIOS ) .. I am currently testing for stability at 4.7g .

I tested at 4.9 for over an hour, but I will be looking to refine my cooling a bit before considering keeping it there 24/7 .. It does get a bit warm.

 

[CraigRT]

Maybe go with Asrock since they seem to be the best early 1155 boards.
I am considering an Extreme4 myself.

 

[Numenorean]

Sounds fun. I upgraded about a month ago, but I went with an i7-870 and a P7P55D-E Pro. Of course, SB wasn't out and I didn't care to wait as there wasn't a large enough difference to bother.

Happy with what I got.

Once 6 or 8 core CPU's are decently priced I will probably upgrade again.

 

[Edrick]

There are always issues with new platforms. Yes it takes a month or two to work out the bugs, but they are generally not too major. I have some small issues with my Gigabyte board as well. Most have already been fixed and just waiting for 1 more which is being worked on. Small price to pay for being an early adopter.

Generally there is nothing wrong with the hardware. Software usually has the bugs (including BIOS).

 

[Linflas]

People with problems are the most vocal for whatever reason..
I suspect that satisfied users outnumber the ones with problems by a hefty margin ..

Other than a bit of a learning curve with the new BIOS, I have had no problems with my 2600K/Asus P8P67 Pro ( 1053 BIOS ) .. I am currently testing for stability at 4.6g .

I tested at 4.9 for over an hour, but I will be looking to refine my cooling a bit before considering keeping it there 24/7 .. It does get a bit warm.

Actually my upgrade from a P5K to the P8P67-Pro is one of the easier updates I have done. The Windows 7 transfer app is amazing, and really the only issue I have encountered with the MB is the cold boot 2X thing. I am using the 1003 BIOS and not overclocking, don't install all the extra ASUS software. So far the machine has been rock solid and working great.

 

[ader098]

l also have a p67a-ud4 and the bios is a mess, no wonder Gigabyte didn't have an EFI bios ready they cant even get an old school bios working properly
Anyway, the issues you mentioned sound familiar and there is a few things you could try.


can't come out of sleep
Sleep is still broken even with latest bios F7f, it reduces my cpu's vcore after waking and needs a reboot to return to previous vcore setting, so I have sleep disabled until a future bios fixes it.

falls back to backup bio on reboot if OC'ed (unless it's drained completely of power) every time
Sometimes the vcore adjustment in the bios will not stick even after saving to Cmos, so before you raise you cpu multiplier for an OC raise the vcore first, save to Cmos, re-enter bios and check to see if vcore setting was saved and then raise the cpu multiplier.

rejects bios update, (says bios is corrupt and reflash with backup one)
In-bios flashing utility can't detect any drives.
Are you using the latest @ BIOS flash utility from the Gigabyte's website because the version included on the cd doesnt work properly from what I understand.

 

[Ausm]

I wouldn't blame the CPU LOL it is definitely a Mobo problem.

 

[beyoku]

falls back to backup bio on reboot if OC'ed (unless it's drained completely of power) every time
Sometimes the vcore adjustment in the bios will not stick even after saving to Cmos, so before you raise you cpu multiplier for an OC raise the vcore first, save to Cmos, re-enter bios and check to see if vcore setting was saved and then raise the cpu multiplier.

I have this issue that why i think i am stuck at a "low" O.C. - 4.1 stable. At 4.5 what is a safe voltage? I hear many things but what are you running at? I have a Noctua D14 and the temps have been excellent 22c idle / 46-49c prime 95.

 

[boozie]

all I can say now.. if you're on the bridge about upgrading.. WAIT.. for all the bugs to be worked out.

Can anyone approximate a timeline for these issues to be fixed?

 

[devilchrist]

well I got the BIOS issue fixed. I just forced it to update to backup BIOS after updating with the primary bios by pressing ALT-F12 during boot (just keep pressing as soon as computer is powered)

with F6 I can actually turn off my pc without having it worry about it going back to defaults.

some of you keep saying it's not sandy bridge but mother board, you can't exactly use a SD cpu without a SD MB.

anyways.. I'd say wait at least a couple of months.

 

[SlitheryDee]

The only problem I have is that sleep doesn't work properly. If I wake my computer back up within say 30 minutes of putting it to sleep, then it works as it should. Any longer than that and it acts like I cut the power off while it was asleep. That is to say, when I wake it up it boots up from the motherboard post screen and then I get the "Resuming Windows" screen. After windows resumes my ethernet adapter doesn't work, requiring a full restart to restore functionality.

Everything else works as it should though. That one issue bothers me, but I can live with it. I've really never had a computer that would sleep properly anyway.

 

[Diogenes2]

You might try un-checking the power saving option in the device manager for the network adapter.. It is usually on by default.

It's not like the NIC chip is going to break the bank with power usage..

 

[Diogenes2]

Can anyone approximate a timeline for these issues to be fixed?

About the time the next platform goes on sale , with a new set of issues...

 

[Haunty]

I always have problems with bleeding-edge components, I was expecting it when I bought sandy bridge components days after they became available, and sure enough I ran into problems. Same thing happened when I bought my last computer, which was right when Conroe came out. Things were mostly fixed in a couple months or so, and it has been a stable system for the 4+ years I had it.

 

[BoomerD]

I almost waited for the Sandy Bridge release instead of building a rig with 1156 components, but there are always "glitches" in new release products that haunt "early adopters," so I opted to go ahead with the i5-760 build. (parts bought in early December, assembled after Christmas)
With the myriad of problems being reported, I'm kind of glad I did. I HATE having to fight the sorts of issues that I see in these and the ASUS forums.
Yes, I know they're probably in the minority...and many of the problems are user-caused, but still...my luck is that I'd have gotten a board with bad BIOS issues or something similar...<shrug>

Maybe next time I'll jump on the bandwagon.

 

[Zap]

My own Gigabyte p67a-ud4 is full of problems as well

can't come out of sleep,
falls back to backup bio on reboot if OC'ed (unless it's drained completely of power) every time
rejects bios update, (says bios is corrupt and reflash with backup one)
In-bios flashing utility can't detect any drives.

Wow..

Asus seems to have it fair share of problems.

Typical early adopter issues. FWIW my wife's Asus P8P67 doesn't have any of these issues you've listed. I flashed from within the UEFI/BIOS from a USB flash drive. S3 STR sleep works fine, even overclocked. If OC fails (only when I was trying to see how low I can set Vcore offset) it will do the typical soft recovery.

Only "issue" it has is that sometimes but not always it double POSTs/boots (turns on, turns off, turns back on and boots into Windows), and it sometimes but not always has a couple second pause between pushing the power button and actually powering on. These are minor annoyances for sure, but they don't seem to affect the actual operation or overclocking of the system.

 

[Insomniator]

Only "issue" it has is that sometimes but not always it double POSTs/boots (turns on, turns off, turns back on and boots into Windows), and it sometimes but not always has a couple second pause between pushing the power button and actually powering on. These are minor annoyances for sure, but they don't seem to affect the actual operation or overclocking of the system.

My (same) board does the same exact thing. I didn't even realize the pause between hitting the power button and it actually turning on is a bug.

 

[beyoku]

^^add me to this problem too,

 

[Linflas]

Ok home now and double checked. My OCZ SSD is on port 1 of the Intel 6Gb SATA, my first spindle drive on port 3, DVD/CD on port 4, and 2 more spindle drives on 5 and 6. Nothing on the Marvel ports. When I did the Windows 7 install the only drives connected to the board were the SSD and the DVD and the BIOS was the one that the board came with which was 0402 IIRC. I updated the BIOS to 1003 post install.

 

[combust3r]

Only "problem" I have on my board for now is incorrect reading on 3.3V from hwinfo32 (and the rest of the sensor monitor sw out there do the same). If someone is willing to confirm this happens on their boards also (Gigabyte P67/H67 lineup). Thanx

I had certain problems after BIOS update to F6 (settings of primary display (onboard video or PEG) didn't had any effect) but after clearing CMOS everything worked.

 

[Diogenes2]

My (same) board does the same exact thing. I didn't even realize the pause between hitting the power button and it actually turning on is a bug.

I have an Asus P5Q that does the same thing..
Minor annoyance..

 

[_Mumak_]

Should be already fixed in HWiNFO32 latest Beta.