Computer Freezing Constantly (weekly)

Michael Jarvis

Reputable
Dec 18, 2014
5
0
4,510
Hey there. So basically, as the thread title states, my PC has plagued me with freezing issues pretty much since I built it last year. I have narrowed down the issue to a few possible causes, but I seem to be unable to fix said issue.

90% of the time, when it freezes the video card is in use, in some form or another -- playing games, working on art (ZBrush), etc -- the other 10% is seemingly random, watching videos, using Google Hangout, browsing the net.

Given that most of the time the freezing happens whist the video card is in use, I figured it must be an issue with said card. So, of course I have updated all of my drivers multiple times over the last year, and by all, I feel quite certain I mean all, mobo, vid card, bios, the whole gamut.

Sometimes I have felt like these have helped, only to be denied a solution when the computer inevitably freezes again.

While doing research on my issue I've come across advice that mentions over heating, power supply failure, etc. I don't think it's a heat issue, since I clean the inside of my computer regularly, and look at the temperatures of my devices right after the freeze. My card is usually never more than 50 degrees, often times hovering in the 40's while in use. It can spike here and there, as graphics cards do, but consistently, after crashes, the temps are well within safe limits.

I also don't think that it is the power supply due to the fact that sometimes, while listening to audio, it will continue to play whatever it was playing, be it game music on loop, internet stream, or even iTunes. Granted when said songs or audio is finished playing it wouldn't play the next track, but if it was a power supply issue, wouldn't the whole system simply fail to respond at all? Or even shut right down?

What I have noticed happening lately is that right before it crashes I get these very short warnings. The system will come to an absolutely crawl, things (buttons and the like) will stop responding, and then the mouse cursor stops and that's it.

This all takes about ... 5 to 10 seconds, at most.

Another issue that I've read it could be is the ram. In this I can not say one way or the other if that is the case, I simply haven't gotten around to sufficiently testing said ram. I've read that it can take hours upon hours, and I simply don't have the time -- yes I realize that if it WAS the ram and I fixed it that would inevitably save me more time, but humans tend to live in the now ... lol

And lastly, one of my internal HDD's IS in a state of failure, I am in the process of getting a new one, but there are things on it that I need to access regularly which is why I don't remove it. I realize as well what a huge risk this is for my data, but that is my risk to take... lol (Not being confrontational, just laying out the facts) -- the reason I bring up the HDD for, is because I am unsure if whether this could be a cause? I don't feel like it would be, simply because I have had this issue well before it was failing, but I am far from an expert so I can't say for certain.

And finally, I will attach my system specs in an hour or so, I am just writing this post from my mac while my system restarts... I am tired of this shit, to be honest, and have finally taken the plunge to ask people smarter than me for help.

Hopefully my cry doesn't go unheard.

Thank you kindly!! And my sincere apologies for the massive post. I just figured I would lay out as much information as possible so that we are all on equal footing.

Cheers!

EDIT: Here are my system specs. Let me know if you need more detailed information on any of these. Copied from Speccy.

Operating System
Windows 8.1 Pro 64-bit

CPU
Intel Core i7 3770K @ 3.50GHz 31 °C
Ivy Bridge 22nm Technology

RAM
32.0GB Dual-Channel DDR3 @ 799MHz (10-10-10-27)

Motherboard
ASRock Z77 Extreme4 (CPUSocket) 31 °C

Graphics
VW246 (1920x1080@60Hz)
Intel HD Graphics 4000 (ASRock)
1023MB NVIDIA GeForce GTX 560 Ti (Gigabyte) 30 °C

Storage
465GB Western Digital WDC WD5000AAKS-00UU3A0 (SATA) 32 °C
465GB Western Digital WDC WD5000AAKS-00UU3A0 (SATA) 30 °C
465GB Western Digital WDC WD5000AAKS-65YGA0 (SATA) 31 °C
298GB Seagate ST3320620AS (SATA) 35 °C
931GB Western Digital WD Ext HDD 1021 USB Device (USB (SATA)) 32 °C

Optical Drives
ATAPI iHAS424 A

Audio
High Definition Audio Device
 
Solution
Try the following.

Start-> Run-> eventvwr.msc. Can also just press Win-key+R and type event-thingie.
In there, select Create custom view, righthandside.
Tick Critical and maybe Error. By log = Tick Windows logs. Press OK.
Try to find the entry which happened at same time as your comp froze.

The logs are usually cryptic, can try google them or ask on these forums.

Michael Jarvis

Reputable
Dec 18, 2014
5
0
4,510
So I have only tested 1 stick so far, out of 4, and after 10 hours and 7 and a half passes, there were no errors, so I decided to move on to the next stick.

Curiously though, the timings on this second stick seem to be different. I could have sworn that the timings on the first stick was 10-10-10-27, 800mhz, but whist testing this second stick, it says the timings are 6-6-6-20 at 666mhz -- it should be noted that these are all the same sticks of ram. Came in two packages and bought them at the same time...

One other question, there was an option to force multithreading, do I want to enable that option? I didn't, just to be safe, but I wasn't sure if that would speed things along or not.

Thanks!
 

mamasan2000

Distinguished
BANNED
10 hours is a bit too much to be spending in memtest per stick, 1 hour max. 1 pass or so.



Memories are usually paired. Should have similar capabilities but it's no guarantee.

What does the other stick say for 800 Mhz speed? Same timings as your other memory?

Mixing speeds and timings isn't the greatest thing to do.
If you can, make sure all memory is running at same speeds/timings.

Do you remember which 2 were in same package? Since they are supposed to be paired, they should work without problems. Does your computer still freeze with just 2 sticks inside? Do you have a 'thing' you can do to force a freeze? That would probably be the simplest way to check memory.

Kinda hard to tell if its the timings, speeds, a bad stick, 4 at the same time etc.
What if you tried running memory at 1333Mhz? Memory controller is on the CPU nowadays so...not sure how good they are. But I've noticed my AMD doesn't seem to have a good one, various issues at 1866 Mhz.
 

Michael Jarvis

Reputable
Dec 18, 2014
5
0
4,510
The main reason I chose more than 5 passes is because I had read online, in many places, that you'd want to run anywhere between 5 to 20 passes. And after 10 hours and 7 passes I just said fuck it, 7 is good enough. Admittedly, most places DID also say that the more common errors show up within the first pass, but that sometimes errors can show up after several passes, due to heat issues and the like.

Luckily for me I actually took a picture of the boxes that the ram came in, if for no other reason than proving that they are, by all accounts, the same ram.

https://scontent-a-lga.xx.fbcdn.net/hphotos-xap1/t31.0-8/903289_10151342712866086_1211069288_o.jpg (this is a facebook image)

What's weird is that both sticks -- all sticks in fact -- have a label that states directly 1600 mhz, 10-10-10-27. So this brings up another question, The RAM information within memtest, is that what the stick is currently running at, or is that what its actual timings should be / are? To be honest, until I ran memtest, I hadn't noticed any discrepancies between my RAM timings, within Windows or through the BIOS.

I honestly haven't tried running my computer with only 2 sticks, since 32gb was always better than 16gb in my eyes (even if programs do not utilize even half that, ever. :p ) If this memtest turns out no results, I may test with 2 sticks instead of 4. and will consider trying out 1333 instead of 1600.

Though, that leads me back to my problem. While I do get freezes on a weekly basis, it could be days before one happens, and, to answer your question, unfortunately, no, I haven't found any reliable way to freeze it.

I consider myself quite intermediate, in terms of computer knowledge, I've built my last 3 computers with hand picked parts, etc, but this has just baffled me and exhausted my patience to no end -- well, to the end of my patience I suppose ... lol. But if it is something as finnicky as a bad slot, or certain ram speeds, or any other combination of cpu / ram / vid card issues, then I am woefully ill equipped to suss out the issue.

It should be noted that this was a fresh install of Windows 7 when I built this PC, and I a currently upgraded to Windows 8.1 (though the issue has persisted since the beginning.

I *think* I have reformatted since then, but can't be certain. I suppose that is always another, annoying, option.

Thanks dude!
 

mamasan2000

Distinguished
BANNED
Try the following.

Start-> Run-> eventvwr.msc. Can also just press Win-key+R and type event-thingie.
In there, select Create custom view, righthandside.
Tick Critical and maybe Error. By log = Tick Windows logs. Press OK.
Try to find the entry which happened at same time as your comp froze.

The logs are usually cryptic, can try google them or ask on these forums.
 
Solution