My computer keeps freezing

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Mar 31, 2018
18
0
10
A few months ago, i upgraded my motherboard, CPU and RAM in my custom PC. Ever since then, my computer would randomly freeze up on me and the only solution is a hard reboot. At one point i also got a boot disk error and i selected the restore normal settings and restart option. I haven't had that error since, but the freezing is still happening. My computer freezes up on me at the earliest at boot up and then there were times where it would be hours before it freezes up. It usually freezes up while watching videos or playing games. I have tried every other possibility, i've updated drivers, there's no overheating and there are no viruses. I think its a computer issue and not windows as i have looked up windows 10 freezing issues and when i do those solutions, it still freezes. I suspect it to either be a CPU or a RAM issue, but i'm not totally sure. Please write back and ask any questions you need from me.
Specs:
CPU: Intel Core i5 6500
RAM: Corsair Vengance 8 GB, DDR4 2400MHz.
GPU: Geforce Gtx 760
Power Supply: Corsair CX 500
motherboard: Gigabyte z170x Gaming 7
 
I ran the test and it said no errors. I moved around the RAM in different slots and it’s still freezing. Though it freezes after longer times now, it’s still freezing. Are there any other things I can try?
 
The freezing is total? (the mouse and keyboard do not work?) or is it very slow?

If the freezing is total it's almost certainly a random RAM problem, although memtest86 does not give errors. If you can, get or borrow a stick to prove it.

If it is very slow can be a sata cable problem.
 


It’s a total freeze. I’m thinking about either borrowing or buying another stick.
 


Hey guys I’m back. So I went to the geek squad and had them diagnose it and they said it was a hard drive issue so I replaced the hard drive, installed all drivers and stuff. But it still froze twice. I went back there and they said it was probably a motherboard issue then. Does anyone else have any other inquiries or heard of an issue like this?