Just built a new system this week. I'm using a 6600 Quad chip - here's the specs:
Q6600 Processor
Crucial PC800 Ram (2GB)
P35-Pro motherboard
Thermaltake 750W PSU
Windows XP Pro 32 bit
Nvidia GE Force 8600 GTS card
Overclocked to 3.0GHz
This is a nice, stable platform and overclocking is very easy. Two bugs that reared their heads immediately on this buildup, were minor but annoying. First: MB does not keep proper time; it loses about a minute a day. Second, the 'NUMLOCK ON' status in the system Bios does not work. Even though that option is checked on, when Windows boots up the Numlock is still off.
The uGuru software seems a bit clunky but appears to work. I loaded the utility for Bios Flashing in Windows too, and it reports that my 1.0 Bios is the latest one. I was hoping that perhaps there was another more updated version.
Any other bugs to report anyone? Abit P35-Pro only.
Just built a new system this week. I'm using a 6600 Quad chip - here's the specs:
Q6600 Processor
Crucial PC800 Ram (2GB)
P35-Pro motherboard
Thermaltake 750W PSU
Windows XP Pro 32 bit
Nvidia GE Force 8600 GTS card
Overclocked to 3.0GHz
Any other bugs to report anyone? Abit P35-Pro only.
NEW BUG: The BIOS setup screen goes blank when I do a restart and try to make changes. DEL key will get me into the system setup, but after a few seconds the screen just goes completely blank as if the power was turned off. Requires a COLD boot to regain control.
Hmmm I haven't noticed that many bugs, but I do have some notices.
I've got mine running for nearly a month now. Put together my own pc.
Q6600 Oc'd with stock fan to 3,0ghz Idle 25 C Load (dont know but it's really low cause my feet are getting cold by the airflow in my case)
Abit P35-Pro "off limits" FSB 333 I must say the board is a good board itself.. It's very stable, and does what it's suppost to do. The only thing I'm looking up to are,
The crappish Uguru software in Windows XP ... It doesn't see too much detail and gives false information. The system runs like a dime on 3,0ghz ... Bios overclocking was easy! Just followed some tips and raised the cpu core voltage a little.
I haven't completely tried the software... I just used uGuru to see if it would be a nice program. I also haven't updated the bios yet, or it must have updated itself... It seems pretty annoying to update the bios... and everything runs fine so I don't know if I should update it. Maybe later on. Their website is "Ok" I think their site also notices what has improved in their new BIOS.
I'm not having any trouble atm except I overclocked my memory and the whole system crashed... had to switch jumpers... but then it worked fine again...
Did I miss it, or did you omit the specific mobo ? And I would assume you know what you are doing in the bios... ?... therefore I'd guess the mobo would be bad.
Num Lock ON in BIOS only controls the keyboard until Windows takes over (kind of like USB support... you can use a USB keyboard in BIOS but if the OS doesn't support USB the devices go away when the OS boots). To get Num Lock on at the log on screen you need to change a registry setting. Windows also saves the num lock status (on or off) on a per user basis, so if you logged off with num lock ON, when you log back in again it should be ON again. Kind of annoying but that's MS for you.
Num Lock ON in BIOS only controls the keyboard until Windows takes over (kind of like USB support... you can use a USB keyboard in BIOS but if the OS doesn't support USB the devices go away when the OS boots). To get Num Lock on at the log on screen you need to change a registry setting. Windows also saves the num lock status (on or off) on a per user basis, so if you logged off with num lock ON, when you log back in again it should be ON again. Kind of annoying but that's MS for you.
-mcg
Thanks MCG but there's still something fishy ... I've installed this XP Pro CD on every build I've had since it came out. Every single PC I've installed on, had NUMLCK on in windows. This one doesn't. Of course, I turn it on each time I start the machine when it finally gets into Windows. But on each reboot, once in Windows it is turned off again.
Did I miss it, or did you omit the specific mobo ? And I would assume you know what you are doing in the bios... ?... therefore I'd guess the mobo would be bad.
Maybe you should rename the thread to specify that it is the IP35-pro
I think my dad might have the numlock problem, don't remember precisely, but at least it isn't as buggy as the AB9 pro with the first 20 BIOS revisions it had. Anyone remember the 2A POST code error?
Are you sure you have the latest BIOS?
It's in the lower right hand corner of the BIOS screen...the last two numbers following the dash I believe.
Latest version is 14
NEW BUG: The BIOS setup screen goes blank when I do a restart and try to make changes. DEL key will get me into the system setup, but after a few seconds the screen just goes completely blank as if the power was turned off. Requires a COLD boot to regain control.
During my overclocking trials, this would occasionally happen to me. In my case, RAM wasn't getting enough voltage.
Message edited by fjabad on 01-10-2008 at 01:56:51 AM
Any other bugs to report anyone? Abit P35-Pro only.
Paul, I fired up the beast yesterday evening and am pleased to report, NO BUGS. I noticed my BIOS is 14 but seems to be functioning perfectly.
Yes, uGuru does seem a bit clunky but like you said, it works.
I am not sure, (no, I am sure), that I won't be trying to flash the bios online. I've read too many horror stories including our beloved IP35 Pro. So, with that said, I went to the 'puter store last night and bought a floppy drive. I felt like I was buying a buggy whip. I will do all flashing the old fashioned way I suppose. I truly hate flashing the bios.
Using the Intel stock fan with no heat issues. (20-C cpu temp at idle) Have not stressed it that much and tested yet.
I am very pleased with the performance thus far by the IP35 Pro. No overclocking yet.
