Windows Problem Reporting service - Phantom hardware error.

[nukecad]

On booting my latop today I noticed in Task Manager "Windows Problem Reporting service" was running (at the highest CPU usage).

Checking the Reliability Monitor I found:

Quote

 

Source
Windows

Summary
Hardware error

Date
‎29/‎09/‎2018 12:57

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name:    LiveKernelEvent
Code:    ab
Parameter 1:    b
Parameter 2:    c0
Parameter 3:    0
Parameter 4:    4
OS version:    10_0_17134
Service Pack:    0_0
Product:    768_1
OS Version:    10.0.17134.2.0.0.768.101
Locale ID:    2057

 

The Code ID and paramaters mean nothing to me, and nothing useful I can find online.

Event viewer, Windows Logs, shows nothing unusual for todays date, just 'information' entries and one warning in the System logs for a DNS server timeout.
Event viewer, Applications and Services Logs, Hardware events shows zero events.

Windows is running fine.
I do have both the camera and microphone disabled, but this has never thrown up an error before.

I'll probably just ignore it and keep an eye on the Reliability Monitor next boot.

Anybody have any ideas what it may have been?

Edited September 29, 2018 by nukecad

[nukecad]

Now this has got very strange/interesting.

I had a Windows update this afternoon, KB4458469.
Some of you may have seen online that MS have been doing strange things with that update - releasing it, then pulling it, then releasing it again with the same number, installing it twice, and so on.
MS say it's " because of a missing solution " whatever that is supposed to mean?
(MS updates have been weird for the past 2 or 3 weeks).
https://www.computerworld.com/article/3309402/microsoft-windows/bizarre-circumstances-surround-fourth-set-of-win10-cumulative-updates-in-two-weeks.html
 

Anyway - now that hardware error is not even showing in the Reliability Monitor - it seems that the update has erased it?

I'll put it down to MS messing about for some reason, probably to try and plug another security hole they are not telling us about yet.

Edited September 30, 2018 by nukecad

[Chas4]

The high CPU usage might be from Windows compressing the report before trying to send the report to Microsoft .  Checking Reliability Monitor there is an option to view all problems.