• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Anyone have experience with Kingston Warranty Replacement?

mplutodh1

Senior member
I purchased some ram from Fry's over the holidays. Kingston ValueRam to be exact and since then my system has rebooted several times. At first I thought it was a driver issue but once I put back in my older 2100 the system is stable. Anyone have experience with the lifetime warranty specifically through Frys?
 
Maybe the RAM needs a voltage bump? Is this in your OC'ed Barton riggie? If so, don't be shy about giving the RAM a little more voltage. Try 2.6 volts at least, if it's vanilla PC3200.
 
if it is less than 30 days, just take it back to Fry's. Kinston otherwise is pretty good at replacing defective products. Just call their 800 number, they will happily take the bad RAM back.
 
Yeah, Kingston is reasonably fast - they will usually cross-ship on a credit card for security. My non-CC RMA took about a week - I shipped First Class Mail, they shipped FedEx...
.bh.
 
I've never had bad Kingston RAM, but I have sent back a couple bad nics, they must've been like $20 or so cards and Kingston promptly sent me new cards with overnight shipping.
 
Lower voltage would cause the system to reboot? I kept getting the "unknown device driver error" then two or three times I got a CPU error report.

I guess I can try playing with the voltage. I have the system running back at 2600 speeds though, not OC'd.
 
Hey mech... any advice on the voltage situation? what should i do about it, would it matter that if I wasn't OC'd
 
Thanks... I have it cranked up to 2.8 right now to see how stable it runs. Is that ok? I tried 2.7 but when it booted up it came up with the device error at boot...

Default it was running at 2.6
 
Back
Top