Still shaky, but running! HELP

[fireandsmoke]

All,
As I said earlier, I replaced the Gigibyte mobo and OCZ stick for
KX7 333R and Corsair pc3200C2, Since I fired it uo and put a new install of xp on it, I've had nothing but problems! I've had to reinstall XP 4 times, as it continually has corrupt/missing file errors about <windows root> \system32\ntokrnl.exe or
\windows\system32\config\system I also installed a new HDD
These errors are non recoverable and the system will not re-boot into windows no matter what I do with the bios (defaults)
It does this when I start messing with FSB, at 150 it dies. It's some Windows XP related problem??? When I toggle through the user definable CPU types it displays xp2100/xp2200, so I think it's a current enough mobo to recognize the unlocked xp2200. I just changed the bios to 133 X 10 and it's still running. Here's all
SoftmenuII
CPU Op Speed - User Define
CPU FSB - 133
Ratio (FSB:AGP:PCI) - 4:2:1
Multiplier - 10
Speed Error - Dis
Enhance for benchmarks - dis

DRAM clock - by spd
Dram timing - manual
Cas - 2.5
Bank Inter - dis
Trp - 3t
Tras - 6t
Trcd - 3t
Dram Queu - 4 level
DRAM command - 2t command

I know the memory and board are good for more, but I'm afraid to crash windows again...Do you guys see anything?? Should I flash the latest bios?? And how? The website gives very nebulous directions on flashing the bios. Is Win XP unstable?? Any suggestions please!!
F&S

[TheDude]

I would examine your unlock job on the cpu...will it let you select different multipliers and actually boot with them?
Are you upping the core voltage when it fails at 150fsb? What is your current core voltage set to?

[docah]

What drive are you using ?
I have two hdd's here that DIE at 155fsb.
Western digital BB drives.

[MrLavender]

Try 166 fsb with 5:2:1 ratio, then the PCI/AGP bus is not overclocked. PC3200 should run max timings at that speed.

Note that on my KX7-333, LOWERING the cpu multiplier requires a CMOS reset otherwise it doesn't work. What a pain.

[fireandsmoke]

Thanks all,
Yes the cpu unlock is good, on the previous mobo and this one I have all multi's. I put in a new Maxtor d740x 40gb. And the default core voltage is 1.66, do I need to up the voltage only going to 150?? And to reset your multi, you've got to shut her down, clear the cmos and start her up again?? How about the flash??
F&S

[TheDude]

I dunno if you would need to up voltage at 150...but if it fails..it is worth kicking it up a notch to see.

[fireandsmoke]

UPDATE:
Running at 10 x 165, going to burn in the rig overnite @1.69v
We'll see...
F&S

[fireandsmoke]

And another, tried 167 and got blue screen with error info, it was recoverable and as MS says a "serious error"
It said these were the naughty files...
C:\WINDOWS\Minidump\Mini091302-02.dmp
C:\Documents\Myname\Locals~1\temp\WER2.tmp.dir00\s ysdata.xml
Any ideas????
F&S

[QuadDamage]

looks like your ram is crapping out (hard to believe) or your HDD. is your hdd getting hot? tried upping voltage supplied to cpu/ram? tried swapping ram in diffrent slots? always use 5:2:1 ratio no matter what. tried upping VIO? maybe your VGA doesn't like high fsb(?) tried lowering multiplier as low as possible and cranking up fsb as high as possible? (to rule out crappy ram stick) tried getting rid of all (i said all) pci cards? disabling USB ports?

[MrLavender]

I have the same mobo, hd and worse memory (Corsair PC3200 CAS2.5) than you and I've run 3dmark on a 210 fsb with no problems apart from agp tearing.

But I get best results at 175fsb with max memory timings - 12016.

These are my settings (Athlon Tbird 1.33);

Softmenu III
----------------

CPU Speed - User Define
CPU FSB - 175
Ratio (FSB:AGP:PCI) - 5:2:1
Multiplier - 8.5
Speed Error Hold - Disabled
Enhance for Benchmark - Disabled

Core Voltage - 1.85v
DDR Voltage - 2.85v

CPU Fast Command Decode - Fast

DRAM Clock/Drive Control
--------------------------------

DRAM Clock - 166
DRAM Timing - Manual
DRAM CAS Latency - 2
Bank Interleave - 4 way
Trp - 2
Tras - 5
Trcd - 2
:
:
Enhance DRAM Performance - Enabled
DRAM Access - 2T
DRAM Queue Depth - 4 level
DRAM Command Rate - 1T

Put the memory in DIMM1, not DIMM4 like it says in the manual. Until I did this I couldn't get it above 173 with max timings.

And to reset your multi, you've got to shut her down, clear the cmos and start her up again?? How about the flash??

You have to clear the CMOS when putting the cpu multiplier DOWN, going up is ok. Or set cpu speed to lowest possible and power off. If you don't you'll get those ntokrnl.exe/system boot errors like you said in the first post. This is mentioned in the manual (page 3-5 "if the CPU is slower than the old one (and is same brand and type)").

I haven't flashed my bios yet, still running the original 7M.

Good luck!

[OPPAINTER]

Sounds to me that this memory sucks fireandsmoke, I would play with the timings, also just for testing try turning off 4 way on this memory and see what happens.

OPP

[shadco]

I don't get it.

That is exactly the way XMS3200 CAS2.5 v1.1 acted on mine but the CAS 2 stuff is supposed to be good stuff.

Put 2.85 volts on that memory and put at least 1.75 on the processor they do seem to burn in, I run mine at 1.82. You gotta have decent cooling.

I can run my ram at 210 2.5 2 6 3 2t fast command decode (you aren't trying ultra are you?) with enhance dram perfomance and enhance for benchmarks on. I use Xtrmemddr PC3200.
210

Anything above that and AGP tearing sets in.

I run 7x24 at 200 2.5 2 6 2 2t and all the other goodies turned on.

Try slot 4 for the ram also.

Good luck and you may have to look into your psu.

Shad

[MrLavender]

Originally posted by shadco
That is exactly the way XMS3200 CAS2.5 v1.1 acted on mine

That's what I've got. It'll run 2.5-3-6-3 2T @ 210 but only with Command Decode set to Normal. I guess that's why 2-2-5-2 1T @ 175 gives me a better 3dmark result?

I also thought the XMS3200C2 was supposed to be much better. The specs say it does 2-2-2 1T @ 166 and 2-3-3 1T @ 200. If it doesn't send it back!

[KnightElite]

I suspect that the issue is your hard drive, or some other PCI device. Have you tried running it at 166MHz FSB with the 5:2:1 ratio? If that is the problem, it should solve it.

I had a similar thing happen to me. I had the FSB overclocked to 166MHz, and it was running half decent, so I went in the BIOS and changed all the performance enhancing settings to the best performance (CPU command decode to ultra, enhace DRAM performance, CAS, RAS, etc....) got a BSOD going into XP and found out that it had nuked my partition table. So in my case it was the RAM.

[TheDude]

If you hit 166 fsb and the 5 divider..I'm pretty sure you have to set the command from ultra to fast for it to work...at least I did

[fireandsmoke]

Guys,
You GUYS ARE THE SH*T!!!!!!!!!!!!!!!
Yup, 5 divider, fast setting, and voltages...
Check out new thread "A little better"
'cause I don't know how to post attachments in Post Reply
THANKS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
F&S