I have been trying to configure my mobo to run with my G-Skill ram and so far I have not much luck.
I come up with the "BLUE SCREEN ERRORS" like : "page fault in no paged area" and "bad spool header"
I just ran the windows "Memory Diagnostics Tool" and it came up with an error
***Problem Event Name: MemDiagV1
According to he ram compatatabily chart on Gigbyte support there are only 2 ram manufactures that are compatable with my mobo, and G-Skill is not one of them "but that is nither here nor there" because this is what they have tested so far. So there must be a fix for this.
If anyone has the correct fix for this in the bios settings, could you please let me know
My Computer specs.
Case: Antec Sonata 3
Power Supply: Corsair 650W
Intel Core2 Quad 9550 2.83GHs LGA 775 95W
Gigabite EP45-UD3P Motherboard Rev 1.6
G Skill 4GB (2X2 GB) 240 PIN DDR2 SDRAM 1066
WD 1TB HD
Zalman CNP 9500 Cooling Fan
GeForce GTX 260 Video Card (overclocked)
Samsung 22X DVD+R
More about :solved gigabyte ep45 ud3p bios settings
I have the voltage set to 2.0. I did have it set to 2.1(specs) but all that did was bring up a red block screen in the bios saying " Failures because of overlocking or changes of voltage Last settings in this page may not coincide with current H/W states", So I set the voltage to 2.0.
I did a mem test and it came up with "hardware Failure"
I changed the ram positions from 1 and 3, to 2 and 4.. Did the mem test again, and it passed, no problems......So everything seems to be running fine now with no blue screens.
Why did the errors stop by switching the ram positions?????
If you haven't yet done it, pull out two sticks, start with a BIOS' "Load Optimized Defaults"
Before we start ramping things up, I want to teach you a new skill involving the BIOS: Do the <DEL> at the boot to enter the BIOS;
notice, at the bottom, the <F11> "Save CMOS to BIOS" - hit this, and you should get a menu that will show a number (the count varies by BIOS) of empty 'slots', each of which will store an entire set of BIOS parameters, to be re-loaded from the corresponding <F12> "Load CMOS from BIOS"; this is a wonderful overclocker's feature. What I do with it, is to save my 'baseline' working parameters, so if I change something that 'irritates' the board, and forces a reset of all the parameters to defaults, or, even worse, get so screwed up I need to do a 'clear CMOS', I can get back to my starting point with no effort, and without having to remember 85 separate settings! Another thing it prevents is two hours' troubleshooting, having forgotten a change to a crucial parameter - like, "wait a minute - didn't I have the Trd at seven?!" It's pretty self-explanatory, and I alway urge people to start right away by taking the time to give the 'slots' names that mean something: in two hours, "Try2" and "Try3" will not be very helpful, but "450@+10MCH" and "450@+15MCH" will! Another use is for 'green' settings; overclocks, as a rule, do not 'play well' with green features, such as 'down-clocking' and 'down-volting'; with the storage slots, you can set up one profile, say "Green", with all the settings at 'stock' values, and all the 'green' features enabled; another, say "Balls2Wall" with a full overclock, and all the 'green' stuff turned off... Another neat feature of this 'slot' system is, for most BIOS, the mechanism itself will keep track of which ones have booted successfully, and how many times (up to, I believe, a max of five)!
On the "Advanced BIOS Features" page:
"CPU Enhanced Halt (C1E)" to "Disabled"
"C2/C2E State Support" to "Disabled"
"C4/C4E State Support" to "Disabled"
"CPU Thermal Monitor 2 (TM2)" to "Enabled"
"CPU EIST Function" to "Disabled"
"Virtualization Technology" to "Enabled" - this allows use of Win7's fantastic VirtualXp feature...
"Full Screen LOGO Show" to "Disabled"
On the "Integrated Peripherals" page:
Your manual shows "Legacy USB storage detect", but later BIOS say "USB Storage Function" - either way, set to "Disabled"
On the "Power Management Setup" page:
"ACPI Suspend Type" to "S1(POS)" (for now...)
"HPET Support" to "Enabled"
"HPET Mode" to whichever OS type you're running - "32-bit" if an x86 version, "64-bit" if an x64 version...
On the "MB Intelligent Tweaker(M.I.T.)" page:
"Robust Graphics Booster" to "Auto"
"CPU Clock Ratio" to "8"
"Fine CPU Clock Ratio" to ".5"
"CPU Frequency" - this one can't be set, it's calculated, and will change when we set the next few items...
******** Clock Chip Control ********
>>>>> Standard Clock Control
"CPU Host Clock Control" to "Enabled"
"CPU Host Frequency (Mhz)" to "401"
"PCI Express Frequency (Mhz)" to "100" (not auto...)
"C.I.A.2" to "Disabled"
******** DRAM Performance Control ********
"Performance Enhance" to "Standard"
"Extreme Memory Profile (X.M.P.)" to "Disabled"
"(G)MCH Frequency Latch" to "400"
"System Memory Multiplier (SPD)" to "2.66" (may have a 'D' after it...)
I think your separate "(G)MCH Frequency Latch" which we mostly refer to as a 'strap', and "Memory Multiplier" may relieve you of having to keep track of these by a cryptic letter or symbol in the multiplier table; with yours, you just tell it 'this one'! The strap is the reason we used a 401 clock instead of a nice even 400: the 'straps' are sets of northbridge timings - much like memory latencies, the faster you go, the 'looser' the timings have to be... There are four straps, corresponding to the Intel FSB ratings: 200 (800FSB), 266 (1066FSB), 333 (1333FSB), and 400 (1600FSB - Intel actually does make a 1600 FSB CPU - the QX9775 - but, I think, it's over $1500 a pop!); each strap has it's own set of available memory multipliers (ratios). The 2.66 we used (which is actually a 4:3 bus to bus ratio) is available only on the 400 strap. Anyway, the strap latencies, for some northbridges, don't 'kick in' until one over the selected strap; so, in other words, setting the clock to 401 guarantees that we're getting the 400 latencies/timings...
"Memory Frequency (Mhz)" - again, can't be set, it's calculated...
"DRAM Timing Selectable (SPD)" to "Manual"
You should be able to leave the rest of the memory settings alone; we haven't changed its actual speed, so it should keep working: We simply took it from a system clock of 333 (1333FSB) times a three point two multiplier (333 x 3.2 = 1066), to a system clock of 400 (1600FSB) times a two point six six multiplier (400 x 2.66 = 1066)
"Load-Line Calibration" to "Disabled" (this works differently on different boards - on mine, it's worse "enabled" than "disabled" - the function is supposed to cure a phenomenon called Vdroop - the CPU voltage regulation circuit causes the CPU core voltage to sag, or 'droop' under high loadings; hopefullt, we're going to be at a low enough voltage to just ignore this...)
"CPU Vcore" to "1.2500V"
& "MCH Core" to 1.200V" if you intend to add more than two sticks of ram...
And that should do it!
I should point out that getting two reboots in a row here is perfectly normal behavior; it seems that, when you change certain settings (and we don't exactly know which ones - the only sure one I know is Trd - if you change it, I think you get the 'twin' reboot) it boots once to 'see where it's at', recalculates its remaining 'auto' settings, saves them, and then boots again. Three reboots in a row, however, usually indicates that the board was 'given indigestion' by your settings, and is going back to defaults. This sometimes goes astray, and it doesn't get back into proper operation - for example, at this point, mine will sometimes 'lock' itself into 111MHz x a six multiplier - and take a week to do a whole boot - that's time to do a CMOS reset, and use your 'stored' <F12> profile to get back to where you were...
I ran the memtest and it failed.. Then I moved the ram to slots 2 an4 and ran the memtest again for about 2 hours and it passed with no errors.. My pc is now working fine with no blue screens.
This is the second mobo i had in this case in the last month. The first one i sent back to newegg for an exchange.. I think if I would have used the 2 and 4 slots on the first mobo I would have had the same results.
I now want to contact gigabyte and tell them about the problem I had and how It was resolved. I may want to add ram to the other slots, and if I do, I think I will have the same problems..