Memory_Management BSOD : F3-12800CL9T-6GBNQ + X58A-UD3R

[chiggah]

Motherboard: Gigabyte GA-X58A-UD3R, revision 2.0
BIOS version: FH
Memory: G.SKill F3-12800CL9T-6GBNQ
Processor: i7-930
OS: Windows 10 Pro, 64-bit
Memory settings : 1.6V, 9-9-9-24 2T
BCLK : Please note I am now running 4ghz (181 x 21 ) but similar settings for the others in images

Few things to note:

- I recently started noticing this bizarre BSOD "Memory_Management" especially upon cold booting. This happens everytime without fail when I come back from work

- I fix it by manually changing any settings (voltage, multiplier etc) in the BIOS and it boots into Windows fine, and also tests Prime95 fine.

- I tried to run Memtest overnight but when I woke up, my computer was asleep...?

- Tried xmp profile1 as per this poster and it gave me 'detecting dram size' crash loop and not able to boot http://www.gskill.us/forum/showpost....0&postcount=11



Can someone please help me ? Still love this machine as the x58 platform is still quite good after 6 years

Screenshots of my BIOS settings and CPU-Z as attached

[chiggah]

Hi, anyone able shed some light on this ? Was thinking to revert back to stock non-overclocked settings and test

[GSKILL TECH]

Settings are all wrong, I'm not sure why you have so many values changed.

Do you have the latest BIOS?

I think the first step is to load BIOS defaults, F5, then manually input settings for the RAM.

DRAM Frequency, timings, and Voltage need to be input.

[chiggah]

Settings are all wrong, I'm not sure why you have so many values changed.

Do you have the latest BIOS?

I think the first step is to load BIOS defaults, F5, then manually input settings for the RAM.

DRAM Frequency, timings, and Voltage need to be input.

Hi there

Thanks for the response

Yes , I am using the latest bios FH 1.29 MB 2012/01/06

WHich settings are wrong ?

I beleive they are correct ?

9-9-9-25 ; 1.5-1.6 Dram voltage

[GSKILL TECH]

Load Line Calibration is unnecessary as nothing is significantly overclocked.

CPU VCore 1.30V for 3.2 -> 3.6GHz is probably too high

QPI/VTT too high, there no need for this.

IOH Core Voltage?

DRAM Voltage 1.64V? It is rated for 1.50V

System Memory Multiplier better off using 10 or 12, leave CPU Host Clock at 133.
CPU Ratio can be increased to OC CPU frequency.

Performance Enhance - Standard

DRAM Timing Selectable - Expert

DRAM sub timings are off possibly because of ratio used or a combination of bad settings.

QPI and Uncore overclock attempt you should probably wait until the RAM and CPU are stable.

You're attempting too many things at once, you need to have a systemic approach to overclocking and tweaking a system.

[chiggah]

Load Line Calibration is unnecessary as nothing is significantly overclocked.

CPU VCore 1.30V for 3.2 -> 3.6GHz is probably too high

QPI/VTT too high, there no need for this.

IOH Core Voltage?

DRAM Voltage 1.64V? It is rated for 1.50V

System Memory Multiplier better off using 10 or 12, leave CPU Host Clock at 133.
CPU Ratio can be increased to OC CPU frequency.

Performance Enhance - Standard

DRAM Timing Selectable - Expert

DRAM sub timings are off possibly because of ratio used or a combination of bad settings.

QPI and Uncore overclock attempt you should probably wait until the RAM and CPU are stable.

You're attempting too many things at once, you need to have a systemic approach to overclocking and tweaking a system.

I will try to load BIOS default. Can I simply use F7 'Load Optimized defaults' ? Or should i press the CLR CMOS button the motherboard itself ?

I'm actually using 1.3Vcore for 4ghz

Yes you are right. It was quite stable at 3.8-4.0 ghz a few years back when I posted here using the settings suggested http://forums.tweaktown.com/gigabyte...tml?highlight=

I went with the below, and other templates online and tweaktown

http://www.overclock.net/t/538439/gu...-930-to-4-0ghz

[GSKILL TECH]

You can try F7 first, but CLR CMOS is a full reset.

[chiggah]

You can try F7 first, but CLR CMOS is a full reset.

I am still getting BSOD after switching the BIOS using F7 optimized defaults

Could this be a faulty RAM ?

[GSKILL TECH]

Test one module at a time to see if a stick performs differently than the other.