E6850 Oc problem vista 64 bsod when stress test

[Saberous]

well i forgot i switched mobo cause my usb stopped working, now instead of the SE version of the 680i i now have the T1

am going to take some pics that way you will see my bios and there is an option in my bios for sli which ill show in a pic,

Right now i haven't been able to get the stable with my native 1000mhz for my ram its only stable at 800.

this entire time i have been trying to oc from scratch and even at 3.1, 3.2, 3.3 and 3.4 it still has errors

 

[Fumz]

Just FYI, SLI-Ready memory has nothing to do with using your video cards in SLI. It's an nVidia marketing gimmick... and in fact, it may be whats causing you headaches?

It's my understanding that SLI-Ready memory is for people who don't overclock. Enabling it loads a memory profile thats more aggresive than normal and may be a very different profile from what you need in order to achieve higher clocks and keep the board stable. I haven't read all this, but you may want to: SLi-Ready Memory/Enhanced Performance Profiles Overview

 

[Saberous]

well i disabled that setting currently running a test @3.4 20 min so far so good

it looks like my mobo isn't able to handle pc 8000 just got off the phone with evga and they said 667,800,1066 are the ones that work best with there systems, so am going to return them and get the 1066

 

[Fumz]

Yeah, enabling SLI-Ready loads a bunch of other timings besides cas, the rases and cycle time you probably don't want. I'd stick with it disabled and play around till you find something good. You can always run the RAM at 1000MHz independent of that setting just fine.

 

[Saberous]

Yeah, enabling SLI-Ready loads a bunch of other timings besides cas, the rases and cycle time you probably don't want. I'd stick with it disabled and play around till you find something good. You can always run the RAM at 1000MHz independent of that setting just fine.

i can't run the ram @ 1000mhz i keep bsod when i set the ram

 

[Fumz]

If you can't run 1000MHz RAM at 1000MHz then either the RAM is bad, timings are off, RAM voltage if off, fsb voltage is off or any combination of the above; however, you're never going to find out which is it booting into Windows.

Again, you're going to have to start from scratch. That means memtest, not Orthos. You're not ready to boot into Windows yet, and if you keep doing it you may very well end up corrupting Windows... it happens all the time.

Forget about what the chip did on another board with another OS; instead, view this as if you just got all your parts today and have just completed your build. Load the optimized defaults and start the OC process with nice and loose 5-5-5-15 2T timings with default voltage across the board. Make sure that SLI-Ready is not enabled and start going up, memtesting all the way.

Not until you're passing memtest at the speeds you want should you boot into Windows. That's just asking for problems. With respect to memtest, errors in tests 1-4 are fsb related and errors in tests 5 and above are memory related errors.

 

[johngalt]

my 780i runs my ram at 1000 without issues - in fact, if I try to bump the RAM to 1066 it starts BSOD'ing.....

But, yeah, reading the eVGA forums about OCing, one of the first things mentioned is to remove all Spread Spectrum stuff, and really soon after that is to remove SLI and configure your RAM independently. There is also a debate as to whether lower clocks and tighter timings gives more of a performance boost to RAM - I tried that with my system but my system CPU's wall is roughly 3.3 GHz - anything higher and it punts.

 

[xguntherc]

Set your Ram to Unlinked, or off Auto. Set it to 800.. and leave the timings on auto. so it adjusts the timings based on the 800 MHz your runnin it at. and then make sure the ram voltage is set to what that brand suggests.

then try to OC it.. also PC2-8000 is just ddr2-100 MHz ram, so returning it for 1066 is only going to waste time, cost money, and get 66 MHz faster ram, and that wont do anything.. I'd keep what you have. disable any SLI profiles or what not. and just run it at 800.. or try to use link and sync'd. if thats an option and run it at 950 or below.. don't try higher until you get s stable oc.. mkay.

 

[johngalt]

I think he is thinking there is a direct incompatibility with him running 1000 based RAM on a board that supports 1066 'natively' - it the price difference is not too great (~$5 - $15) I wouldn't argue8e against the change as the newer RAM may actually run a bit more stable than what he has in there now.

Since I have the 780 and not the 680, I cannot say one way or another whether it is the board or the RAM causing the issue, but I *an* say that the 780 has no issues whatsoever at running my RAM at 1000.

 

[Saberous]

evga said that the 680i mobo can't handle the 1000mhz ram only the 1066 I said so what's the 66MHz difference in ram going to do? Any way so far i was able to get a oc of 3.4GHz stable for 12 hours but when ever i push it past that i get massive errors, Oh and i went back to 4X1 gig sticks of 6400 ram.

 

[Fumz]

evga said that the 680i mobo can't handle the 1000mhz ram only the 1066 I said so what's the 66MHz difference in ram going to do? Any way so far i was able to get a oc of 3.4GHz stable for 12 hours but when ever i push it past that i get massive errors, Oh and i went back to 4X1 gig sticks of 6400 ram.

You were speaking with someone at EVGA that was reading from a script. The 680i, despite it's limitations, can "handle" 800MHz, 1000MHz and 1066MHz DDR just fine.... guys are doing it all the time. There's a difference between "official support", and "run". The 680i will run your RAM at 1000MHz with no probs if your 680i does not have some prob with the board.

 

[Saberous]

found my prob i keep getting this error when i bsod how do i fix it cause evga doesn't know how to


stop 0x0000016

NVLDDMKM.SYS
FFFFFF.A600381
482e07f5

 

[Saberous]

does anyone now how to fix this??

 

[Fumz]

ok... I'm a glutton for punishment... let's roll. I shouldn't (for my own peace of mind), but, you did ask nice... and I can't turn down a man in need.

First though, you're going to have to ditch every preconceived notion you had in your head about what your stuff "can" do, what it "should" do, or anything like that. It is what it is. Can you run with me on this?

Second, you're going to have to ditch any preconceived notion about what some 16 year old told you on the phone, while reading nonsense from a manuscript, about what your hardware can and cannot do (like that utter bs about your board not being able to run 1066 ram). We still good?

Yes... no... maybe?

We're a blank slate.

The reality regarding, "NVLDDMKM.SYS": there is no fix.

If there was a fix you'd have found it by now. Guys have "resolved" their issues, for the time being, true; but what works for guy A does not work for guys B through Z. Again, there is no fix because both nVidia and Microsoft refuse to accept responsibility for the problem. With neither of them working on a fix, how can you expect one? We can try stuff, but, nothing is guaranteed... still good?

 

[Saberous]

ouch, and so darn true, oh well s.o.l i guess

 

[sctrwsch]

i had a problem with the same memory i ahd to drop the voltage down a bit