It's impossible to run it stable at DDR333 speeds no matter what. System specs are:
Celeron 1.7
1*256MB Kingston DDR333 CL2.5 Value RAM
ECS P4S5A/DX+ motherboard
Good quality 300W Fortron PSU which worked 100% stable in a high power consuming Athlon XP 1800+ rig (which I ditched in favour of a Celeron).
No, please don't tell me it's a bad PSU. Because I know it isn't. Anyway, the PSU is more expensive that this mother of a board so if I have to choose between the two I'd rather ditch the moboard.
Funny thing is that the system is absolutely stable at 100/133, 'normal' RAM timings and CL2.5. If I set it to 100/166, it would display application crashing errors shortly after booting into Windows. If I set the timings to 'safe' and CL to 3 it seems to work some time (haven't hanged yet). I have to use it longer to be sure, though. But man, these are slower than normal timings and CL3 instead of the advertised 2.5! WTF is this? What did I pay for? For DDR333, which this board can't run. I'm sooo pissed :|. This finally got me.
Do you have any ideas if such behavior is normal for this third-party chipset or is it the board? Any input?
Celeron 1.7
1*256MB Kingston DDR333 CL2.5 Value RAM
ECS P4S5A/DX+ motherboard
Good quality 300W Fortron PSU which worked 100% stable in a high power consuming Athlon XP 1800+ rig (which I ditched in favour of a Celeron).
No, please don't tell me it's a bad PSU. Because I know it isn't. Anyway, the PSU is more expensive that this mother of a board so if I have to choose between the two I'd rather ditch the moboard.
Funny thing is that the system is absolutely stable at 100/133, 'normal' RAM timings and CL2.5. If I set it to 100/166, it would display application crashing errors shortly after booting into Windows. If I set the timings to 'safe' and CL to 3 it seems to work some time (haven't hanged yet). I have to use it longer to be sure, though. But man, these are slower than normal timings and CL3 instead of the advertised 2.5! WTF is this? What did I pay for? For DDR333, which this board can't run. I'm sooo pissed :|. This finally got me.
Do you have any ideas if such behavior is normal for this third-party chipset or is it the board? Any input?
