BSOD (Various types); unknown cause

Ah, I see! Well, I have already wiped out everything and am now re-installing windows on my desktop. Thank you for all your help! The mobo actually doesn't come with a built-in wireless card which I overlooked when purchasing it, but other than that, I think I'll just suck it up and buy a card for the empty slot that would fit a wireless card

This netgear adapter has been causing me problems from day one but at the same time, it's my current source of internet for the PC so I'll have to deal with it until I order a new PCI card. I'll let you know if any other issues arise-- thank you!

Okay, just an update on everything:

I decided to re-install windows. The problem? When I tried re-installing to my SSD, I BSOD'd again and the error it gave me was related to a Ntfs.sys file. I did this a few times. This kind of led me on to something here-- that maybe I did have a hardware issue, but with my SSD. My SSD is compatible with my motherboard, but I might have just gotten a buggy or defective one. To test my theory, I tried re-installing windows several times on the SSD and received the same error. I then installed it on my regular HDD. Windows installed successfully without BSOD'ing on set up. The issue I'm having now is that a lot of utilities just "Stop Working" but it doesn't hinder performance or BSOD. I'm just curious as to what my next step should be -- to keep Windows on an HDD, or to try and contact my SSD manufacturer and see if I can get a new one and try and re-install windows on there once again. Thanks!

That'll do it. What brand of SSD do you have? Please avoid OCZ and Rosewill brands, since they have a high rate of failure. Samsung, Intel and Crucial drives are considered the most reliable right now (though keep away from drives with a Sandforce controller).

I've had to work with clients here at SF who've turned in their OCZ drives to have tested and returned to them with OCZ saying they were good when actually further testing turned out it was still a bad apple. I would not trust their testing procedures any more than I would trust their competence to make drives and the firmware that runs em. Consider their response with a liberal dose of salt.

Nevertheless, if it's still crashing without the SSD, then the SSD is not the cause of your woes (or at least not the sole influence). However make sure that the drive is completely disconnected. Regardless if it's the Windows drive or not, having it present on the system can cause BSODs. Make sure that the system is BSODing without the SSD at all to confirm it ain't that.

Since it's been a while, I've reviewed the thread to recover my bearings. So far we were working on the Gigabyte software and whatnot as being suspect but that has been resolved. Then attention turned to the netgear adapter. You were planning on replacing it but your attention was diverted to the SSD drive. I recommend us focusing on the netgear adapter first. I recommend going through the process of elimination as usual.

Btw, no crashdumps existing in your most recent attachment.

And of course, I let memtest86 run for more than 25 passes (for 16gb of ram I think that's a lot), and VOILA, over 300,000 errors. Now I'm going to check each individual stick, and send whichever one of them is bad back to Corsair! Hopefully this solves the issue, and I think it all makes sense now to be honest, with Windows Explorer crashing, Flash crashing and program installers crashing and whatnot. I'm still not sure about letting the SSD off the hook either though, so for now I'll play it safe and send that in for testing too!

Just an update: I finished memtest after a few days, and testing showed 500,000+ errors ()

I sent the RAM back to Corsair and they will replace it for me. Thank you all for your help and I hope this solves my issue, but until I can confirm, I will leave this thread open! :)

UPDATE: I received my new RAM from Corsair and nothing has crashed! I've been running a lot of high-level tasks, installing programs, Chrome hasn't crashed and neither has explorer! I will go ahead and mark this thread as solved. :) Thank you for all your help!

Splendid! Glad to hear the good news, skipper. This will remind me of how crucial it is to start testing on hardware first before digging in deeper. Thanks for keeping us updated.