If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
There is no main core temp that the BIOS displays. The temp in the BIOS is from a sensor in a different location. This in general can be ignored. You may want to investigate if the temperature is very high, but other than that the only temps worth bothering with are actual DTS sensor temps derived from distance to TJMax.
To see those temps, as you may know, you need a piece of software such as RealTemp or CoreTemp, and if possible (ie if your sensors aren't stuck at idle like mine are) you should calibrate the readings before trusting their accuracy.
Coolermaster CM 690 II advance Case Corsair HX750(CWT, 91%(80+ Gold rated @230V) single 62A 12V rail P55A-UD4 v2.0 @ F14 Core i5 760 @ 20 x 201, 4.02GHz TRUE Black with a single Noctua NF-P12pumping out 55 CFM @ 19db. 2 x 2GB Mushkin Ridgeback (996902), @ 7-10-8-27, 2010-DDR, 1.66v 2 x Gigabyte GTX 460 1024MB in SLI (Pre OC'd to 715MHz core and 1800MHz VRAM) @ 850 Core / 4100 Mem. Intel X25-M Boot Drive (OS and Programs) 200MB/s Read & 90MB/s Write Corsair X32 200MB/s Read & 100MB/s Write WD Caviar Blue 640GBC (Steam, Games, Storage, Temp Files & Folders, etc) Samsung F3 500GB Backup/Images Noctua 1300RPM 19dBcase fan (rear extraction) 3 x 140 MM Coolermaster LED fans (one front intake, one top extraction, one side intake) Dell Ultra Sharp 2209WAf E-IPS @ 1680x1050
That is true for some boards. In my experience it's usually older or lower end models (P43, P33 etc) that have hidden features.
Most current boards will still respond to [Ctrl] + [F1] by blinking the screen, but there's no extra settings revealed. I guess Gigabyte have realised it's pretty pointless hiding features and adjustments. Makes sense, as if it were designed to stop the less experienced breaking components then they wouldn't let us set 2V+ Vcores.
Coolermaster CM 690 II advance Case Corsair HX750(CWT, 91%(80+ Gold rated @230V) single 62A 12V rail P55A-UD4 v2.0 @ F14 Core i5 760 @ 20 x 201, 4.02GHz TRUE Black with a single Noctua NF-P12pumping out 55 CFM @ 19db. 2 x 2GB Mushkin Ridgeback (996902), @ 7-10-8-27, 2010-DDR, 1.66v 2 x Gigabyte GTX 460 1024MB in SLI (Pre OC'd to 715MHz core and 1800MHz VRAM) @ 850 Core / 4100 Mem. Intel X25-M Boot Drive (OS and Programs) 200MB/s Read & 90MB/s Write Corsair X32 200MB/s Read & 100MB/s Write WD Caviar Blue 640GBC (Steam, Games, Storage, Temp Files & Folders, etc) Samsung F3 500GB Backup/Images Noctua 1300RPM 19dBcase fan (rear extraction) 3 x 140 MM Coolermaster LED fans (one front intake, one top extraction, one side intake) Dell Ultra Sharp 2209WAf E-IPS @ 1680x1050
That is true for some boards. In my experience it's usually older or lower end models (P43, P33 etc) that have hidden features.
Most current boards will still respond to [Ctrl] + [F1] by blinking the screen, but there's no extra settings revealed. I guess Gigabyte have realised it's pretty pointless hiding features and adjustments. Makes sense, as if it were designed to stop the less experienced breaking components then they wouldn't let us set 2V+ Vcores.
Indeed, the only thing I've found with CTRL+F1 on my UD3P is under "PNP/PCI Configurations" I can change the PCI Latency Timer from the default of 32.
Well I'm an idiot, I was still using f9b and was getting the issues with the cpu case, system and nb temps dropping out after sleep until the pc was rebooted. I guess all these issues including the low cpu temp was fixed with f9c. Sorry, I'm a tard for thinking I was running f9c. Yay gigabyte and bios geeks! Thanks everyone.
Well I'm an idiot, I was still using f9b and was getting the issues with the cpu case, system and nb temps dropping out after sleep until the pc was rebooted. I guess all these issues including the low cpu temp was fixed with f9c. Sorry, I'm a tard for thinking I was running f9c. Yay gigabyte and bios geeks! Thanks everyone.
Hey Dank, I want to ask you did you use Q-Flash in all your bios's from going to f9a f9b and f9c?
Hey Dank, I want to ask you did you use Q-Flash in all your bios's from going to f9a f9b and f9c?
Yeah I use qflash. Qflash with the bios on a usb stick has worked great everytime. I will shuttdown, clr cmos, boot, load optimized, reboot, flash, reboot, load optimized, then set my settings. Sometimes I'm lazy and don't clear the cmos cause it's really overkill. Flashing makes me nervous though but that's probably typical of anyone that has bricked something flashing firmware before.
Well, I updated to bios f8f. Didn't really help for my booting problem, but I investigated the problem further. Now I had to do the power off / power on cycle from power supply about 10 times until my PC succesfully booted, but this time with default clocks (2.66ghz). I also got a message that said something like "Boot failures happened because of overclocking or voltage settings" during the post sequence after the successful boot. This didn't happen before.
That is strange, because I can run prime95 without problems for 10 hours (highest core temps according to realtemp and coretemp is about 75 c with my Noctua cooler) with my moderate overclock (3.4ghz) when my pc successfully boots.
So why does my mainboard refuse to post and says it's because of oc? Is it a problem with the board, bios, or is there something really power consuming going on when my pc boots? Like I said, Prime95 with 100% load on every core goes on without problems for 10 hours. All voltages should be within safe limits (vcore 1.200, dram 1.64, qpi 1.335, ioh core 1.12). I bought the UD5 board and not the cheaper ones because I wanted to be able to safely overclock a little, so I can safely say this sucks.
New GA-EX58-EXTREME F8g BIOS works for me. (Although I haven't used any of the ones between F8b and F8g.)
-It's fixed the reboot loop problems I used to have when trying to disable Hyperthreading.
A few issues though, I still can't seem to get it to boot up to Windows at 20x multiplier with a Bclk of 200 (4GHz). I used to be able to get it to boot at 4GHz (not stable) but can't even get it to do so now...
I also have 12GB (6x2GB) of 1600MHz Corsair Dominators; they're 2 6GB kits. It keeps locking up at the Windows 7 loading window unless I set it to 1200MHz. Is this an issue that can be resolved through other settings or maybe a future BIOS revision? Or is it a limitation of Intel's memory controller or just the RAM itself?
Thanks for any help. I can provide more detailed settings and specs if necessary.
New GA-EX58-EXTREME F8g BIOS works for me. (Although I haven't used any of the ones between F8b and F8g.)
-It's fixed the reboot loop problems I used to have when trying to disable Hyperthreading.
A few issues though, I still can't seem to get it to boot up to Windows at 20x multiplier with a Bclk of 200 (4GHz). I used to be able to get it to boot at 4GHz (not stable) but can't even get it to do so now...
I also have 12GB (6x2GB) of 1600MHz Corsair Dominators; they're 2 6GB kits. It keeps locking up at the Windows 7 loading window unless I set it to 1200MHz. Is this an issue that can be resolved through other settings or maybe a future BIOS revision? Or is it a limitation of Intel's memory controller or just the RAM itself?
Thanks for any help. I can provide more detailed settings and specs if necessary.
It seems Gigabyte mb:s are not really suitable for overclocking. I downgraded my EX58-UD5 to official bios v F7 and I can now boot ok with default clocks, but the mb refuses to boot with overclocked settings unless I do power off / on cycle for 5-10 times.
After I finally get successful boot everything works fine, but the very annoying power cycling mess definetily was not what I thought I'd get for my 250 euros when I bought the mb. Next time I'll spend my money to more reliable brands.
Comment