3 rmas???? so you had 4 boards? DAMN! :eek:
guys, imma update the first post of this thread now so people dont have to tight through all this post jungle :D
please help me and lmk if why im posting is bs or what i should add.
thanks! :toast:
Printable View
Damn, my Striker II Extreme killed two windows-installations in 3 hours, i hope they find a bloody fix for this..!
Saaya ,taking into account that this is true, and that is REALLY part of the problem, and that is almost impossible to program one "AUTO" setting in bios to work with all CPU´s. Woldn´t be a good idea for the motherboard manufacturers to release 2 or 3 bios each one with the AUTO settings optimized for a specific kind of CPU? :shrug:
For example one BIOS for 45nm CPU´s and other for 65nm CPU´s or one BIOS for DUAL´s and another for QUAD´s or a combination of the two.
Althought this was never been done before, it could really help resolve a big part of the issue´s we hare having.
Or someone taking the time to make a gtlvref volt table with all the volts assumed good for each cpu. So we atleast had the option to look up which volts that is recomended.
Yep, that can be done to, but i really think motherboard manufacturers must put more effort releasing BIOS that are stable. Even if that means releasing 2 or 3 BIOS for diferent kind of processors. This is the minimum i ask when i buy a TOP PREMIUM board that cost around $400 that is supossed to be an AWESOME OVERCLOCKING board .....
Not as simple as that. Gtlrefs that work for some don't for others. Even with the same chips.Quote:
Or someone taking the time to make a gtlvref volt table with all the volts assumed good for each cpu. So we atleast had the option to look up which volts that is recomended.
RLM
Well I think I've cracked it. Still testing.Quote:
RLM, do mentioned you had blue screens if you changed to 1T, dont you think that already messed your OS installation and might be the cause of the BSoD from the display driver? or probably corruption somewhere else is leading to the bsod you are experiencing.
Im glad to hear you are somewhat progressing through this and not having to mess with the GTLRefs. However, something tells me this might be a a good key for system estability whether we like it or not.
It took an increase in volts to the northbridge SPP. Upped to 1.45v 3d mark ran for a minute before garbage and nv4_disp. Upped then to 1.5v and it ran through no problems at 1800mhz 8-8-8-1T.
Wouldn't want 1.5v as a 24/7 and could possibly do with water cooling on the northbridge. Interesting to see this making a difference though.
RLM
Well, 1.5v didn't do annything for me, but I hope it solved your problems. Then there might be a solution more to try.
That's a shame mate. It does seem that there's no one simple answer. My GTLs for what it's worth were +80 +60 0 0Quote:
Well, 1.5v didn't do annything for me, but I hope it solved your problems. Then there might be a solution more to try.
Here's a couple runs I did with 1T and 1.5v to the Northbridge
http://img265.imageshack.us/img265/8...k06rlm5yc7.jpg
http://img141.imageshack.us/img141/4...k03rlm5fq9.jpg
RLM
well to some degree thats the case.
you release the first bios, which should work for most people, ideally all, but thats never the case. the idea is that people only update their bios when they have a problem. so then lets say 60% of the people can work with the first bios release, then you make another one with lower default gtl ref values and vtt values by default. that takes care of lets say 30% of the people.
and then you release yet another bios with higher vtt and gtl ref values by default... and the remaining people that couldnt get their system stable with bios1 or 2 should have it stable with bios3 now.
well, thats over simplyfying things, but this is similar to what mainboard manfuacturers do afaik. some of them at aleast... :D
well, go ahead, please post your results and ill add them to the first post of this thread as reference. but as RLM said, they vary from one cpu to the other... even from the same batch of chips...
you might think its the fault of the cpus having a too widely spread spectrum, some prefering low vtt and others high, some prefering lower gtl ref, some higher... but then again, they all work on intel chipset mainboards... so it IS possible to get them all working without tweaking vtt and gtl ref voltages bit by bit.
My current S2E works without touching vtt ot gtl. I'm running e8400 @ 4.1 (1840 1.328v) Prime and OCCT stable and the only thing I've changed are cpu/ram voltage and manually set the timings. My 3rd mobo crashed in seconds no matter what vtt/gtl combination but it never corrupted anything. And I've tried them all for 2 days. And the first two corrupted Windows like now tomorrow, change anything in bios and Windows will go away. I decided to sell it while it's working and "docile". Trust me, this mobo is a weird animal.LOL!!
Well i had a try on tekjunkie settings on my QX9650:
QDR/RAM=1780 Unlinked
PCIE1/PCIE2 = 100
SPP<-> MCP= Auto
vCORE=1.375(1.344 in windows per cpuz)
Loadline =Enabled
vTT = 1.28
PLL=Auto
vDIMM=1.9 (Manually put the stock voltage for your ram)
vSPP =1.46
vMCP = 1.55
CPU GTL_REF0 = -29mV
CPU GTL_REF1=-32mV
But QDR/RAM was set to 1800 Linked and Sinked.... and for the first time i was able to boot and load windows at 1800FSB on my QX9650 :clap::clap::clap:
The problem is that i cannot finish Super PI and system seems to have some minor instability. In fact i forgot to enable Loadline Calibration and my memory is runnig at 1800Mhz 7-7-7-16 1T at 1.84V , and this, may be the cause... :shrug:
But, for me, this seems the way to go i will work on his settings next days to see if i can run at 1800FSB with system stable and complete Super PI 32M without errors. :up:
For now im limited with my NB temperatures that reach 61-63º under load, and this might be a problem for me, i will have to take the board out and apply some MX-2 grease on the NB and SB cooling blocks, and add a side fan to directly blow air to the NB, only then i will make more tests.
I don't know...
First test with evga, original bios, I take 111k 3d03 at 500x9
Attachment 77896
but bios very buged...led "hot cpu" and FF on display many times..than I upgrade to P04 and corrupted 4 O.S:D....445x9 corrupted.
Now I set Vfsb 1.25/1.35v and take this with 8400
Attachment 77897
Attachment 77898
gtl auto
Strange chip
gandalfone, sounds to me like the vtt and gtl ref values have changed from the original bios to pr04.
apparently your cpu liked the original auto settings for vtt and gtl ref better...
I just want you guys to promise me something.
You will help me out if I run in trouble with my SIIE ok? not asking much... ^^
hi mate
check my testing notes for volts and FSB
http://www.xtremesystems.org/forums/...d.php?t=179484
and also enable both P1 and P2 and your score will jump with P04 bios
Try locking HTT @ 200. Also, good to see somebody making a progress.
Is anybody else having problems when going over 450 FSB with the screen flickering. In XP, the screen goes blank for a second or two and comes back.In vista, the screen flickers and I get a notification that the drivers have stopped working and has recovered. This only happens only going over 450 FSB and only when I put load on all 4 cores(like priming and SPI). I am on my 3rd board and don't want to go through Asus to RMA as I am beyond the deadline through ncix.
Update:
ARGH!!!!. This is really painful. I boot into XP and wanted to run 3dmark06 to compare my vista score and this is what I get.
http://img354.imageshack.us/img354/4...tionwa7.th.jpg
Corruption?? IDK. I am gonna reinstall 3dmark06
Can't even freaking unintsall
http://img253.imageshack.us/img253/3...tallfl6.th.jpg
Moe Updates:
I ran 3dmark06 in a loop and had a system freeze in xp. I also see a ton of errors in the event log. So I guess my xp installation is borked. I am gonna do the same on vista for more than 3 hpurs(thta's how long I ran itin vista succesfully last time around)
Wow a news...for me
If I set in bios and pres F10 for save and exit I have a problem....11....C3....safe boot. If I chose in bios "save and exit setup" I haven't problem.
hmmmm that sounds like a basic bios programming bug.
This started lastnight, I have no idea whats going on.
Sure don't look good...