**The ASrock 939dual-SATA2 (ULi M1695) thread**

Well I'm running my Opteron 144 at 256 x9 = 2300 at default volts
HTT 4x = 1024
memory at 5/6 = 213 (Corsair Value RAM)

I'm using version 1.50 BIOS.
I don't want to try the beta versions, and if I go any higher I have to go an even lower HTT 3x and also an even bigger divider on the RAM, which will both hurt performance, so I think I've found the sweetspot. In any event, the machine will be running 24/7 under full load so although the CPU won't be a problem I don't want to stress the motherboard too much.

A great purchase, and the comments in this thread have been particularly valuable.
 
Dropping the HTT speeds probably wouldn't affect performance. You'd be running the SB-NB and NB-CPU HTT links at a speed of at least 771MHz (257x3). If those HTT are set to 16 bits width, 771MHz HTT gives over 3GB/s of bandwidth. That should be enough.

I agree about the memory, though. That's one reason why I stopped at 250x9.
 
Well, went to Craplins, and picked up a cheap Akasa HS that uses the clip mounting. Not as good, but I'm typing this from the X2 system (YAY! At last!)

As for Flashing the BIOS on this board, is it ok to do it through windows, or the Usual DOS way. Any problems with the 1.50 BIOS?
 
Is it just my set-up or is anyone else suffering from this.

When you elect to restart from within XP, it'll log out as normal, but when it comes to the POST, your screen remains blank, you get some h/d activity(which stops after a few seconds)and nothing else happens? The only way to correct this is to perform a hard boot.

It's an intermitant problem but it seems to do this more when I've manually selected memory timings from within the BIOS, or set the HT multipliers to anything other than Auto. It also does this if I set it to T1(needless to say I just leave it at T2 all the while now).

It doesn't happen when I start my system up.

I think it may something to do with my Crucial RAM as CPU-Z can't pick up the SPD readings :confused:

I'm using the official v1.5 BIOS.

Cheers, dagwoood.
 
Hey all,

Has anyone benchmarked the RAID on this board? I want to run RAID1 (mirror) on a pair of Maxtor Diamondmax 9's (160gb SATA 1). I know this is a 'value' board but I've not seen one review that comments on the RAID controller.

Many thanks,

Andy
 
@dagwood
i had this problem over the weekend (using ocwbeta2 bios)
even managed to wipe all the bios settings back to default
not sure what the rpoblem was but it is intermittant

i had this prob in the past on a socket a dfi board - all i did was switch off, then power up rather than restarting
 
dagwoood said:
Is it just my set-up or is anyone else suffering from this.

When you elect to restart from within XP, it'll log out as normal, but when it comes to the POST, your screen remains blank, you get some h/d activity(which stops after a few seconds)and nothing else happens? The only way to correct this is to perform a hard boot.
Cheers, dagwoood.
Click to expand...

i find that its down to my overclock and the system doesnt like it.

would suggest upping the vcore or reducing the overclock.

on mine i can run fine at 295x8 on 1.4vcore but 300x8 is a not go even with 1.45vcore, it works but on restarting it does the same as the problem u have.

to get mine back i've had to remove 2 of my 4 sticks of 512 memory and boot that way then boot back with the 4x512 in.
 
mp260767 said:
i find that its down to my overclock and the system doesnt like it.

would suggest upping the vcore or reducing the overclock.

on mine i can run fine at 295x8 on 1.4vcore but 300x8 is a not go even with 1.45vcore, it works but on restarting it does the same as the problem u have.
Click to expand...

Mp260767, I don't think it's an overclocking issue as I've had this happen when my systems running on stock settings. I could be wrong though, so I'll bear that in mind when I'm o/c'ing and see if it happens more.
 
dagwoood said:
Is it just my set-up or is anyone else suffering from this.

When you elect to restart from within XP, it'll log out as normal, but when it comes to the POST, your screen remains blank, you get some h/d activity(which stops after a few seconds)and nothing else happens? The only way to correct this is to perform a hard boot.

It's an intermitant problem but it seems to do this more when I've manually selected memory timings from within the BIOS, or set the HT multipliers to anything other than Auto. It also does this if I set it to T1(needless to say I just leave it at T2 all the while now).

It doesn't happen when I start my system up.

I think it may something to do with my Crucial RAM as CPU-Z can't pick up the SPD readings :confused:

I'm using the official v1.5 BIOS.

Cheers, dagwoood.
Click to expand...

The only way I can get mine to do that is to use SysTool to overclock a little further within Windows. Systool will fail to set the higher speed I set but the system is still fully stable while in Windows. As soon as I restart the system hangs.

e.g.
I boot into Windows at 2740Mhz (274x10). I use Systool to set a higher speed of 2800Mhz and it sets that fine. I then use Systool to set a slightly higher speed of say 2850Mhz and it doesn't set it but stays at the previous speed. The system will almost always not restart afterwards and I have to power down to get it to boot again at the bios set 2740Mhz.
 
A couple of quick questions before i go to work :/
Is the latest bios ok for this board or should i leave it for a bit,still has the same bios when i bought it 3 months ago.

And last i have my 2 raptors in raid 0 on sata 1+2
Also i have a backupdrive i want to put on,should i put in the sata 2 red plug?
Thanks :)
 
ns400r said:
The only way I can get mine to do that is to use SysTool to overclock a little further within Windows. Systool will fail to set the higher speed I set but the system is still fully stable while in Windows. As soon as I restart the system hangs.

e.g.
I boot into Windows at 2740Mhz (274x10). I use Systool to set a higher speed of 2800Mhz and it sets that fine. I then use Systool to set a slightly higher speed of say 2850Mhz and it doesn't set it but stays at the previous speed. The system will almost always not restart afterwards and I have to power down to get it to boot again at the bios set 2740Mhz.
Click to expand...

Ns400r, after reading your post, I think this is a problem to do with trying to get compatible monitoring s/w for the m/b's chipset, and is related to our earlier posts( http://forums.overclockers.co.uk/showpost.php?p=6222367&postcount=1002 and http://forums.overclockers.co.uk/showpost.php?p=6222399&postcount=1003 ).

I've been using SysTool to monitor temperatures and voltages and sometimes when I try to open the CPU overclocking option it hangs and I get the XP error message that this program isn't responding. When this happens and I try to reboot my system, I then have to hard boot. Ditto if I try to use Everest to access the sensor readings.

It's an interesting problem as I need s/w to monitor my system why I'm trying to find a stable o/c that I'm happy with, but, the monitoring s/w seems to be the only area of instability :( I ran prime for nearly 7 hours without any errors, but I try to open Everest to check something, that crashes, then I get a restart problem because of it!!
 
cheers
that would explain a few things for me - i have had probs after using systool now that you mention it

the other thing i have used is central brain identifier - will have a go and see if it causes problems
 
Remember that Systool is Alpha software (i.e. it's not stable).

Up until now, Everest has never caused me a problem.
Speedfan has failed to find the sensors on occasions.
Systool has also failed many times in try to open the CPU overclocking page.

In the settings for Everest you can :-

24. When starting EVEREST Ultimate Edition, right after the main window appears it suddenly locks up the computer. How can this be avoided?

Create a new text file in EVEREST folder, name it: "EVEREST.INI". Write the following 2 lines into the new file:

[Generic]

LowLevelSMBus=0
LowLevelSMART=0
 
encephalopathy said:
cheers
that would explain a few things for me - i have had probs after using systool now that you mention it

the other thing i have used is central brain identifier - will have a go and see if it causes problems
Click to expand...
Have Central Brain Identifier now. What do I have to do to try and recreate your problems as it 'seems' stable.
 
ns400r said:
Remember that Systool is Alpha software (i.e. it's not stable).

Up until now, Everest has never caused me a problem.
Speedfan has failed to find the sensors on occasions.
Systool has also failed many times in try to open the CPU overclocking page.

In the settings for Everest you can :-

24. When starting EVEREST Ultimate Edition, right after the main window appears it suddenly locks up the computer. How can this be avoided?

Create a new text file in EVEREST folder, name it: "EVEREST.INI". Write the following 2 lines into the new file:

[Generic]

LowLevelSMBus=0
LowLevelSMART=0
Click to expand...

I was using the freeware version of Everest, which is quite an old version, so it's not surprising I'm having problems with it. I did create the .ini file and opened Everest up. It didn't lock up as it has done, but when I tried to drag the border of the window to resize it, it did it in fits and starts. As an experiment I restarted my system and it locked up again.

So I've removed Everest and SysTool to see if it totally eradicates the restart "hang". I do understand that Beta s/w by its nature is going to be buggy, but it was unusual in that I couldn't re-create the error every time I used Systool :confused:

Thanks again ns400r for your help :)

As an aside, I've downloaded a small utility called Sensorsview. It's a h/w monitoring tool that sits in your notification area and monitors temps, voltages and fan speeds in real time(no log creation functionality though). It's compatible with this boards sensors and you can configure it to show what info you want. Came across it on MajorGeeks. Hopefully I'll have more luck with this s/w.

Cheers, dagwoood.
 
Thanks Dagwoood, i use CPUZ on my PC's but it doesn't like the Asrock. The only way I can get it to work is to start it twice, wait about 5 minutes untill it appears then close the 1st one! I then sometimes get the second session with data for the memory?

I will try Sensorsview in the morning (The nippers asleep now and it's his PC)!
 
You must log in or register to reply here.
Back
Top Bottom