New, self-built PC keeps getting BSOD at random intervals.

Check your board manual, I think the Intel SATA ports are the white ones on the side.
You only need one LAN driver unless you use both connections and I would recommend the Intel one for that.

You don't really need a VGA driver unless you use the built in Intell VAG on the CPU, just your nVIDIA driver.

As essenbe said use driver from Gigabyte
GIGABYTE - Motherboard - Socket 1155 - GA-Z77X-UD5H (rev. 1.0)
You should be able to uninstall the unneeded drivers through Control Panel, find the controller in the list, right click and choose Uninstall.

Memtest should be run for at least 6-7 passes for a thorough test. Also test one DIMM at a time and in different slots. If a DIMM passes in one slot and fails in another you likely have a bad board. If you have any errors, stop and go to the next test.

Good job. I hope it resolves your problems. Let us know if you have issues. Hopefully, we can help resolve them.

Dywindel said:

Ok, I've reinstalled the OS and all the correct drivers now. I believe this should be fine, but I will come back in a day or two to update on whether or not I'm still getting blue screens.

Thanks for the help!

Well done !!

A huge thanks to Steve and Gary, for helping us solving the issue :)

Good job, I'll accept thanks if all goes well.

One more thing I thought of is to recheck all of your PSU connections to make sure they are fully connected, also the RAM and GPU card.

Just a little reminder. I recommend staying away from all Marvell SATA 3.0 ports. They cause nothing but head aches to most that try to use them.

Try this. tutorial on Dump Files - Configure Windows to Create on BSOD and you will want the mini dump files.

Also, why not install windows to another hard drive to see if it is the SSD. If you do an install to another hard drive and the BSODs stop, you will know the reason.

The settings will create a dump file on the next BSOD. It will be located in C:/windows/minidump. As for replacement, you can try if you like, but as of right now, I know of no demonstrable reason you can blame it on the SSD. However, it is possible. Did you do a clean install on it, and where did you get the windows disk?

Try running an administrative command prompt (click start, in the search box type cmd, in the entry that appears, right click it and select run as administrator and provide permission) Copy/paste sfc /scannow. If you decide to type it notice the space between sfc and /. It is a system file checker and will check system files and attempt to repair them.