Printable View
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 :PQuote:
Originally Posted by TheHardCase
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!
Good to hear a bios update will do the trick :up:Quote:
Originally Posted by dinos22
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:Quote:
Originally Posted by dinos22
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 :DQuote:
Originally Posted by BenchZowner
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.Quote:
Originally Posted by slim142
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.Quote:
Originally Posted by TheHardCase
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? :?Quote:
Originally Posted by dinos22
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?Quote:
Originally Posted by dinos22
some boards work fine, others dont, if this would be a bios problem then everybody would have the same problem at the same clockspeeds.Quote:
Originally Posted by dinos22
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
Using 0601 at the moment, and gonna give 0603 a shot as well later on.Quote:
Originally Posted by Roger_D25
Just got up and fired up memtest for the last time ( it's pain time, 50 loops of test #5 :D )
And yes, I will be reporting my progress & findings here ;)
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
I'm memtesting to make sure my sticks are stable there.Quote:
Originally Posted by saaya
For the corruption issue I will be running other stuff.
First I want to make sure that all my components are stable, and then I'll look into "what" causes the corruption ( if possible )
Dont forget 3d game stable, thats what seems to be overlooked sometimes.Quote:
Originally Posted by BenchZowner
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.Quote:
Originally Posted by Coupa
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.