Random Freezing

I can't help there as people wont have access to the same software I use. It did crash once when playing Life is Strange the other night briefly though.
 
cadmunkey said:
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.
Click to expand...

I have a Z170-A with 6700k. I tested most of the newer bios versions and nothing helped. If you have ad no problems until now, then it is most probably the new driver issue. How long have you had that oc for?
 
cadmunkey said:
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.
Click to expand...

Its defiantly annoying! still haven't had any issues and have had system running all day. Will keep this thread updated, and would like to know if you find anything out :)
 
dreamcat4 said:
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.
Click to expand...

I tried to find the cause when trying to re create crashes, but they were always at random times with random applications. Happened twice with CSGO, and once whilst in a skype call with light browser work also.
 
deffo sounds like an overclock issue as apposed to driver , only start to reapply your overclock after a few weeks of non freezing . and then just up it a bit by a time.
 
joedeath332 said:
deffo sounds like an overclock issue as apposed to driver , only start to reapply your overclock after a few weeks of non freezing . and then just up it a bit by a time.
Click to expand...

I was having crashes often within one week time period, so after not having an oc, and no crashes I am now slowly testing oc's. I have been running 4.4GHz for two days stable so far. Will keep updated.
 
joedeath332 said:
deffo sounds like an overclock issue as apposed to driver , only start to reapply your overclock after a few weeks of non freezing . and then just up it a bit by a time.
Click to expand...
I'd usually agree, but had my overclock for months without problems, and sounds like all 3 of us started with this crashing around the same time. Too big a coincidence for it to be just the OC?
 
cadmunkey said:
but had my overclock for months without problems
Click to expand...

Hmm. I would question if anything else changed too. Not excluding BIOS update and / or intel microcode...

I would also mention ambient temperature. But if you live in UK then presumably it's been going the other way.

And can you guys please post your CPU / RAM / MOBO if it isn't already in our signature? Thanks.
 
dreamcat4 said:
Hmm. I would question if anything else changed too. Not excluding BIOS update and / or intel microcode...

I would also mention ambient temperature. But if you live in UK then presumably it's been going the other way.

And can you guys please post your CPU / RAM / MOBO if it isn't already in our signature? Thanks.
Click to expand...

BIOS update yes. I have tried most of the newest versions from the Asus website, and all didn't affect the persistent crashes.

And sure system specs are:

i7 6700k
Z170-A
Corsair Vengance 16GB @ 3000MHz
GTX 980TI
Seasonic G Series 650w
 
Right. So the only things me & you seem to have in common are the Corsair LPX ram, and the fact that we are overclocking our skylake z170. Unless you also happen to have the same OEM mfr as my Silverstone Strider PSU.

What I have been able to do (since yesterday) is reproduce the problem reliably. Unfortunately the test requires installation of a demanding commercial software and therefore cannot be shared for everybody to use / try to reproduce.

Anyway at this point I have run quite a few tests. With slightly different freqencies and multipliers. Just gotta keep going to hone it down further.

I'll let you guys know probably by this evening.

BTW: the tool "BlueScreenView" is really essential for viewing these freezes and/or BSODs. So it's recommended for anyone else who experience such unpredictable crashes. As we have all of us already described here ^^.
 
dreamcat4 said:
Right. So the only things me & you seem to have in common are the Corsair LPX ram, and the fact that we are overclocking our skylake z170. Unless you also happen to have the same OEM mfr as my Silverstone Strider PSU.

What I have been able to do (since yesterday) is reproduce the problem reliably. Unfortunately the test requires installation of a demanding commercial software and therefore cannot be shared for everybody to use / try to reproduce.

Anyway at this point I have run quite a few tests. With slightly different freqencies and multipliers. Just gotta keep going to hone it down further.

I'll let you guys know probably by this evening.

BTW: the tool "BlueScreenView" is really essential for viewing these freezes and/or BSODs. So it's recommended for anyone else who experience such unpredictable crashes. As we have all of us already described here ^^.
Click to expand...

I actually thought it was related to the ram modules, but ran memtest for a day and there were no issues.

I was never able to re create my crashes, so atleast you have been able to determine that.

I have been using the BlueScreenView to be able to find out it was related to ntoskrnl.exe.
 
OK. Have now finished my testing for today with the reproducible fail case. My system had Prior to testing (and with this instability issue) the following settings were being overclocked:

* CPU CORE FREQ
* RING BUS / 'UN-CORE' FREQ (includes IMC)
* DDR4 RAM FREQ

My findings were that (for my specific system):

* System stability was NOT improved by lowering the:
* RING BUS / 'UN-CORE' FREQ
* DDR4 RAM FREQ

* System stability WAS improved by lowering the:
* CPU CORE FREQ

So my best advice for others is to lower their Core CPU Freq.

HOW MUCH?

By approximately 1 BIN (100 Mhz) is the best figure I can come up with ATM. (well for me it was 88 Mhz actually).

Because when I did that my test case went from fail every time --> run successfully 9 times in a row. Which was the maximum length of my testing. Meaning 0 failures detected.

Therefore system's measurable stability increased by at least 9 times. So the rate of failures occuring again should be now be at most 1/9th of the prior value (11%). But we would hope it to be even less than that.

I will have to conduct further test runs in order to gain a higher degree of confidence in this result. And also leave it like this for at least 1 week (like other guy here ^^ earlier in the thread).


[EDIT]
System specs were:

* Intel i5-6600K
* 2x8 GB Corsair Vengance LPX Black DDR4 rated @ 2400Mhz C14-15-15-31 timings
* Gigabyte Z170X Gaming 3 Rev 1.0, with Latest Beta Firmware F5j
* Silverstone Strider SST-SX500-LG PSU
* Windows 10 Pro v1151, Build 10586.36
* Killer NIC disabled in windows / networking adapters
* CPU Core Voltage ~ 1.2v (the mfr's auto-voltage setting)
* XMP Profile --> On, VCore Loadline Calibration --> High
* Moderate air cooling
* Memtest x86 - All OK
* Prime95 In-Place Large FFTs (CPU stress test) - All OK
* BSOD Analysis Tool: "BlueScreenView"



Test case:

Install Adobe AfterEffects CC 2015

Test results:

# default OC settings 101.96 * 45 ---> 4.588 Ghz
# uncore - 43 --> 4.38 GHz
# ram 2448 mhz
# 1st time - FAIL

# cpu bclk 101.96, multiplier 45 --> 44 ---> 4.484 Ghz
# uncore - 43 --> 4.38 GHz
# ram 2448 mhz
# 1,2nd time - NO_FAIL <----- SUCCESS CASE #1

# bclk 101.96 --> 101.54 ---> 4.57 Ghz
# uncore - 43 --> 4.36 GHz
# ram 2437 mhz
# 1st time OK, 2nd time - FAIL

# bclk 101.96 --> 101.33 ---> 4.56 Ghz
# uncore - 43 --> 4.36 GHz
# ram 2431 mhz
# 1st time OK, 2nd time - FAIL

# bclk 101.96 --> 101.12 ---> 4.55 Ghz
# uncore - 43 --> 4.35 GHz
# ram 2426 mhz
# 1,2nd time - OK, 3rd time - FAIL

# cpu bclk 101.96 --> 100.00 * 45 ---> 4.50 Ghz
# uncore - 43 --> 4.30 GHz
# ram 2393 mhz
# 1,2,3,4,5,6,7,8,9 th time - NO_FAIL <----- SUCCESS CASE #2

# cpu 46 * 99.74 ---> 4.588 Ghz
# uncore - 43 --> 4.28 GHz
# ram 2393 mhz
# 1st time - FAIL
 
Last edited:
dreamcat4 said:
OK. Have now finished my testing for today with the reproducible fail case. My system had Prior to testing (and with this instability issue) the following settings were being overclocked:

* CPU CORE FREQ
* RING BUS / 'UN-CORE' FREQ (includes IMC)
* DDR4 RAM FREQ

My findings were that (for my specific system):

* System stability was NOT improved by lowering the:
* RING BUS / 'UN-CORE' FREQ
* DDR4 RAM FREQ

* System stability WAS improved by lowering the:
* CPU CORE FREQ

So my best advice for others is to lower their Core CPU Freq.

HOW MUCH?

By approximately 1 BIN (100 Mhz) is the best figure I can come up with ATM. (well for me it was 88 Mhz actually).

Because when I did that my test case went from fail every time --> run successfully 5 times in a row. Which was the maximum length of my testing. Meaning 0 failures detected.

Therefore system's measurable stability increased by at least 5 times. So the rate of failures occuring again should be now be at most 1/5th of the prior value (20%). But we would hope it to be even less than that.

I will have to conduct further test runs in order to gain a higher degree of confidence in this result. And also leave it like this for at least 1 week (like other guy here ^^ earlier in the thread).


[EDIT]
System specs were:

* Intel i5-6600K
* 2x8 GB Corsair Vengance LPX Black DDR4 rated @ 2400Mhz C14-15-15-31 timings
* Gigabyte Z170X Gaming 3 Rev 1.0, with Latest Beta Firmware F5j
* Silverstone Strider SST-SX500-LG PSU
* Windows 10 Pro v1151, Build 10586.36
* Killer NIC disabled in windows / networking adapters
* Moderate air cooling
* Memtest x86 - All OK
* Prime95 2nd Stress test (moderate FFT) - All OK




Test case:

Install Adobe AfterEffects CC 2015

Test results:

# default OC settings 101.96 * 45 ---> 4.588 Ghz
# uncore - 43 --> 4.38 GHz
# ram 2448 mhz
# 1st time - FAIL

# cpu bclk 101.96, multiplier 45 --> 44 ---> 4.484 Ghz
# uncore - 43 --> 4.38 GHz
# ram 2448 mhz
# 1,2nd time - NO_FAIL <----- SUCCESS CASE #1

# bclk 101.96 --> 101.54 ---> 4.57 Ghz
# uncore - 43 --> 4.36 GHz
# ram 2437 mhz
# 1st time OK, 2nd time - FAIL

# bclk 101.96 --> 101.33 ---> 4.56 Ghz
# uncore - 43 --> 4.36 GHz
# ram 2431 mhz
# 1st time OK, 2nd time - FAIL

# bclk 101.96 --> 101.12 ---> 4.55 Ghz
# uncore - 43 --> 4.35 GHz
# ram 2426 mhz
# 1,2nd time - OK, 3rd time - FAIL

# bclk 101.96 --> 100.00 * 45 ---> 4.50 Ghz
# uncore - 43 --> 4.30 GHz
# ram 2393 mhz
# 1,2,3,4,5th time - NO_FAIL <----- SUCCESS CASE #2

# cpu 46 * 99.74 ---> 4.588 Ghz
# uncore - 43 --> 4.28 GHz
# ram 2393 mhz
# 1st time - FAIL
Click to expand...

Further showing that this is related to CPU OC stability. Not saying this is everyone's scenario, but with two users having results after altering cpu ratios its seeming more like the suspect.

Would be great to hear from the other guys to see if adjusting their OC reduced their crashes like dreamcat4.
 
I dont have much time to test today as I'm busy with work. Still no crashes today with no OC despite running several intense CPU/GPU programs. Will start notching up the overclock a bit each day over the next few days and report back.
 
cadmunkey said:
I dont have much time to test today as I'm busy with work. Still no crashes today with no OC despite running several intense CPU/GPU programs. Will start notching up the overclock a bit each day over the next few days and report back.
Click to expand...

Ok sounds good. I will be doing the same, will also run the RAM modules through a test again to be sure.
 
Well I suppose if adobe still lets you download the free trial version of aftereffects from their website, then anybody else can try running the same kind of tests as me too :)

Tried everything else, playing 4k HEVC videos etc, and nothing else would reliably reproduce the failure case.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom