Lent 1 of my RAM to another friend, to see if he gets any BSOD on his machine.
1 day past, no BSOD at all.
Neither in mine, with the current configuration above.
Should we enable D. Verifier?
Would it make the system crash due to RAM and not any driver issue?
Was this one of the old RAM that supposedly is causing the BSODs? Where did he put it in his system? Be aware that depending what slot he placed it in, the system may not even be using it at all (as in the system never reaches a point where it needs to use it). Kernel activity (Windows n drivers) sits at the very top of the memory range (last stick of RAM), and userland (applications and services) start at around the bottom and grow upwards. Keep that in mind when setting up the RAM for testing. If you want to make quite sure the RAM is bad, make sure it's placed in the last numbered slot on the mobo since there it'll hold Windows kernel and drivers.
Anyways, remember that this may not be an issue with the RAM itself but your configuration of it. The mix of RAM and their amounts could've been enough to bug your mobo out. When you got the new RAM kit, was it same make/model as the old?
Btw, what happened with the mobo? The warranty on it is looking pretty tight right now, have you considered RMAing it?
As for Driver Verifier, not really. It will make the system panic more in the event of an issue, as in more prone to BSOD, and will take up a modicum of more RAM and CPU activity to do all the extra checks, but that doesn't necessarily mean it'll catch bad RAM. Driver Verifier is just as its name says, it's designed to verify drivers. It has absolutely nothing to do with testing any form of hardware. If you want to do that, it'll be through Memtest, but we've already proven the issues evading that program. Again, I really do think we're dealing with a motherboard incompatibility problem or just a bad mobo altogether.
The RAM I lent was from the NEW kit I got Tuesday. I followed my intuition at this.
Lent one stick, stayed with the other.
If his machine had BSOD on tests, we would have found the problem.
As mine would crash in any way.
This stick is the only one he's using on his machine to help me.
In this case, would it matter the slot?
I don't really know which slot he's using.
Yes, it's exactly the same RAM model as before.
I'm still not considering MoBo.
But im really scared about the warranty, though.
I'll just test RAMs as far as I can.
Something is telling me the problem is the stick I lent. Intuition.
UPDATE:
By the time I was writing the reply, my friend called me.
HE HAVE HAD BSOD TWICE, CONSECUTIVELY!
So the RAM stick I lent him is with problem.
I'll just have to check my machine now.
As said before, I am using ATM:
1 RAM from the NEW kit + 1 RAM another friend lent me (spent 15 days with this stick without crashes).
No crashes yet.
So, I guess we can finally forget about the motherboard..?
Just have to find out if BOTH RAM sticks are with problems, or just the one I lent him. (:
Here's hoping the BSODs weren't coincidental and caused by something else. Nevertheless, we'll approach that RAM as the suspect for now.
Would be too much coincidence if not true.
His computer has been built over a year and never had crashes.
When working with the RAM I lent, gone BSOD.
Took that RAM out, no BSODs again.
This afternoon I went to the store to RMA them again.
The vendor was a really nice guy, and gave me another kit once again, without tests this time.
Running system with new RAM kit, lets hope for the best
Hi there. It's been a while. Any update on that RAM and how it's working?
It has crashed BSOD again..
XMP Profile 1 at 2400mhz
Took a week to do so.
I changed to XMP Profile 2 at 2132mhz: BSOD at windows start up.. twice
Went for JEDEC Profile at 1333mhz: no problems since.. computer stabilized. 2 weeks.
Then I gave up..
Since there are not any more problems with JEDEC Profile, I'm letting as it is..
Looks like timing may have been the problem after-all. Glad to hear it's stable. You can mark this thread as solved at your discretion.
Quote