![save bios settings asus sabertooth x58 save bios settings asus sabertooth x58](https://bjorn3d.com/wp-content/uploads/2015/05/150524022501.jpg)
It suffers from the words Sabertooth x58 to weigh heavily.
#SAVE BIOS SETTINGS ASUS SABERTOOTH X58 DRIVER#
Download Asus Sabertooth X58 Renesas USB3.0 Driver 2.0.4.0. Irvinj in Virginia Beach, VA w.GA-X58A-UD5 LGA1366, i7 920 4.Asus Sabertooth X58 Review Manufacturer. My problem is not quite as bad as some of you for I can live with mine. I was just about to order some different RAM when I checked this forum and found all you people having the exact same problem I have, so I shall save myself some cash and keep plugging along here with what I have. I have tried various adjustments in the BIOS from voltage to MeM timings, flashed the BIOS to the latest and greatest (FB) all to no avail. But allow the machine to be turned off and become cold, turning on the computer will invariably give a incorrect MeM count during POST.
![save bios settings asus sabertooth x58 save bios settings asus sabertooth x58](https://www.manualowl.com/manual_guide/products/asus-sabertooth-x58-sabertooth-x58-users-manual-42810ba/89.png)
After that I can Restart the computer a thousand times and the RAM will always count correctly. I can say this about the GIGABYTE board: during POST if the MeM count is bad I can turn off the power, wait a few seconds till everything settles down and then turn on the power again and usually during this 2nd Cold Boot the RAM is counted correctly. After CPU replacement problem persisted so I had the board RMA'D not once but 3 times! The problem remained. While on the P6T I RMA'D the CPU at ASUS'S request, the TECH told me (after trouble shooting via phone Virginia Beach, VA to someplace in CA) that his test prove its the MeM Controller onboard the CPU. I just came off an P6T utilizing the same CPU & RAM and on both boards I had the same problem. I run with a i7 920 on a GA-X58A-UD5 with 12GB GEIL Black Dragon PC3 10660 1333MHz CL 7-7-7-24, yes I overclock depending upon what I am doing at the time (rendering or word processing) I run 2.8GHz 1333MHz C6 to 4.01GHz 1504MHz C7. I am like everyone else here MeM problems during POST not calculating correctly, sometimes it will be 10GB, then other 8GB and once in awhile 6GB. took one of the good sticks that was in the red slot closer to the socket, plopped that in the furthest one, rebooted. Then it struck me that the black socket furthest from the socket may be 'weaker' than the other 2 like the red ones. Dicked around in the BIOS for about an hour, upping/lowering QPI and IOH trying to find some ratio that would work. I threw 82 83 and 85 in the red slots, thinking those were my best sticks that worked in all slots, trying to get the board to recognize 12GB with 3 sticks, think it worked, but it may not have, can't remember at this point, but it may have cause I moved on to testing all 6 sticks/24GB. So 80, 81, 84 didn't work in the farthest slot, and 82, 83 and 85 did. Got to 82 though and it booted! 83 was good to, 84 no, 85 good. Right off the bat I found 80 and 81 didn't work in the slot farthest from the socket, what I'll call "C." was pretty frustrated thinking this board had another set of bad slots. The serials on each stick end in 80, 81, 82, 83, 84 and 85.
![save bios settings asus sabertooth x58 save bios settings asus sabertooth x58](https://static.tweaktown.com/content/3/6/3613_21.png)
I already knew the black slots don't work if there's nothing in the red, so I started with the red. No dice.ĭecided to be systematic about it, so tested each stick in each slot, or was planning to. no worries, didn't do anything in the BIOS so there was some hope left: upped QPI, enabled the weird asus bios option "lock memory settings" or something like that, etc. RMA board arrived today, threw all 6 slots in it, booted. So, I watch for two things on every reboot.) This is why I stopped my OC attempt halfway. (I also learned the hard way that a CMOS reset turns off the RAID function of the Matrix controller in the BIOS and breaks your array if you forget to change it back. (I haven't attempted to find its limit.)īut I mentioned all of this as although I've only seen it happen once on its first time of being turned on, and although I run it 24/7 and rarely even reboot (right now it's been up 12 days, last reboot before that was nine days previous as well), I still remember to watch for it on every reboot. And the computer was doing absolutely nothing at the time. I have experienced one hard lock with the system. And I did not physically do anything inside the system to the CPU HSF or RAM at all. (First i7 build, was not familiar with this BIOS.) Seeing nothing, and not willing to first think of Mushkin RAM as bad, I did a CMOS reset. I think the BIOS was also reporting 4GB, so I looked in the BIOS for any possible settings causing this. I went ahead and installed updates and rebooted. My first thought was wrong version of Windows, but no.
#SAVE BIOS SETTINGS ASUS SABERTOOTH X58 WINDOWS 7#
Upon first boot, apparently I had this occur and didn't notice it at POST, as Windows 7 was reporting 4GB of RAM once it was installed. Five weeks ago I build an i7-920 system with an EVGA 132-BL-E758-A1 X58 mobo and 3 x 2GB Mushkin RAM and dual GTX 480s.