New Memory Tweaker for Intel Chipsets

[FELIX]

Try with this version: memset

[boblemagnifique]

Support for P35 chipsets coming soon, but I need the datasheet for do that,
and Intel don't provide it for now... probably in June.

Contact me by pm

[xgman]

Any luck on the P35 memset that may work on the Asus PK5 dlx yet?

[Brama]

Any luck on the P35 memset that may work on the Asus PK5 dlx yet?

....and or on Gigabyte DQ6 and similar one?

I am available to test any upgrade, I own a DQ6 with latest bios (F4).

[FELIX]

If memset support P35,it work on a asus and gigabyte or other MB with this chipset, but I need more info for finish the update... coming soon.

[GoriLLakoS]

If you need any help and we can help...please tell it to us

[caesarean]

If you need any help and we can help...please tell it to us

OK, Please see this picture ,PLEASE !

[ziddey]

what's the question???? help with what?? looks like buffalo d9gkx

[caesarean]

what's the question???? help with what?? looks like buffalo d9gkx

Question is,
@MemSet, Display 751.7Mhz
&
@CPU-Z, Display 644.3Mhz

Question is WHY?????, PLEASE

[xs64]

If memset support P35,it work on a asus and gigabyte or other MB with this chipset, but I need more info for finish the update... coming soon.

Nice to hear that. I'm waiting for latest version that support my Asus P5K Deluxe

[ziddey]

Question is,
@MemSet, Display 751.7Mhz
&
@CPU-Z, Display 644.3Mhz

Question is WHY?????, PLEASE

nothing to worry about. trust cpuz.

you lowered your multiplier from 7 to 6. Here's how memset made the calculation:

default / actual x fsb / divider.

so in your case, 7 / 6 x 429 / 2 x 3 = 750

dont worry about it

[FELIX]

Exact, memset don't detect correctly the multiplier,
so if you see a difference in memset between cpu-z, cpu-z is right.
Sorry for this inconvenience, I dont find a solution for now...

[The Stilt]

It seems that there won´t be Memset or any similar programs for P35 or it´s successors.

The dram timing registers of Bearlake chipsets can be read and virtually written, but there is no real effect what so ever.

This is because the different dram timings are more or less tied together by several algorithms that are executed during memory initialization sequence.

In practice this means that the dram timings cannot be changed without resetting the mch. The timings can only be changed from the bios.

To prove a point, I changed dram timings to 1-3-3-7 (tCL-tRCD-tRP-tRAS) on the fly. It is clear that there is no such ram that can operate with those timings at DDR1000 (without mentioning P35 supporting tCL 1 Clocks).

CPU-Z Validation at DDR1000 with 1-3-3-7 timings

To prevent people from cheating in memory overclock / timing records none of this data will be published.

[harleybro]

It seems that there won´t be Memset or any similar programs for P35 or it´s successors.

Darn that is terrible news. Maybe bioses will eventually allow adjustments of all ram timings.

[FELIX]

It seems that there won´t be Memset or any similar programs for P35 or it´s successors.

The dram timing registers of Bearlake chipsets can be read and virtually written, but there is no real effect what so ever.

This is because the different dram timings are more or less tied together by several algorithms that are executed during memory initialization sequence.

In practice this means that the dram timings cannot be changed without resetting the mch. The timings can only be changed from the bios.

To prove a point, I changed dram timings to 1-3-3-7 (tCL-tRCD-tRP-tRAS) on the fly. It is clear that there is no such ram that can operate with those timings at DDR1000 (without mentioning P35 supporting tCL 1 Clocks).

CPU-Z Validation at DDR1000 with 1-3-3-7 timings

To prevent people from cheating in memory overclock / timing records none of this data will be published.

...I'm not surprised of that for tCL, it's already the same for P965 chipsets.
But for tRTC and others, it's a bad news... perhaps more infos in datasheets.

[The Stilt]

...I'm not surprised of that for tCL, it's already the same for P965 chipsets.
But for tRTC and others, it's a bad news... perhaps more infos in datasheets.

Yes, tCL is not a surprise, but everything else is "locked" too.
I doubt the datasheet will make any difference, since I have already talked with one of the chipset architects who was working on Bearlake.

[ziddey]

wonder why they decided to do so that way

[dinos22]

bugger

[RealTelstar]

boo

one point minus to p35... maybe x38 will be less locked

[IluvIntel]

I've already got one P35 board, not buying anymore till' this is fixed. IF it gets fixed...

[xgman]

It seems that there won´t be Memset or any similar programs for P35 or it´s successors.

The dram timing registers of Bearlake chipsets can be read and virtually written, but there is no real effect what so ever.

This is because the different dram timings are more or less tied together by several algorithms that are executed during memory initialization sequence.

In practice this means that the dram timings cannot be changed without resetting the mch. The timings can only be changed from the bios.

To prove a point, I changed dram timings to 1-3-3-7 (tCL-tRCD-tRP-tRAS) on the fly. It is clear that there is no such ram that can operate with those timings at DDR1000 (without mentioning P35 supporting tCL 1 Clocks).

CPU-Z Validation at DDR1000 with 1-3-3-7 timings

To prevent people from cheating in memory overclock / timing records none of this data will be published.

ouch!!! I was counting on Memset to come to the rescue here.

[GazC]

Well, that's a kick in the nuts

Edit, I just got it, 1337 timings for DDR1000 lol!

[The Stilt]

[The Stilt]

Good news for Gigabyte users and bad for Asus users.

It seems that only Asus is locking the dram timings registers since they can be actually written on Gigabyte boards.

There is something in Asus bios that makes MCHBAR locked.

The MCH programming is completely different between Asus and Gigabyte.
And so is the MCHBAR address. Thats why the testers could not get any data extracted.

Atleast tRCD, tRP, tRAS can be changed on Gigabyte.
I haven´t tested the other timings yet.

[ziddey]

OH BOY! :thumbsup: