You will probably need to increase Vmch and Vtt as well once you get to the higher FSBs.
[WTA] Overclock problem
[WTA] Overclock problem
|
|
Sep 25 2008, 04:27 AM
Return to original view | Post
#1
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
You will probably need to increase Vmch and Vtt as well once you get to the higher FSBs.
|
|
|
|
|
|
Sep 25 2008, 11:47 PM
Return to original view | Post
#2
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
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 |
|
|
Sep 26 2008, 02:35 AM
Return to original view | Post
#3
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
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? |
|
|
Sep 26 2008, 02:48 AM
Return to original view | Post
#4
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
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. |
|
|
Sep 26 2008, 03:01 AM
Return to original view | Post
#5
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
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? |
|
|
Sep 26 2008, 03:05 AM
Return to original view | Post
#6
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
So the number reported where 640 used to be is 533 or 1066?
|
|
|
|
|
|
Sep 26 2008, 03:09 AM
Return to original view | Post
#7
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
Sigh ok stop the test. Set the multiplier to 4.0 pls, so the number reported is 1066.
Then, rerun test. |
|
|
Sep 26 2008, 03:12 PM
Return to original view | Post
#8
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
OK, so your RAM isn't the problem. Probably the board then.
Try going 1Mhz at a time la. |
|
|
Sep 26 2008, 05:40 PM
Return to original view | Post
#9
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
No la not his RAM. He proved his RAM is fine d via memtest. TS, your proc should have no problem at all at 333x9.
I'd say your motherboard is faulty. Try flashing it la, if it doesn't help, RMA board. |
|
|
Sep 26 2008, 06:31 PM
Return to original view | Post
#10
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
Tested d man =p
Can't be anything else, has to be the board. |
|
|
Sep 26 2008, 11:00 PM
Return to original view | Post
#11
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
Can try to RMA la. I'm sure his board is rated for more than 266FSB, which is what he's getting now. If it can't get to 333, I'd RMA it.
|
|
|
Sep 29 2008, 09:22 PM
Return to original view | Post
#12
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
Don't spam pls. TS: any updates?
|
|
|
Sep 30 2008, 04:55 AM
Return to original view | Post
#13
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,864 posts Joined: Jun 2008 |
I think it's exactly as per his sig. Very weird tho, the P35-DS3 should have no issues.
|
| Change to: | 0.0174sec
0.58
7 queries
GZIP Disabled
Time is now: 10th December 2025 - 09:22 PM |