Computer Freeze

ExcessiveEvil · 14 Oct 2011 at 08:13

Hey guys I was wondering if anyone can help me.

I recently built a system and I've been getting random freezes, where the computer literally freeze, no blue screen. There is no warning when this happens, it just stops. It often seems to happen when I leave my computer idle, I come back to my login screen, and the cursor is either missing or frozen, and the computer is unresponsive.

My processor is overclocked to 4.8ghz using the drop down menu on my motherboard's bios, I stress tested for several hours and no errors occurred.

I suspected this was a graphics driver problem until I was playing music and my speakers started buzzing when the freeze happened.

Basically I just wanna know where I can start to find where this is happening.

Thanks in advance

System:

Code:

------------------
System Information
------------------
Time of this report: 10/14/2011, 08:04:07
       Machine name: LUKE-PC
   Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
           Language: English (Regional Setting: English)
System Manufacturer: To Be Filled By O.E.M.
       System Model: To Be Filled By O.E.M.
               BIOS: BIOS Date: 06/21/11 12:06:29 Ver: 04.06.04
          Processor: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 CPUs), ~3.4GHz
             Memory: 8192MB RAM
Available OS Memory: 8104MB RAM
          Page File: 2677MB used, 7473MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7601.17514 32bit Unicode
Graphics card: 570 GTX

Plec · 14 Oct 2011 at 09:22

You ideally need to rule out the clock as the culprit as stress testing is not definitive proof of a stable machine. Most of my unstable clocks have passed every stress test i've thrown at it and the proceeded to BSOD/freeze during general apps use, browsing etc...

I would save your present clock in a profile and the reset the CMOS and load optimised defaults - but set your memory up manaully to its recommended spec.

If it doesn't replicate the problem at stock then you know you may need to fine tune your clock settings (vCore, RAM settings, PLL etc...)

I would also set the memory up manually to the optimum spec and run teh latest memtest overnight to help rule out the memory.

ExcessiveEvil · 14 Oct 2011 at 09:25

Thanks for the quick reply!

I'll give what you said a go

Plec · 14 Oct 2011 at 09:25

NP - good luck with it.