Is this the 8IRXP reboot problem?

[jpetermann]

Ok, I am really frustrated now. I go this 8IRXP and a 1.8a. I have had it to 2.4 with no problems at all, but I had a problem with booting up and with rebooting at times. WHen I cold boot, I always have to hit the reset to get it to boot. The board will hang at the memory test. What can I do, if anything. The board ocks other than this. This is my second one. I actually rma'd my first one thinking there was a problem with the board. I am using the f6 bios.

Thanks for your help,
PJ

 

[Mark0999]

Increase the vcore and vdimm to the next setting. Many of the P4 boards under volt the CPU.

 

[RalfHutter]

Yes, this is the Gigabyte reboot issue. I got rid of my 8IRXP becase of this. Some people claim that the f6 BIOS fixed it, it didn't work for others. See my post in this thread for a little history of this, and Gigabyte's tech support issues.

 

[TLS]

I had the same problem as you and finally figured out that it wasn't the reboot problem but a problem with the memory settings. Most people with the reboot problem have increased the vcore voltage on the CPU. I am overclocking but have never increased the CPU voltage above default. The board was autodetecting the memory as CL2 memory but the memory I have is CL2.5. The memory settings in the BIOS default to SPD with a CAS latency of 2.0. I just manually changed the CAS latency to 2.5 and immediately got rid of the problem. I guess this explains why my board was stopping during the memory check???

System specs
GA-8IRXP BIOS F6
P4 1.6A overclocked to 2.13 (133FSB)
512 MB Kingston PC2100 CL2.5 running at 266mhz
Maxtor 40GB 7200 RPM
GeForce 3 Ti200

BTW
I have found that I get better hard drive performance (SiSoft Sandra) using the Intel ATA100 controller than the Promise ATA 133 controller. Anybody else had this problem?

 

[Barrei]

Hey TLS I have the same board and my memory settings are cas 2.5 and I have cas 2.5 memory , it automatically detects the settings to match my memory and is right , what kind of memory are you using that your board detects cas 2.0 when your memory is really 2.5? Because the board SHOULD detect the right settings like mine does. I can manually adjust the cas settings to go to 2.0 cas , but if I dont manually set the cas it will detect it at 2.5, therefore something is wrong with your memory or your board.