790 corruption issues?

Printable View

Show 100 post(s) from this thread on one page

05-24-2008, 06:27 PM
BenchZowner

Quote:

Originally Posted by Roger_D25

Good point Dinos22 but its difficult when it seems so very easy for many of us to replicate this "issue" and have been for some time now?

Dinos is always having good & valid points ( just wanted to say that :) ).
Thing is... I have had corruption as well as some other people here, but even with BIOS v0701 and v0601 ( the 0601 surely doesn't have the "corruption fix" ) starting from the past 2 weeks I haven't had any corruption and I've been pushing the board ridiculously high and outside what most people would even think of.
1.75V SB & NB on stock cooling ( just fans over the heatsinks ) [ changed the thermal paste as well ], 1.8V QX9650 CPU @ watercooling, 2.3V RAM at DDR3-2050+ 7-7-6-21 1T and more.
I wasn't even using memtest to "pretest" my RAM for errors before trying to get into windows and bench or run stability programs & stressing the components :D

It's crazy, because I've had corruption with the v0601 BIOS for sure in the past, and I haven't really changed anything in the system.
Same CPU, same RAM, same VGA, same PSU, same HDD, same Norton Ghost Image, everything.
Even the settings, every setting I use ( successful or not ) is being recorded, so I have "logs" to check back anytime.

Quote:

Originally Posted by Roger_D25

However I have no idea how they or any other vendor handles this kind of research (I always assumed they have a handful of people actually using the motherboards they sell, and using them outside of stock settings? Once again however, the handful of us having "issues" probably represent a fairly small percentage of overall users (and although I assumed they had a handful of people testing I don't think they can test thousands of motherboards to replicate "issues" only a small percentage of us are having)? Hopefully that makes some sense, lol!

The more the testers the better.
If you can separate the testers into categories that might be more effective as well.
Still I wonder how Asus missed the malfunctioning tRFC setting in their BIOSes for the Striker II Extreme ( from some version & all the newer versions ), it just ignores your setting.
Now, if their testers are leaving the sub-timings @ auto, that's not going to help them find the bug, right ? ;)
Manufacturers use their own "weapon of choice"...erm... I meant way to beta test their stuff.

Quote:

Originally Posted by Roger_D25

With that all said Dinos22 do you actually know how this kind of research happens at a place like Asus given your relationship with them?

You missed the relationship a bit :p:
Dinos is "helping" Gigabyte :)
But that's not my job, he can speak for himself and I bet he will :p:
Let him get some rest, he had some seriously long flight home.
05-24-2008, 06:37 PM
Roger_D25

There I go again speaking when I have no idea what I'm talking about (in regards to relationship with Asus), sorry guys! I also had no idea Dinos22 that you were just getting back from long journey, next time I'm give you a few minutes before berating you with so many questions:ROTF: With that said thanks a bunch Zowner for explaining those things, much appreciated! I believe it was already posted (by yourself Zowner) but its good to know I'm not the only one having no luck with tRFC (been trying for weeks to lower it with no luck what-so-ever)! I assumed it was because of some "other" setting but it looks indeed to be a bug?
05-24-2008, 06:41 PM
BenchZowner

It is a bug.
With the very first BIOSes it was working fine.
But then again... things can go bad in the BIOS Eng. department right ? :p:
For the time being I'm stuck with MemSet... but this BIOS bug has ruined some of my benches.
Forgot to adjust tRFC with MemSet before running some benches :(

I will be giving Asus some feedback soon ;)
05-24-2008, 06:46 PM
dinos22

i was at Nvidia editor's day in the last few days and i spoke to a few online news site editors >> i did not have a single one confirm that they had any abnormal corruption issues so it's probably not as common or they just have no idea what they're talking about

every manufacturer i've been involved with has the same procedure when it comes to hardware problems like this......they need confirmation from a few sources that it is withspread and then they need to be able to replicate those problems in their test labs so that they can first understand and second fix and retest the boards
05-24-2008, 07:19 PM
gmcg

Quote:

Originally Posted by dinos22

i was at Nvidia editor's day in the last few days and i spoke to a few online news site editors >> i did not have a single one confirm that they had any abnormal corruption issues so it's probably not as common or they just have no idea what they're talking about

every manufacturer i've been involved with has the same procedure when it comes to hardware problems like this......they need confirmation from a few sources that it is withspread and then they need to be able to replicate those problems in their test labs so that they can first understand and second fix and retest the boards

While they do it, competitors don't sleep :) BTW where did you get F1 EE?
05-25-2008, 01:19 AM
saaya

Quote:

Originally Posted by dinos22

saaya pls let ppl that actually have a problem test the board and report results.....

how am i keeping anyone from testing their boards or posting results? :confused:

Quote:

Originally Posted by dinos22

if it has not been resolved and i can and will also confirm this when i get a chance....it will be reported to nvidia MCP guys direct from my end

thanks for your efforts man :toast:

very nice post bill! :toast:
so the corruption problem is completely fixed now for you with 0701?
and performance? is it a lot slower than other bios versions?

could you give me some tips for tweaking/configuring the 0701?
i could add that in the first post of this thread :)
05-25-2008, 01:49 AM
hifiking

I have experienced the same as BenchZowner, I had corruption and SLI problems in the start, but after pushing things to the max they are gone. No corruption for over a week now, and SLI is rock stable. EVGA P04-05
05-25-2008, 04:00 AM
slim142

Over here, 100% trouble with P1 and P2 enabled. However, when in Auto, 100% rock estable w/ SLI enabled.
05-25-2008, 04:05 AM
BenchZowner

Will update with more details later on.
P.S. Flashed to 0703 just before I hit the bed, gonna give it a try later on.
05-25-2008, 04:36 AM
slim142

Quote:

Originally Posted by BenchZowner

Will update with more details later on.
P.S. Flashed to 0703 just before I hit the bed, gonna give it a try later on.

Hey BenchZ
Any trouble while running with P1 and P2 enabled when you were on 0701?
05-25-2008, 04:40 AM
BenchZowner

Nope, P1 & P2 always enabled.
But with P1 & P2 enabled, depending on your FSB you need more chipset voltage.
05-25-2008, 04:47 AM
nachthymnen

E8500 @ LN2: no corruption problems:up:

http://www.pctunerup.com/up/results/...mmagine015.jpg

http://www.pctunerup.com/up/results/...1037_35872.jpg
http://service.futuremark.com/compare?3dm05=4284144

http://www.pctunerup.com/up/results/...1045_92662.jpg

And my best:)
http://www.pctunerup.com/up/results/...055_114094.jpg
http://service.futuremark.com/compare?2k1=9380307
05-25-2008, 05:40 AM
slim142

Quote:

Originally Posted by BenchZowner

Nope, P1 & P2 always enabled.
But with P1 & P2 enabled, depending on your FSB you need more chipset voltage.

For 450mhz FSB, what would you recommend?
Right now I have 1.44v in BIOS and according to PC Probe II it is 1.46 Real.

Im running out of ideas on how to make this thing estable with P1&P2 enabled.
05-25-2008, 05:47 AM
BenchZowner

Can't really help you out this time.
I haven't bothered testing the SB & NB voltage "requirements" yet.
Since I'm pushing it to the limits I'm using high voltages which will more than likely be more than needed ( currently using 1.65V for SB & NB ) at 442MHz FSB
05-25-2008, 06:35 AM
gmcg

Quote:

Originally Posted by nachthymnen

E8500 @ LN2: no corruption problems:up:
And my best:)

You know, nachthymnen, I have exactly doubled all other guy's setting in my system, he runs 9650 24/7 at 4.5, as he said, and I can barely boot in Windows and get cpu-z validation, all tests failed. It looks that stability issue is different on different 790i motherboards, and even more, it is random - for example I got my computer frozen after 2 hours, someone else reported the same after 14 hours!!! or running Prime. Today you get it as soon as you turn on your PC, tomorrow the whole day it runs without any problem. I moved back to default settings to be stable enough for now waiting for Foxconn Blackops.
You are a lucky one with your board ... Thats why people with stable 790i based systems couldn't understand others.
With 1T on memory my systems was absolutely unstable (BSOD, restarts, etc), with 2T I got it more or less stable with random freezes only.
05-25-2008, 10:38 AM
slim142

Quote:

Originally Posted by BenchZowner

Can't really help you out this time.
I haven't bothered testing the SB & NB voltage "requirements" yet.
Since I'm pushing it to the limits I'm using high voltages which will more than likely be more than needed ( currently using 1.65V for SB & NB ) at 442MHz FSB

Oh well thanks anyways
Are you planning on running the system on air for personal use? You might be able to help us...
05-25-2008, 10:47 AM
BenchZowner

Will do m8.
Just gotta get some things done first.
When I start the "normal" measurements for the review I'll be examining stuff thoroughly, like the required voltages for every "configuration", etc.
When I'm done with the review it will be used as my gaming rig, so 24/7 stuff will come.
05-25-2008, 11:14 AM
BenchZowner

Quote:

Originally Posted by pmp

PM me known bugs (at least other than tRFC, which worked for me iirc :|).

That's weird.
tRFC doesn't work for me and 2 people ( haven't asked any1 else ) with most BIOSes ( 0601, 0602, 0603, 0701, 0702, 0703 for sure ).
Try setting tRFC to 36, 48, 52, 60, 72, 80 and you'll find out that it sets random numbers each time.
The same symptoms occur to any other number that I've tested, just told you these ones because I've used those for sure.
05-25-2008, 11:31 AM
slim142

Quote:

Originally Posted by BenchZowner

Will do m8.
Just gotta get some things done first.
When I start the "normal" measurements for the review I'll be examining stuff thoroughly, like the required voltages for every "configuration", etc.
When I'm done with the review it will be used as my gaming rig, so 24/7 stuff will come.

And hopefully that will be soon :D
05-25-2008, 03:04 PM
dinos22

guys i cannot test this bios because my board is dead
i killed it on the last LN2 session it seems as i have a stuck FF code
i did have that before and the board revived but not this time :(
replacement is DOA as well...i'm really unlucky here
i'll change PSUs maybe that's what's causing it donno :shrug: as i'm using X900 seasonic atm as it was handy(in case of incompatibility of some kind)......will try HX620 sometime soon
05-25-2008, 03:12 PM
slim142

That sucks dinos
hopefully you can get a replacement soon
05-25-2008, 10:11 PM
bingo13

Quote:

Originally Posted by saaya

i really really dont like that FAQ...
it sounds like only anandtech had this problem, and it sounds like it only happens if you try really strange fsb/dram combinations that dont really make sense to run... and they say 1600 is out of spec? but at the same time they advertize 790 as ddr3 2000 capable? :mad:

and they say a bios was released that fixed the problem.
thats not true... they make it sound like the issue was fixed a long time ago, when its still happening! the situation has improved, but the problem is not solved! :mad:

That text is for the P05 BIOS that was released last week. We had it earlier than that for testing and it resolved the majority of data corruption problems we could replicate on a consistent basis (400/1600 was repeatable). I am still testing it, but for the data corruption problems that were consistent in our testing, they are fixed. I am sure there can be other instances where data corruption can still occur because the GTLRef/VTT tables are still not quite correct.

ASUS, starting with BIOS 0703 has implemented some of the base code from NVIDIA, a full update will not occur until next week from all indications. With 0703, increasing SPP and MCP voltages slightly while manually tuning GTLRef helped solve about 95% of the repeatable corruption problems we had.

As far as the first line of the text, NVIDIA knows other users have had this problem, our name is on it as we seemed to be the only "website" that reported our findings to them. ;) It appears that telling the emperor he is not wearing any clothes is difficult for some. I find it funny that certain websites dismissed our claims and a few hours later, NVIDIA admits there is a problem and releases a BIOS update for it. :rolleyes:
05-25-2008, 10:13 PM
OBR

i am playing many days with stability and GTL voltages, thousand of restars but NO CORRUPTION! With 0703 BIOS on SiiEX
05-25-2008, 10:16 PM
bingo13

Quote:

Originally Posted by BenchZowner

You missed the relationship a bit :p:
Dinos is "helping" Gigabyte :)

That might explain why their board is three months late. :rofl: Sorry, but that was one large opening you left for us. :D
05-25-2008, 10:20 PM
dinos22

Quote:

Originally Posted by bingo13

That might explain why their board is three months late. :rofl:

now now Gary :p:

Show 100 post(s) from this thread on one page