Ok I built my machine back in Feb. Everything runs awesome! Except my ram! To me this is very odd - Sometimes I can change the timings and run the parts at their rated DDR3 1866 speeds other times I change the settings and Windows (or the Motherboard ???) rejects them and I have to let the board clock them down to 1333MHZ or 1600MHZ. - Which is against the point of me trying to get faster RAM? The board and the RAM both support a Dual Channel config. What am I doing wrong? My build: AMD FX 8350 at 4GHZ water cooled with Cooler Master Seidon 120V Gigabyte GA-990FXA-UD3 rev 4.0 Motherboard G.SKill Sniper Gaming Series RAM DDR3 1866 - 32GBS Kingston SSDNow v300 240gb SSD Western Digital Blue 2TB Sata 3 6.0Gbit\s Cooler Master V850 - 805W power supply - Modular ASUS Blu-Ray burner - 16D1HT Cooler Master HAF 932 Advanced Full Tower Case BitFenix Recon 5 channel Fan Controller 2X Sapphire Tech Vapor-X R9 270X GPUs - Crossfire - 2GB GDDR5 256-bit Mem Interface
I'm not familiar with the GA-990FXA-UD3 but just turning on xmp should be all you need to do. Are you overclocking the cpu? This affects the ram speed, so perhaps the ram gets clocked higher, fails post, then resets to 1333/1600... Just a thought...
I do not overclock the CPU and I turn on XMP it posts it gets to loading windows and then windows crashes in the middle of the boot. so idk what I am doing wrong - even on a clean install with XMP and the timings changed to what the ram says it supports helps in the windows BSOD.
pull the memory, write down what modules you have in what slots mark them if you need to. you might have your A's and B's mixed up if more than 2 sticks of ram, If not try using #1 slot and #3 or #2 and #4. You get the idea. Slot 1 Match a 2 Match b 3 Match a 4 Match b It shouldn't be (most of the time) Slot 1 Match a 2 Match a 3 Match b 4 Match b if nothing else, pulling them and putting them back in the same place still might solve the issue if they only need reseated.
The bsods are always logged. Look in Windows Logs\System. Sort by Level & look at whats listed as Critical...
Nope did not log! - I think it was because it was not in user but kernel mode very preboot like windows logo then death @EFA11 This should not matter - All the RAM is the same model, make, and capacity.
LOL well I did this about a month ago anyways - nothing changed - I think I might RMA the RAM - G. SKill told me if it did not work just tell them and they will send a set that will run at or faster than the 1866 speed
yeah best to rma and try another set if can. memtest never really tests the memory thoroughly imo anyway. Ive run memtest on faulty memory in the past, and the test was fine lol
I dont know why EFA11 says memtest is no good its the program i always use its never let me down. what can happen is you run memtest and it says ram is faulty when really the ram is just not compatible with the mb. i saw 2 possible solutions to your problem but i am prevented from posting links because i need to post 20 times which i find ridiculous this is my last post goodbye good luck. just google GA-990FXA-UD3 1866 and the tomshardware post check them
memtest is great when it works Had a problem that memtest reported bad ram, then I updated bios and now memtest shows everything is fine. I wonder how many people sent their memory back due to this?