checking 6600 CPU defaults

[BUFF]

OK at 2:3 & 2.8GHz your RAM is running at 465 or DDR2 930 which is just slightly above it's rating & especially if you aren't giving it the recommended voltage (plus 4 DIMMs is a bit more stress for the memory controllers).
I would suggest giving it the recommended voltage & if that doesn't steady it down try dropping to the 1:1.25 divider.

[OldRoy]

Buff, by "recommended voltage" you mean 1.8v? Where is this divider ratio set? I can't find it.
Right now in Guru, the ExtClk is set at 268 Mhz and the DDR2 voltage is 2.0v. I'm getting totally confused about this. And I'm convinced that Guru is buggy - it has crashed the pc several times even when nothing has been reset.
If I load up something to make the processor work it's curently running @ 2412 Mhz.

[Richh]

Ok folks
many thanks for the feedback. You have (as they say) made an old man very happy.

There's something I could say to that, but seeing as this is a family forum... :wink:

(I have no idea what most of these represent except that the frequency looks odd to me as the Corsair ram is rated at 800)

DDR stands for double data rate - the memory is read twice per clock cycle. Ergo, DDR800 memory has a nominal base clock frequency of 400MHz. If you see 408 as the memory clock, your memory is effectively running at 816MHz once the double bit is factored in.

What I'd really like to do is get this all running at safe settings - a bit above minima wouldn't hurt though.

The one thing I would suggest to you now is to calm down and adopt a more structured approach to your build. You are, as things stand, trying to run before you can properly walk, and as a result are getting frustrated with multiple problems while at the same time doing about six or seven other things. Forget overclocking for the time being until you have a stable base configuration. Once you have that, you can start to look for more performance, one step at a time.

Could someone comment on the current values and tell me if there's anything that looks wrong. Then maybe walk me through the sequence of settings required to achieve this. Remember I'm not as sharp as I once was and this is new to me.

The most important thing you need to understand is that overclocking is a fundamentally simple thing to do well, but you're not going to get anywhere with the bull in a china shop approach.

Re; RAID failure.
Well, whenever I tried to set the RAID configuration in the BIOS setup (CTRL I if I recall correctly) I got bluescreen crashes - a couple of times (whilst installing the os).

Eh? You got a bluescreen while you were still in the RAID setup utility (i.e. the ctrl+I part)? Both BUFF and I have posted a link to the raid setup walkthrough on the Abit USA forum. Unfortunately the forum is down just at the moment, but when it comes back, follow the FAQ to the letter and tell us exactly where and how it goes wrong.

I tried to set up the RAID 1 mirroring in XP

You're better off forgetting about that. Windows' built-in software RAID is a complete waste of time and effort. You'd be far better advised getting the Intel hardware RAID to work.

I have looked at the Intel utility which is listed somewhere

You mean the Matrix Storage Console?

Reading them and some of the posts elsewhere on how to set up mirroring on an already configured system, simply left my head spinning.

Again it doesn't help that you're trying to learn so many different things at once. Converting an OS that is already configured in IDE mode to run on Intel hardware RAID is a pest. Again though it can be done and there are some comments on this on the Abit USA FAQ.

This is a bit of a pity. I bought these components with a precise configuration in mind and I'm a bit depressed to have reached the point where I feel I can't hit the target.

Again, calm down, solve one problem at a time, rather than trying to deal with a stack at once.

To make matters a bit worse I was hoping to use Acronis... Unfortunately Acronis won't image dynamic drives - and you can't revert to basic!!! aaarrrgggghhhh.

Dynamic drives are again unnecessary. If you have all your important data previously backed up, you are probably better off just wiping your disks and installing Windows again - this time making sure you get your RAID configuration right from the start.

I have tried a couple of modest tweaks in Guru under Windows. Someone suggested that in my current configuration I should up the RAM voltage to 2.1. I just increased it to 2.0v. In addition I increased the clockspeed to 2.8 (which seemed modest too). Immediate system hang. Is this indiucative of anything other than my own lack of understanding?

It indicates firstly that your system won't run with the settings you selected, and consequentially that you don't know how to overclock properly! Again, cool your jets a bit, plenty of time to learn about this stuff. It's not like your system will be disappointingly slow if running at default speed, so stick to that for the time being.

In fact it has just hung again by opening Guru and looking at the settings. I adjusted nothing - looks buggy to me.

That shouldn't happen. Which version of uGuru did you install, 3.107? If your system is stable, uGuru should certainly run stable - at least in its monitoring mode. As mentioned earlier, using it to switch between different speed/voltage settings can cause lock-ups if you make too big a performance jump, but otherwise it should be stable.

I should add that I have not changed the BIOS on this board.

That means absolutely nothing to us, in a context where we don't know which BIOS was onboard when you got it!

Buff, by "recommended voltage" you mean 1.8v?

No, that's the JEDEC (memory standards body) default for DDR2 SDRAM. Check Corsair's website for their recommendation. I would suspect it's 2.000 volts when running at its default 800MHz DDR speed. If you run above this speed - as you tried earlier, you'll almost certainly need to raise the voltage a little.

Right now in Guru, the ExtClk is set at 268 Mhz and the DDR2 voltage is 2.0v. I'm getting totally confused about this.

Leave the hardware at that setting for the time being. Softly softly catchee monkey.

And I'm convinced that Guru is buggy - it has crashed the pc several times even when nothing has been reset.

uGuru (at least recent versions thereof) is not "buggy" under passive usage. This is another vote in favour of reformatting your system and starting afresh with reliable base hardware settings.

[OldRoy]

Guru version is 3.1.0.3
The only common event causing the crashing seems to be the activation of Guru - even without settings changing. It's happened enough to be more than a coincidence. I haven't seen anything else trigger a crash.
I'll check the BIOS version on next reboot.

BTW anyone who can manage to work out how to install RAID from the mb documentation has psychic powers. This shouldn't surprise me but having written documentation for a pretty big application it offends me. I'd have been fired if I produced documentation missing something that essential.
The problem with the reinstallation of the os is that I have done it so many times trying to install RAID.

The bluescreening I mentioned occurred repeatedly whilst doing the installation of XP after first setting the RAID in bios - not WHILST setting the RAID configuration in the BIOS. I think I said this earlier.

Given the absence of a straightforward description of how to do it there are obviously several approaches and opinions. So one begins to follow one line then some alternative comes along whilst the original contributor drops below the radar. The threads devoted to this sort of thing rapidly diverge into a discussion of the minutiae of interest to very experienced contributors. I could do the same thing if we start a thread about automated pagination systems; maybe not, I'm relieved to have mostly forgotten it all...

So I'm a bit reluctant to start all over again unless it's clearly an unstable system and by and large it doesn't seem to be - unless I touch muGuru.
But I'm learning all the time, even if I'd rather be doing the VR photographic stuff for which I'm building this box.
I appreciate the well-informed suggestions and take note. What I'd like to do right now is run this at baseline, then once I'm sure its stable maybe crank it up a little bit, under advice. If it isn't stable I'll rebuild it, for sure. After an entire week of struggle I'm just a bit weary of it. If my time had much value to anyone else these days this would be an expensive exercise!
Roy

[BUFF]

Buff, by "recommended voltage" you mean 1.8v?

No, Corsair appear to recommend 2.1V for that RAM.

Where is this divider ratio set? I can't find it.

on the IP35 Pro it's in OcGuru > DRAM Speed (CPU : DRAM)

And I'm convinced that Guru is buggy - it has crashed the pc several times even when nothing has been reset.

uGuru isn't perfect but it isn't that buggy - if it's crashing the system as Richh says it's probably because the system isn't really stable in the 1st place.
(or possibly because you have it & CPU-Z open at the same time - there's a known clash as they both seem to want control of the same resources)


Creating a RAID array on ICH8R equipped boards - Universal abit USA Forums

[Richh]

Guru version is 3.1.0.3

Where'd you get that version number from, the installation Setup.exe file, or the uGuru.exe program file? Either way, as mentioned above, 3.1.0.7 is the current one, stick it on and see if the instability gets fixed.

BTW anyone who can manage to work out how to install RAID from the mb documentation has psychic powers.

No, you just need to know how to translate Taiwanese Engrish into English Engrish.

The problem with the reinstallation of the os is that I have done it so many times trying to install RAID.

While it sounds harsh, we're not responsible for the amount of time you've been banging your head against the proverbial. If you want RAID working, now is the time to get it sorted out, as it's far less hassle to reformat a drive with bog all on it than it is to wait, and then be stuck with reinstalling all your apps.

The bluescreening I mentioned occurred repeatedly whilst doing the installation of XP after first setting the RAID in bios - not WHILST setting the RAID configuration in the BIOS. I think I said this earlier.

It wasn't completely clear from what you said exactly where the BSOD was popping up. I inferred that it was during XP setup, but always better to ask, and be certain. Assumptions being the mother of all f**k ups, as you know.

Anyway, this being the case, I would be interested to know which driver you installed via the F6 sequence. If you download the current version of the Intel driver floppy creator from here, and create a new driver installation diskette with it, the correct driver to select is "Intel(R) ICH8R/ICH9R SATA RAID Controller (Desktop/Server/Workstation)"

Given the absence of a straightforward description of how to do it there are obviously several approaches and opinions.

Erm, nope. There may be several opinions, only one of them is correct, at least as far as creating a RAID array prior to OS installation is concerned. The method outlined in the FAQ you've already been referred to works. That's why both BUFF and I have suggested you follow it - to the letter. If you do, and you run into problems, then we know it's not because you're going about it the wrong way.

So one begins to follow one line then some alternative comes along whilst the original contributor drops below the radar. The threads devoted to this sort of thing rapidly diverge into a discussion of the minutiae of interest to very experienced contributors.

There's a danger here that you're starting to sound like you're biting the hand that feeds. If you want to deal with this on your ownsome, you always have that option. If, on the other hand, you're posting in a public forum there's an assumption that you're here to be helped. Your choice, but if you're insistent on doing it your way despite considered advice, just let us know and we can go do something else with the time.

What I'd like to do right now is run this at baseline, then once I'm sure its stable maybe crank it up a little bit, under advice.

If RAID is something you want, now is the time to get it sorted, because it'll just be a bigger pain in the ass in future, and because the blue screens you experienced previously may be a pointer to a system that is less stable than it should be. If this is the case it's better to attack the problem now, and definatively pin down the cause, than skirt round it in the hope that it's not too bad.

If it isn't stable I'll rebuild it, for sure. After an entire week of struggle I'm just a bit weary of it. If my time had much value to anyone else these days this would be an expensive exercise!

Again, without wanting to sound blunt, your head/brick wall interface ain't our problem. However long you spent getting to this point, fact is you're here, now, and you've got some very good advice and suggestions to be getting on with. If you'd rather do your own thing, don't let us hold you back, but equally, don't waste our time asking questions when you're not gonna listen to the answers.

[OldRoy]

"or possibly because you have it & CPU-Z open at the same time - there's a known clash as they both seem to want control of the same resources"
I think this is almost certainly the reason.
"on the IP35 Pro it's in OcGuru > DRAM Speed (CPU : DRAM)"
? I can't see this anywhere in the GUI. Is it only accessible via the BIOS?

[Richh]

"on the IP35 Pro it's in OcGuru > DRAM Speed (CPU : DRAM)"
? I can't see this anywhere in the GUI. Is it only accessible via the BIOS?

Correct. BIOS version of OCGuru only.

[OldRoy]

Rich - don't get me wrong, I know when I'm getting sound advice! That much I do definitely know!
The crashes of late have only occurred (as far as I recall) when CPU-z has been running at the same time. I will torture the beast with some heavy Photoshop interpolations and anything else I can think of. Pity I'm not a gamer t this point.
I'll probably have to abandon this until Sunday as I have some responsibilities that I'm neglecting this week and they are catching up with me. I'll download the update you suggest (I got the version via the .exe properties; if it's appended to the GUI it's well hidden)

Thank you both again. I hope I don't try your patience too much.

Roy