![]() |
|
|||||||
| Central Processing Units (CPUs) Advice and discussions exclusively related to Central Processing units. |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
problem when changing to corsair memory - please help
Hi everyone
I have had a new PC built with these specs: Extreme KV2 939 motherboard AMD 64 processor 400w jeantech psu M - audio 24/26 s card Geforce 5200 graphics card 160gb C drive 200gb D drive 2 x 256 memory I use this for audio mixing and for the internet browsing only, so I needed to upgrade the memory. I have now purchased 2 x 512 twinx matched platinum corsair memory When I took the old memory out and replaced it with the corsair memory and then restarted the PC, it starts to load windows but then starts again from scratch ie: rebooting. I have gone into the BIOS and the memory is there, the Booklet with the motherboard states this memory can be used, So its now driving me nuts. Can any of you exerts shed any light on this problem. Many thanks Ian. |
|
||||
|
Re: problem when changing to corsair memory - please help
Hi ian, welcome to itsallPC
![]() It's not uncommon for high performance memory to be unable to run at maximum performance on certain motherboards. Try going into the BIOS and ensuring that the latencies (CAS, tRCD, tRD etc) are set to Automatic or Configure by SPD (Serial Presence Detect). If this is the case, try manually setting higher latencies (higher values give the memory more time to respond to certain actions). As a general rule, new memory should always be tested with a memory diagnostic utility. I recommend Memtest86+. This ensures there are no defects in the module. For Memtest86+, follow these steps: Download the pre-compiled package for floppy (click here for version 1.65. current as of 16/02/06) or ISO (here; version 1.65. current as of 16/02/06). For the floppy image, run the bat file. For the ISO, burn it to a CD. Boot of the media. Allow memtest to complete at least 1 pass. If there are no errors, your memory should be fine. If there is an error, reboot and try again; it's possible for memtest to catch freak occurrences. if the error persists, it indicates a fault somewhere in the memory subsystem that could be the fault of the motherboard, memory itself or the BIOS settings. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|