Wisecracker :
Did you *un-gang* the memory controller ?
Did you try each stick independently by themselves ?
This won't be very reassuring but there is not a single stick of Corsair on the MSI QVL list for that motherboard. I like MSI stuff for the most part but have run into memory issues on older boards.
http://www.msi.com/uploads/test_report/TR10_2061.pdf
I have to assume that the SPD setting would be correct as the mobo is reading them. Running MemTest (or the Win memory diagnostic) may give you an idea of where you stand with the sticks.
Hi! I happened to read your response just now. Let me introduce myself. Actually, I am the victim of the BSOD problem being discussed here and man30 is a dear friend of mine who has been helping me troubleshoot the problem. So thanks for all your responses.
I am not sure what "ungang" means. Can you elaborate?
I ran Memtest 86+ on the system today. It ran for over 7 hrs, 45 mins and displayed 2 errors in 8 passes. I am not sure if this would mean anything, but here are the error details:
TST - 7, Pass - 3, Failing Address - 00108ccb2bc - 4236.7 MB, Good - e359e6c0, Bad - e35966c0, Err-Bits - 00008000, Count -1, Chan -
TST - 8, Pass 5, Failing Address - 001006c32bc - 4102.7 MB, Good - b936fbd3, Bad - b9367bd3, Err-Bits - 00008000, Count - 2, Chan -
I've not run Memtest on the individual RAM sticks though. As man30 has already mentioned, when the system is run on the RAM sticks individually [one stick at a time], there is no instance of BSOD. BSOD occurs only with both RAM sticks together.
Yesterday, I had used a software called "Blue Screen View" to check out the details of my dump files. The first 2 dump files display a bug check string "Bad Pool Caller/Header" while the remaining 4 dump files display "IRQL Not Less or Equal"
So what do you think could be causing the BSOD? Are both the RAM sticks corrupt? And why is it that they run fine individually?