If you can run prime for 2 hrs your computer is stable. Have you seen how many watts that CPU Stability Test is pulling? I have and its more than prime with small FTTs. My guess is it just over heating your cpu. My advice junk it.
Printable View
If you can run prime for 2 hrs your computer is stable. Have you seen how many watts that CPU Stability Test is pulling? I have and its more than prime with small FTTs. My guess is it just over heating your cpu. My advice junk it.
Dude, the P5E3 is a very odd board for finding stability on - many of use can run X/Y/Z stability program for N hours in a row with no issues, and yet fail SuperPI or experience random crashes. You just have to narrow it down - and with those temps it's not a heat issue.
File Spiro,
My heat temps are somewhat over the top since I own a not too good aftermarket cooling (air) solution (Scythe MUGEN). My idle/load temps on Real Temp are as the picture shows...
http://www.imageshack.gr/files/tni2b89cbuvy320h03mj.jpg
Anyway, I manage to have success on SuperPI (even on 32MB) and stable error-free Prime95 (for over 2 hours) and MemTest86. :up:
Your problem on the core sensors is common on this CPU (C0 revision on CPUZ). If you google on "QX9650 stuck sensors" you'll see that many other owners of this CPU have the same issue as you... It's actually an erratum that INTEL never confessed openly (as AMD did, on the honest side), so the prices never went down... :cool:
I happen to be on the lucky side, since my CPU (purchased from France) has no such issues, except the permanently reduced temperature of the last core (core #3), which, of course, doesn't stay the same while testing, but always in a much less value from the others... Maybe it's a variation of the above mentioned erratum, I dunno...
Of course, if you keep having this bug, prohibiting you from having a stable system, you should RMA. I would.. :rolleyes:
Yeah i run prime for 12 hours with no erros and when playing or browsing my pc just reboots or has a bosd.. i had to increase the vcore.
About the stuck sensors, my first Q9450 went to rma because of 2 stuck sensors and they gave me another one with 1 stuck sensor and 1 core with a lower temp lol. But that has nothing to do with stability... it's just a temp.
This not a odd board. Please reread my post. What part about "New" dont you understand? I will repeat. This is a great board. With an immature bios. A bios is a set of instruction that tells the hardware what to do.
They have had Visa out for 2 years and they still dont have it right. This board has been out for 2 months. Give me a break. After a while you become the problem not the hardware. Example. You say can i do 400? Than you do 400. But YOU are not happy. You say can i do 425? Then you do 425. But again you are not happy. Than you say can i do 450? Than you do 450. But again you are not happy. Than you say can i do 475 but you cant and then you blame the hardware. You see a pattern? You became the problem not the hardware. Theres a reason some people say never buy hardware less than a year old. So if you cant handle being a beta tester untill write a better set of instructions than you should not be in this business
People with the randon reboot problems please tell what OCCT is showing for the 3.3v. loaded and unloaded thanks
Mate, you need to chill - I said that the P5E3 was an odd board to find stable settings on. Which it is - just read over the posts in this thread. Noone's commenting on whether it's a bad board full stop (which reviews and some outstanding results say it definitely is not) or whether it's just down to an immature BIOS. Calm down, noone's attacking you or the P5E3 Premium, just wanting to try and find stable settings and sharing our experiences with it. You're not helping the situation by making snippy posts telling XtremeSystems members that they don't understand what a BIOS is.
Back on topic, I'm starting to think these low-or-changing-load crashes are definitely down to RAM CLK skew not being set right. By way of experiment, I'm trying different CLK skew settings, and finding that if I deviate too much from what I'm running now then all benchmarks except SuperPI will run fine for as long as I want to keep them going for, and yet I'll get random reboots and shutdowns at low load or when ramping up/down (eg. gaming). When these skew settings are very close to ideal, SuperPI will run fine, but extended gaming will still trigger reboots, so it's a good indicator of when you're getting close.
Yes its a memory problem and the next bios will fix it. What volts are you getting on the 3.3 rail? Undervolting the memory will cause random boots. Doesn't this board have a dual phase memory power supply? I am testing another power supply that puts out more volts on the 3.3v rail.
Just because you are member doesnt mean you know all there is to know. I notice there are some new members and thought i help them out by explaining what a bios does. Of course if you know everything then this does not apply to you. You call it snippy some call it thanks. It goes back to the you problem.
Out of curiosity, are you running the PERFORMANCE setting for loadline calibration? It is my understanding that using that setting can cause exactly the condition that you are describing as the cpu will actually recieve less voltage while idle than when under load. Even when that is not the case, increased "bounce" will mean that the cpu is subjected to excessive voltage for a few milliseconds as well as more significant droop for a few milliseconds that can lead to this kind of instability. Anandtech went into detail regarding this a couple of months back. Sorry if I am off base, but I figured it was something to consider.
You mean that when I have Loadline Calibration set at PERFORMANCE, I would probably have more unstable system ??? Is it preferable to have it at AUTO ???
I am curious because, even with a stable system (Prime95, MemTest86 AND SuperPI), last night I experienced my first BSOD and a glorious reboot of the system, while simply playing an avi file with media player and downloading a file in the background.. :shrug:
Thank you in advance for any clarification or suggestion on this matter. :)
Mine is always 3.31v idle or load.
About the random reboots, don't trust in prime because it won't tell you when u need more vcore. Although my system is prime stable i had to increase my vcore to browse or play without reboots.
A good site to test it is www . tvtuga . com. Using bios 0204 it just reboots in 5 secs. Yesterday upgraded again to bios 0401 and it took some minutes to reboot. I increased my vcore and didn't reboot anymore with that site and i played for 3h30mins without a crash.
went there and no reboot so
using bios 0503 beta , ATM 3.6ghz with those settings occt 2.0a /games /stable:
strap auto
dram set manually 7-6-6-18 @1600 mhz
multi x 9
vcore 1.1375 ( 1.11 load )
cpu pll 1.56
vtt 1.32
vdimm 1.84
nb voltage 1.41
all gtl's auto
sb voltage auto
LLC performance
spectrum disable
dram static enable
transaction booster set at PL 6
skew settings auto
Im liking the 503 better to... system got stable where it hasnt been..
btw, what max fsb can you get with 266 strap? and what bios?
and thanks for the link!
Hi all,
My experiences with the p5e3 primium started of fine. I managed to get decent memory performance in the first week an were able to run some prime blends for few hours. At the end of week 1 i started to experience hard lockups which were followed by raid0 harddisk errors.
Did alot of rebooting and reinstalling, changed harddrives but the hard lockups did not go away. I have no clue what was causing these lockups.
I could run the system stable (3-4 hour prime blend) one days and the next day after a insignificant reboot the system would become utterly unstable (unable to run prime for 2-3 mins), without having made any changes to system or bios.
After 2 weeks i thought that it was time to update the bios to v0401 because of random unstabilities and lockups. With the new bios the system ran stable for another 2-3 days (prime blend on all four cores for 3-4 hours) and some games without problem. Next day, rebooted with no system changes, after which the system turned utterly unstable again.
At the end of week 3, system does not want to post after a reboot. Only after clearing CMOS or leaving the system unpowered for a few hours it seems willing to post.
Now the think is that board does not want to post after making changes to the bios settings. So i cant set bootdrives what so ever.
I feel i have reached a dead end with this board, as i dont dare to update bios, with the system in this condition. Besides i cant think of a reason why it shoud matter anyway, as the system ran fine for a few days with v0401 and now it can only post after clearing CMOS.
Anyone have any clue why my system suddenly does not want to post?
It start with 1 beep i normaly hear (could it be a undetected keyboard?), then the mobo powers on, the monitor powers (like it seems to get a signal) but the post screen just doesnt show.
I am totualy lost here, all tips welcome,
Thx
Kazi
bios 402 or 503 beta will post after making changes
Kazi, If you haven't already done so, disable express gate.
I have had continued difficulties with OCZ Platinum DDR3-1800 and system stability. I have tried all of the various recommended settings including clock skew. I just got off the phone with OCZ tech support. I can say that I am very impressed with their customer service. I am going to exchange 2 sticks of the platinum for 2 sticks of the Reapers. It sounds like these are much more compatible with this board. I'll let you know how it turns out.
You are correct regarding their customer service. Their helpful attitude kept my frustrating situation from becoming un-bearable. The reapers helped in my case as well. I don't know which chips are used in the Reapers, but compared to the 1600mhz Platinum, setting these up was a walk in the park. Strange too, when you consider my setup is 2x2gb and I went from 1600mhz to 1800mhz.
Mine never drops, it only increases 0.08v @ load.