

Nothing on the monitor. Sometimes the power goes off, but more frequently it just freezes and doesn't respond to network pings."always crashes after a few hours of compiling." what kind of crash? anything on monitor? oops? panic? power goes off
I'm afraid that I can't answer this as I have already RMA'd the memory.is memtest telling you anything consistent about which bank is failin


No. I generally used stock settings --which yielded 1333 for memory, even 'tho it is sold as 1866. I also tested it at 1600 and 1866, with the same results.I'll repeat DONOHUE's question... Are you overclocking anything? I don't know how to equate speeds between Crucial, Newegg, etc.
The UEF| is merely an option that can be used. I chose not to use it, so from my point of view it was just like standard bios.By the way, I've been interested in this board, but am afraid of UEFI. What instructions did you use

Mine did too and the memory in question is on its list.I don't remember any asus motherboard i have brought that didn't include memory module compatibility list in its manual

No apologies required. In fact I enjoyed (and needed) your clear explanation.If this is stuff you already know, I apologize for being pedantic.

I certainly understand that feeling, but gkrellm (via lm_sensors) never showed temperatures over 50C when compiling, and usually they were in the high 30's or low 40's. I may be missing something, but would the load really be high when "j=4" in /etc/make.conf? (while running emerge -eq @world)waiting to fail and failing under load screams overheating to me
Good suggestion, but I will have the replacement memory and the water cooler before turning it on again. Until then, I will have no memory at all in the house.while waiting for replacement memory and/or water cooler it might be worthwhile to reseat the stock cooler with a fresh thin coat of arctic silver or shin etsu thermal grease

It could be something as simple as the memory not getting enough voltage.nlsa8z6zoz7lyih3ap wrote:I have recently built A PC based on
(1) AMD FX-8350 cpu
(2) ASUS M5A97 R2.0 mob
(3) CORSAIR Vengeance 32GB (4 x 8GB) 240-Pin DDR3 SDRAM DDR3 1866 Desktop Memory Model CMZ32GX3M4X1866C10
(memory)
To the best of my knowledge, after considerable reading, these should be compatible.
However the memory fails memtest after a few hours and the PC always crashes after a few hours of compiling.
Heat is not the issue as I have set the make_opt j=4 and this keeps the temp below 50degC.

Thanks for the suggestion I have already learnt lots of interesting stuff that I will use in the future.. I would suggest a little time with google and 'linux thermal zones" would give you some peace of mind.
This certainly gives me an "aha" moment. As I am not an overclocker, I had overlooked the fact that this is promotedIt could be something as simple as the memory not getting enough voltage.
That's something to check in the bios.
1866 is an overclocked memory, which needs higher voltage.
Hi, I have exactly the same problem and partial solution. I bought the same hardware just only two RAM modules(2x8GB) the CPU and motherboard are the same. I had some talk to the seller about this problem, but they refused it saying that this CPU cannot handle such big RAM modules at the speed. I played with the system for a few days and I discovered partial solution. Setting DRAM voltage to the 1.35V(instead the 1.5V default) removed the memory failures with memtest and made the system stable. The downside of this setting is that it won't let you set RAM to more that 1600Mhz.nlsa8z6zoz7lyih3ap wrote:I have recently built A PC based on
(1) AMD FX-8350 cpu
(2) ASUS M5A97 R2.0 mob
(3) CORSAIR Vengeance 32GB (4 x 8GB) 240-Pin DDR3 SDRAM DDR3 1866 Desktop Memory Model CMZ32GX3M4X1866C10
(memory)

I was able to do this with only one module installed, but with two, I was unable to boot and had to clear CMOS in bios to get up and running again. However even with only the one module at 1.35V, I was still unable to compile gcc or chromium without disabling all but cores 1 and 2. Increasing memory voltage makes things worse.Setting DRAM voltage to the 1.35V(instead the 1.5V default) removed the memory failures with memtest and made the system stable.
Did the seller mean that the 8GB modules are too big for the FX-8350 (I could not get them to run stably at ANY speed, no matter how slow (800mghz for ex))I had some talk to the seller about this problem, but they refused it saying that this CPU cannot handle such big RAM modules at the speed.

actually the seller's customer service was quite annoying. They just kept repeating that those AMD CPUs are unreliable and problems are common. They told me to use 2x4G modules at 1333MHz, but it is not acceptable for me. From technical point of view I do not see a reason why "big" 8G modules should be the problem. On the other hand more modules can make the situation worse.Did the seller mean that the 8GB modules are too big for the FX-8350 (I could not get them to run stably at ANY speed, no matter how slow (800mghz for ex))
If so do you know what size of modules it would support. Do you know how I could get information on what memory would run stably with this mob cpu combination.
I spent countless hours fiddling with bios settings and memtest and finally i gave up and bought G.Skill modules.However the memory fails memtest after a few hours and the PC always crashes after a few hours of compiling.

(2) I currently have this running at 1733mhz by first using the mob',s memory overclock tuner, second choosing 1733 for the DRAM speed, and third setting the memory voltage to 1.4000 volts..What was interesting is that for this category of motherboard, "max 32G", when I tried to get ECC DIMMs they would not recommend 32G, but only 24G. I'm presuming that from a sheer numeric point of view, 32G might be right at the top end in terms of bus loading, and when you start adding the extra chips for ECC you go over the limit.
However I am fortunate in getting the 1733 speed. I haven't tried 1866 yet with the new PSU, but that did pass memtest with the old PSU, so perhaps it willSetting DRAM voltage to the 1.35V(instead the 1.5V default) removed the memory failures with memtest and made the system stable. The downside of this setting is that it won't let you set RAM to more that 1600Mhz.
I now believe that the answer is that the cpu does matter. The mob manual states that....... that not all memory compatible with an mob
will work well with all cpu's that are compatible with that mob?
The manual has other such comments as well. While I don't overclock my cpu, the mob defaults this memory to 1333 and claims that I have overclocked it when I set it to anything higher. All of this makes it very difficult to choose parts and design a system from part specifications. For that reason I am very glad to have depontius's helpful commentWhen overclocking, some amd cpu models may not support DDR3 1600 or higher frequency dimms
So thanks to the help of everyone who responded in this topic, I now have a fully functioning system that has not crashed in 3 days.Crucial's web site has a memory configuration tool, where you can punch in the hardware by brand/type/product and they will recommend a memory product
Sadly, I know you asked for the kernel configuration, not the CFLAGS. I suspect that for now you're probably better off with generic, as you have done. I'm pretty sure that gcc-4.6.x won't support "-march=native" for piledriver, so here are some other references.nlsa8z6zoz7lyih3ap wrote: Question: What is the correct kernel setting for cpu type. ? Opteron/Athlon64/Hammer/K8 comes with the advice Select this for an AMD Opteron or Athlon64 Hammer-family processor. │
│ Enables use of some extended instructions, and passes appropriate │
│ optimization flags to GCC Of course the FX-8350 doesn't look to me like and opteron or Hammer family cpu. It doesn't even support all of the instruction set from my previous 4 core.
For that reason I have chosen Generic-x86-64.. Does anyone know if Opteron/Athlon64/Hammer/K8 would be a reasonable or better choice?

Thanks.I'm pretty sure that gcc-4.6.x won't support "-march=native" for piledriver, so here are some other references.