Question New Build, Random Temporary Freezing

[noidis]

Hey guys, just finished building a new PC, and upon updating Windows 10 I get these intermittent and somewhat random freezes coupled with a minor CPU usage spike. Though the screen freezes audio isn't distorted and whatever actions I take are carried out once the system 'catches' back up.

I'm not sure how to go about fixing it, as I've already tried reinstalling Win 10 three times.

Specs:
i9 - 9900k (no OC yet)
Gigabyte Aorus Master
64GB Trident Z RGB (xmp disabled currently, memtest86 pass for 1.5 hours)
Zotac AMP! 2080
HP EX920 - 1TB M.2 (OS)
Intel 660p - 2TB M.2 (Not formatted or used by system yet)
EVGA G3 1000w PSU
Coolermaster ML360 RGB aio

My idle CPU temps are 32C - 45C
My temps under Prime95 are 68C - 82C


Any help or direction would be amazing, I'm really unsure what is to blame for this annoying problem.

 

[onespeedbiker]

You might try and disable CSM support in the BIOs. The manual also shows 3 m.2 slots, two shared with sata and one exclusive PCIe, I would make sure your PCIe ssd is in the exclusive PCIe slot.

 

[noidis]

You might try and disable CSM support in the BIOs. The manual also shows 3 m.2 slots, two shared with sata and one exclusive PCIe, I would make sure your PCIe ssd is in the exclusive PCIe slot.

I'll give disabling CSM a try, but for the m.2's they're in the top two most m.2 slots, with the EX920 being in the top spot. It seems from the manual that's the correct way to have them right?

Thanks

 

[onespeedbiker]

I guess it depends on the orientation. Your ssd is PCIe not sata. The m.2 PCIe slot is the m2P slot, which in this diagram is on the bottom.

 

[noidis]

Oh that's interesting, okay I'll swap the EX920 to the bottom and see if that helps as well. Do you think I should remove the Intel SSD from the other slot temporarily as well?

 

[Calvin7]

64GB Trident Z RGB

Part number and/or link to it?
https://www.gskill.com/en/finder?cat=31&series=2860

 

[onespeedbiker]

Yes, it shouldn't be an issue, but it's just one thing less to worry about.

 

[noidis]

64GB Trident Z RGB

Part number and/or link to it?
https://www.gskill.com/en/finder?cat=31&series=2860

2 sets of the following:
https://www.newegg.com/g-skill-32gb-288-pin-ddr4-sdram/p/N82E16820232750

 

[noidis]

So I tried to reorient the drives, but the bottom most slot is too short for either of my NVME drives. Searches related to the drives slots seem to suggest that it's fine to run the drives in the top two however.

That being said after removing the intel 660p and just using the HP the issue persists.

I did disable CSM support, and while the issue still seems to occur it "feels" much less frequent compared to previously, though as the system is on the frequency definitely seems to pick up.

Another point of note, the freezing issue only becomes apparent after I get Windows 10 up-to-date, prior to that in the original pre-1809 build that I install from my USB stick there is no freezing taking place.



Some side observations about the freezing, when typing this post I noticed that if a "freeze" occured the blinking cursor in the reply window continued to blink even if my text wouldn't show when letters were typed until the the system "caught up".

Watching my temperature monitors closely (Both Core Temp and HWMonitor), I'm noticing that a single core always seems to spike to near 100% prior to every instance of the freeze. What could be causing this in windows?

 

[onespeedbiker]

Overheating is the primary cause of the issues you are describing. I would remove your fan and CPU, clean them, reapply the paste and reinstall.

 

[noidis]

Overheating is the primary cause of the issues you are describing. I would remove your fan and CPU, clean them, reapply the paste and reinstall.

You might be right, I've already tried remounting once before, but I'll give it a go with another cooler I know works (just in case my new aio is the issue)

I'd ran Prime95 for 20 minutes before (while the freezing was occurring) and my temps while high were sitting in the mid 80's, could this really be a temp problem, especially with the CPU utilization spikes?

Thanks for the help btw!

 

[onespeedbiker]

Watching my temperature monitors closely (Both Core Temp and HWMonitor), I'm noticing that a single core always seems to spike to near 100% prior to every instance of the freeze. What could be causing this in windows?

If you have already remounted your CPU to the cooler, than don't do it again, it can damage your CPU..OTOH, you might want to try reseating it in the plug; too much pressure before pushing down the clamp arm can cause problems.

 

[onespeedbiker]

What is your computer doing when if freezes? What app or program(s) are you running? I have read up on a single core (usually the 0 core) being overused with programs not designed to work with multiple cores, you can have 2 or more programs all using just one core and that can cause a freeze.

 

[noidis]

What is your computer doing when if freezes? What app or program(s) are you running? I have read up on a single core (usually the 0 core) being overused with programs not designed to work with multiple cores, you can have 2 or more programs all using just one core and that can cause a freeze.

Generally I've had chrome and/or edge (chrome has often not been able to access the web, but I figured that problem could be remedied once the system is stable), and then HWMonitor or core temp running.

The spikes only impact a single core, as when I reset the min-max in HWMonitor I'll see upon the next freeze a single cores maximum reach 100% while all others are sub 40%.

I'll try to reseat the CPU, I wasn't aware remounting the cooler could damage it, luckily this being a new build I've only adjusted it three or so times thus far.

 

[onespeedbiker]

The problem looks to be some program not designed to run on multiple cores hogging a single core, as I said it's almost always the 0 core (0-7 with an 8 core CPU), because that is the core addressed by software that runs only on a single core. You may have to use trial and error find out what program(s) are only using one core and might causing the spikes and freezing. It's doubt full it would be a windows application; try using the Task Manager Resource Manager which can track individual programs and see which is using only one core. It can also be malware..

 

[noidis]

The problem looks to be some program not designed to run on multiple cores hogging a single core, as I said it's almost always the 0 core (0-7 with an 8 core CPU), because that is the core addressed by software that runs only on a single core. You may have to use trial and error find out what program(s) are only using one core and might causing the spikes and freezing. It's doubt full it would be a windows application; try using the Task Manager Resource Manager which can track individual programs and see which is using only one core. It can also be malware..

The issue is that outside of drivers from Gigabyte's site, my Nvidia driver, Chrome and Core Temp + HWMonitor, I'm literally not downloading or installing anything else to the PC.

When I run programs to test it's only Edge, and HWMonitor. I tried Coretemp pretty much just to see if it was HWMonitor, but the problem persisted.

Additionally it's not just the 0 core spiking to 100%. Here's an image of my HWMonitor after about 25 mins of the pc being on: Imgur

Each of those maximums are established one by one as the PC enters into an instance of "freezing", as right at boot the numbers are fairly low.

I've been watching Task Manager in the hopes I'd see which service or program is spiking with my CPU utilization spikes, but I can only see the list update AFTER a freeze has happened, so I have no idea what is rising with it.

I'm going to try reinstalling Windows again, and not updating anything to doubly check that the issue occurs AFTER I update Windows only, but I'm kind of at a loss for how else to figure this out.

 

[noidis]

Another windows 10 install down, installing only the wifi driver and hwmonitor, and deffering updates my system seems stable. Two cores reported high maximums (90% on core#4 and 86% on core#6), but the rest were all 50% or below.

I'm going to update again and see how this changes things.

 

[onespeedbiker]

I see your MB has onboard graphics. In order to eliminate the Graphics drivers as the/a culprit, I would pull the GPU card and run off the Intel graphics for a while.

 

[noidis]

I see your MB has onboard graphics. In order to eliminate the Graphics drivers as the/a culprit, I would pull the GPU card and run off the Intel graphics for a while.

I'll give this a shot and report back.

As for my update, I updated and left the PC idling (Without installing anything), upon return I found that none of the cores had reached 100%, though a few were in the 87%-96% ranges.

Using the PC a bit (Mainly browsing for more ideas on how to troubleshoot with Edge) I didn't encounter any total freezes.

I then downloaded LatencyMon and left it running unattended for a while (The system again never reached 100% on any single core, but had the high 80+%'s on a few of the cores).

I am not sure how to read anything on this program however, but I could share that information if it might help.

After seeing the system hadn't reached 100% on any core I decided to try reinstalling Chrome, and low and behold the system began to freeze up once again, and while previously none of my cores were at 100%, now quite a few are.

 

[onespeedbiker]

Search Chrome freezing Windows 10 and you'll get many many pages. Here is one with some fixes. https://www.blogsdna.com/29640/fix-chrome-crashing-freezing-not-responding.htm

Edit, Here are some more Chrome fixes. https://windows101tricks.com/fix-google-chrome-high-cpu-usage/

 

[noidis]

Search Chrome freezing Windows 10 and you'll get many many pages. Here is one with some fixes. https://www.blogsdna.com/29640/fix-chrome-crashing-freezing-not-responding.htm

Edit, Here are some more Chrome fixes. https://windows101tricks.com/fix-google-chrome-high-cpu-usage/

Thanks for the suggestions, sadly after having gone through almost all of them (Bar a few that weren't applicable like disabling extensions, I currently have none as this is a fresh install) the problem persists.

Some more testing has yielded even more strange info on my problem however.

When running LatencyMon's IDLT (In Depth Latency Test), the application forces my CPU's utilization to crank up and stay near 100% usage on every core.

Here's where it's interesting, while this is happening my system is snappy, Chrome works just fine, and it seems like the issue isn't present at all.

I'm going to try other stress testing programs again, this time while trying to use the PC to see if I get similar results.

It's very perplexing that when a single core hits 100% this build freezes up entirely, but when it's pushed it seems to perform as it should...


EDIT: Ran prime95, same results. The freezing issue isn't present when the CPU is under heavy load it seems. That being said my temps on a small ftt test were high 90's (Which maybe suggests my AIO isn't cooling well?)

 

[Calvin7]

Multiple kits of F4-3000C16D-32GTZR have no guarantee to be compatible together. Freezing is a sign the memory is not compatible with each other. Try using one kit and enabling XMP.

 

[noidis]

Multiple kits of F4-3000C16D-32GTZR have no guarantee to be compatible together. Freezing is a sign the memory is not compatible with each other. Try using one kit and enabling XMP.

That's good to know, is the chance of incompatibility high?

I've removed both sets (Alternating which two were in, as well as which slots they occupied [A1/B1 and A2/B2] per the manual).

No change. I still am getting cores ramping up to 100% one at a time. However the freezing feels like it doesn't last as long with X.M.P. enabled in the bios, though it's really hard to say if it's actually freezing for less time or not.

LatencyMon also displays the following when I am using it to monitor my system with only Chrome open:

_
CONCLUSION
_
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:04:16 (h🇲🇲ss) on all processors.


_
SYSTEM INFORMATION
_
Computer name: ATTT
OS version: Windows 10 , 10.0, version 1809, build: 17763 (x64)
Hardware: Z390 AORUS MASTER, Gigabyte Technology Co., Ltd., Z390 AORUS MASTER-CF
CPU: GenuineIntel Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
Logical processors: 16
Processor groups: 1
RAM: 32702 MB total


_
CPU SPEED
_
Reported CPU speed: 360 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 761.10
Average measured interrupt to process latency (µs): 3.132985

Highest measured interrupt to DPC latency (µs): 758.80
Average measured interrupt to DPC latency (µs): 1.213924


_
REPORTED ISRs
_
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 154.506111
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0.051471
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0.065610

ISR count (execution time <250 µs): 169034
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_
REPORTED DPCs
_
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 1236.843333
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.021514
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 419.67 , NVIDIA Corporation

Total time spent in DPCs (%) 0.055988

DPC count (execution time <250 µs): 668109
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 2
DPC count (execution time 1000-1999 µs): 1
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0


_
REPORTED HARD PAGEFAULTS
_
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: chrome.exe

Total number of hard pagefaults 12268
Hard pagefault count of hardest hit process: 3592
Number of processes hit: 49


_
PER CPU DATA
_
CPU 0 Interrupt cycle time (s): 15.194427
CPU 0 ISR highest execution time (µs): 154.506111
CPU 0 ISR total execution time (s): 2.687918
CPU 0 ISR count: 168903
CPU 0 DPC highest execution time (µs): 498.457222
CPU 0 DPC total execution time (s): 2.234633
CPU 0 DPC count: 653051
_
CPU 1 Interrupt cycle time (s): 9.133910
CPU 1 ISR highest execution time (µs): 3.100556
CPU 1 ISR total execution time (s): 0.000131
CPU 1 ISR count: 131
CPU 1 DPC highest execution time (µs): 124.120
CPU 1 DPC total execution time (s): 0.006022
CPU 1 DPC count: 834
_
CPU 2 Interrupt cycle time (s): 8.263946
CPU 2 ISR highest execution time (µs): 0.0
CPU 2 ISR total execution time (s): 0.0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 140.218889
CPU 2 DPC total execution time (s): 0.006817
CPU 2 DPC count: 1634
_
CPU 3 Interrupt cycle time (s): 10.316872
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 44.30
CPU 3 DPC total execution time (s): 0.000704
CPU 3 DPC count: 257
_
CPU 4 Interrupt cycle time (s): 6.749056
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 1236.843333
CPU 4 DPC total execution time (s): 0.004418
CPU 4 DPC count: 901
_
CPU 5 Interrupt cycle time (s): 8.639355
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 81.978889
CPU 5 DPC total execution time (s): 0.000991
CPU 5 DPC count: 351
_
CPU 6 Interrupt cycle time (s): 8.015479
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 121.743333
CPU 6 DPC total execution time (s): 0.007890
CPU 6 DPC count: 2250
_
CPU 7 Interrupt cycle time (s): 8.345397
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 90.455556
CPU 7 DPC total execution time (s): 0.001194
CPU 7 DPC count: 297
_
CPU 8 Interrupt cycle time (s): 7.100241
CPU 8 ISR highest execution time (µs): 0.0
CPU 8 ISR total execution time (s): 0.0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 95.550556
CPU 8 DPC total execution time (s): 0.002205
CPU 8 DPC count: 800
_
CPU 9 Interrupt cycle time (s): 9.496930
CPU 9 ISR highest execution time (µs): 0.0
CPU 9 ISR total execution time (s): 0.0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 70.076667
CPU 9 DPC total execution time (s): 0.001066
CPU 9 DPC count: 302
_
CPU 10 Interrupt cycle time (s): 6.494046
CPU 10 ISR highest execution time (µs): 0.0
CPU 10 ISR total execution time (s): 0.0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 82.603333
CPU 10 DPC total execution time (s): 0.001931
CPU 10 DPC count: 542
_
CPU 11 Interrupt cycle time (s): 8.335309
CPU 11 ISR highest execution time (µs): 0.0
CPU 11 ISR total execution time (s): 0.0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 54.550
CPU 11 DPC total execution time (s): 0.000454
CPU 11 DPC count: 116
_
CPU 12 Interrupt cycle time (s): 6.580966
CPU 12 ISR highest execution time (µs): 0.0
CPU 12 ISR total execution time (s): 0.0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 301.151111
CPU 12 DPC total execution time (s): 0.009192
CPU 12 DPC count: 2877
_
CPU 13 Interrupt cycle time (s): 8.067165
CPU 13 ISR highest execution time (µs): 0.0
CPU 13 ISR total execution time (s): 0.0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 101.477222
CPU 13 DPC total execution time (s): 0.001651
CPU 13 DPC count: 441
_
CPU 14 Interrupt cycle time (s): 6.246464
CPU 14 ISR highest execution time (µs): 0.0
CPU 14 ISR total execution time (s): 0.0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 94.212778
CPU 14 DPC total execution time (s): 0.010286
CPU 14 DPC count: 2680
_
CPU 15 Interrupt cycle time (s): 7.571899
CPU 15 ISR highest execution time (µs): 0.0
CPU 15 ISR total execution time (s): 0.0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 133.526667
CPU 15 DPC total execution time (s): 0.004367
CPU 15 DPC count: 779
_

 

[noidis]

I decided to go for broke and try to push the 1903 May update for Win10 to my system. So far about 30 mins in and I've not had any freezing, and the highest a single core has gone is 75%.

I'm really not sure why this would have corrected it, and I'm still really keen to know what exactly was wrong before...

Chrome still doesn't work (Pages hang, as if there is a connectivity problem while Edge and Firefox have no such issues), though I've no idea where to try and tackle that issue from considering I've done just about everything I can think of to remedy it already (Including fixes posted in this thread).

I don't know if I'm out of the woods, but I'm not sure how I should test for stability now either as all stress testing on this system hadn't caused any crashes.

Thanks for the help thus far, but if anyone's got any more suggestions or ideas I'd still love for any direction with regards to this confusing issue!