Continual BSOD's over a 12 month period

LOL, more BOSD's since I last posted and very frequently. So I was ready to RMA the RAM. But first off to cover all angles, I made a thread in the Corsair forums about this matter and got a reply back about changing the QPI voltage, increasing it till there is no more BSOD's.

I have never worried about overclocking this system as its too complex and beside that I have the Sata 3 SSD and fast CPU and am satisfied with the present speed.

So I did a search for references to my RAM and MB in the Corsair forum and found a link to this explanations for BSOD's
Most of the BSOD error codes I have experienced are referenced below. What I have done is go to the RAM settings and set them as stock standard settings and raised the RAM voltage till there was no more BSOD's.

If there is no more BSOD's in the next 24hrs, I will then run memtest to see if I am still getting faulty memory.

BSOD Codes for i7 x58 chipset
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

BSOD Codes for SandyBridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage

Please feel free to comment, advise, correct, and add to this list. I am not the original author and will not take credit for it. I simply thought that it should be posted by itself. I am only repeating the info that I got here at OCN. This is currently for Intel i7 systems, but I would like for everyone to help me set it up for other systems as well.

Thanks, just giving back,
/eVo/HaMMeR=GoM=

Here is the link to further discussion on these types of BSOD codes.
The OverClockers BSOD code list

Do you get a prize for the most BSOD's in a week.

I counted 50 BOSD's so far.

Can anybody get their heads around this problem or problems.

I have adjusted the CPU Vcore voltage to compensate for the voltage settings of my memory and am still getting BOSD codes of 0x1a and 0x7E.

The BOSDs codes above are suggesting from the table above this is either wrong voltage or corrupt memory stick?
I have since installed the Gigabyte easytune6 program to adjust the voltage values, so I can actually see what the different voltages are running at, here is a picture of what the actually present voltages are set at. Also the latest BSOD's.

zigzag3143 said:

Pat

I do appreciate your situation but adjusting the voltage may fix the problem or make it worse.

A 124 error is a generic hardware error, not just a ram error. By changing the voltage you may actually make it worse.

Sorry I use a user name on forums, my name its actually Paul and Yes I didn't achieve anything with those codes and their supposed explanations by upping the voltage. I have never overclocked this system as for a start it was too unstable.

I went back to Corsair forums and started a new thread about tests on the RAM with memtest, I had done yesterday and got all sorts of opinions on what and might be the cause.
Finally "Wired" the Corsair forums Admin said just take each stick of ram and check them individually in the first slot on the MB.
18 months of BSOD's with CMX6CX3M3A1600C9 - The Corsair Support Forums

The results are below. I have just posted on their forum and am hoping they will do a RMA on the RAM. The first two sticks reported no errors but the third one did.

zigzag3143 said:

Paul

If you pull the memory that fails does the system still crash?

Would be nice if it were as simple as one ram stick

Ken

I hope I am not stuffing the system but I looked at my MB book/manual and read slots 1 and 3 will run duel memory and put the two good sticks in and am using the system to write this reply.

I still think a 24hrs period will tell all, but right now with the XMP profile1 set in the MB BIOS and running the MB at defaults. The RAM is set to its specs at 9-9-9-24 2T 1.65v 1600Mhz without a instant BSOD as soon as the desktop comes up sort of indicates it might have been the problem all a long.

As you said if its just one stick of RAM I have wasted the last 12 months of pulling my hair out tiring different fixes and checks.

I can't count how many times I have re-installed Windows 7 and all the time windows 7 adviser was saying run a memory test but when I did it came back with no errors. I suppose too, I won't really know everything is right till I hopefully get a RMA off Corsair and try the triple channel memory that they give me as a replacement.

@zigzag3143
I wonder too...
If it is this problem with a defective ram stick.
That the Dvico TV card I removed and the Marvell sata 3 controller that I have disable should be switched back on and used to see if I get any more BSODs.?

No, But I have been off doing things on this computer for the past 2 hrs without one single BOSD.
I am just about to re-slot the PCIe TV card and also if that works fine. I will change the both sata 3 drives back onto the Marvell 9128 sata 3 controller and see if they cause a BSOD.

I am presuming that the stick of RAM was the problem.

@zigzag
What your saying is try "A' stick of RAM in each slot at a time, then turn on the system?