Page 2 of 2
Re: Win7--->Win10 evidently solved a bad problem with T60
Posted: Wed Aug 03, 2016 3:49 am
by ajkula66
Muse wrote:
I suppose one could substantiate the 8GB actual usage by doing benchmarks using 4GB and 8GB in a T61 and comparing the results. Has anyone done that?
I don't know where you're going with this. In a 64-bit environment, *61-series (excluding "Z" units) can most certainly
use 8GB of RAM. When Intel first announced this chipset, 2GB was the largest single DIMM produced and that's where the 4GB limit cited by both Intel and Lenovo comes from.
It's really *that* simple.
Re: Win7--->Win10 evidently solved a bad problem with T60
Posted: Wed Aug 03, 2016 4:39 am
by RealBlackStuff
Fact is also that T61 will always run at 667MHz FSB, even with DDR2-6400/800MHz modules.
The main reason for recommending/using DDR2-6400 modules is, that they run
cooler than DDR2-5300 (and quite often they are also cheaper).
Some more info:
http://www.zdnet.com/article/clearing-u ... confusion/
Re: Win7--->Win10 evidently solved a bad problem with T60
Posted: Wed Aug 03, 2016 1:48 pm
by Muse
ajkula66 wrote:
I don't know where you're going with this. In a 64-bit environment, *61-series (excluding "Z" units) can most certainly use 8GB of RAM. When Intel first announced this chipset, 2GB was the largest single DIMM produced and that's where the 4GB limit cited by both Intel and Lenovo comes from.
It's really *that* simple.
Thanks for the clarification!
Re: Win7--->Win10 evidently solved a bad problem with T60
Posted: Wed Aug 03, 2016 1:49 pm
by Muse
RealBlackStuff wrote:Fact is also that T61 will always run at 667MHz FSB, even with DDR2-6400/800MHz modules.
The main reason for recommending/using DDR2-6400 modules is, that they run
cooler than DDR2-5300 (and quite often they are also cheaper).
Some more info:
http://www.zdnet.com/article/clearing-u ... confusion/
Thanks for this info. I had no idea concerning why PC2-6400 was suggested/recommended.
Re: Win7--->Win10 evidently solved a bad problem with T60
Posted: Wed Aug 03, 2016 4:22 pm
by Muse
I just received my 2 4GB sticks of Elpida PC2-6400 and swapped out my 2GB sticks and now the machine reports 8GB. No surprise there. I think the thing to do is run memtest86 to make sure I don't get any errors. I suppose a single pass is sufficient.
Re: Win7--->Win10 evidently solved a bad problem with T60
Posted: Wed Aug 03, 2016 6:13 pm
by excal32
Good thing I decided to do the free Win10 upgrade on my T60, then?
The X61 remains running Windows 7 as Run10 rubs me the wrong way.... don't like Cortana waiting for me to talk to her.
Re: Win7--->Win10 evidently solved a bad problem with T60
Posted: Wed Aug 03, 2016 7:58 pm
by Muse
excal32 wrote:Good thing I decided to do the free Win10 upgrade on my T60, then?
The X61 remains running Windows 7 as Run10 rubs me the wrong way.... don't like Cortana waiting for me to talk to her.
You can eliminate Cortana annoyances, etc.
How to reclaim your privacy in Windows 10, piece by piece:
http://www.pcworld.com/article/2971725/ ... piece.html:
Re: Win7--->Win10 evidently solved a bad problem with T60
Posted: Sun Sep 18, 2016 3:51 pm
by Sweater Fish Deluxe
Muse wrote:
I have had persistent 2-5 minute timeouts almost daily ever since... until I installed Windows 10 five days ago. Not one since then. There were days I must have had 1/2 dozen such timeouts... they were very aggravating. The computer would become completely unresponsive. Windows Event Viewer Windows log showed iastor() timeouts with the storage device, obviously the SSD.
It seemed I was the only person on the planet who had to say that moving from a HD to an SSD was a terrible experience, all things considered.
Running Intel SSD Toolbox's Optimizer (weekly, and then daily) seemed to slow down the frequency (I may be mistaken there), but it certainly didn't resolve the problem. I thought the SSD might have been bad, but I was uncertain and I let the 3 year warranty slide by. One person posted that if I tried to RMA the SSD, I'd have a very frustrating experience.
I'm glad the update to Windows 10 solved the problem for you, but just in case anyone else is suffering with this and doesn't want to install Win 10, the problem is caused by Device Initiated Power Management (DIPM), which can be turned off in the Intel SSD Toolbox. The program will complain that it's a recommended feature, but the slight increase in power consumption is more than made up for by not having these periodic freezes.
Re: Win7--->Win10 evidently solved a bad problem with T60
Posted: Mon Sep 19, 2016 10:52 am
by Muse
Sweater Fish Deluxe wrote:Muse wrote:
I have had persistent 2-5 minute timeouts almost daily ever since... until I installed Windows 10 five days ago. Not one since then. There were days I must have had 1/2 dozen such timeouts... they were very aggravating. The computer would become completely unresponsive. Windows Event Viewer Windows log showed iastor() timeouts with the storage device, obviously the SSD.
It seemed I was the only person on the planet who had to say that moving from a HD to an SSD was a terrible experience, all things considered.
Running Intel SSD Toolbox's Optimizer (weekly, and then daily) seemed to slow down the frequency (I may be mistaken there), but it certainly didn't resolve the problem. I thought the SSD might have been bad, but I was uncertain and I let the 3 year warranty slide by. One person posted that if I tried to RMA the SSD, I'd have a very frustrating experience.
I'm glad the update to Windows 10 solved the problem for you, but just in case anyone else is suffering with this and doesn't want to install Win 10, the problem is caused by
Device Initiated Power Management (DIPM), which can be turned off in the Intel SSD Toolbox. The program will complain that it's a recommended feature, but the slight increase in power consumption is more than made up for by not having these periodic freezes.
I never noticed the option to turn off DIPM in the Intel SSD Toolbox. Anyway, AFAIK I've had no freezes since installing Windows 10. Windows 10 hasn't been a big problem for me so far and it's solved a huge issue on that machine.