790 corruption issues?

[tekjunkie]

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
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...
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.
For now im limited with my NB temperatures that reach 61-63&#186; 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.

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.




Corruption?? IDK. I am gonna reinstall 3dmark06

Can't even freaking unintsall




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)

[M@G!C]

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.




Corruption?? IDK. I am gonna reinstall 3dmark06

Can't even freaking unintsall

This seems a never ending story..... Damn data corruption!!

[gandalfone]

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.

[hifiking]

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.

I have that problem too, but I haven't tried the "save and exit". I just keep trying until it boots.

[TheHardCase]

This started lastnight, I have no idea whats going on.
Sure don't look good...

[RLM]

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

[TheHardCase]

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.

[MateoTTR]

This started lastnight, I have no idea whats going on.
Sure don't look good...

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.