Weird lagging problem

Hello guys, I'm new here, very pleased in Windows 10, but have one problem. I've installed Windows 10 on my HP ProBook 6540b last week.

It was running perfect and very fast, and it still does, but sometimes (after maybe 1-2 hours of use) it starts lagging like hell, and I need to restart it then. Then it works normally again. Performance monitor looks normal too when it laggs. I did a clean install and activated it with original Windows 7 key.

This problem started yesterday, last week laptop was running normal (whole week after install). I thought maybe it's because of the Adobe Flash Update that installed the day before yesterday, so I've deleted that update, but the problem is still here.

Laptop has i5, 8 GB RAM, 250 GB HDD (7200 rpm), it's not weak.

Please help me, because it's really annoying that I need to restart it every time. Thanks in advance.

dalchina said:

Hi, ideas:
Inspect your update history- what changed in that time? Any driver updates?
Do you have a system restore point prior to the start of the problem?
Have you installed anything or changed settings about the time this started?

1. Post a screenshot of your task manager, highest to lowest CPU use, highest to lowest disk use or whatever is of interest when lagging, if that's possible. (Or a photo).
2. Run Sysinternals Procmon and let it capture events, continuing until lagging occurs. The idea would be to inspect the log file if you can. However if you can't stop the program normally, I don't know what happens to the log file. Maybe it's saved- or maybe by killing other processes you can manage to gain enough control to save it.
3. Run LatencyMon and inspect the output when lagging is occurring.
4. Note when lagging is occurring and
a. Inspect your Reliability History (type 'reli' in the cortana search field)
b. Inspect your event log

5. Process of elimination.
Does lagging occur if you wait 'long enough' in Safe Mode?
" " " " " " " " " " " "" " " " " "" " " " " "" " " " " "" " after a clean boot?

Thanks for the response.

Ok, that day, when the problem started, this update installed automaticly : Sigurnosno ažuriranje za Adobe Flash Player za 64-bitno izdanje sustava Windows 10 Version 1511 (KB3163207)
(Security update for Adobe Flash...)

No programs installed on that day (14th May), except Avast antivirus, but that's after the first problem came, because I've installed it because I thought it's a virus or smtg.

BUT, I've installed some programs on 13th May, maybe they are causing a problem...



About CPU usage. Without lagging, it's about 5-10%, and with lagging, it's around 15-30%. Sorry, don't have the picture.

Reliability History - everything looks fine, same as in Event Viewer, no "Critical Events" on 14th May. No errors on 13rd too.

The problem still occurs, once or twice a day, I use laptop 4-5 hours a day. There's nothing in the event viewer. I'll try LatencyMon when the problem comes, and try the safe mode. Thanks again.

dalchina said:

Would suggest you uninstall each of those programs in turn, starting with Intel turbo boost, testing each in turn for 'long enough'.

Or restore an appropriate system restore point if available, test, install 1 program, test.... etc

Yup, just wanted to do that, because it's weird that those programs have 13rd May as instalation date, and I've installed them on 6th May, when I've installed Windows too. Sorry, don't have restore point, I'll try with reinstalling them these few days -_-

Thanks :)

Damn, I still haven't find the solution. Reinstalled all programs and drivers that from the first day when the lagging came and days before, but it's now even worse. Restart is not helping anymore. When I restart it, it laggs same like before restart, after ~15 mins it's back to normal and laptop runs fast as hell (as normal). I've found out that lagging always comes around 8.30 AM (GMT+1), 3 days in a row.

Any ideas?

dalchina said:

Hi, if you know it starts regularly, suggests a scheduled task e.g. maintenance.

You can capture what happens using Sysinternals ProcMon (very detailed technical trace) - so as you know the time, that will help. You can filter the trace to the nth degree to eliminate things not of interest.

E.g. with PC idle set filter so nothing is captured, being specific as to what you eliminate, then new activity (assumption) at 8:30 would show up. The whole trace is kept- the filter just applies to creating the trace displayed so is easily undone to reveal more.

Will do it tommorow, thanks.

I was wrong about the 8.30 AM, it's not related with time at all. Here's the event log (System) when the lag came (around 10.20 AM). I restarted it immediately, but it didn't help. Lagging stopped around 10.45 AM.

Here's the event log file.

file