- Joined
- Oct 28, 2017
Ram (667 running @over 900..sort of)
It's actually low vtt
View attachment 195542
Uodate!: 1.35vtt, errors, but it did delay them showing up when bumping vtt few notches until I reached said value. Now dropped bclck don't want to go above that 1.35vtt voltage. At this point, I'm renegotiating with my NB <--loving this smiley
Update2: this is so much fun, I dunno why, but it is!!
Update3: smack! Again errors. Maybe at this point, it really is ram hickups and not NB. Lowered down to 181bclk, same vtt voltage
Update4: even at 181bclck it would still poop at 4 mins into test. Just to make sure it's not ram, decided to bump dram voltage to 1.6v temporarily
Update5: eh nope, still doing it. Bclock now 180, refused to boot. Power cyxlet, try again, GOLDEN, she's alive!
Update6: still no good, at this point I'm determined to keep that 1800 ram speed(900) and upped vtt 1.375 to see what happens. Having a puppy certainly makes OC easier. Many restroom breaks. He keeps picking,up all these wooden gadgets from yard that I take out of his mouth once we come inside. He doesn't mind though, very sweet about it. As I type I glance at the screen to see if she's still green...eh, blue technically. I'm in memtest86 because if prefer to see her good for some time before I let Windows into the jaws of possibly unstable ram or north ridge. I definitely know cpu is stable because I have 1.268vcore and it's good for up to 3.9ghz, and now I'm at 3.8ghz
Update..#? Whatever: STILL NO GOID! ojay, one last time. 1.4vtt
Update: still refusing grr. Ojay, time for plan, lemme think. Okay, let's try this:
View attachment 195543
Update: just thinking,out,loud as I'm watching the screen. What will,come out of this testing? I can't exactly run my ram at specific values. Its all tied to multipliers and if I'm say at like 4ghz, I can only wiggle 1528 or 1910 for ram. I know it won't run at higher for sure. (191x21) I mean I >could< drop cpu multi and crank bclock to match closer to what I'm testing right now, but I'd rather not go that route. So what's the point? For the sheer adrenaline rush of overclocking? Is this what separates us from regular joes?(no offense to joes) We.Are.Top.
...anyways, getting a bit poetic here, back to regular broadcast. So far 9 mins, soo...lower vtt, ram voltage or increase bclock? Hmm, fascinating
Decision: dram voltage goes down first. 1.5v
Update: great, it ran for 6 mins fine, time,to go down on vtt 1.362vtt
Update: okay, I'm down to 1.35vtt after 6 mins stable. Sorry for documenting all these updates, I'm writing a book.
Update:great 7 mins passed, let's go into Windows and prime! Bah!! She bsod 3 seconds later 124 code
Update: tried increase vcore, still bsod124, okay, let's increas vtt...and it runs longer now! So far 1 minute ojay, but I'm at 1.375vtt (1.2125vcore if anyone interested. 175x21 htON)
Update: its still, GARR!! just right now crashed! It ran fine for uuh, more than 5 mins, just long enough to say night prayer and then crashed! Dropping bclck to 173, keeping voltages same
Observation: interestinf, this new prime only runs like 2 tests of each. My very old version kept grinding like 15 tests of each every time..
Observation2: so I probably *could* get ram a little faster, but unfortunately my NB wouldn't let me, unless I increase vtt beyond 1.37 and probably closer to 1.4, and I don't want to go there. I7 920 needs NB at twice ram speed..
She's passing..been over 10 mins. I'm shutting down
---QUITTING FOR TONIGHT--- end of log for now.
Okay, just one more:
Food for thought.
NB frequencies and voltages.
Up to 2666 - default 1.2vtt
2983 - 1.268vtt
3063 - 1.275vtt
3468 - 1.375vtt (if she's even stable..)
Middle two were tested stable, but I'm sure a notch lower would have worked. I just punched them in maybe a little higher than necessary because I didn't want to fiddle with it after spending time caressing vcore. Didn't feel like optimizing vtt all that much because it was still low enough to be comfortable and passed testing. G'night.
It's actually low vtt
View attachment 195542
Uodate!: 1.35vtt, errors, but it did delay them showing up when bumping vtt few notches until I reached said value. Now dropped bclck don't want to go above that 1.35vtt voltage. At this point, I'm renegotiating with my NB <--loving this smiley
Update2: this is so much fun, I dunno why, but it is!!
Update3: smack! Again errors. Maybe at this point, it really is ram hickups and not NB. Lowered down to 181bclk, same vtt voltage
Update4: even at 181bclck it would still poop at 4 mins into test. Just to make sure it's not ram, decided to bump dram voltage to 1.6v temporarily
Update5: eh nope, still doing it. Bclock now 180, refused to boot. Power cyxlet, try again, GOLDEN, she's alive!
Update6: still no good, at this point I'm determined to keep that 1800 ram speed(900) and upped vtt 1.375 to see what happens. Having a puppy certainly makes OC easier. Many restroom breaks. He keeps picking,up all these wooden gadgets from yard that I take out of his mouth once we come inside. He doesn't mind though, very sweet about it. As I type I glance at the screen to see if she's still green...eh, blue technically. I'm in memtest86 because if prefer to see her good for some time before I let Windows into the jaws of possibly unstable ram or north ridge. I definitely know cpu is stable because I have 1.268vcore and it's good for up to 3.9ghz, and now I'm at 3.8ghz
Update..#? Whatever: STILL NO GOID! ojay, one last time. 1.4vtt
Update: still refusing grr. Ojay, time for plan, lemme think. Okay, let's try this:
View attachment 195543
Update: just thinking,out,loud as I'm watching the screen. What will,come out of this testing? I can't exactly run my ram at specific values. Its all tied to multipliers and if I'm say at like 4ghz, I can only wiggle 1528 or 1910 for ram. I know it won't run at higher for sure. (191x21) I mean I >could< drop cpu multi and crank bclock to match closer to what I'm testing right now, but I'd rather not go that route. So what's the point? For the sheer adrenaline rush of overclocking? Is this what separates us from regular joes?(no offense to joes) We.Are.Top.
...anyways, getting a bit poetic here, back to regular broadcast. So far 9 mins, soo...lower vtt, ram voltage or increase bclock? Hmm, fascinating
Decision: dram voltage goes down first. 1.5v
Update: great, it ran for 6 mins fine, time,to go down on vtt 1.362vtt
Update: okay, I'm down to 1.35vtt after 6 mins stable. Sorry for documenting all these updates, I'm writing a book.
Update:great 7 mins passed, let's go into Windows and prime! Bah!! She bsod 3 seconds later 124 code
Update: tried increase vcore, still bsod124, okay, let's increas vtt...and it runs longer now! So far 1 minute ojay, but I'm at 1.375vtt (1.2125vcore if anyone interested. 175x21 htON)
Update: its still, GARR!! just right now crashed! It ran fine for uuh, more than 5 mins, just long enough to say night prayer and then crashed! Dropping bclck to 173, keeping voltages same
Observation: interestinf, this new prime only runs like 2 tests of each. My very old version kept grinding like 15 tests of each every time..
Observation2: so I probably *could* get ram a little faster, but unfortunately my NB wouldn't let me, unless I increase vtt beyond 1.37 and probably closer to 1.4, and I don't want to go there. I7 920 needs NB at twice ram speed..
She's passing..been over 10 mins. I'm shutting down
---QUITTING FOR TONIGHT--- end of log for now.
Okay, just one more:
Food for thought.
NB frequencies and voltages.
Up to 2666 - default 1.2vtt
2983 - 1.268vtt
3063 - 1.275vtt
3468 - 1.375vtt (if she's even stable..)
Middle two were tested stable, but I'm sure a notch lower would have worked. I just punched them in maybe a little higher than necessary because I didn't want to fiddle with it after spending time caressing vcore. Didn't feel like optimizing vtt all that much because it was still low enough to be comfortable and passed testing. G'night.
Last edited: