That's likely the 790i NON Ultra.Quote:
Originally Posted by lopri
Printable View
That's likely the 790i NON Ultra.Quote:
Originally Posted by lopri
Ok update, I have been running this computer real hard.
Gaming all day, running all kinds of programs & it's running like a champ.
So I have no idea about what happened the first time but, this time the computer has been running for almost 2 full days with 0 problems.
I had a 680 almost kill my raptor 150 aswell. The raptor150 has been cause for several sata errors on various boards. NEw firmwares should have addressed this by now. I got rid of the pos 680 though after my second try. My raptor turned out to be fine on intel board.
as anyone tried a pcie/pci sata controller yet?
Poll reset to zeros on saaya's request as some didn't understand.
Vote for one only please and everyone above this post please vote again.
Thanks.
actually, you can vote for both if you do/did have access to reference board and the asus board :)
so those hdds dieing could be a problem of the WD firmware?
i dont know... then how come they only seem to die on nvidia chipsets?
1. it weighed quite a few kilosQuote:
Originally Posted by slim142
2. it was huge... way oversize which doesnt make sense... itll make the airflow worse.
3. i didnt like the design tbh
4. you had to literally take half the case apart to change the psu depending on the size of the psu
5. cheap plastic bad quality usb and sound plugs on the top
thanks vince :D looks like youll have to vote again tho ^^Quote:
Originally Posted by k|ngp|n
we had to reset the poll :D
so there was b0, b1 launched, and now there are already c0 and c1 is beeing worked on as well? 0_o geez...Quote:
Originally Posted by lopri
You think the problem is hardware or just the bios immature ?
Thanks
i don't think that ppl that voted can actually vote againQuote:
Originally Posted by Movieman
lol don't scare me saaya :DQuote:
Originally Posted by saaya
but this feedbacks sounds really said, but we don't know for how long use time coming this hdd corruptions...
i use the S2E till one week with 0507 bios and the only issue wich i've recognised is some memory instability at make round clocks like 1600.00mhz
but back to hdd problems, has smbody experience about when and how coming this issues? with high nb voltage, or if you test max fsb, push the mobo some high clocks ect... this could be REALLY important...
I haven't voted since this is 790i but my 780i corrupted HD [WD?] and hence OS after plus 470FSB oc'ing with DDR2 MEM under 650 always, so I'm not sure you can say it's a problem restricted to only 790i. I have a dual boot with Ubuntu 64b, 64b is always more vigilant to catching MEM errors so I try it. I just booted the Ubuntu install after I felt the errors were being caused with very heavy fragmentation and it showed all the offsets which were corrupted at boot and when booting Windows again, the drive kept needing Checkdisk to fix physical errors. SATA II drive, E8400, S2F. CPU/MEM can do these settings easily though and they seemed fine on the S2F until I rebooted.
You'd have to test very accurately to determine any corruption at low and stable settings, for a first, you'd have to know the state of hardware and OS right before the "corruption inducing" tests.
hmmm i emailed gary from anandtech but didnt get a reply yet...
ask xt0m, he had 2 hdds die on him, he should be able to give you some details.
if he tells you interesting details please post them here :D
and dinos, you cant vote?
you should all be able to vote again, editing wasnt possible so i asked for a clear reset.
KTE, well, this hdd corruption thing seems to be related to the southbridge, which on 790 and 680 is identical right?
the memory instability causing corruption seems to be yet another problem related to the northbridge, or maybe just the bios...
hopefully just the bios...
Yep can't vote again. :( "You have already voted on this poll"
I'll be watching this to see how it develops.
Maybe this is why Vista64, kept blue screening on me. Finally resulting in NTFS Failure and had to reinstall.
I went back to XP this go around, and haven't had the issue from that point on.
Now I have been having problems getting it to run stable with memory at 1333, but it could just be the ram. I have had the bios come up as corruption but a reset makes it go away. This is with the ram being set to 1333.
Also, the people that have been experiencing this corruption are using nvidia sata drivers or vista ones (assuming it has their own)?
I don't think it's a driver related issue ;)
nvidia sata drivers here
im waiting for staff to fix the poll guys, just hang in there :D
it should dissapear soon, then there will be a fresh poll and i will pm you all asking to vote again :D
sorry for the hassle... seems polls arent working very well in vbulletin...
nvidia SATA drivers a CR@P and always seem to have been, EVGA recommended NOT using them over on their forums.
What does EVGA recommend us using?Quote:
Originally Posted by 5010
Microsoft's default Windows drivers.Quote:
Originally Posted by Big Myke
i use nForce drivers, no raid, xp sp2, 2 SATA HDDs, 1 SATA DVDRWQuote:
Originally Posted by slim142
NVIDIA ANSWERED ME ABOUT THE FSB AND MEMORY CLOCK ISSUES
http://img217.imageshack.us/img217/8...suesgf3.th.jpg
Troubleshooting
http://nvidia.custhelp.com/cgi-bin/n...p?p_faqid=2166
Hopefully this means something (dont know how serious NVIDIA is, but remembering 680i, we might have a solution soon). We need the fix ASAP as I have components ready to be OC! :D
I think you mean nForce 9.64 since I dont remember 9.46Quote:
Originally Posted by fadetoblack
Hopefully like said by other user, this is related to the non-ultra version since many ASUS owners are gonna be pissed! eVGA usually gives discounts or trade-ins for their boards but not ASUS. Do you think ASUS would exchange the board if NVIDIA made an announcement saying B1 SPPs are defective?Quote:
Originally Posted by lopri
Nice to hear somebody is at least booting and running XP. Dont know what to say about your RAM problems.Quote:
Originally Posted by DaMulta
Saaya, does weight matter? Most people dont move their cases around that much. Yes, you are right, even though it is very big, I forgot about air flow, but with that many fans, do you still think air flow is REALLY affected?Quote:
1. it weighed quite a few kilos
2. it was huge... way oversize which doesnt make sense... itll make the airflow worse.
3. i didnt like the design tbh
4. you had to literally take half the case apart to change the psu depending on the size of the psu
5. cheap plastic bad quality usb and sound plugs on the top
The design, seems ok for me, and about the PSU, yes thats right TT has always made the worse PSU space designs. About the cheap plastic well, not all is made of plastic, bad quality USB? Im not gonna use that neither the sound plugs :)
The reason why Im interested on that case is because is spacious and it has cable management (not as good as Antec but has one)
See? ;)Quote:
Originally Posted by 5010
Prolly is not a driver issue, but I would exclude that cause.
From Anantech's website........about this problem:
Data Corruption - not Political Corruption - with NVIDIA’s Latest Boards
i can't saaya....but i will probably stay out of it anyway as i am doing in the OSes during RAM testingQuote:
Originally Posted by saaya
i corrupted another OS last night while testing RAM
this is getting on my nerves now :confused:
lol during my initial testing all i did is leave RAM at 2GHz 8-7-6-20 1T and go about usual tests lol and now with all the RAM tests i keep losing OSes
it's definitely unusual. i cannot remember last time i took out an OS with a mobo...............................intel or nvidia chipset :confused:
the thing with my setup is i have usually 3xpartitions >> XP > vista or win2008 server > backup partition
i only lose the OS i try to boot to if something unstable >>> the rest of the data is still intact and second OS works and all my screenshots and software is fine >> not a corruption of the drive
i think BenchZoner is right......i don't see this as a software issue but i will test that..........i will just install naked systems and do RAM tests again and see what happen >> hit prediction is that i will still kill an OS
i've been using memtest (1x loop#5) last night for most of the testing but this time i didn't do it as my RAM settings were within the normal range but my CPU was vcore starved as i was booting at 5.4GHz
i've reported my issues to nvidia as well
I have a theory that the data corruption is caused by bad FSB Voltage, usually too much combined with possibly bad GTLREF's, with increased traffic on the memory controller/NB from higher FSB and tighter RAM timings. 0 & 1's are getting back to the NB from the CPU a little confused and some of those are being written to the HDD.....
Got my reasons to theorize this
So I guess is a bad time to buy a 790i?
Unless you're a hardware maniac, I'd say stay away for now until further info is released, and hopefully a fix or cause is found.
My Striker II Extreme should be here tomorrow they told me earlier on the phone :)
you hardware maniac you :ROTF: :DQuote:
Originally Posted by BenchZowner
Hopefully by the end of the month everything might be solved.
Is not that Im a hardware maniac, but I have hardware to BURN BABY BURN!!! :D
Well if anybody knows what setup was kinping using on his 790i and could please tell me, I would really appreciate.
EVGA I belive.
OCZ 2x1 GB DDR3-1600 7-7-7-20, working well in eVga 790i¿?
which memory you recommend with good value ?
I not found memories List supported for this mobo.....Someone knows?
Thankss bros!
I am extremely close to ordering one of these, but the RAM I want is impossible to find so I havent yet.
Maybe its not meant to be?!!??!
pretty much, at least not for the next 4 months.Quote:
Originally Posted by Borgod
Just get a cheap D9GTR 2GB kit to play with in the mean time.Quote:
Originally Posted by Borgod
I guess I need to check the spam folder. ;)Quote:
Originally Posted by saaya
Answered in our quote section -
"We have two 74GB Raptors that are basically dead, they will power up but cannot be low-level formatted. The WD 250GB drive basically had the same problem. The two 500GB Samsungs will power up and repeat a click-clack pattern. The Samsungs have been returned for analysis as will the 74GB Raptors.
I am getting ready to do the same for a pair of 150GB Raptors that I wrote off in December. However, those drives failed (no longer accessible) during RAID testing on the 780i board (usually I yell at myself when that happens as I have had far too many RAID 0 arrays drop a drive over the years). I did not think much of it until we started having these data corruption problems over the past six weeks.
Between Kris, Raja, and I there have probably been around 14~16 image reloads the past six weeks after overclocking. We fully except to trash the OS when exploring the boundaries of memory/fsb rates, but it might happen once or twice a month at best and is not limited to NVIDIA chipsets. However, all of these failures have been on the 780i/790i boards and we were not really pushing the systems except for two times when the drives failed or the images were corrupted.
The frustrating/perplexing problem is that the 790i testing with Kris resulted in some of the best overclocks we have ever experienced and they were 100% stable. We changed the settings to a normal overclock at 400FSB/1600 DDR3 and the images are corrupted or the drives went south. It is not repeatable at a given setting. We have seen results like ours in various forums so there is something amiss here, just trying to find it right now.
In all cases, we have had the memory settings set at something other than stock/default. I am still working with Derek as he has experienced several data corruption problems during SLI testing the past couple of weeks. I did not mention that until we figure out if his problems are related to ours."
data corrupted on IDE HDD on reference board, but after many days of playing ... worst is very bad ocing possibilities of this mobo ...
Has anyone approached nVidia so they can start a proper investigation into this?
In any case, I alerted a focus group member about this thread. Hopefully, it will get reviewed as well as the Anand article.
could you guys PLEASE stop posting links to that anandtech article?
there must be 5 people who already posted a link there :D
slim142, yeah sure you can get good ariflow in a big case too, but you need more fans and itll prolly end up noisier. i prefer a small case... its easier to create propper airlfow in there. but then again, i dont use any case whatsoever for... 6 years? :D
Oh well, I just decided to go for the Armor because of the space but I would also consider the P182 as a nice 2nd option ;)
Hey slim142 did you get the Asus S2E yet? Newgg is having a -$40.00 off coupon plus free shipping a $50.00 savings for a 24-hour sale...
L I N K
ROFL saaya he got you good there :rofl:
i emailed you from 2 email addresses, please check :DQuote:
Originally Posted by bingo13
so its not just the wd drives suffering from problems, thanks, thats good to hear. well, NOT, but you get what i mean :DQuote:
Originally Posted by bingo13
so you had 2 raptors and two samsung drives fail? or even more?Quote:
Originally Posted by bingo13
yeah i remember raja having a good time with crysis :lol:Quote:
Originally Posted by bingo13
i recommended him to use ghost since i think he didnt use it by then cause he didnt have that many corruption issues before.
it def makes your life THAT much easier :D
well yes, thats the weird thing, isnt it? on intel and amd chipsets i blow a partition after 300-3000 boots at unstable speeds id say, and even then most of the time you can repair the install with the console or by replacing some files. i wonder if amd and intel and other chipset makers use some special ECC like technique to prevent corruption at unstable speeds or whether nvidia is maybe using bigger cashes/buffers which then dont get flushed if something goes wrong and bigger chunks of data are missing or corrupt.
well thats the thing with nvidia chipsets... everybody who spent enough time with one or a few boards knows about this... from what i heard this inconsistency in something working once and then not working and suddenly working fine again is typical for nvidia chipsets ever since the 5 series. i really wonder what it could be, i can only imagine that some plls or some dividers lock every time the chipset is configured and initialized and for some reason it doesnt always happen the same way every time the chipset is reset.Quote:
Originally Posted by bingo13
but the bizarre thing really is that those problems happen at 1600, which is exactly where you would expect everything to work fine, as thats what you want everybody to run. if it would corrupt or give you a hard time at 1700, well, thats above the spec, too bad, we are working on it but for the moment only 1600 is stable. that would be fair enough. but the memory failing at 1600 while much higher speeds work fine is... odd...
i first thought maybe nvidia tuned the performance so at 1600 its tweaked really tight to win reviews and be fast at stock speeds, but if that would be the case with all those problems people are having id have expected them to release a relaxed stable bios by now. so it seems to be something else, or nvidia is really stubborn and doesnt want to losen timings to give up some extra performance :D
well overall it seems quality control is falling apart industry wise... at least thats the impression i got over the past 5-10 years :/Quote:
Originally Posted by bingo13
which is really too bad... there are so many power users who are actually willing to BE abused as beta testers from manufacturers, and most users are more than happy to work with the manufacturers on a solution, but 95% of the feedback seems to be ignored or takes a month to reach the right people.
who? gary? you mean the spam folder thing? up yours hinterland ozzi! :ocau: :P heheheh :DQuote:
Originally Posted by dinos22
This is exactly what happened to the S2E that I RMAed. Memtest was hanging (3 consecutive times)RAM@1600 unlinked with 1333 QDR(default). Guess what, same RAM, same settings, I tried the same thing again after some time playing around with the board, it worked fine:confused: . It was also randomly rebooting for some reason, while windows was idle with no to moderate OC and one time it rebooted when I was in the BIOS. I also eliminated the possibilty of a bad PSU.Hope my replacement board which should be here tomorrow is much better.Quote:
Originally Posted by saaya
Ehh Saaya, I still can't get anything to happen like it did the first time.
I'm starting to wonder about 1600MHz, I changed out the ram to 1800Mhz & no problems at all, I'm definitely going to say there is a problem at 1600MHz corruption issue.
Currently installing Windows at 400MHz FSB and the RAM @ DDR3-1800.
I'll do some testing later on, don't know how many tests...as I'm finishing a review simultaneously :p:
I don't know if any of you know this but the Q6600 doesn't run over 1630 on the 790i. No posts whatsoever at any settings. Check out the EVGA forums for more info if you are having problems. It might be a definate QDR 1600 problem.
we need the P03R2 bios, if anyone has it please share.
http://www.momoshare.com/file.php?fi...426289f325f84a
here you go. Let us know how things go with this bios.
No go for today... none of my Twintech nVIDIA cards here work on it.Quote:
Originally Posted by BenchZowner
Especially those Twintech 8800GT's are so full of incompatibilities :( :shakes:
Quote:
Originally Posted by BenchZowner
Not looking good .... :(Quote:
Originally Posted by saaya
....current problems notwithstanding anyone have any idea when we might get the DFI variant?
Don't worry...those Twintech's didn't work on my Gigabyte X48T-DQ6 as well...Quote:
Originally Posted by Biker
It's a graphics card BIOS related issue.
I'll grab some VGAs tomorrow ( if I make it in time ) and start my tests with them.
For now... I'm stuck with a PCI "SuperPi" graphics card on the Striker II Extreme :p:
hi guys
i've a striker ii extreme here to test and also have serious problems. anything above 350mhz fsb isn't stable at all.
also my 74gb raptor got corrupted a few hours ago. :(
5200 PCI FTW! new 06 WR i'll bet :rocker: :DQuote:
Originally Posted by BenchZowner
When I say not looking good I was actually referring to all these incompatibilities we keep getting that seem to be cropping up with more and more regularity.
After building close to a thousand systems over the last 10 years I can honestly say that I have had more hardware throwing its toys out of the pram in the last 12 months than the last 7 years put together.
I am not liking this trend line :/
lol.
I'm going to NYC this weekend and I was going to pick up a 790I while I was over.... but because of all the problems the UK price has dropped so much it is barely more expensive here now... :rolleyes:
try to raise CPU VTT and NB-Voltage a little. Not too much. For NB 1,45 Volt is ok.Quote:
Originally Posted by Turrican
Have you tried it??? did you get it from a trustworthy source???? i dont want to brick my board, thanks.Quote:
Originally Posted by Delirious.
Flawless...loss :D
Data loss to be precise.
My first corrupted Windows installation.
Gay RAM timings ( 100% stable ) and low FSB ( 450MHz ).
Thank you 790i, thank you Asus!
I have not tried it. I got it from the EVGA forums. It is the bios that was sent out to one of the board review websites. Let me see if I can find more info for you.Quote:
Originally Posted by GAR
edit: it came from here http://www.hardwarextreme.de
That's all I know. I would gladly delete this post if someone else has a more reputable source. Sorry, I just thought I would make it available.
Oh crap.Quote:
Originally Posted by BenchZowner
Pulled my S2E out again to play around with my E8400, and have had a better time, although there are some serious FSB holes...
ASUS Striker II Extreme
CellShock DDR3-1800
nVidia 8600GT
WD RaptorX 150GB
ALL AIR COOLED
CPU - Arctic Cooling Freezer Pro 7
S2E - Stock cooling
ALL TEST: Unlinked, Memory speed locked at 1800 8-7-6-21 1.9V
ALL VOLTAGES: AUTO except CPU/RAM and stated otherwise
P1 P2: AUTO
FSB 333 - default - boot - stable
FSB 425 - no boot
FSB 450 - no boot
FSB 500 - boot - 100% stable - no corruption
FSB 525 - boot - 100% stable - no corruption
FSB 550 - boot - 100% stable - no corruption
FSB 575 - bumped VTT - Boot - not stable - no corruption
All of the above settings had crappy bandwidth, 8000 read 11500 write 74ns.
With P1P2 Enabled the board behaves very erratic.. if you manages to post, then the system seems stable, with memory performance on par with EVGA reference 790i.
Swapped out the E8400 and fitted a Q6600.
First Boot: FSB 450 x8 - boot - restarted after 20min of ORTHOS
after that all went into crap... with the same settings, it may boot, it may not. P1/P2 or not, the S2E has got an attitude problem with quads... :shrug:\
HOWEVER; seems that having memory at 1800 is NOT causing corruption of the OS("is preventing OS corruption" would be too conclusive). Silver lining?:rolleyes:
Couldn't have put it better myself...Quote:
Originally Posted by Biker
I used it, and it is fine. However flash at your own risk.Quote:
Originally Posted by GAR
Do you know how pissed I am right now? wow I cant believe I missed that one!!!Quote:
Originally Posted by Lu(ky
Well at least ZZF seems to be lowering the price of the board. Thanks for the heads up but wow all because I needed to sleep one day and this big promo happens the day I deciede to take a break...
All these problems make me think it's an SPP problem. Since it's NV's firstQuote:
Originally Posted by eternal_fantasy
DDR3 memory controller, I think they have a lot of divider issues.It reminds me of my early P5WDH memory divider issues.Hope it's gets better as the bios matures. It got better on the P5WDH as the BIOS matured, so hoping the same(Crosses fingers).
I've been lucky so far, no corruption yet.
when trying to push the memory to extreme I got tons of OS corruptions - even when running dual Spi 32m, and I crash - after reboot XP will be corrupt50% of the times. Thanks god it only takes me 1min to restore OS thanks to xxcopy
My board just died after 1 hour!!! :eek: i set up an advanced rma, hope i get a new one soon.......it just died, just like that, refuses to boot, i get a blue power light on the board, but the board is dead......crap quality for a $350 board.
lol you sure you didn't brick it :p:Quote:
Originally Posted by GAR
Yeah bro, i couldnt even get the bios in there, i tried with ntune and it said bios id didnt match, it died while i was installing my software.Quote:
Originally Posted by dinos22
lol crazy holes thereQuote:
Originally Posted by eternal_fantasy
This is BS ...
My results with E8400Code:Originally Posted by eternal_fantasy
FSB 333 - default - boot - stable
FSB 425 - no boot
FSB 450 - no boot
FSB 500 - boot - 100% stable - no corruption
FSB 525 - boot - 100% stable - no corruption
FSB 550 - boot - 100% stable - no corruption
FSB 575 - bumped VTT - Boot - not stable - no corruption
FSB 333 - boot - stable
FSB 400 - boot - stable
FSB 450 - boot - stable ... everything on default except RAM
FSB 500 - boot - stable
FSB 525 - boot - unstable
With Q9300
The same, but max stable is 470MHz FSB ...
With Q6700
No go higher then 370MHz FSB ...
Argh !!!! I am having no luck with this board at all. Got my replacement S2E, put everything back together with my E3110, reinstalled windows xp just to be safe. Ran everything @ default, SPI 32M frezees the system. I mean the system is hard locked with everything on auto. This is crazy. $450 worth POS. ARGH:mad: :shakes: :brick: and I am running out of smilies.
Here is the Bios P03r2 Post 74# of this thread :rolleyes:Quote:
Originally Posted by day187
better make a northon ghost image alread before things go bad :DQuote:
Originally Posted by BenchZowner
:doh: too late, saw your other post :D
yeah i know what you mean... btw, for those who are trying, the asus xonar soundcards do not work on 790 boards it seems :doh: a bios update is needed to get it working according to asus.Quote:
Originally Posted by Biker
my god... uk shops arent overpricing everything anymore?Quote:
Originally Posted by Biker
the world must be coming to an end :eek: :lol:
thanks a lot man! :toast:Quote:
Originally Posted by eternal_fantasy
thats really helpfull... if you have time and enough sanity left ( :D) it would be cool if you could maybe map that fsb hole space in more detail.
what about the q6600 then? same fsb holes for it as for the 8500?
50% of the time? hmmmm xxcopy... is that some tool for your areca raidcard? :DQuote:
Originally Posted by mikeguava
1min os restore... man... awesome! :slobber:
this should be a free add on to all 790 boards :lol:
your board died? :confused:Quote:
Originally Posted by GAR
out of nowhere? did you use high vdimm or high nb voltages?
any idea what could have killed it?
please calm down man... just cause you get different results it doesnt mean his results are BS :PQuote:
Originally Posted by OBR
Please post the detailed settings and bios version your using and what cpu multiplier, maybe there is some detail that improves the stability at different fsb speeds :)
hummm... :(Quote:
Originally Posted by tekjunkie
what mem speed?
did you try different mem speeds? :(
Man, can you relax and take it easy sometimes ?Quote:
Originally Posted by OBR
Chill out.
If you think somebody's wrong you can easily talk things out and play nice.
No need to use such expressions.
P.S. The FSB holes seem to depend on the Memory Clocking mode ( linked/unlinked ) and your selections.
For example ( hypothetical numbers, didn't take any notes or did many tests ) [ but this theory comes from my experience with the 680i ] 400MHz FSB with the RAM at 1777 won't work, while it works with the ram at 1600 and 1866 ;)
i've given some detailed feedback today to nvidia guys
fingers crossed they get to the bottom of this QUICK :D
This morning I started up to get blue screen blue screen blue screen lock in nvp_dspl.
Then I turned my memory to 1000 and it went away....I thought I lot everything on this install....
http://www.newegg.com/Product/Produc...82E16820145183
Must be bad ram even tho it passes memtest, but it could be a issue with this ram and the ASUS 790i.
I havent been able to run them at 1333 but at 1066 from day one.
Sure I'll try and go into finer FSB for the E8400, with a short ORTHOS run and a screeny if I manage to boot into windows.Quote:
Originally Posted by saaya
The Q6600 I can not tame... one minute it boots and are semi stable, the next minute it refuses to boot... I would leave it to anyone feeling more adventurous to map the Q6600. Good Luck!!:D
My results are very repeatable as I have listed all the settings and parts I used. So anyone should be able to replicate my results. OBR's result seems to have P1P2 enabled, while I did not.Quote:
Originally Posted by saaya
The S2E is very unreliable... one moment it boots fine, the next it does not at the same settings...:shrug:
Oh well I will plough on!:up:
So they acknowledge the problem and working on some sort of fix??Quote:
Originally Posted by dinos22
Any possibility of sharing that feedback? :D
well i complained i had some OS corruptions mainly while RAM testing and they asked for more details
nothing specials just detailed hardware configs and bios settings and bla bla bla
when i get some more info will update :)
lets hope the fix doesn't bring some different problems or affect speed we enjoy now :D
haha I see, looking forward to that update!:up:Quote:
Originally Posted by dinos22
Mhh.. When I reported mine to the XFX guys, no one seemed surprised.. :shakes:Quote:
Originally Posted by dinos22
yeah thats what i exprienced as well.Quote:
Originally Posted by BenchZowner
if you select unlinked mode but use a memory ratio which exists in linked mode too, you arent really running unlinked, and it might work fine, while REAL unlinked, using some very odd memory divider will not work.
i talked to two people who then talked to nvidia about this as well, the more sides they hear about this from the better :DQuote:
Originally Posted by dinos22
if you can, hook them up with mike!
i think he had way more corruptions than anybody else here. hes using a professional areca raid controller with 2 120mb/s ssds, so restoring a corrupt windows install takes him 1 minute :D
he said hes blowing windows installes every couple of minutes and then restoring them :D so he probably has a good "map" in his head of where the "minefield" is more dense and where its not so bad :)
and im sure hed be willing to trouble shoot and try different stuff for nvidia, as for him its no big deal to blow a windows install and then restoring it. plus he will be spending the next days home anyways :D
again, get well soon man :toast:
Problems like this are usually not a BIOS problem if nV/MFG hasn't given you a fix or replied to testers with contacts with some future BIOS hope mentioned - that usually always means a hardware problem they know about and are working on a new revision to fix for it. We have no concrete proof for that yet but to me, I would gather it's something along these lines :(
P1/P2.. hmm.. you guys incl. saaya working in RAM firms would probably know - when DDR2 was first released, the white papers all stated channel A, channel B and labeled one channel P1 and the second one P2 for dual channel. I wonder what P1/P2 here is and if the naming scheme derives off something similar... :shrug:
It looks like a BIOS issue to me.
But I won't be the one to touch the fire m8 :p:
If the solution shall require a new revision of the chip... there will be CHAOS :D
Quote:
Originally Posted by BenchZowner
Then I'm glad I got an EVGA in case that happens.
I remember when they let me upgrade via RMA my 680i AR revision mobo for an A1 rev. when it was found the AR's didn't overclock quads well at all.
1333 QDR linked and synced with the memory,evrything on auto and I got a lard lock when I ran memtest from DOS. Actually my board came damagedQuote:
Originally Posted by saaya
http://img169.imageshack.us/img169/6...8061cm6.th.jpg
http://img378.imageshack.us/img378/6...8063ab1.th.jpg
I am now trying to talk to ncix and find out my options. What do you guys think I should do refund or replace???
I would replace it, if you are unsatisfied (let say corruption, ram or FSB problems) then refund it.Quote:
Originally Posted by tekjunkie
I want to see new BIOSes from ASUS :rolleyes:
Here is a little more detailed analyses of the FSB hole on the Striker II Extreme with Intel Core 2 Duo E8400
All of the following will be ran at these configuration and settings;
ASUS Striker II Extreme nForce 790i Ultra
CellShock DDR3-1800
XFX 8600GT XXX Edition
WD RaptorX 10K RPM 150GB
Enermax PRO 82+ 625W
DD Torture Rack
Cooling;
CPU: Arctic Cooling Freezer Pro 7
Motherboard: original heatpipe cooler, reseated with MX-2
BIOS Settings;
CPU multiplier adjusted to maintain as close to 3Ghz as possible.
Memory set UNLINKED at 1800 8-7-6-21 1t P1&P2: AUTO
Voltage: CPU set at 1.35V in BIOS, 1.312 CPU-Z
Memory set at 1.9V
All other settings left on AUTO unless stated otherwise.
http://i225.photobucket.com/albums/d...6/DSC00720.jpg
Upon loading Windows Vista 64, a memory benchmark is performed.
A short run of ORTHOS BLEND of around 10 minute is performed to establish preliminary stability.
A system files integrity check is performed after the ORTHOS run to check for file corruption.
FSB are checked in 25Mhz increments. Where one FSB works and the next setting does not, further FSB speeds are ran with settings in between to establish the starting point of the FSB hole.
FSB350 - boot - window loaded - stable
http://i225.photobucket.com/albums/d...asy_86/350.jpg
FSB375 - boot - window loaded - stable
http://i225.photobucket.com/albums/d...asy_86/375.jpg
FSB388 - boot - window loaded - stable
http://i225.photobucket.com/albums/d...asy_86/388.jpg
--------------------------------------------
FSB389 - boot - hangs before window loaded
FSB400 - boot - hangs before window loaded
--------------------------------------------
FSB401 - no boot
FSB425 - no boot
FSB450 - no boot
FSB475 - no boot
--------------------------------------------
FSB476 - Boot - window loaded - stable
http://i225.photobucket.com/albums/d...asy_86/476.jpg
FSB500 - boot - window loaded - stable
http://i225.photobucket.com/albums/d...asy_86/500.jpg
FSB525 - boot - window loaded - stable
http://i225.photobucket.com/albums/d...asy_86/525.jpg
FSB550 - boot - window loaded - stable
http://i225.photobucket.com/albums/d...asy_86/550.jpg
FSB575 - boot - window loaded - manual voltage increase needed and didnt get it stable enough for ORTHOS run
http://i225.photobucket.com/albums/d...asy_86/575.jpg
Make from it what you will from these data.:up:
I have tried using different memory settings away from 1800Mhz on FSB that weren't able to boot, but they don't seem to help... for example with FSB at 400, setting memory at 1866 still resulted in hanging at windows starting... :shrug:
Sorry for getting ya fooled, the numbers were imaginary :DQuote:
Originally Posted by eternal_fantasy
I'll check it out later on, have to get some work done first, and give you some specific settings to check if you can boot at 400MHz FSB with them.
haha yeah I know, I've tried many different memory settings, but none of them seems to have an effect. the above was just an example. :DQuote:
Originally Posted by BenchZowner
Anyhow looking forward to your results!:up:
Wow, I cant believe that less than 400mhz FSB (388Mhz) still beats 500,525 and 550Mhz FSB in memory read/writing and latencies with L1 and L2 cache. One thing I hate from NVIDIA chipsets.
Is 400Mhz FSB a hole with Yorkfields? Because I might want to keep mines at 400Mhz FSB since it will still be decently OC @ 3.2Ghz with good latency reading/writing speeds.
I use the Stiker II Extreme. I got the following error during post (trying to boot at 9x 400 fsb linked, sync) "ntoskrnl is missing or corrupt and re-install copy of this file to root/.../winnt32". Actually I got excatly the same error during post when I had a WD MyBook connected by eSATA to the Jmicron eSATA (everything stock in BIOS and the Jmicron controller enabled and drivers installed). Unplugging the eSATA cable or plugging it to the eSATA port on the case solved the problem and let me boot.
I suppose this is a sign of the data corruption problem or?
I tried to run "sfc /scannow" but did not succeed since it was asking for my Windows XP Pro 64 CD (the DVD drive letter have been changed since Win XP 64 was installed).
Anybody else experiencing the "ntoskrnl is missing or corrupt and re-install copy of this file to root/.../winnt32" error?
Thanks in advance!
no problem yet here
running q6600 @3825 .. 1700 fsb mem linked 850 7 6 5 18 1t 1,9vdimm 1,42nb 1,53vcore
Wow,eternal good work. I think when all the dust settles with my S2E and when and if I get a replacement, maybe i would go the other way, i.e, keep FSB/QDR constant and run memory unliked with various frequencies. I really think that it's a memory divider/SPP issue which is gonna get better as the BIOS matures.Quote:
Originally Posted by eternal_fantasy
when you enable P1 and P2 it doesn'tQuote:
Originally Posted by slim142
he is only testing FSB holes here
not performance
:up:Quote:
Originally Posted by dinos22
Enabling P1/P2 brings a whole new set of problems I just don't have the strength and will power to test through... :rolleyes:
lol
yeah for P1 and P2 i need cold temps for some reason to get high FSB lol