Learning to OC... is it wise?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
No, EIST is related to automatically adjusting the clock speed. Mostly it's used to downclock the CPU at idle to save power. If you look at CPUZ it usually shows only a 9x multiplier at idle but under load it goes up to 21x or whatever. It also is needed to use Turbo Boost, which requires the use of a few different multipliers.
 
YAY! FOUND IT! well, the fan speed control anyway. it's under "Hardware Monitor", and then Q-fan control or something similar. i saw it earlier, but i didn't change it then because i didn't want to screw my pc up any more than it already was 😛

so now there's just the "no drives detected" issue, which isn't really an issue as windows loads fine, but i'd still like that fixed.

do you have any idea what it could be? i have everything set to IDE, because i got a BSOD when i set the storage control to AHCI. though when i first got it it didn't work because it wasn't in AHCI.... any ideas on that?

and my last question: is it (relatively) safe to start OC'ing again? because now i know that it's safe at 1195 MHZ. though i'll try again with some MSAA.

oh, btw

THANKS WOLFRAM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! you are my hero 😛 i seriously thought i'd ruined my whole pc.

and now i did learn my way around BIOS, so it's actually pretty good that this happened! but now we have to just fix that last HDD issue, but still, THANKS! =D
 
If you installed Windows with it set to AHCI then that's what it should be. If it gives you a BSOD again it's because Windows isn't loading the right drivers. There's a fix for it, but you have to poke around in the system registry.
 
allright. i'll look into it. as for OC'ing, how long should i test if i think i have the right frequency? i just got artifacts and a crash with my mem at 1180 MHZ, with furmark at 1680x1050 with 8x MSAA. is that too much? because i could reach 1205 MHZ, but then again, that was at 1024x768 with 0x MSAA...

edit: apparently the temp matters a lot, even when it's low... i don't get it over 65-70*C, but it ran fine at 1175 MHZ, then i let it pause for 2 minutes, started furmark again and got a crash anyway.... do you have this 'problem' too wolfram? or is this just common in OC'ing?
 
You're still at stock core speed and voltages right?

8xMSAA can be pretty hard on it. Try it at 4xMSAA and see what happens. Maybe start back down at 1150 like this. I find if the test is stuttering a lot it's likely to crash, especially if the stutters are seemingly random or last different amounts of time. The wierd thing about GDDR5 ram is that instead of crashing right away, if there's an error it can just resend the data. You end up with a lower framerate at a higher speed setting. The key is to find that point where you get stability and best framerate.
 
If you have a no name PSU then I suggest you don't overclock anything. I had a Diablotek 550W PSU that fried my GPU while refusing to allow it to even overclock a little bit. The stupid thing gave it bad voltages and fried it.

Of all the components to skimp on when overclocking, the PSU is not it. I happened to have a UD3P board so most of my system survived but I had to RMA the GPU multiple times as a result of said frying.
 
oh... is there any way to check?

looked at my PSU again, it can do 650W =D
i also found the model number; it's an "Advance EA4G-650"
on all +12v rails it can do 18A, on the +3.3V and 5V rails it can do 27A, and on the -12V and "+5Vsb" rails it can do 0.8A and 2.5A respectively.

i'm just typing what it says on the tin, i have no idea what i'm talking about 😛

so what rail do i need to check to see if it has enough amperage? Google isn't being very helpful by showing lots of guitar amps, lol.
 
you are amazing 😛

well ok, but i just got a BSOD saying "page fault in non paged area". i just turned automatic restart off after this BSOD, so should it happen again i'll have time to read it. the crashdump is empty for some reason, but i just tried to open it with notepad and not with anything else. I wasn't overclocking btw, just regular PC use, not even gaming.

i hope it doesn't happen again, and i hope it does happen again because then i'll be able to see it, lol. anyway, could i have (partly)fried my GPU memory? internet says this could happen because there is damaged memory in either the HDD/RAM/GPU mem. i'll run a memtest and lay off the OC'ing for some time, i want to keep my system running :/
 
allright tnx!

though i have another question: last time i tried to get a final memory clock, when it was hot it keeps running at 1195 MHZ, but when pause furmark and let it cool down to idle temps, then fire it up again, i still get a crash. how do i now know when my clock is stable? because crashing everytime can't be good for any piece of hardware...
 
Acutally I had a similar thing happening... AFAIK it's a heat issue with the VRM/VRAM so if you're only using Afterburner you won't be able to see those temps. GPUZ can read them tho, usually. Generally they don't have as good cooling as the core itself.
 
i got another bluescreen... and i think its my HDD. i can now hear it spin-up at boot, which i never could. also the boot was VERY slow, it took it like 3-4 seconds to go from the end of "welcome" to actually showing my background o.o

i don't know if you can do anything with this, but this is what windows says:

Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.1.7600.2.0.0.256.1
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF88004B02817
BCP3: FFFFF88006DB2900
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\011111-26988-01.dmp
C:\Windows\TEMP\WER-38469-0.sysdata.xml

i just left for guitar lessons for about 1 1/2 hour, and left my HDD defragging, because it was time anyway. when i got back my screen was just blank o.o
i think i screwed something up >.<
and i'll stop OC'ing whatsoever, at least until i get a new PSU >.>

update: it's the display driver that's causing those last BSODs! my pc still works! i'm still looking into it though 😛
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom