*****OFFICIAL OcUK/JW IP35 Pro THREAD*****

I'm having major problems with this board. Granted I'm using BIOS 1.2 BIOS ATM but I just need it to work for now. Anyway, here's my symptoms:

1. I set everything up and got everything working, format HDD, re-install windows/drivers etc. I restored my backup and heard the HDD click 4 times then pause then repeat a few until my PC restarts. It went into some kind of infinite loop so I thought I'd have to start again. Tried to format again and won't get past 0% (just hear that same 4 click loop) So, I'm thinking the mobo has killed my HDD. Great. :mad:. It been solid as a rock for the past how ever many years and suddenly a new mobo and boom, dead HDD, can't be co-incedence.

2. The wireless dongle for my keyboard and mouse sometimes won't light up every boot

3. The PC sometimes freezes when in BIOS. (no overclocking at all)

So, I'm lead to believe that this board is dodgy or more likely that my PSU has given up on me? would this be a correct assumption. Enermax 365W 20pin/4pin 12v (26A on the +12V) is my PSU.
 
yeah, an 80Gb drive is having xp installed on it as we speak...... What do you think caused the failure of the first one? bad settings, faulty mobo or insufficient power from PSU?
 
It is entirely possible (I am not saying this is the case, just being devils advocate) that this was the time for that particular hard drive to fail. When you changed to the new setup, did you move the hard drive, unplug cables etc? all of which could have been the straw to break the camels back so to speak.

However, I feel for ya, having a drive fail is never a good thing, least of all during build-time as you can rarely tell what the root cause is.

However, I don't really think that the mobo is at fault.
 
I've just bought a second Radeon X1950 Pro to run in crossfire on my IP35 Pro but the option is greyed out in the cat control center. Do i need to change any BIOS settings to enable it?

I've reinstalled Cat 8.3 drivers and the crossfire cable is on.

Edit - Do i need 2 crossfire cables connected?
 
Last edited:
Ummugumma said:
I've just bought a second Radeon X1950 Pro to run in crossfire on my IP35 Pro but the option is greyed out in the cat control center. Do i need to change any BIOS settings to enable it?

I've reinstalled Cat 8.3 drivers and the crossfire cable is on.

Edit - Do i need 2 crossfire cables connected?
Click to expand...

You do indeed need 2 Cossfire cables connected, and they have to be oriented the correct way. They usually say H1 and H2 on them. H1 is the card nearest the CPU, H2 is the card furthest from the CPU. This is not pointed out in the manual, but if you hook them up the wrong way you do sometimes get a warning message about missing or misadjusted cables.
 
Ceryndrion said:
It is entirely possible (I am not saying this is the case, just being devils advocate) that this was the time for that particular hard drive to fail. When you changed to the new setup, did you move the hard drive, unplug cables etc? all of which could have been the straw to break the camels back so to speak.

However, I feel for ya, having a drive fail is never a good thing, least of all during build-time as you can rarely tell what the root cause is.

However, I don't really think that the mobo is at fault.
Click to expand...

Too much of a coincidence I think...:(

I have a theory that either the board's IDE controller borked it, or that my PSU did because the board draws more power than my last one? But, I've really no idea...:confused:

EDIT - It wasn't moved during the new build, was still screwed in to the chassis from when I got it, roughly 6-7 years ago.
 
Last edited:
WJA96 said:
You do indeed need 2 Cossfire cables connected, and they have to be oriented the correct way. They usually say H1 and H2 on them. H1 is the card nearest the CPU, H2 is the card furthest from the CPU. This is not pointed out in the manual, but if you hook them up the wrong way you do sometimes get a warning message about missing or misadjusted cables.
Click to expand...


Ok thanks for that.

I'll have to go hunting for another somewhere local to me. Hopefully pc world might have one as that's only 5 mins walk from me.
 
6-7 years? Well, I know I have drives laying around that are that old, and still in use, but none of them as primary drives as the risk of 'clunk.. click... whirrrrr... fizzzle' is too high. The average life of most computer parts, is only 5 years, so 6-7 is good going, but, if you are determined to blame the board, blame it..
 
Cairnsey said:
Too much of a coincidence I think...:(

I have a theory that either the board's IDE controller borked it, or that my PSU did because the board draws more power than my last one? But, I've really no idea...:confused:

EDIT - It wasn't moved during the new build, was still screwed in to the chassis from when I got it, roughly 6-7 years ago.
Click to expand...

I agree with Ceryndrion,

and also, the PSU is not new, right?
 
Last edited:
Right, I've just flashed to the latest BIOS revision (1.4), but I've noticed I now have only two divider options - 1:1 or Auto. And, my command rate setting has disappeared. Why?

EDIT - Also, whats with all those "----------" posts on page 18?
 
Last edited:
Got this board on saturday with a q6600 for my first venture into overclocking. Ive gone for a simple 3GHz (333*9 and a 1:1.2 and upped the volts on the ram +0.20) I am Very pleased with it.

Make sure you install the lan drivers for vista as the ones detected with the vista install give you ipstack errors which lead to bsod's! the drivers on the JW disk sort that out :D
 
What divider do I need to run my RAM at 400 when my FSB is 333? Logic tells me it should be 1:1.2 but it just beeps rapidly when I try this, even though the previous BIOS version (1.2) would run my RAM like this but instead of being 1:1.2 it would be 1:1.6 - giving me 1110Mhz RAM (booted into windows every time, seemed stable, but never tested). Now, for the life of me, I can't get it to do this again. Maybe the flash has changed some other setting to default that I've missed?
 
Cairnsey said:
What divider do I need to run my RAM at 400 when my FSB is 333? Logic tells me it should be 1:1.2 but it just beeps rapidly when I try this, even though the previous BIOS version (1.2) would run my RAM like this but instead of being 1:1.2 it would be 1:1.6 - giving me 1110Mhz RAM (booted into windows every time, seemed stable, but never tested). Now, for the life of me, I can't get it to do this again. Maybe the flash has changed some other setting to default that I've missed?
Click to expand...

Go back to page 18 of this thread and you will see the answer to your memory questions in the form of a super nice table by WJA96.

You know looking through this post thread and you might actually find the answer to most of your questions it woudl also save you from asking questions that has alreayd been answered.
 
Cairnsey said:
Right, I've just flashed to the latest BIOS revision (1.4), but I've noticed I now have only two divider options - 1:1 or Auto. And, my command rate setting has disappeared. Why?
Click to expand...

The Command Rate adjustment did indeed disappear between 1.2 and 1.3, so you'll just have to live with 2T I'm afraid. The RAM options haven't changed, so I'm not sure what's up with yours.

Cairnsey said:
EDIT - Also, whats with all those "----------" posts on page 18?
Click to expand...

It was an off-topic, private, conversation that we've mutually removed.
 
Jumping said:
Go back to page 18 of this thread and you will see the answer to your memory questions in the form of a super nice table by WJA96.

You know looking through this post thread and you might actually find the answer to most of your questions it woudl also save you from asking questions that has alreayd been answered.
Click to expand...

I've seen the table, it doesn't answer my question if you re-read my post (clever ****, lol ;))
 
You must log in or register to reply here.
Back
Top Bottom