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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |