New system freezes...do I need to change my overclock settings?

Toggle sidebar Toggle sidebar
P

plymgary

Reputable
Oct 22, 2014
8
0
4,510
Hi there,

I've recently built myself a new system with the following components:

CPU: AMD FX-6300 3.5GHz 6-Core
CPU Cooler: Cooler Master Hyper 212 EVO 82.9 CFM Sleeve Bearing
Motherboard: Gigabyte GA-78LMT-USB3 Micro ATX AM3+
Memory: Crucial Ballistix Sport 8GB (2 x 4GB) DDR3-1600
Storage: Western Digital Caviar Blue 1TB 3.5" 7200RPM
Video Card: Asus GeForce GTX 760 2GB DirectCU II
Case: Zalman Z11 Plus ATX Mid Tower
Power Supply: Corsair 600W ATX12V

Now, whenever I power it up everything works okay for around 30 minutes before it freezes up. This happens randomly, and there isn't any one event that triggers it.

I have attached images of the current overclock settings I have used.

1.JPG


and for the bit missing at the bottom of the top image:

2.JPG


Now, do all these settings look okay or is there anything I can change in order to try and get it to perhaps stop freezing? I was thinking it might be something or other not getting enough voltage?

I've run memtest86+ for three hours and no faults were found. I've also got an idle temperature of around 35 degrees, and when it's put under a stress-test this increases to around 53 degrees.

So, any ideas of what I can change in those overclock settings please?

Many thanks,

Gary
 
Solution
tomr4lph
Have you tried checking the system logs in event viewer? If you don't know how to do this, boot it into windows, hold the Windows key and press R, then release them both. Type "eventvwr" in the box without the quotes and press enter. Wait for it to load, then click on Windows Logs in the menu on the left, then double click system, then wait for it to load. Once it's loaded, it should show you system logs, listed in order of the time they were recorded. Look for any that happened leading up to the time of the crash, and take a screenshot of the information, and upload it to any external image host site, then copy + paste the link here.

EDIT: I know I'm not supplying any overclocking settings here, but I would like to determine if the...
Sort by date Sort by votes
tomr4lph

tomr4lph

Reputable
Oct 21, 2014
204
0
4,760
Have you tried checking the system logs in event viewer? If you don't know how to do this, boot it into windows, hold the Windows key and press R, then release them both. Type "eventvwr" in the box without the quotes and press enter. Wait for it to load, then click on Windows Logs in the menu on the left, then double click system, then wait for it to load. Once it's loaded, it should show you system logs, listed in order of the time they were recorded. Look for any that happened leading up to the time of the crash, and take a screenshot of the information, and upload it to any external image host site, then copy + paste the link here.

EDIT: I know I'm not supplying any overclocking settings here, but I would like to determine if the processor is in fact the root cause, as if it still crashes without being overclocked it looks less likely.
 
Upvote 0 Downvote
Solution
P

plymgary

Reputable
Oct 22, 2014
8
0
4,510


Hi Tom,

Thanks for your help. :)

I booted it up again at 17.03 and at 17.31 it froze again. The only way of turning it off is using the power button (task manager doesn't work when this PC has frozen). I've taken some screenshots to see if they mean anything to you?

If it's any use, the core temperature was 11 degrees when it froze, and the other temperatures around the 30 degree mark.

Here are the screen shots.

3.jpg


4.jpg


5.jpg


Thanks again,

Gary :)
 
Upvote 0 Downvote
P

plymgary

Reputable
Oct 22, 2014
8
0
4,510


Tom, is this your website or is it just a coincidence you're called Tom? I imagine I look really stupid now and TOM is actually some computer term that I am unaware of!!

I've taken a couple of screenshots of that error. Not sure if they give much away though? Next time...I'll pay someone to build the damn PC for me!! :p

6.jpg


7.jpg
 
Upvote 0 Downvote
tomr4lph

tomr4lph

Reputable
Oct 21, 2014
204
0
4,760


Nope, just a coincidence that I'm called Tom :p
And once again I read things too fast. It would seem that the log of the unexpected shutdown says the shutdown was at 17:32:28, and the log right before that time is windows update, so it would seem that it's trying to update something that doesn't like what it's doing. If I could see the windows update one, that might help, sorry about all this I know I'm not the best :p
 
Upvote 0 Downvote
P

plymgary

Reputable
Oct 22, 2014
8
0
4,510
Hi Tom,

No, don't apologise...it's nice that someone takes the time to help. I've been looking on this forum for posts where I can contribute (I can't bear newbies on forums that don't contribute!) but there's not much my limited knowledge allows me to answer!

That update was the Windows Service Pack. I wonder if that will stop the crashing? Shall I see if it happens again and then, if it does, post the log for it? Maybe that will solve it (or is that just wishful thinking?! :) )
 
Upvote 0 Downvote
P

plymgary

Reputable
Oct 22, 2014
8
0
4,510
Argh, the stupid PC is still shutting down. I think I'll save myself the headache and take it into somewhere for them to have a look at.

Thanks for your help though. :)
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom