New Memory Tweaker for Intel Chipsets

[Fungus]

I don't think that's exactly possible, because of the drivers. Unless they are kept in resources and loaded on the fly.

[FELIX]

Portable = no installation needed.

Portable apps can be run from anywhere on a drive, or from a USB stick, etc. A portable version of MemSet would be great.

First memset version don't use an installer,
but I need to use it since I added support for OS 64 bit.
It's a drawback come to TVicPort driver.

[Dee]

First memset version don't use an installer,
but I need to use it since I added support for OS 64 bit.
It's a drawback come to TVicPort driver.

Yes, when I tried to make my own portable version I found that it wouldn't run because it gave an error about a certain DLL and TVicPort.

No worries, Felix. Thanks for the reply.

[Steffche]

Hi,

Can someone please explain the Tref value? My memory has a Refresh Period specification of 12us. How does that relate to the values set by the Tref parameter? eg, 3120T etc...

STeve.

[mikeyakame]

tREF = tREFI / tCK

tREFI = self-refresh interval in us, its usually 7.8us but some cases are higher on lower end memory ics.
ie. for 7.8us its value is 7800[ns]
tCK is the clock period,( 1us / ddr_io_frequency )
ie for 1066mhz ddr, tCK = 1000 / 533 = ~ 1.86ns to complete a clock cycle.

tREF = 7800[ns] / 1.86[ns] = 4194 clock cycles in a 7.8us self refresh interval for ddr-1066, since tCK = x[T], tREF = 4194T

Hope that explains it well enough for you mate

edit: additonal info

Self refresh exists on its own plane with no real relationship to precharge, write, read and activate timings as a method of minimizing re-fetching data externally that is lost over time as memory cells lose their charge, and with higher IO frequencies this has a substantial effect on resultant latency, ie if the hit to fetch the data from the CPU is say 60 clocks, then we've added an additional 55ns of latency for 1066mhz ddr, where instead by ensuring that the data is paged correctly in advance the latency to access and read it back is simply CAS turn around + row precharge + read preamble + burst latency + minimum wait to align data strobe with next rising edge of clock. That is best case scenario for a memory read and requires the minimal amount of time to complete, which is essentially why a Higher tREF shows a respectable drop in resultant latency, since any fetching is done while the data isn't being requested so even the worst case scenario of a hard drive read is negligible since it is being done while the data is having a lunch break! It's possible that too large an interval for self refresh may work the opposite and increase latency as memory cells begin to lose their charge before the next self refresh cycle, but theoretically unless the IC's are very poor quality they should hold their charge at least long enough for an extreme worst case scenario that may excessively delay the next self refresh cycle.

[FELIX]

I would not have better made.

Also, higher value is better for tREF.

[Nosfer@tu]

hey FELIX.

get tool, Used it for Years now
Any chance of Intel G41 Support ?

I can help you test if you want

[FELIX]

Could you send a register dump (with cpu-z->last table->register.txt) at memset@hotmail.fr

[Cornflake]

Hi everyone,

I just downloaded MemSet 3.5 to tune my DDRII RAM because my BIOS only allows me to set CAS# latency, not the other 3 values (tRTC, tRP, tRAS, etc). The program works great when changing my timings in-windows as long as I don't do anything stuipid. However, when the program is set to startup and apply the settings when windows loads, it causes my system to completely lock-up. Even when the values are correct. It seems for some reason executing the MemSet\MemSave\MemSet.exe file at any time causes this to happen, regardless of the timings set in the program.

Any ideas why this happens? My system:
Gigabyte GA-M55SLI-S4 mobo with nForce 4 chipset
AMD Athlon 64 X2 5000+ dual core processor (2.6GHz)
nVidia GeForce 8800GTX w/ 177.92 drivers
2GB of G.Skill DDRII ram @ 800MHz (Product name:F2-6400CL4D-2GBPK)
Windows XP Pro SP2

[Compiller]

Hi everyone,

I just downloaded MemSet 3.5 to tune my DDRII RAM because my BIOS only allows me to set CAS# latency, not the other 3 values (tRTC, tRP, tRAS, etc). The program works great when changing my timings in-windows as long as I don't do anything stuipid. However, when the program is set to startup and apply the settings when windows loads, it causes my system to completely lock-up. Even when the values are correct. It seems for some reason executing the MemSet\MemSave\MemSet.exe file at any time causes this to happen, regardless of the timings set in the program.

Any ideas why this happens? My system:
Gigabyte GA-M55SLI-S4 mobo with nForce 4 chipset
AMD Athlon 64 X2 5000+ dual core processor (2.6GHz)
nVidia GeForce 8800GTX w/ 177.92 drivers
2GB of G.Skill DDRII ram @ 800MHz (Product name:F2-6400CL4D-2GBPK)
Windows XP Pro SP2

In your BIOS press CTRL+F1 - it will allow you to change more timings.

[Cornflake]

Nope, already tried that. It does bring up hidden settings, but not for the RAM timings screen

[FELIX]

hey FELIX.

get tool, Used it for Years now
Any chance of Intel G41 Support ?

I can help you test if you want

...support was added for G41 and Q45 in this version: memset359beta
Let me know the result...

[FELIX]

Hi everyone,

I just downloaded MemSet 3.5 to tune my DDRII RAM because my BIOS only allows me to set CAS# latency, not the other 3 values (tRTC, tRP, tRAS, etc). The program works great when changing my timings in-windows as long as I don't do anything stuipid. However, when the program is set to startup and apply the settings when windows loads, it causes my system to completely lock-up. Even when the values are correct. It seems for some reason executing the MemSet\MemSave\MemSet.exe file at any time causes this to happen, regardless of the timings set in the program.

Any ideas why this happens? My system:
Gigabyte GA-M55SLI-S4 mobo with nForce 4 chipset
AMD Athlon 64 X2 5000+ dual core processor (2.6GHz)
nVidia GeForce 8800GTX w/ 177.92 drivers
2GB of G.Skill DDRII ram @ 800MHz (Product name:F2-6400CL4D-2GBPK)
Windows XP Pro SP2

...could you send me a register dump (with cpu-z->last table->registers.txt)
and the memset.ini file you add in C:\MemSet\MemSave\
Send it at memset@hotmail.fr

[radaja]

does any body know why i get this everytime i click spd button? ive tried 3.5.3/3,5,8/ 3.5.9 all do the same thing,thanks

[dinos22]

hey felix did anyone send you a dump file for nehalems

[WaterFlex]

radaja
I have the same situation. Dunno why`s that.

[DMF]

Memset running on P5Q Pro. Notice anything wrong? Hint: the board doesn't support DDR3.


BIOS is 1306. OS is Vista x64 SP1 + updates. DRAM is Mushkin HP2-6400.


Oh, and it's a minor issue but BIOS FSB setting is 416.

[DMF]

With the situation above, what timings are worth experimenting with? tRD?

Voltage is currently 1.82V and I'd prefer not to go above 2.00V.

[dinos22]

this is not a memset issue

other software like CPUz reports the same thing

its a chipset thing

[FELIX]

-> radaja or WaterFlex: could you send a register dump (with cpu-z->last table->register.txt) at memset@hotmail.fr

-> dinos22: I already get some NHM dumps, but Intel datasheet is not available for now,
so don't expect a new beta before 2 or 3 weeks.

[WaterFlex]

-> radaja or WaterFlex: could you send a register dump (with cpu-z->last table->register.txt) at memset@hotmail.fr

Done.

[dinos22]

-> radaja or WaterFlex: could you send a register dump (with cpu-z->last table->register.txt) at memset@hotmail.fr

-> dinos22: I already get some NHM dumps, but Intel datasheet is not available for now,
so don't expect a new beta before 2 or 3 weeks.

oh i see
no worries

[radaja]

im not sure how to do it. but it looks like waterflex already sent it

[DMF]

other software like CPUz reports the same thing

No. CPU-Z 1.48 correctly reports DDR2.

[gymenii]

No. CPU-Z 1.48 correctly reports DDR2.

latest cpuz vs memset.

doesn't bother me cause I know about it and everest reads it fine.