Discuss Problem mixing two similar memory modules in the Memory forum on Dev Hardware. Problem mixing two similar memory modules Memory forum for discussing chips and modules from brands such as Corsair, Patriot, OCZ, Mushkin, G.Skill, Crucial and Kingston. Learn to fix RAM problems, overclock memory, adjust latencies, change timings, and use Memtest86.
ASP Free and Iron Speed Designer are giving away $5,500+ in FREE licenses. Iron Speed's RAD CASE toolset can save up to 80% of your coding time. One free license per week, one perpetual license per month!
Receive the tools necessary to be the rock star of your field. Our 12-month program teaches you the evolving world of multi-channel marketing as well as the complex issues and opportunities found in the industry.
The ASP Free website provides in-depth information on the latest developer tools available from Microsoft. Our cadre of writers, highly experienced industry experts, reveals the best ways to use established technologies as well as new and emerging technologies. Our coverage of Microsoft's development and administration technologies is among the most respected in the IT industry today. .
Posts: 3
Time spent in forums: 42 m 22 sec
Reputation Power: 0
Problem mixing two similar memory modules
I am new to this forum. By the way, sorry for my horrible English.
I have a Dell 530s with 2 GB of ram (2 x 1 GB) and I bought two additional modules (up to the maximum: 4 slots x 1GB). Apparently new and old of different brands but all the same technical characteristics: 1 GB each, DDR2-666 MHz PC2-5300U CL5-5-5-15.
Initially Vista-32 bit said that the 4 GB were correctly installed, but some days later I began to suffer unexpected system restarts. Then I searched the web looking for the details of the message I received, and most of the similar cases pointed to ram among other possible causes. Memtest gave immediately some errors so, I removed the new ram and the problem disappeared.
Now, I still have the opportunity of changing the modules at the shop, but I should do it tomorrow or the day after tomorrow. So, if someone could help me so quickly, I would appreciate any advice.
Details of the old modules: Hinyx(Hyundai) HYMP512U64CP8-Y5 DDR2 1GB/64 @ 667 MHz 16x(64Mx8) CL5-5-5-15
New modules: Corsair VS1GB667D2 DDR2 1GB/64 @ 667 MHz 8x(128Mx8) CL5-5-5-15
I guess all of them should be 64M and not 128M. That's the only difference I can observe. If that was the case, alternatives available at the same shop are:
1) Buffalo DIMM 1 GB DDR2-667 Valueline (64Mx8) CL5-5-5-15
2) Dolphin DIMM 1 GB DDR2-667 (64Mx8) CL5
3) takeMS DIMM 1 GB DDR2-667 (64Mx8) CL5-5-5-15
Price makes no difference. I would appreciate a quick answer
Location: Centrally located in the middle of nowhere, CA
Posts: 9,250
Time spent in forums: 10 Months 3 Weeks 2 Days 14 h 2 m 52 sec
Reputation Power: 17383
As long as the pairs are appropriately socketed in the correct banks, then there shouldn't be a problem with the mixed brands.
I would suggest you reinsert the 'bad' modules and make very sure they are installed correctly and the locking tabs click into place-- it may be that one went in a little cockeyed and worked initially, but over time came loose enough to cause problems.
Once installed, run memtest again and verify whether the modules work or not. If you don't get failures immediately, let memtest run for a good 24 hours or better to get some good heat-tolerance testing.
"In front of a monitor is a dangerous place from which to view the world." --Terri Wells
Enable BSOD: Control Panel/Systems, Advanced Tab, hit the Settings button under Startup and Recovery, and under the System Failure area, uncheck the Automatically Restart checkbox.
Posts: 3
Time spent in forums: 42 m 22 sec
Reputation Power: 0
Quote:
Originally Posted by Dngrsone
As long as the pairs are appropriately socketed in the correct banks, then there shouldn't be a problem with the mixed brands.
I would suggest you reinsert the 'bad' modules and make very sure they are installed correctly and the locking tabs click into place-- it may be that one went in a little cockeyed and worked initially, but over time came loose enough to cause problems.
Once installed, run memtest again and verify whether the modules work or not. If you don't get failures immediately, let memtest run for a good 24 hours or better to get some good heat-tolerance testing.
Ok. I'll do it so tomorrow morning and will check every module individually. I suspected not from being different brands but from some other technical detail such as the 64Mx8 - 128Mx8. Thanks for your quick answer.
Posts: 3
Time spent in forums: 42 m 22 sec
Reputation Power: 0
I've been testing both modules this morning, one by one, and the result was that one gave errors from the first second, and the other is still on test, but without errors for 4 hours. So, apparently, one is defective.
Anyway, the shop now doesn't have availability of those modules, so I will return both and will change them by a pair of exactly the same modules, but in kit (2 x 1 GB, for Dual Channel). In three or four days I hope to have them and test them again.
Your diagnostic, Dngrsone, seems completely correct. Thanks a lot.
Posts: 1
Time spent in forums: 12 m 14 sec
Reputation Power: 0
Quote:
Originally Posted by Dngrsone
As long as the pairs are appropriately socketed in the correct banks, then there shouldn't be a problem with the mixed brands.
I would suggest you reinsert the 'bad' modules and make very sure they are installed correctly and the locking tabs click into place-- it may be that one went in a little cockeyed and worked initially, but over time came loose enough to cause problems.
Once installed, run memtest again and verify whether the modules work or not. If you don't get failures immediately, let memtest run for a good 24 hours or better to get some good heat-tolerance testing.
Very useful posting is this.Really it is important for me and i think for others also.
Thanks for this important posting.
LOADING INFUSIONSOFTLOADING INFUSIONSOFT 1debug:overlay status: OFF overlay not displayed
overlay cookie defined: TI_CAMPAIGN_1012_D
OVERLAY COOKIE set:
status off