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...
I've had this before (or very similar) and not on an nvidia board. It was on a P5K deluxe, when I first got it.
Can't quite remember, the why's and wherefores. I know I've corrupted raid before with memtest, setting overly tight settings on the fly.
Get backed up now, while you can.
RLM
Yeah I'm backing up for sure, it's going in & out with that message raid failed. So I'm sure 2 drives are gone. They were new when I installed them on this board.
I have 2 new IBM drives 150GB so I'll install them, I just hope that 790i is not killing my harddrives, thats what worries me.
I'm no expert on Raid, but I'm not sure if they are buggered.
I know when I googled for a solution, when it happened to me, a lot of threads were pointing at failed drives and having to replace them. Mine were pretty new at the time.
However I setup raid again, formatted and re-installed the OS and no problems.
RLM
Thats why Im using my 7200.9 250gb from my old computer :P
Hey guys, BIOS 0402 really sucks @ss. Everything at AUTO with stock settings (except for RAM, they are in XMP) fails orthos in 5 seconds lol.
However, I want to upgrade to BIOS 0511 but since I dont have a dam floppy drive, I cant. Also, having the Intel heatsink doesnt help neither.
guys i've spoken to nvidia guys about this and the engineers think the corruptions are cause by some memory related bios abnormalities
they are working on a fix and believe it will be a simple bios update. I will update if i hear any more news :up:
i am not really that fussed as i bench with my board mostly and i will not get corruptions if i keep RAM at 2GHz 8-7-6-20 1T 1.95v on my Corsair 1800MHz sticks but i understand the frustration you guys are experiencing running this motherboard in a 24/7 setup so let's hope it gets sorted soon :up:
Great news dinos22 thanks for sharing with us, feeling better already!
this is nothing official and it's not 100% yet that it's a bios issue so pls read it with a grain of salt...... :up:
Oh come on man, you said it was a done deal, lol! Just giving you a hardtime, I understand what you meant when you posted it! Its just nice to know that the issue is at the very least being taken seriously!
i'm finding that the more posts i get the more pressure there is to make things crystal clear on this forum....it's hard not to step on anyone's toes around here lol :rolleyes::D
:up:
Make sure you got your toes covered up :p:
Starting from tomorrow I'll be torturing the S2E again.
I'm currently memtesting at DDR3-1780 ( Linked & Sync ) with super-duper-tight timings & sub-timings for a review, memtest looks clear.
Testing starts tomorrow...will be running various benchmarks and games, so... corruption here I come ( maybe not ) [ hopefully :p: ]
Can't wait BenchZowner, what BIOS are you currenlty testing on? Also will you be posting any of this information here at XS? Thanks man!
i'll be ok :D
http://img177.imageshack.us/img177/6...sprotecih8.jpg
Looks like my above problem is a huge problem.
I installed 2 new IBM 7200 in Raid 0 & nothing but problems, first 2 window installs I got \Boot\BCD OXC0000032 after I installed vista. Could not restore files...
It don't like IBM drives thats onething for sure.
3rd install finished but now I have corruption.
I never had this problem like this, I now know that my harddrives failed because of 790i, it does something with harddrives 100%.
I'm not sure what I'm going to do...:shrug::shrug::shrug:
try running the RAM at 2.0v set in bios at 2GHz with 8-7-6-20 1T timings please
i'd like to see if that changes anything
0511 is really easy to upgrade to, just put it on a USB stick. Then go to EZFlash in the BIOS - it reads my usb drive as B:\, you can flash 0511 from there.
However, i found 0511 to be less stable then 0402. In 0402 ive set all the voltages manually and it gains a bit of stability. If i play around with the PCIe frequencies it gets even more stable.
When I first installed Raid on my Evga, I had real problems. Couldn't even install drivers in the OS without lock-ups.Quote:
Looks like my above problem is a huge problem.
I installed 2 new IBM 7200 in Raid 0 & nothing but problems, first 2 window installs I got \Boot\BCD OXC0000032 after I installed vista. Could not restore files...
It don't like IBM drives thats onething for sure.
3rd install finished but now I have corruption.
I never had this problem like this, I now know that my harddrives failed because of 790i, it does something with harddrives 100%.
I'm not sure what I'm going to do...
The stripe block I think is initially set to Optimal, and I had manually configured it to 32K. The same setting as I had previously used on my P5K deluxe.
So due to these problems I setup Raid again, but this time I set the stripe block to 128K. In addition I upped MCP(southbridge) from 1.50v to 1.55v.
I don't know if it was just fluke, but these adjustments did seem to do the trick. No problems.
Edit: This obviously isn't going to help if the problems are memory related though.
RLM
Just want to mention I had this critical error message on one of my raid arrays with the s2e.
It happened while I was running prime95 on all 4 cores and simultaneously used winrar to compress tons of files with the best quality (yes I like to stress my stuff).
I imagine my settings were not stable (the archive had a corrupt file by the way), so I rebooted and changed settings. The OS is not corrupted and I never got this message again. I believe the critical error happened due to instable oc / mem timings, I am doubtful that my brand new hdds are damaged.
Note for everyone claiming rock stability:
I have tried shltloads of different settings over the last few weeks, and most of the time prime95+memtest will pass for 10h+, when other tests (that involve hdd/gpu activity) will immediately trigger instability:
- run the crysis benchmark tool with for instance 50 runs of 2 loops: the famous lockup can occur in-game or while loading a level. Setting vtt+gtlvref is key to work around this issue, as pointed out by 5010.
- install/uninstall assassin's creed from an iso on disk, do that multiple times in a row (5 times at least). Many settings that were stable with prime95, memtest86 and crysis can fail here making crc errors while extracting the large .forge files from the cab archives. I think the setting of ram timing jointly with vtt/gtlvref has a big impact here.
My current settings:
fsb: 1733
cpu: 8*433 = 3.46GHz
ram: 8-7-7-20 2T linked and synched
NB: 1.34v (more doesn't help)
SB: 1.55v
vcore: 1.35v
vdimm: 2.0v
vtt: 1.28v
gtlvref: -21 and -24 (lanes 0 and 1 resp.)
I tried vtt from 1.20 to 1.36 with all kind of negative values for the gtlvref (from 0 to -50), I kind of realized that:
-50 <------------------------------> -25 -------------------------> 0
CRC errors during AC install <---> seems stable <----------> lockups/freeze with hdd activity
that's just my 2c, honestly prime95 is now the last test I run when trying a new setting, because my 2 other tests are so much more sensitive.
sorry but how is this good news? :?
months after the problems appeared they now "THINK" the problem is "some" anomaly... so they still dont know what exactly the problem is, then how will they fix it anytime soon?
how can you work on a fix if you arent even sure what the problem is?
some boards work fine, others dont, if this would be a bios problem then everybody would have the same problem at the same clockspeeds.
Id say nvidia is FAR off from solving this problem.
From all we know it seems to be VTT causing those instability and corruption issues and nvidia is still guessing its "some" bios bug...? :/
sorry for the poke dinos, i know your just the messanger, so dont take this personal. from what nvidia told you i can conclude that nvidia either
1. still has no clue what the real problem is
2. they do know it and dont think they can fix it but of course cant admit it so they bs you
3. they know what the real problem is and they can fix it or dont know yet if they can fix it, but the guy you talked to isnt aware of it and is bsing you cause he doesnt want to admit he has no clue
dude, i think your wasting your time, people reported memtest and orthos stability all the time, and then, whooops, the install was gone after a day or two :D
Dont forget 3d game stable, thats what seems to be overlooked sometimes.
Ive found, the best thing for testing 3d stability so far that ive tried is actually CoH:OF, which comes with the motherboard. Freezes my system faster then CoD4, Crysis and 3dmark06 (in fact, i had 3dmark06 looped for 3 hours at 1680x1050 and it didnt freeze, played Call of Duty 4 for 30 minutes, thought i might be stable, played CoH:OF for 2 minutes, freeze, awesome >.<).
Yeah, CoH is definitely a fast crash game :D
Crysis would take three loops to crash, while CoH crashed in the first 15 seconds :D
( that's from the past, not current testing )
Agreed, CoH OF is very fast to freeze.
Also Crysis but only if you use the benchmark tool to reload the same level ever and ever.
Be sure to tweak around vtt+gtlvref to work out the freezing issue.
Does anyone own Assassin's Creed?
Honestly I have installed loads of games on my system so far, and for some reason the install of AC is very very good at triggering mem instability/corruption.
To date, it is the most critical test I could find to check my 790i-based system.
I had run a SFC and it encountered corrupted files on my system, that where all corrected... But then, just after, i had run SFC again and he still finds corrupted files that he says it have corrected....:shrug:
And this keep appening no matter how much times i run SFC...
Anyone have a clue?
Reboot at stock fsb 1333 and run sfc again to see if it's a false alert.
This also makes me wonder how system files can possibly get corrupted after a long period of time:
Basically you install your system, you run SFC at first boot and make sure everything is fine. Then how the hell can system files become corrupted a week after, when all those sytem dlls are read-only and should never be written back to disk?
See my point? To corrupt a file you have to write to disk.
All this corruption stuff is very confusing IMHO.
thats true...
the only thing that comes to my mind right away is that maybe data packages get corrupted and the hdd controller then writes them to the wrong sectors on the hdd? so then he basically writes some jibberish into a part of the file, overwriting the original data and hence corrupting it.
I would understand that the registry gets corrupt though, being a kind of database stored in a file that is frequently updated.
GRRRRRRRRRRRR ......:mad: I´m getting pissed with this board....
I was running on 1400QDR and 1800 memory for five days and everything was just fine, no BSOD or any FREEZE at all...
Today i reverted for 1333QDR and 1333 memory to run the SFC to see if the corrupt files apear... and guess what..... gave me BSOD 3 times when i was in windows...
I have run SFC and again same thing he always says he finds corrupted files and that have corrected them again and again...
I just can´t understand what´s going on....
Just 2 words:
CRAPPY BOARD:mad:
Try to understand this guys, maybe something...:eek:
Ok back up without corruption.
1st I went out today & got another 2 new harddrives, installed vista 64 + SP1 all software & games noproblems at all.
2nd Still using same timings ect, no difference at all.
3rd I tried to install new IBM Hitachi Deskstar drives again & corruption all over, nothing but problems. Back to Seagate...
Do I smell hardware problems? Yes Sir 100%
It has nothing to do with my bios settings! All points at different types of drives, trust me.
How can it install on 1 set of drives & not on another?:shrug:
So basically if you dont own Maxtor, you screwed? lol
I had no problems with my 7200.9 so far...
I have had corruption with Maxtor drives as well slim, so nope :p:
The issue has nothing to do with the HDDs themselves.
is this corruption problem a matter of luck on getting the motherboard?
Yeah I understand.
Cant wait for saturday to torture this board... like I said, is here in my hands already but the challenge will be this saturday night.
-----TO EVERYBODY w/ AIR COOLING-----
What heatsinks are you using for your S2E???
ThermalRight Ultra-120 Extreme currently.
Swiftech MCX159-CU and ThermalRight HR-05 for NB/SB ( not all the time ) [ stock heatsinks are good enough, provided you have a fan over the NB cooler ]
Up SPP voltage to 1.35V and MCP to 1.55V at stock settings (probably good for most setups), cured our data corruption problems with 14 different drives. Now if only that worked at 1600 Sync, we might be getting somewhere. With the VTT tables being borked when clocking up, it is hard to cure that problem with voltages. ;)
and from my previous postQuote:
Up SPP voltage to 1.35V and MCP to 1.55V at stock settings (probably good for most setups), cured our data corruption problems with 14 different drives.
By the way does sfc /scannow take in to account microsoft updates?Quote:
So due to these problems I setup Raid again, but this time I set the stripe block to 128K. In addition I upped MCP(southbridge) from 1.50v to 1.55v.
RLM
OK fellas, ive been running for 2 weeks without ANY issues on my eVGA at 475fsb, i dont wanna jinks myself LOL, everytime i post my stable settings, the next day i get a failure or some sort, anyway here it goes.........
Voltages used are as follows in the bios for other people with similar setup to help you out with 475fsb............Following settings is what i use, my computer sometimes stays on for days, i have played crysis for over 2 hours to test, played team fortress 2 for hours, every game i have thrown at it, handles with no problems, passes prime95 for hours, blend and small....good luck
FSB = 475x8, all spread spectrums disabled, cpu features disabled, P1/P2 enables.
cpu = 1.4250 in windows 1.39idle, 1.33 load
memory = 1.900
fsb = 1.400
spp = 1.500
mcp = 1.600
http://img146.imageshack.us/img146/2581/38ghzjn8.jpg
Thanks for sharing GAR:up:
RLM
Great job GAR on that Q9450, is that about the highest FSB you can get for 24/7 use? Just curious because I've got an Q9550 C1 with similar results (but on my old Blitz Extreme) not on my current S2E. Also can you clarify your VCORE for me please (what do you actually set the VCORE to in BIOS), thanks very much!
I had corruption "problems" on my old nForce4 board.
Solution was extremly simple: Do not install nforce mobo/ide/sata drivers.
It is not the board, or the harddrives - it is the DRIVERS.
How PC work. Read from HDD -> load to RAM -> "process with" CPU -> back to RAM -> write to HDD.
If there is a HDD error - it will corrupt everything. If CPU is unstable - you will notice.
However if its RAM it can be a "bit random". But again - after a few hours of burn-in bench... you will notice.
More likly error occures in the drivers. Silent killer that waits to be triggered.
Why in drivers? There can be many reasons: badly written code, code that reads wrong values, mobo sends wrong values to driver etc etc.
For any data to be corrupted it must first be processed. It can't just "happen" by it self. Why OS? It is accessed each second, on each boot.
And the only place this ACTUALY can happen - in drivers. Anyone tried to look "inside"?:
# SMBus Driver (v4.62) WHQL
# SataRAID Driver (v9.99.09) WHQL
# SataIDE Driver (v9.99.09) WHQL
# RAIDTOOL Application (v9.99.09) "Sedona"
That is whole banch of software just to access the HDD's?
PS: not all hdd's are the same. I bet if you install SCSI disc's you wont get any error.
if its the drivers then why does the corruption only take place after altering the default FSB of the cpu to overclocked levels? im no expert but if it really was that simple then everyone in this thread would be posting their immense overclocking results without corruption instead of asking other users if there are any fixes available or newer bioses to correct the problem.
Maybe, but again who really tested without drivers? I know it worked for me on all previous nForce boards. It just for me it looks like people are trying to adjust their systems so that drivers can "work". I suggest to drop nvidia mobo drivers and let windows do the disc work by it self.
I'm currently on Vista 64 and I just ran a windows update and it showed new nvidia Sata drivers for me to update. They were released yesterday (May 7). curiosity got the best of me again and I updated them and rebooted. I'll do some testing. Anybody else get this update to show up in their windows update?
Will check windows update drivers. However, I dont think they are in the nvidia site are they?
Corruption has occured with the standard drivers as well gcardinal.
Both "old" and "updated".
so before the driver update the drivers didnt work, now they do?
but initially they worked even without the update, right?
saaya, what happened was I got 2 new IBM drives & tried to install vista 64 4 x times & corruption issues everytime.
I never changed speeds, timings ect. left what was always working stable on my system.
This time I installed IBM drives again with vista 64 & sp1, along with nvidia updates from windows update & no corruption this time at all.
I can't answer if the updates made a difference at all but this time it's working. I never changed any settings thats all I can tell you...
Evga 790 Vista 64 sp1 maxtor 500gb external HD: was having trouble transfering 30gb+ folders with multiple files/music from the maxtor
after 25gb or so it would just lock up
Did the windows update (optional).......... restart #1 same thing lock up ...restarted in safe....restart #2/3......and problems gone just transfered a 100gb folder no problem
Hope this helps
hmmm so you couldnt even finish the vista install before, right?
and now... you could finish it and then you updated the drivers.
well.. i dont think the drivers fixed the corruption issues then :/
is this the same set of drives you used before?
or a different set of drives?
did you change anything else?
I got my S2E for 2 weeks now : never had any corruption problems running @ stock and clocked to 1600 FSB.
Using 2x 74Gb raptors 16Mo RAID 0 array running on XP SP2 first then vista 64 SP1.
I also test different bios (511 601 603) and never get any corruption problems!
another try from my side... this looks like a lot like "Clock skew". And from what I can see on SAS spec's it can't be effected by that. Maybe SAS discs are way to go?
with SIIEX BIOS 0603 are corruption issues back in my rig ... after some days after updating i have to reinstall OS, games are crashing, rig is freezing (at the same FSB + CPU, MEM setting)
you might be onto something
i was testing my new Gigabyte X48T-DQ6 board for max bootable FSB
i have a CPU which cannot really attempt to boot past 530MHz on Intel boards in general...........well after playing with clock skew and another reference measure which connects all CPU/MCH/and something else i forgot i actually made the CPU boot as high as 580 or 590Mhz i can't recall
now the funky part >>> i could could still not actually load windows any higher than 530 >>> but without CPU skew control alternation the board refuses boot even at 535 let alone 580-590
some more testing needed definitely....it could be the answer on Gigabyte Intel boards at least how to push past your average FSB into monster FSB i can do on P5B DLX 965 C2 chipset :shrug:
Wait, you guys talking about LDT right? the one that can be changed from 1x to 5x?
Wouldnt that slower the performance?
hmmm did you leave the timings and vtt and gtl ref at auto?
or did you set the exact same settings with bios 0603 as with bios 0601?
LDT aka hyper transport multipliers, yes, lower means less bandwidth, but so far there has been no situation in which i noticed lower ldt multipliers degrading performance. i think the bus is fast enough even with 1x and 2x to satisfy all bandwidth needs.
http://img301.imageshack.us/img301/6...8006no6.th.jpg http://img341.imageshack.us/img341/7...8007gn0.th.jpg http://img171.imageshack.us/img171/1...8011un2.th.jpg http://img171.imageshack.us/img171/5...4200bu6.th.jpg
Sorry for average quality, cellphone pictures ;)
Yes 3D stable.Quote:
Originally Posted by Coupa