Recent content by rogelio

I had noticed corruptions (permanent) in windows with F10 as well... it's so funny (yet sad :( ) that you mentioned that. I had problems using alcohol 120 mounting drives, some files were corrupted in windows, and other stuff... I restored from a ghost backup prior to using F10, and the...

I have no doubt that this board was pushed out to beat others in the market... at the cost of numerous issues that have continued to surface (memory issues). I would like ALL of you who continue to experience problems to please email me with a detailed description of both the hardware and...

Well... even with my new board from 2nd RMA... still having memory issues. I'm back to about a year ago when I was having video game crashes with 2 sticks of RAM. So... I upped the voltage to the ram to 2.7v (0.2+v). I also tried something new... upping the voltage +.1 to the AGP...

F9 Seems to be running fine *so far*. I would have to concur with joesmith123456, beware of F10! They should never have released that BIOS, let alone, in the final (and not BETA) release section.

I've RMAed my board... and I'm still getting weird artifacts/problems in XP (with the F10 bios, I might add). Here are a couple screen caps of what I'm talking about... This is probably somehow due to the F'd up F10 bios. (I'm running 2 sticks of 512MB Corsair DDR400). Previously, I was...

A single stick of RAM must always be in Slot 1 (placing it in Slot 2 or 3 will result in a memory-test error beep)... when you use a second stick, you may place it in Slot 2 or Slot 3. I agree about the memory limitations at running at DDR400 speeds... Gigabyte just seems to disregard this...

I had suspected from the beginning that there was some defect in the memory controller because of stability... I had to keep upping the voltage to the RAM... eventually it got to the point where it could only function with one stick before giving a posting error and freezing up in the bios...

Bullman... I HAD EXACTLY THE SAME PROBLEM! I was the first to purchase the K8NS Pro... except now mine doesn't work with ANY memory at all anymore.

My mobo finally kicked the bucket. I suspected it was the memory controller (or rather, the flow of power to the memory controller) from the beginning. Had to do a DDR voltage bump with 2 sticks, wouldn't work with 2 sticks (only 1) ... then had to bump the voltage up again... and now it...

I *wish* I could run two sticks of 512 PC3200 at 333MHz. Problem with mine is severe instability and lock-ups in 3D games with 2 sticks (running underclocked at 333MHz). I've done a complete test on my RAM (Tuff Test) at every inteveral and the results are always that the RAM is in tip-top...

Sounds very possible that Gigabyte had a bad batch of boards with memory controller problems (in handling two ram sticks). It's just such a pain in the arse to have to RMA the board and swap out the CPU and all the devices. I wish I could just "Trade-in" my two sticks of 512mb corsair pc3200...

Yup... tried everything, new bios, upping dram voltage, trying 2 different sticks of pc3200... nothing works.

Looks like i'll never be able to use 2 sticks or more of RAM... causes crashing and severe instability when I use the 2 sticks of 512 Mb PC3200 Corsair DDR. You think it's possible Corsaiar would send me a single stick of 1 Gb PC3200 for my two sticks of 512 Mb... considering the rather...

Hmm... Vestan Pance Looks like it VERY WELL might be a "bad batch" of mobos with DRam controller issues that develop over time. Urghh... I really can't do an RMA now (as I have 3 months of college left until winter break... in which case... I won't be able to take my PC home to rebuild)...

I had been running 2 sticks of 512 Mb at the default (undercloceked) 333 MHz. After 3 months I got persistent crashes in 3D games (still running underclocked at 333)... I upped the DRam Voltage and that solved the problem... for a month. The only way I can run stable now is to have only 1...