Newly built system isn't stable.
So I have a gigabyte atx motherboard am3+ dual bios with a single ddr3 8 gb stick and an ASRock AMD processor that runs at 4.2 before overclock. I forget the name. A 500 gb ssd. I forget the name of it also. Powered by a cougar A 760. The only thing that wasn't bought new is my old Nvidia NVS 300. Its all layed out on a home made aluminium support frame I threw together. The cpu has a dedicated fan and heatsink and I have a secondary fan blowing across the whole board. My problem is after a few 2 or 3 large zip extractions, compressions or something like patching a 4 gig mod file it starts to get errors and all my right click menus and new windows just show big black squares instead of the menus or programs. Eventually everything slows down and its unusable. This happens even if I just use the computer to browse the web for more than an hour. The system obviously isn't stable and I'm assuming its because there's something I have to do after putting all the parts together and just hitting the power button that I don't know about. Can anyone help me with this? I have the drivers cd for the motherboard and the cpu but I feel like theres all kinds of other drivers for a newly built system I can't even begin to think of.
Is this a good question?
4 
2 
1 
You should check the Bios site for your motherboard. https://www.gigabyte.com/Motherboard/GA-...
by NR26
Hi,
Check in Event Viewer (press Win Key + x key - both together to get link) for any Critical, Error and Warning events that are logged at the same time that the problem occurs.
Once you get a pattern with the same Event ID and Source occurring at the time it happens, search online for the Event ID and Source to find out what it means.
by jayeff
Oh man, this seems like a good start. Theres drivers for everything on there. Between that and the event viewer I should be iff to a good start. Should be able to try today or tonight.
by Theodore Bundy
I have 14 errors and 205 warnings. Is that alot?
by Theodore Bundy
@Theodore Bundy
Click on Errors and check if they're all the same error i.e. event ID and source.
The same with the Warnings.
Although with both sometimes they come in batches after an update and then don't reappear until the next update so the idea is to check if they occur regularly and of course it depends on the time frame for the errors i.e. 205 warnings in 24 hours or 7 days either way it seems high. The same with the errors so it may not be that many different problems and only the one that is causing them.
There's also the possibility that some are spurious or that they're known and MS deems it not worth fixing as they're not causing problems only event reports.
It depends on exactly what they are
by jayeff