yeap

well, for intel, just pump the fsb up and thats it lor...but make sure ram divider is at 1:1 first

Try bios F4, because it seems to have better OCing capabilities, unless of course, you need the bios update to solve some bugs la

If you set your ram timings to 5-5-5-15, did you set it in bios or via windows using memset?

What are the other sub timings you set? other then the ram timings


FSB ocing lor...F3 gives higher FSB ocing but has issues with rams

P35 DS3
average chipset wall is 450 at stock volts

as a really really last resort

take out the battery, cut off the power supply and go to sleep, when you wake up tomorrow, it might boot

Try this timings in bios, set ram divider 1:1 first

Cas Latency time 5
Dram Ras to Cas delay 6
Dram ras precahrge 5
precaharge delay 15
act to act delay 3
rank write to read delay 10
write to precharge delay 13
refresh to act delay 50
TRD auto
TRD precahrge delay auto


Try this settings





many reason for it to KO, can be mobo...ram gc...and the list goes on...best you try the cpu on another mobo and another cpu in this mobo..

Try my suggestion, pop out the battery, turn off the power to the psu and go to sleep, tomorrow when you wake up, retry it, best of luck bro :3

@Are_keem

btw, waht was your idle and load temps with the xigmatek and oced at 2.8ghz?

and what was the estimated ambient temps?

hmm...using wut program?

my HDT-S1283 with bolt-through kit does 51c on load.. and that is undervolting it already...using lavalys :S
and that temp is at nite..when it is the coldest...am i doing something wrong?

im not suspecting your ram, but i am suspecting the TRFC as well as the sub timings from the NB tot he rams...

just try out the settings and see
btw, you can save your old bios settings by pressing F11

you have the bios write protect turned on in the bios, its somewhere inside..forgot which section, consult ur manual book

and tick

- CLear DMI data pool
-Clear PnP data pool

but you will lose all your previous settigns saved. but tis safer to start fresh no?

This post has been edited by bryanyeo87: Nov 27 2007, 12:26 AM

YOu have the bios write protect on in the bios, you need to disable it first and then

Tick the following:
- Clear DMI Data Pool
- Clear PNP Data Pool

drop the cpu multi by 1 and retry

drop the multi to either 8 or 9 and retry with 1:1 la >_>"
as well as use my timings posted (needs to be adjusted etc etc)

hmm ok, so max is 310 fsb at multi 9

try 8 and then 7

from my testing, e2xxx series sort of like 8 multi on the average x__X?

no wor...maybe ur unlucky thats why :S

mine still alive and kicking

Sure its enough.....for how long that is the question

hmm, i found something interesting about these e2xxx series, the max voltage for it is 1.5v as stated on intels processor finder

Sauce:
http://processorfinder.intel.com/details.aspx?sSpec=SLA93





and if you look at the datasheet of the E2xxx series, the max operating voltage is 1.55v

Sauce:
http://download.intel.com/design/processor...ts/31698104.pdf
Page 18, 19 and 20

-all of these are of course including the vdroop la..
- does this also mean that the processor is warrantied up to 1.5v??



anyone can clarify these?

This post has been edited by bryanyeo87: Dec 9 2007, 03:46 AM

@ clawhammer,


duno la bro, maybe use a mulimeter and probe the mobo itself for exact voltage? x_x


the specs says up to 1.5v...does it mean its warrantied up to 1.5v?

Intel c2d chips contains a "blackbox" which records why and how the chip died, the "blackbox" is trigerred whn the processor reaches the specified over temp OR over volt. If it is below that conditions, then the black box will not be triggered.

IIAnm la...

like i said, the black box theory...

Colin, try to ask ur friend, how do they verify the cpu failure.