Having problems with my 200 FSB machine. Every so often, particularly under load, it BSODs. Seems to be all over the shop - portcls.sys, bootvid.dll, hal.dll.. but most of the time it's ntoskrnl. If I bring the FSB down to 166 the problem seems to vanish.
Fortunately I have another machine I can swap parts around in, but the CPU is a native 133 FSB, OCed to 166 with 166 RAM so I can't really test it properly. I've tried swapping the CPU and RAM to the other mobo and repeated the error, so it doesn't seem to be linked to the vid or the mobo so I think it's got to be either CPU or RAM. Generally I would associate this kind of error with RAM - I have 3 sticks, 2x512 and 1x1024, but any combination seems to kill it so if it was RAM all three would have gone at once. Plus I've run the latest version of memtest x86 overnight on 200FSB with all 3 sticks in, 8.5 passes with no errors. Which leads me to suspect the CPU, but this isn't the sort of error CPUs usually present... at least not that I've seen... which makes me wonder whether I'm getting a reliable result from memtest.
Running something like Burn In Test will BSOD the system in about 5 minutes or less. I should also mention that I'm not overclocking at all.
Everything is only a few months old, still under warranty so it's purely a case of finding the problem - any suggestions will be greatly appreciated.
Fortunately I have another machine I can swap parts around in, but the CPU is a native 133 FSB, OCed to 166 with 166 RAM so I can't really test it properly. I've tried swapping the CPU and RAM to the other mobo and repeated the error, so it doesn't seem to be linked to the vid or the mobo so I think it's got to be either CPU or RAM. Generally I would associate this kind of error with RAM - I have 3 sticks, 2x512 and 1x1024, but any combination seems to kill it so if it was RAM all three would have gone at once. Plus I've run the latest version of memtest x86 overnight on 200FSB with all 3 sticks in, 8.5 passes with no errors. Which leads me to suspect the CPU, but this isn't the sort of error CPUs usually present... at least not that I've seen... which makes me wonder whether I'm getting a reliable result from memtest.
Running something like Burn In Test will BSOD the system in about 5 minutes or less. I should also mention that I'm not overclocking at all.
Everything is only a few months old, still under warranty so it's purely a case of finding the problem - any suggestions will be greatly appreciated.