overclocking to 4.2-4.4ghz help

Status
Not open for further replies.
good job :thumbsup:
Download hwmonitor, start it, then run LinX for a while.
Post up a screenshot so I can see your idle and load temps.

overall that's a pretty nice OC you've got
 
good job :thumbsup:
Download hwmonitor, start it, then run LinX for a while.
Post up a screenshot so I can see your idle and load temps.

overall that's a pretty nice OC you've got

this is the lowest voltages i got if i go lower i get an error on LinX

http://i265.photobucket.com/albums/ii234/nybadboy767/2010-04-15220222.jpg

and this is the temps with those settings



I WAS JUST RUNNING Prime95 AND I GOT A BLUE SCREEN that means the system is not stable right and my temps were at 77 MAX
 
Hmmm, your temps are spread very wide. I'd suggest reseating your heatsink, make sure you only apply a small amount of thermal paste about the size of a grain of rice.

Also, you may want to get rid of that incriminating evidence on your desktop ;) illegal torrenting isn't tolerated here
 
Hmmm, your temps are spread very wide. I'd suggest reseating your heatsink, make sure you only apply a small amount of thermal paste about the size of a grain of rice.

Also, you may want to get rid of that incriminating evidence on your desktop ;) illegal torrenting isn't tolerated here

lol i deleted the pix anyway is that why i get a blue screen ?
 
The blue screen means the system is unstable. What was the error code?

Bump up your voltages a little more. If you post the error code I may be able to give your more specific advice on which voltages to raise.
 
The blue screen means the system is unstable. What was the error code?

Bump up your voltages a little more. If you post the error code I may be able to give your more specific advice on which voltages to raise.

i will run prime95 again but i wont be able to tell because it gives me like 5 seconds to look at it

so this is how it was befor

http://i265.photobucket.com/albums/ii234/nybadboy767/2010-04-15225610.jpg

and after

http://i265.photobucket.com/albums/ii234/nybadboy767/2010-04-15225907.jpg
 
WHAT THE ****! You've taken off the cpu support?! that's BAD! put it back on!

Also, you can get rid of that extra fan on the mosfets. You'd only need that if you were gonna clock higher. Right now all it'll be doing is impeding airflow.

and yes, about that much thermal paste looks good.
 
WHAT THE ****! You've taken off the cpu support?! that's BAD! put it back on!

Also, you can get rid of that extra fan on the mosfets. You'd only need that if you were gonna clock higher. Right now all it'll be doing is impeding airflow.

and yes, about that much thermal paste looks good.

i will put that back now lol



*edit*
WHAT THE ****! You've taken off the cpu support?! that's BAD! put it back on!

Also, you can get rid of that extra fan on the mosfets. You'd only need that if you were gonna clock higher. Right now all it'll be doing is impeding airflow.

and yes, about that much thermal paste looks good.

ok i put back the cpu support how can i tell what is the error ? the blue screen just pops up and restarts the pc it counts some memory dump
 
TechSpot OpenBoards - View Single Post - win home laptop bootloop (bsod flashes to fast to read)

I'd suggest setting the QPI/DRAM to 1.29375v and the vcore to 1.28750v
Decrease one at a time. Feel free to do it in bigish steps (say by decreases of 0.0125v) until you start erroring. Then bring it back up by 0.0125v again and test for an hour with LinX. If it passes, lower it by 0.00625v and test for at LEAST an hour in LinX.

Once you've got one as low as it will go, move onto the next voltage.
 
TechSpot OpenBoards - View Single Post - win home laptop bootloop (bsod flashes to fast to read)

I'd suggest setting the QPI/DRAM to 1.29375v and the vcore to 1.28750v
Decrease one at a time. Feel free to do it in bigish steps (say by decreases of 0.0125v) until you start erroring. Then bring it back up by 0.0125v again and test for an hour with LinX. If it passes, lower it by 0.00625v and test for at LEAST an hour in LinX.

Once you've got one as low as it will go, move onto the next voltage.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041510-20139-01.


The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff8000336656d, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041410-17456-01.
 
Status
Not open for further replies.
Back
Top Bottom