|
![]() |
Overclock.net - Overclocking.net > Intel > Intel Memory | |
Help me identify flakey RAM module.
|
||
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) | |||||||||||||
|
Windows Wrangler
![]() |
Hi, my sig rig originally had 12GB of Kingston HyperX DDR3 memory sitting in a Gigabyte UD5 mobo. Two of the 6 modules have died and have been removed, however Kingston only processes RMA's for whole sets (3 modules). I did some research on the batch my units are from and it is known to have hundreds of cases of defective units slipping through QC which all go bad sooner or later due ot no fault of the user. I have thusly been waiting for a 3rd module to crap out on me so i can send the kit back. Well, last week one finaily started going bad. It would sometimes show up as being completely dead and at other times work but cause memory errors until the computer would eventually blue screen.
Well Kingston approved my RMA... and then as soon as I went to test the modules to check which one was dead, they all started working again with no errors. Talk about freak timing. I've been running memtest on these things for days, have done several reboots, and cant get them to give any errors. I KNOW I have a flakey module, and i already have 2 dead ones. I need to send them back as a pack of 3 to gey my rig back up to a reliable 12 gb as opposed to an unreliable 6-8gb. What can i do to identify the bad module? I'd really rather not send in all 6 modules an not have a computer for a few days/weeks. Especially if they're only going to reburbish the units not actually replace them (they took them off the market, no doubt due to the hugely bad reviews because of this batch of almost entirely defective units with hue price tags). For all I know i could end up with more dead modules than i had before if i send them all in. =/
__________________
Systems: Prodigy | Tempest | Arcane Logs: Build Log - Arcane | Video Logs: Project Arcane | Other: Left 4 OCN Zero MMXZ: OCN just autocorrected my "comming soon" to "cumming soon" whynoqueer: o.O Zero MMXZ: mah computer is totally jacking off apparently whynoqueer: Ten point for your computer doing what you should have done LONG ago Zero MMXZ: 0_o i should have jacked off a computer?
|
|||||||||||||
|
|
|
|
|
#2 (permalink) | |||||||||||||
|
Crimson Mantle Commander
![]() |
Run these test on a couple of sticks at a time or just one at a time.Memtest and there is also a memory diagnostic tool in Vista just type it in the start menu.
http://www.memtest86.com/download.html
__________________
Q6600@3.9 http://valid.x86-secret.com/show_oc.php?id=383427 WISCONSIN OVERCLOCKERS![]()
|
|||||||||||||
|
|
|
|
#3 (permalink) | ||||||||||||||
|
Windows Wrangler
![]() |
Quote:
__________________
Systems: Prodigy | Tempest | Arcane Logs: Build Log - Arcane | Video Logs: Project Arcane | Other: Left 4 OCN Zero MMXZ: OCN just autocorrected my "comming soon" to "cumming soon" whynoqueer: o.O Zero MMXZ: mah computer is totally jacking off apparently whynoqueer: Ten point for your computer doing what you should have done LONG ago Zero MMXZ: 0_o i should have jacked off a computer?
|
||||||||||||||
|
|
|
|
|
#4 (permalink) | |||||||||||||
|
Crimson Mantle Commander
![]() |
I can understand that,I would stick in a couple of modules for a period of time(doing your normal stuff or whatever you where doing when the problem occurs) to try to determine which set is causing the problems.Have your tried prime95 blend test with the cpu set to default,that might help you out.GL
__________________
Q6600@3.9 http://valid.x86-secret.com/show_oc.php?id=383427 WISCONSIN OVERCLOCKERS![]()
Last edited by reezin14 : 4 Weeks Ago at 04:57 PM |
|||||||||||||
|
|
|
|
#5 (permalink) | ||||||||||||||
|
Windows Wrangler
![]() |
Quote:
As for running normally/as i was when it was bugging out. I've actually been doing exactly that when NOT running a test, to try to get those errors to happen again - as youve said.
__________________
Systems: Prodigy | Tempest | Arcane Logs: Build Log - Arcane | Video Logs: Project Arcane | Other: Left 4 OCN Zero MMXZ: OCN just autocorrected my "comming soon" to "cumming soon" whynoqueer: o.O Zero MMXZ: mah computer is totally jacking off apparently whynoqueer: Ten point for your computer doing what you should have done LONG ago Zero MMXZ: 0_o i should have jacked off a computer?
|
||||||||||||||
|
|
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
|
|