Crucial Ballistix PC3200 Fails in Dual Channel - Faulty ?

Associate
Joined
5 Nov 2004
Posts
1,593
Location
Central UK
Hi

I have a Crucial Ballistix Dual Channel DDR 1GB Kit that has performed fine for several months but recently I have become plagued with blue screens, windows stop errors, sudden restarts etc, all problems that go away when I remove either RAM stick and just run on one single 512MB module.

Stop errors I get are :

PFN_LIST_CORRUPT
DRIVER_IRQL_NOT_LESS_OR_EQUAL

And a couple of random others, Googling reveals possible causes as bad RAM but Memtest86 doesn't show any errors with both sticks installed when run from floppy disk but once in Windows the problems start, maybe not for an hour or so, but sooner or later the crashing starts. NEVER does anything wrong with only one RAM stick installed.

CPU is an AMD 64 4000+ and OS is Windows XP SP1

No new software has been installed and regular virus/anti spyware checks are done.

Nothing is overclocked and I've set the memory timing to 2T from 1T and also tried the RAM sticks in the other two memory slots on the mainboard (Asus A8V)

Could it be the CPU memory controller ??

Thanks for any advice
 
I've just tried memtest again, ran it for 2 hours solid from the floppy at start up and no errors. I'll have a look at the Prime95 'Large FFts' suggestion, I don't have it but will download now and give it a run.
 
Prime95 'Large FFts' seemed to run OK with no errors but I didn't run it for too long, about half an hour, will run it for longer bit later.

The GPU is an nVidia 6800GT, I'll try updating to the latest drivers but it's always been fine on them up until now - can they degrade/corrupt ? The drivers are Forceware 81.85
 
OK, updated the nVidia drivers, modem drivers and as many others as I can find, reseated all the cards and the CPU and reset the BIOS, it's just getting worse 8 times out of 10 it wont boot into windows in dual channel, just stops with :

DRIVER_IRQL_NOT_LESS_OR_EQUAL

STOP 0x0000000A

Take a stick out, either stick and it's fine, but runs fine for hours in dual channel on memtest... just not windows.

If I use both RAM sticks BUT in the wrong slots, ie, one stick in blue socket and one in a black socket (should be two in blue or two in black for dual channel) boots up fine and is rock stable, shows full 1GIG memory but only as single channel in CPU-z

I'm thinking it's the motherboard or CPU memory controller now so going to leave it 1 GIG single channel, can't notice much real time performance loss but Sandra now only shows 2600mbs bandwidth down from 5000+ Bit annoying gah ...

Anymore thoughts appreciated though.

Thanks for help.
 
There's only two different errors listed, quite a few events of :

"The ieupdater service failed to start due to the following error: The system cannot find the file specified"

And a few :

Error code 0000000a, parameter1 0000000b, parameter2 00000002, parameter3 00000001, parameter4 804efbe3.

The latter I presume is the blue screen stop error, just looking into the former, google suggests this may be a virus/rootkit or something ?

"That ieupdater.exe from ms-counter.com/ms-counter/load.php was complete hell. I downloaded it to take a peek and accidentally ended up executing it on my live machine when trying to determine it's packer (FSG) and unpack it.

After accidentally executing, I figured I'd take one for the team and just let the infection run it's course.
Royal hosing, indeed.

It dropped at least half a dozen patched system files, as Windows File Protection went crazy!

The downloader (ieupdater.exe) I believe either attaches to or somehow manages to replace svchost.exe (yes, the real on in System32 dir). After this, it downloads a few goodies and does a cold reboot of the machine.

After this, Windows failed to boot. It apparently attempted to attach to or replace ndis.sys, but failed terribly, thus killing Windows. After replacing ndis.sys with a working version I was able to get back into Windows and let it continue the hosing"
 
i had a similar problem with my 3700+, it would work with one stick of ram but putting both (single or dual channel) caused masses of crashes. I thought the processor was duff as the 3000+ put back in worked fine as before. Since getting a new cooler however i thought i'd give it another go and to my suprise its worked fine. Not sure what it was that upset it but its working great @ 2.8. I was blaming the ram up untill i put my old processor back in, really confusing!
 
Back
Top Bottom