Service Host: Diagnostic Policy Service seems to be going bezerk

Topic

New Reply

[SteveP]

“Service Host: Diagnostic Policy Service” has been running for about an hour since I started my computer this morning and has created over 10,000 log files just this morning. I stop the process with Task Manager and the process starts again in a couple of minutes. The process just started again but does not seem to be creating log files this time. It was creating multiple logs per second. It is using about 11% of the CPU. The SRUDB.dat file is about 7GB.

I only recently noticed this service using a fair amount of CPU time a few days ago late at night. It stopped on its own after about an hour. I did not notice a large number of log files then.

FWIW, I updated my computer last night to the latest version of 21H1.

Is this normal behavior? Online I found ways to permanently kill the service but that seems ill advised since it would kill diagnostics.

Should I just let the service do its thing and ignore it?

Thanks,
Steve

Update: service is adding 30 to 40 logs per second again.
Update 2: service finally stopped on its own after creating over 16,000 log files.

• This topic was modified 2 years, 10 months ago by SteveP.
• This topic was modified 2 years, 10 months ago by SteveP.

Reply | Quote

Replies

You can stop it long enough to clean out files (Instructions here, although as mentioned do not update your BIOS unless it is very important.)

You can look in Event Viewer for events that describe possible corruption.

1 user thanked author for this post.

SteveP

Reply | Quote

Thanks for the information.

I read the information on the links you posted and read other articles. I assume SRUDB.dat is needed if there are problems with the system. Will the Diagnostic Policy Service recreate the dat file when it finds problems?

Some people deleted the sru folder and mentioned it never came back, which other people said was a problem since errors would not be logged. I assume deleting the sru folder is not good–true? BTW, my previous 16,000 log files were deleted by my system and only a few log files exist currently.

Thanks,
Steve

Reply | Quote