Random Freezing

Associate
Joined
1 May 2015
Posts
107
Hello all & happy holidays. Was wondering if anyone can help me with my freezing issue i have been having for awhile. I have a dump file from the crash, which i will attach, but cant read it.

The crash seems to be related to ntoskrnl.exe. Not too sure what else to do.

I thought I would add that my CPU and GPU are overclocked.

6700k @ 4.6GHz 1.36 on the core

GTX 980 TI +60mV / +152 core clock / +400 memory clock

Thanks! :)
 
When you say freezing, is the entire PC crashing/freezing and you need to reboot it?

I would also suggest downloading BSOD viewer as you can then read the dump file. It sounds to me like an unstable overclock...does it do the same if you put everything to stock?
 
After some Googlefoo:

How to fix ntoskrnl.exe BSOD
Check your memory
The ntoskrnl.exe BSOD is usually related to memory so you might need to simply replace your RAM. Take out each stick of RAM one by one and try to boot your system, this may help you find the faulty memory but the lot might need replacing.

Overclocking
If you're overclocking your system with a higher CPU clock speed, put this back to normal as it might be causing problems.

Update drivers
If you have a RAID setup of disk drives, update your drivers. Also update other drivers for hardware as this problem can be caused by drivers not matching the OS.

Above from PC Advisor
 
When you say freezing, is the entire PC crashing/freezing and you need to reboot it?

I would also suggest downloading BSOD viewer as you can then read the dump file. It sounds to me like an unstable overclock...does it do the same if you put everything to stock?

The entire PC freezes meaning I have to hard reset it. I haven't tested stock, but will be running stock now for a few days to see if it occurs. It is a very random crash and the last one I had was a little over a week ago.


Reset all cpu and gpu to default and see if it problem reoccurs.

I will do this as mentioned above, and hopefully there are no freezes. If I don't crash can I then try an overclock on the CPU and see if the problem occurs?
 
After some Googlefoo:

How to fix ntoskrnl.exe BSOD
Check your memory
The ntoskrnl.exe BSOD is usually related to memory so you might need to simply replace your RAM. Take out each stick of RAM one by one and try to boot your system, this may help you find the faulty memory but the lot might need replacing.

Overclocking
If you're overclocking your system with a higher CPU clock speed, put this back to normal as it might be causing problems.

Update drivers
If you have a RAID setup of disk drives, update your drivers. Also update other drivers for hardware as this problem can be caused by drivers not matching the OS.

Yesterday i ran a memtest for over 9 hours with no errors at the end. I think this could be highly related to the overclocks like others have mentioned, so reverting to stock to see if this issue arises again.

All drivers are up to date, and i'm not running a raid setup.

Thanks for the reply!

Above from PC Advisor
 
Its probaly to do with your overclock on your cpu, you could downclock it to say 4.4 ghz and see how it is .

Just an after thought what psu you got ?
 
Its probaly to do with your overclock on your cpu, you could downclock it to say 4.4 ghz and see how it is .

Just an after thought what psu you got ?

Probably yes, I'm hoping anyway. Ill run stock on CPU for a little over a week and see if I run into a crash. If I don't I'll start a mild overclock and work up. Thanks for the help, I will update with any crashes through the week.

Just saw your edit, I have a Seasonic 650W G Series PSU.
 
Probably yes, I'm hoping anyway. Ill run stock on CPU for a little over a week and see if I run into a crash. If I don't I'll start a mild overclock and work up. Thanks for the help, I will update with any crashes through the week.

Just saw your edit, I have a Seasonic 650W G Series PSU.

Quality unit, good luck.
 
Thought I would update. Didn't have any crashes over the week, so tomorrow I will start with a mild CPU overclock and work my way up. Hopefully can get everything stable this time around :)
 
Very well could be, how often do you crash?

After removing any OC I had there was no crashes over the week, so don't think there is a driver issue on my side.
Every day since I installed the latest Nvidia drivers. What motherboard do you have? I've reduced my overclock and so far so good but this seems more than a coincidence to me. Never had any problems with OC before until now.
The usual google'd solutions do nothing.
 
I'm getting the same thing happening. No NVidia or AMD graphics card just the Intel IGP. Mine is a Gigabyte Z170X Gaming 3... with overclocking. So am going to try to go back without any OC. Ran memtest today and it came back clean. Corsair C14 2400mhz LPR Black RAM.
 
Memtest clean for me too but I wasn't expecting anything different. Reason I suspected Nvidia is the update was same day my problems started even though its not usually associated with the bluescreen I got. Maybe a sly windows update has changed something?
 
It's more likely that something in the newest NVIDIA drivers is causing a pattern of CPU usage which is more likely to trigger the same underlying freezing issue.

As an example: every time I try installing a particular software, it will freeze fairly reliably at the very end of the install. And elsewhere, if I open up a specific Hi-Def video stream (with a particular less-used encoding) in Kodi, the freeze will occur every time.

So it that is the case you may find you can trigger the freezing in certain other specific ways (if after you rolled rollback your nvidia software).
 
I haven't rolled back yet, I wanted to test the cpu overclock first like krome_ninja has. So far today no crashes.
I use my machine for pretty GPU stressful tasks, so when an Nvidia driver release is dodgy I find out pretty quickly. Just never had bluescreens before so I'm keen on tracking down the rogue item. Thanks for posting about yours.
 
Yeah I haven't removed my OC settings yet. Not until I have a reliable test case / fail case with which to reproduce the problem. Perhaps an HVEC video file or youtube link would be a good candidate. i.e. something that others here can also try to use to reproduce it with.
 
Back
Top Bottom