"The worst" Windows NT description of an event I've ever read

"The worst" Windows NT description of an event I've ever read

I think this is "the worst" Windows NT description of an event I've ever read:
...
Bucket -295570786, bucket table 5, EventType mptelemetry, P1 0x8007066f, P2 patchapplication, P3 am bdd, P4 11.1.4501.0, P5 mpsigstub.exe, P6 4.4.304.0, P7 microsoft security essentials, P8 NIL, P9 NIL, P10 NIL.
...
 

10 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Undecipherable error message.

>>...Undecipherable error message.

Actually, when it comes to Microsoft I see similar error messages since 1990...

That is true.Everything is done to hide the implementation and confuse the user(developer).

Is plain English always better? The best error message ever, by an OS, during bootup:

"Keyboard not detected. Press any key to continue."

引文:

dboggs 写道:

Is plain English always better? The best error message ever, by an OS, during bootup:

"Keyboard not detected. Press any key to continue."

That's the most ridiculous error description I have ever read.

引文:

Sergey Kostrov 写道:

I think this is "the worst" Windows NT description of an event I've ever read:
...
Bucket -295570786, bucket table 5, EventType mptelemetry, P1 0x8007066f, P2 patchapplication, P3 am bdd, P4 11.1.4501.0, P5 mpsigstub.exe, P6 4.4.304.0, P7 microsoft security essentials, P8 NIL, P9 NIL, P10 NIL.
...
 

It looks like parametrized mptelemetry event which is usually sent to MS by Defender or MSE programs.

I hope that MS Support Engineers sometimes look at Intel Forums! ;)

引文:

Sergey Kostrov 写道:

I hope that MS Support Engineers sometimes look at Intel Forums! ;)

unlikely

引文:

Sergey Kostrov 写道:

I hope that MS Support Engineers sometimes look at Intel Forums! ;)

They will learn how to troubleshoot properly their software products.

Leave a Comment

Please sign in to add a comment. Not a member? Join today