New PC at Xmas, random freezing

Associate
Joined
20 Jun 2010
Posts
69
Hi guys, since Xmas after building my new PC, ive had one big problem, at any random time, my computer just freezes, as in, mouse not moving, no CTRL ALT DEL, or anything, so I have to hold the power button and turn it on again

PC Specs:

Intel 6700k CPU
Corsair Vengence 8GB
Nvidia 660TI 2GB
Evga Modular PSU
Thermaltake Lv10 GT Case
2 SSDs, and 3 HDDs
Coolermaster H 212 EVO
Asus Xonar DSX Sound Card
Windows 10 Pro
MSI Krait Z170x Motherboard


Over the past week, I have been doing some tests in a attempt to fix my PC:

I have ran the PC without the GPU (Reverting to Intergrated)
Used 3 types of GPU drivers
Running Memtest against the RAM
Disabling ECO mode on the PSU
Running without the sound card
Rewiring the SATA cables for the HDDs -
  • in the case, the 5 HDD's are connected to power by one SATA power cable, so I redid the wiring so each drive now has their own power


All of these have failed, my next plan was to run the PC without any of the drives apart from the OS, if that fails then I am planning to remove the CPU from the MB and see if there is any bent pins. Oh and try Windows 7 (Or a Linux Live CD)


I have no idea what to do, can any of you guys help?

EDIT: Forgot to add the motherboard
 
Last edited:
Does event log point to anything just before it freezes? I suspect not but its worth a check.

Tried a BIOS update?
 
Tried just running with the boot / OS disk attached?

Certainly has the same symptoms as a disk on the way out.
 
Have you checked temperatures with HW Monitor or similar?
Andi.

Yep, everything seems ok, I've ran furmark and prime 95, the PC can handle load just fine

Tried just running with the boot / OS disk attached?

Certainly has the same symptoms as a disk on the way out.

I'm going to try that later today, I have ran a quick SMART test on all the drives and its not giving me anything bad

What's in the Event Log? Any clues?

Nope, I check it everytime it restarts, apart from some messages from VMWare, nothing wierd showing up

EDIT 3: The only thing I get is "Event 41, Kernel-Power" error each time


Tried a BIOS update?[/QUOTE]

Yep, everything is up to date, I found a post on reddit talking about some problems with the Z170 chipset, nevertheless, Im running the latest BIOS (A5) and I can tell no difference between that and the Version I used what it shipped with (A0)


EDIT: Forgot to add what motherboard I have (Z170A MSI Krait)

EDIT 2: This is the SMART log from my oldest drive I have in the PC ( Seagate 1tb Sata 2 drive) via HDTune

HD Tune: ST31000528AS Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 108 99 6 19158060 Ok
(03) Spin Up Time 94 94 0 0 Ok
(04) Start/Stop Count 88 88 20 13014 Ok
(05) Reallocated Sector Count 100 100 36 0 Ok
(07) Seek Error Rate 86 60 30 426085149 Ok
(09) Power On Hours Count 86 86 0 12381 Ok
(0A) Spin Retry Count 100 100 97 0 Ok
(0C) Power Cycle Count 96 96 20 4347 Ok
(B7) (unknown attribute) 100 100 0 0 Ok
(B8) (unknown attribute) 100 100 99 0 Ok
(BB) (unknown attribute) 100 100 0 0 Ok
(BC) (unknown attribute) 100 99 0 20 Ok
(BD) (unknown attribute) 100 100 0 0 Ok
(BE) Airflow Temperature 76 52 45 404095000 Ok
(C2) Temperature 24 48 0 24 Ok
(C3) Hardware ECC Recovered 30 22 0 19158060 Ok
(C5) Current Pending Sector 100 100 0 0 Ok
(C6) Offline Uncorrectable 100 100 0 0 Ok
(C7) Ultra DMA CRC Error Count 200 200 0 9 Ok
(F0) Head Flying Hours 100 253 0 25070 Ok
(F1) (unknown attribute) 100 253 0 159032258 Ok
(F2) (unknown attribute) 100 253 0 -1430909628 Ok

Power On Time : 12381
Health Status : Ok
 
Last edited:
There are a few things you can try, firstly right click on start and click Command prompt (Admin) type in sfc /scannow and hit enter , allow it to run System File Checker, it should find and fix and core file integrity issues.

Then you can try run in safe mode, if none of your symptoms exist in safe mode then most likely it is a driver conflict of some kind.

Have you overclocked? could be unstable if so run at stock speeds to determine if it is that.

Please check your event viewer for any errors given and post back with your findings, to do so simply press Windows+R to open the Run dialog, enter eventvwr (or eventvwr.msc) and hit OK.
 
There are a few things you can try, firstly right click on start and click Command prompt (Admin) type in sfc /scannow and hit enter , allow it to run System File Checker, it should find and fix and core file integrity issues.

Then you can try run in safe mode, if none of your symptoms exist in safe mode then most likely it is a driver conflict of some kind.

Have you overclocked? could be unstable if so run at stock speeds to determine if it is that.

Please check your event viewer for any errors given and post back with your findings, to do so simply press Windows+R to open the Run dialog, enter eventvwr (or eventvwr.msc) and hit OK.


Is there a difference between the sfc command and going to Properties/Tools -Error checking when right-clicking the drive in my computer? As i've allready done that one with no errors coming back

Nothing is overclocked, apart from the memory which was running on a XMP profile, although after testing it and finding the computer crashing with and without the RAM OC running, the RAM isnt the issue in my build

EDIT: I'm going to try safe mode later, after running my PC without my oldest HDD, if it crashes again, i'll move on to testing safe mode (Although its annoying that the freezing is random so I could be in safe mode for hours)
 
What you described is a disk check which just checks the hard drive for any hardware faults, sf scan checks the core windows files for any system integrity problems and will try to resolve any it may find.

Running ram in xmp profile is fine and as you previously mentioned you ran memtest and I assume it passed it all clear all runs right?

As I mentioned previously I would like to see what your event viewer is throwing out so as to locate the culprit.
 
In my experience with machines I have built / had and troubleshooting friends, 99% of times if an OC is not involved, lockups are caused by GPU, either PSU not doing it's job or the GPU either failing or GPU memory working beyond it's limits.

Are you saying that even with integrated you still got identical lock ups?

Make sure if your PSU is multiple rail that you have it laid out correctly. That is to say, not everything daisy-chained off of the same rail. So make sure you have enough amps on that to cover everything it's plugged into. If you have a PSU issue, when put the GPU in it may only magnify the issue, especially if it doesn't have it's own two feeds with enough amps to run.

Have you tried OCCT power test and checked to see what the system voltages are doing?

If you haven't mind, run OCCT at your own risk, I've set fire to overclocked systems motheboards with that application lol.
 
Sorry, just to add, whenever I have seen disk errors they tend to result in blue screens that relate to either a file that was not read, or failed to load in the OS, same as system memory dropping what's stored in it, I don't think I have ever seen a lock up. Even with a failed HDD controller I have seen blue screens and then the inevitable disk failure symptoms (fail to even mount the device).

I would still be looking towards power myself?
 
In my experience with machines I have built / had and troubleshooting friends, 99% of times if an OC is not involved, lockups are caused by GPU, either PSU not doing it's job or the GPU either failing or GPU memory working beyond it's limits.

Are you saying that even with integrated you still got identical lock ups?

Make sure if your PSU is multiple rail that you have it laid out correctly. That is to say, not everything daisy-chained off of the same rail. So make sure you have enough amps on that to cover everything it's plugged into. If you have a PSU issue, when put the GPU in it may only magnify the issue, especially if it doesn't have it's own two feeds with enough amps to run.

Have you tried OCCT power test and checked to see what the system voltages are doing?

If you haven't mind, run OCCT at your own risk, I've set fire to overclocked systems motheboards with that application lol.

He listed "Evga Modular PSU" which depending on which model would be single or multi, but regardless of layout should still not cause locks ups like mentioned as it has more than sufficient amperage on their rails.

Testing with Furmark would tell pretty fast how stable the gpu is, instability in a video card would more than likely cause the video driver to crash, that's partially why I suggested that op posted his findings of event viewer.However artifacts, freezing,crashing,instability can also be symptoms of a dying card.

Simplest method I can think of off hand would be to install the card in a friends pc and run something like Furmark.

Windows Kernel event ID 41 error is usually from a bad oc, overheating, memory or power supply.. It also just means that your pc was improperly shutdown, so if his system locked up and he held the power button down to turn it off he would get that error regardless.

You can test the power supply if you have a multimeter handy, some power supplies just don't play nice with other hardware.

In my personal experience and I have had this issue several times but on most recent in first case it was my power supply and in my second it was an unstable factory overclocked evga gtx 980 ftw, I was having several display losses ,driver crashing, lockups and sure enough I exchanged it for an asus model and all problems stopped.

When it was my power supply I was having boot errors and random restarts until I tested the rails with a multi meter.

just my two cents..
 
In my experience with machines I have built / had and troubleshooting friends, 99% of times if an OC is not involved, lockups are caused by GPU, either PSU not doing it's job or the GPU either failing or GPU memory working beyond it's limits.

Are you saying that even with integrated you still got identical lock ups?

Make sure if your PSU is multiple rail that you have it laid out correctly. That is to say, not everything daisy-chained off of the same rail. So make sure you have enough amps on that to cover everything it's plugged into. If you have a PSU issue, when put the GPU in it may only magnify the issue, especially if it doesn't have it's own two feeds with enough amps to run.

Have you tried OCCT power test and checked to see what the system voltages are doing?

If you haven't mind, run OCCT at your own risk, I've set fire to overclocked systems motheboards with that application lol.

Yep, running on integrated, I still got the PC crashing, so luckily its not my graphics card??


I have my PSU from my past machine (A not moduar XFX PSU that sometimes clicks :( ), I could test my machine on that. Its good I have a list of other things to test if I have another crash. (Just got back home, will continue to use pc without the Seagate HDD as posted earlier)

I've ran OCCT and with the GPU and Processor on full, it seems ok...

EDIT: if its any help, im more than happy to make a diagram or somthing to explain how my PSU is wired up, I just havent had one before so I have no idea if im doing anything right or wrong
 
Would do no harm to test the other supply(that click u hear is likely just a relay which is perfectly normal btw).

Out of curiosity, is your version of windows 10 an upgrade from a previous version of windows eg 7 8 or 8.1? I ask only because I had a lot of bugs until I clean installed win 10 after upgrading myself.

If you are still crashing in safe mode it's likely hardware related but if its fine then its a driver conflict most likely.

These kind of things can prove frustrating but on the upside you will learn a lot from it when finding the resolution.

I have a suspicion that the psu could be the culprit, just my gut feeling. Test your older psu and report your finding's fingers crossed for you :)
 
Would do no harm to test the other supply(that click u hear is likely just a relay which is perfectly normal btw).

Out of curiosity, is your version of windows 10 an upgrade from a previous version of windows eg 7 8 or 8.1? I ask only because I had a lot of bugs until I clean installed win 10 after upgrading myself.

If you are still crashing in safe mode it's likely hardware related but if its fine then its a driver conflict most likely.

These kind of things can prove frustrating but on the upside you will learn a lot from it when finding the resolution.

I have a suspicion that the psu could be the culprit, just my gut feeling. Test your older psu and report your finding's fingers crossed for you :)

Hmm, I was thinking it was the PSU too, well, i'll keep looking and will be updating what happens as much as I can :)

Also, when I set up the PC, it was fully a clean install (Apart from the key ofcourse)
 
Ok, another report, It crashed again (So the old HDD isnt the problem) so I have changed to my old PSU, all I have to do is wait...

Highly highly doubt its the old hdd unless it had the os installed on it, hopefully all goes well with the older psu, sometimes some hardware just doesn't play nice together
 
Back
Top Bottom