Solved Random, frequent BSOD. Mostly 0x124. Still happening after new install

[KenjiJU]

I swapped sata cables and it came back. Still BSODing, which was making getting ss of CPUZ a massive pain.

I'm currently installing windows on my other SSD to rule out that being the issue. Could be that the cable was causing a borked install as well?

Edit: Nope.. BSOD while installing.

Going back to try to get screens of cpu-z.

 

[essenbe]

Yes, a bad cable will do that.

 

[KenjiJU]

1 of 2. Will try to get the other in the next couple mins.

Edit: Did not BSOD this time so I felt like running memtest86+, but that still gave errors. After I seat my other pair, if not having BSODs, I'm going to reflash my BIOS to an earlier version to see if memtest86+ will still give me errors.

 

[essenbe]

Those look fine. I would suggest you change the Command Rate (CR) from 1T to 2T. 2T is a little more stable, but other than that, they are spot on. There is nothing there that should cause errors in memtest, other than the ram having errors or a bad Dimm Slot on the Motherboard.

 

[KenjiJU]

Well I tried all slots earlier and had BSODs. Could all slots fail at the same time? Otherwise that would mean both my RAM sticks failed at the same time and that these two new ones are both bad out of the box. (I did make sure to get a set that was in a sealed box.)

Do you know which is more likely? I'd hate to drive out again just to come back with more sticks that don't change anything.

 

[essenbe]

Yes, it is possible that all slots are bad, but it is more likely that the ram sticks are bad. If you have access to another computer, run memtest86+ with your sticks in the other computer.

 

[KenjiJU]

Unfortunately not.

I tried Windows Memory Diagnostic tool and it's showing 'Hardware problems were detected' immediately, whereas, like before with memtest86, it ran fine before flashing the BIOS. Maybe I ended up damaging something while troubleshooting?

Seems my only choice now is to waste more money on RAM or get a new CPU/Mobo set. There're no good 1155 boards at my store to replace what I'm using anyways.

 

[essenbe]

You have Corsair ram and they have a lifetime warranty on their ram, I'm sure. Can you download and flash the bios back to the previous one? I'm not sure about Gigabyte boards, but Asus boards you can, so I would think Gigabyte's could do the same. When you go into bios, look and see if BIOS recognizes the ram. I assume you have already set the bios to optimized defaults?

 

[KenjiJU]

Yea, that last post was when I flashed the BIOS to the earliest version I could download, and followed by running memtest86+ and windows mem diag.

What do you mean by recognize? I'm not sure if it shows a name of the modules, but it always displays voltage and frequency actively on the main tab.

Just BSOD during another Win install, just while waiting for activation key prompt.

 

[essenbe]

OK, run the BSOD posting instructions and let me look. www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html#option2

If you are doing a clean install, make sure you are configured for Small Memory Dumps.
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

By recognize, I just meant that it could 'see' all of your ram modules.

 

[essenbe]

The real early versions of any chipset are usually much less stable. It takes them a while to work out all the kinks. The later versions are more stable and give you more options usually. I'm going through that now with the X99 Chipset. I had fits with the Z77 chipset, but it runs great now.

 

[KenjiJU]

This is from my latest reinstall. I'm currently experiencing less overall BSODs, but I can provoke it by trying to install .net 4 (usually BSODs while extracting).

My board is Rev 1.1. There's a Rev 1.0 and 1.2 listed on Gigabyte's site. Not sure if it matters, but I always made sure to use the drivers under 1.1.


Also, I can't seem to get speedfan to run. It just hangs after 4 lines. But it's not surprising since a couple things have crashed randomly. I might try to reseat everything tonight.

 

[essenbe]

Make sure to run all of the Important and recommended Windows updates. You should get .NET 4 as a Windows update. It may be crashing because other things need to be installed first.

 

[Golden]

My board is Rev 1.1.....but I always made sure to use the drivers under 1.1.

Thats the correct approach.

 

[KenjiJU]

Make sure to run all of the Important and recommended Windows updates. You should get .NET 4 as a Windows update. It may be crashing because other things need to be installed first.

As with my last install, the updates were hard to get or broken due to BSODs in the middle. Downloaded about 8 updates and as soon as it reaches the install point, it BSODs. I only tried .Net4 first this time as it was part of my mobo drivers disc.

 

[essenbe]

Welcome back, Golden.

 

[essenbe]

KenjiJU, I don't understand. You have had Memtest86, memtest86+ and Windows Memory Diagnostic all say your ram is throwing faults and errors, yet you still don't seem to believe them. You are having BSODs during an installation where there are no drivers to blame. You have a lifetime warranty on the ram, so it isn't a matter of money. The number of errors is irrelevant. 1 Error is a fail. You are still having BSODs right now. All the evidence is right there, I'm having trouble understanding your reluctance. It is either your ram or your board, as I see it.

 

[Golden]

I'm in agreement with Steve, all evidence points to RAM or motherboard failures. You need to act on the evidence.

 

[KenjiJU]

Well, what's hard to accept is that my first two sticks ran in two of those test programs with no immediate issue vs a bucketload of mass failure immediately upfront, same happening to two new modules. Any configuration of these give the same BSOD frequency as back when I thought the issue was a software/driver issue, so memtest reads have changed, but the BSODs that have been happening haven't.

Thanks for your time, guys.

I'll come back to report any solution.

 

[Golden]

Failures with memory often manifest themselves in bizarre ways. However, if MemTest86+ reports errors, it is very rarely incorrect.