model of the motherboard: DFI LP DK X48-T2RSB PLUS LGA 775 Intel X48 ATX Intel
model of the memory: F2-8500CL6D-4GBNQ DDR2-1066 PC2-8500 CL 6-6-6-18 2.0~2.1v
model of the CPU: Intel Core 2 Duo E8400 3.0 Ghz @ 3.0 Ghz
what is the problem:
Bought this RAM about a month an a half ago from Newegg and initially it seemed to be working properly. I believe I even tested it with Memtest86+ to make sure. However, this could have been when it was defaulted to an underclocked setting by the bios.
Once I figured out that my ram wasn't running at the correct speed, I went into bios and got it to the 6-6-6-18 settings with voltage ~2.05. After that, I went back and checked with memtest86+ and it seemed to give me errors, only on Test #5.
In case I had to send the ram in, I decided to test each stick individually (and in different slots of the motherboard just for good measure). When I did this, neither stick had a problem running individually. So it seems it's only when they're being used together (hence, not working in Dual channel?)
Also to verify this problem, I used Orthos Stress-testing program and again, the same ordeal. I never got a halting error on Orthos when testing the sticks individually, but only when I used them together.
Basically, I'm getting weird errors in 3D games (Counter-Strike: Source, Farcry 2, Left 4 Dead). After playing a certain amount (probably 30 to 45 minutes) my videocard would artifact. Showing distorted colors / missing textures / blown-up textures / weird renders of models.
Again, I supplied the same testing method and did not appear to have random crashes / artifacting in 3D games when using only one stick of ram.
Sorry for the length, but I wanted to be informative as possible.
Also, I THINK (not sure) I tried testing the ram at a lower clock rate.... the 5-5-5-15 and if I recall correctly, it did not give me ram errors on test #5 in memtest86+
So what's the verdict? Bad faulty ram? Incompatibility? Solutions?
(Also, I just placed both ram sticks back in, so I'm going to play these games over to verify that I'm getting errors.)
Thanks,
-Michael
EDIT:
Just after posting this. I went into Far Cry 2, played maybe not even 20 minutes and I received a BSOD.
DRIVER_IRQL_NOT_LESS_OR_EQUAL
IMAGE_NAME: kmixer.sys
(if you would like the debugging log, I have it available, let me know.) Guess I'll test some more and see what else happens.
EDIT:
Did some more testing. Decided to have Far Cry 2 running with both RAM sticks in to see if it would artifact or blue screen while I was in shower. Turns out it did.
Decided to test ram separately and did not receive a blue screen. I then placed both ram sticks back in and appear to not be getting a blue screen yet (35 minutes into the game). I'm not sure what to make of it.
EDIT:
Now I'm completely baffled. After running Far Cry 2 last night with both sticks and not receiving anything bad. I decided I'd leave on Orthos for stress testing overnight. I would expect to receive error well within 20 minutes of testing. Turns out...it's been running for 6 hours and not any kind of error. Since only 3.25 of the ram is used (32-bit system) Could that just mean the bad ram just hasn't been accessed? Or...what?
model of the memory: F2-8500CL6D-4GBNQ DDR2-1066 PC2-8500 CL 6-6-6-18 2.0~2.1v
model of the CPU: Intel Core 2 Duo E8400 3.0 Ghz @ 3.0 Ghz
what is the problem:
Bought this RAM about a month an a half ago from Newegg and initially it seemed to be working properly. I believe I even tested it with Memtest86+ to make sure. However, this could have been when it was defaulted to an underclocked setting by the bios.
Once I figured out that my ram wasn't running at the correct speed, I went into bios and got it to the 6-6-6-18 settings with voltage ~2.05. After that, I went back and checked with memtest86+ and it seemed to give me errors, only on Test #5.
In case I had to send the ram in, I decided to test each stick individually (and in different slots of the motherboard just for good measure). When I did this, neither stick had a problem running individually. So it seems it's only when they're being used together (hence, not working in Dual channel?)
Also to verify this problem, I used Orthos Stress-testing program and again, the same ordeal. I never got a halting error on Orthos when testing the sticks individually, but only when I used them together.
Basically, I'm getting weird errors in 3D games (Counter-Strike: Source, Farcry 2, Left 4 Dead). After playing a certain amount (probably 30 to 45 minutes) my videocard would artifact. Showing distorted colors / missing textures / blown-up textures / weird renders of models.
Again, I supplied the same testing method and did not appear to have random crashes / artifacting in 3D games when using only one stick of ram.
Sorry for the length, but I wanted to be informative as possible.
Also, I THINK (not sure) I tried testing the ram at a lower clock rate.... the 5-5-5-15 and if I recall correctly, it did not give me ram errors on test #5 in memtest86+
So what's the verdict? Bad faulty ram? Incompatibility? Solutions?
(Also, I just placed both ram sticks back in, so I'm going to play these games over to verify that I'm getting errors.)
Thanks,
-Michael
EDIT:
Just after posting this. I went into Far Cry 2, played maybe not even 20 minutes and I received a BSOD.
DRIVER_IRQL_NOT_LESS_OR_EQUAL
IMAGE_NAME: kmixer.sys
(if you would like the debugging log, I have it available, let me know.) Guess I'll test some more and see what else happens.
EDIT:
Did some more testing. Decided to have Far Cry 2 running with both RAM sticks in to see if it would artifact or blue screen while I was in shower. Turns out it did.
Decided to test ram separately and did not receive a blue screen. I then placed both ram sticks back in and appear to not be getting a blue screen yet (35 minutes into the game). I'm not sure what to make of it.
EDIT:
Now I'm completely baffled. After running Far Cry 2 last night with both sticks and not receiving anything bad. I decided I'd leave on Orthos for stress testing overnight. I would expect to receive error well within 20 minutes of testing. Turns out...it's been running for 6 hours and not any kind of error. Since only 3.25 of the ram is used (32-bit system) Could that just mean the bad ram just hasn't been accessed? Or...what?
Comment