Windows 10 delay and lag on brand new computer

DejanMars

Reputable
Aug 13, 2016
8
0
4,510
I recently built computer with SSD. I installed Windows 10 Pro (clean install) and a few programs.



If I open right-click menu/ click on start menu, type on some form, move window... windows freezes for 2 - 10 seconds. Sometimes I can move mouse and see animations, but buttons don't respond.



That wired behaviour doesn't appear every time.



What I tried:

  • - Restart computer
    - Assign more memory to windows
    - Delete some Microsoft bloatware (like Xbox, MSN news, ...)

Computer specifications:

  • - CPU: Ryzen 5 1600X
    - GPU: Gigabyte GTX 1060 6GB WINDFORCE OC
    - RAM: 8GB 2666 MHz
    - SanDisk SSD plus 240 GB
    - MOBO: MSI B350 PC MATE
    - OS: Windows 10 Pro (Slovenian) clean install

Some programs that I installed:

  • - MS office
    - Arduino
    - Netbeans
    - Android Studio
    - Firefox
    - WinRar
    - Java
    - Git
    - Photoshop (trial)
    - Drivers


Thanks in advance,
Dejan
 
Start Task Manager and look at network activity. With new PCs Windows has to do a good bit of updates to get current. One other thing to look at is C: drive busy percentage. Sometimes your antivirus program can do a lot of I/O to the C: drive and cause these delays.
 


I already updated Windows.

My antivirus (Panda Dome) uses disk at 0.1 MBps.
System32/ntoskml.exe (System) sometimes uses up to 6Mbps.

Overall, disk usage jumps between 0% and 1%.

Network activity is all time on 0%.
 
Check Device Manager for entries flagged with ! or ? to the left, indicating the need for the correct driver. You could also check the cryptic system event log for entries flagged ERROR. It's a lot like looking for a needle in a haystack, but that's the nature of the beast.
 
@wpgwpg here is first image: https://i.imgur.com/CoLv6H9.png (i forget to post it).. and more errors here: ttps://i.imgur.com/wCQzMTe.png ...

Now the better news: I have no idea what I did, but after several (a lot of) restarts problem dissapeared (at least for now). I'll report here, if problem comes back.

Thanks a lot for your help,
Dejan
 
I'm glad you got rid of the problem. The last link you posted showed a whole lot of critical errors in the data for the Get Started app. There was a comment at the bottom that it was attempting to correct corrupted data. I guess it finally succeeded in correcting the problem.