erm...firstly i do set the cpu voltage to 1.35
but it doesnt help, until i have to reset the cmos in order to start my cpu

but i dun see any digit like 1.35 there..

nono...before this screenshot 0.0
this is my 2nd try

Any possibility the PSU is the culprit?? TS, if u shut down your PC about half and hour, and then u switch on, does it able to boot?

when i turn off the psu, and replug it

it still got possibilty to boot my computer without reset the cmos

---

Added on September 25, 2008, 10:35 pmand i tried to use 2 rams only...and it wont works = =

This post has been edited by hong1380: Sep 25 2008, 10:35 PM

btw, i just saw ur advanced bios feature option there.
under 'init display first', u shud set to [PEG] not [PCI]. dis one makes u boot from ur PCI-E card first.

actually, i hv nearly the same mobo as urs, same proc (but different VID). but then, my OC not as painful as urs.
ask u smtg. did u mount ur heatsink properly??normally,334X 9 sure can boot a Q6600 without even up a single notch of Vcore by default.

ok la.try another way.if u fail again, u reset ur bios.
Disable CPU Enchance Halt ( in Advanced Bios Feature)
Disable CPU EIST (in Advanced Bios Feature)
Disable CIA2 ( in MIT)
Enable CPU Host Clock Control (in MIT)
CPU Host Frequency set to [334]
PCI Express Frequency set to [100]
Performance Enchance [Standard] <--if u get ur system stable only mess wif dis. got something to do wif ur performance
System Memory Multiplier [2.0] or [2.4] or [2.5] <<<- any setting which is below and closest to 1000 Mhz of ur RAM specifications
System Voltage set to [Manual]
DDR2 Overvoltage [+0.2]


u try dis setting see can or not. things tht i din mention, dun touch pls.

i think the heatsink ok gua..
when i change the intel stock cpu cooler to ccf
maybe i applied too much thermal paste on it...will it affect the cpu to boot@@?

---

Added on September 25, 2008, 11:02 pmis it my ram causing the cpu cannot boot?
cuz my ram doesnt blink at all...and others seems running

This post has been edited by hong1380: Sep 25 2008, 11:02 PM

check if ur rams are in place properly... sometimes people tend to forget that their rams are not in place.....

hmm..double check alr..
normal setting...can boot
once i change the setting....cant booot

Wait you said 2x1GB doesn't work? Might be a RAM issue then. Ok do this: (Use all 4 sticks of RAM)

1. Reset CMOS to default. (9x266, all voltages default).
2. Bump system memory divider up until you get your memory frequency as close to 1066 as possible. Don't go above 1066 yet.
3. Bump Vdimm to 2.0
4. Run memtest: http://www.memtest86.com/
5. Tell us whether your RAM passes =p

my ram's memory frequency looks like run in 800 instead of 1066mhz..
how do i increase it to 1066?

if not,i cant set it near to 1066= =..
oh ya, btw how to set / where to check the vdimm, i searched from google seems cant find the exact answer

The system memory divider controls your DDR2 frequency. Change it until your memory frequency gets to as close to DDR2-1066 as possible.

Vdimm is the DDR2 overvoltage control. It's all there in your first screenshot. I thought you read the guide already?

erm...from the screenshot,
memory frequency 800 640

i change the multiplier and makes the 640 become close to 1066 right?
but the 800 - -?

Correct, the '640' as close to 1066 as possible without going over. That will be the max tested stable speed (hopefully).

640 represents the speed derived from your FSB times your multiplier. 800, you can't do anything about don't worry.

now im running the memtest using default setting

Ok I've never used the one in Windows. Prefer the one with the bootable image. Oh well, test all 4096MB and see how it goes =p

What's the frequency of your RAM now?

i think 533 mhz now

So the number reported where 640 used to be is 533 or 1066?

now...the fsb is 266 multiplier 2.0

---

Added on September 26, 2008, 3:08 amthe 640 is using 320mhz frequency and 2.0 multiplier
which oced


This post has been edited by hong1380: Sep 26 2008, 03:08 AM

Sigh ok stop the test. Set the multiplier to 4.0 pls, so the number reported is 1066.

Then, rerun test.