• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Vcore on E6600

B

brock01

Member
Hello
just wondering what are some symptoms of not enough vcore being put out?
application stability? bsod? besides not booting, or all the way booting
and how much do you think i even need at 3.5ghz on my E6600, or whats more than enough- right now i have it at 1.4375
 
What is happening to your PC at that speed?

Donwload and install "orthos" or Prime95 to test your pc's stability.....

If it passes, your Voltage is good enough. If it doesn't, up the vcore some more.

My E6600 needs 1.48-1.5 for 3.6ghz!
 
for some reason its not orthos stable, at 385*9 but its stable at everything else it seems like
i get some random bsod's but i think that is my vid card related
also when i lowered my vcore it was lasted longer in orthos then when it was higher
 
What board, psu, cpu cooler do you have?


What are your temperatures like?

Download Coretemp or the Intel Thermal Analysis tool (TAT)


What about your RAM? Manual timings or by SPD?
 
58 is getting sorta high imo. I would shoot for sub-50 on a dual-core OC (I have an X2 though).

I'd consider 1.43v low for voltage. My plan was to see what clocks I could get out of 1.5v through a C2D, but I planned on using water. There are plenty of people pushing 1.5v through a C2D on air though, but not necessarily with the Zalman 9500.

If you're failing Orthos, either increase the voltage or lower the clockspeed. Your BSODs are probably caused by CPU issues. That's why we use stress programs like Orthos/Prime95/etc; they show us potential weaknesses. If you fail Orthos, then that's probably an indication that your CPU is the issue.
 
Fix your problem. Don't worry about what other people's chips are at...those will of course clock differently from yours! If it fails Orthos, its not stable. Simple as that.
 
58c is high -

See my sig - E6600 @ 3.4 - 1.49 vCore - Big Typhoon cooling - idle at 35c - Running orthos up to 49c

Nice

Lou
 
Originally posted by: LouPoir
58c is high -

See my sig - E6600 @ 3.4 - 1.49 vCore - Big Typhoon cooling - idle at 35c - Running orthos up to 49c

Nice

Lou
Click to expand...



What are you using to read temps with Lou?

 
Originally posted by: Technonut
Originally posted by: LouPoir
58c is high -

See my sig - E6600 @ 3.4 - 1.49 vCore - Big Typhoon cooling - idle at 35c - Running orthos up to 49c

Nice

Lou
Click to expand...



What are you using to read temps with Lou?
Click to expand...

Asus PC Probe2 - supported by bios readings at idle of course -

Lou

 
Originally posted by: brock01
anyone else have a E6600 oced, and if so what do you have it oced to and how much vcore you got it at?
Click to expand...

Mine needs 1.25V (1.2V actual) to be Orthos stable at 3.2Ghz. It needs 1.43V (1.38V actual) to be Orthos stable at 3.6Ghz.
 
Originally posted by: LouPoir
58c is high -

See my sig - E6600 @ 3.4 - 1.49 vCore - Big Typhoon cooling - idle at 35c - Running orthos up to 49c

Asus PC Probe2 - supported by bios readings at idle of course -

Lou
Click to expand...
Download TAT or CoreTemp, and you'll be 56-59°C runnig Orthos. That's why Technonut was asking.
 
what does it mean if in orthos i can run the "Small FFT's - stress cpu, i can do that for hours and no erros
but if i do the "Large in-place FFts - stress some ram" i get errors
this is with the orthos beta that does both cores
 
Originally posted by: brock01
what does it mean if in orthos i can run the "Small FFT's - stress cpu, i can do that for hours and no erros
but if i do the "Large in-place FFts - stress some ram" i get errors
this is with the orthos beta that does both cores
Click to expand...



More than likely, your RAM is not stable..... Run Memtest86+ to find out.
 
i ran memtest for 8hrs last night at 800mhz (1:1) and i got a ton of erros, vdimm at 2.2 with timings of 4-4-4-15
 
It has been my general experience that BSOD is a result of RAM failures. Your CPU's stability can be easily checked using Prime95 set to Small FFTs, just make sure that you run two instances. I'm running at 3.8 GHz with 1.54V on a P5W DH Deluxe at the moment but my CPU is at close to 0C under load so my results aren't typical. I built a cooler out of some abandoned pieces of equipment around my dorm and a $20 budget...
 
Try changing your divider to see if your ram still giving your errors. You might have reach your mem's ceiling.
 
kinda weird, when i run orthos beta, on the large fft test, i runs for 10-11 and stops
but the small test for the cpu works for 7+hrs stable
any ideas?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top