Post by Jonathan N. Little Post by Paul
On a Windows 10 system, you'd have to prepare in advance for
this, by reading up on WinDBG and remote debug using serial cable.
Because we are all clairvoyant enough to know we are going to BSOD? I
don't think this is a fair comparison.
LITTLE WORKS STUDIO
You made the statement that Windows is some sort of monolithic blob.
Just because no one here knows how to burrow into it,
doesn't mean it can't be done.
I have no interest in looking for such a solution. My interests
lay in real things that happen in the room, or in the rare case
where I can reproduce someone elses problem in the room, *then*
I'm interested in tools and techniques. If the frequency that
things happen is not sufficient to justify a setup, I'm not
A "ping" tells me what I need to know. If a machine was
frozen, it would not answer a ping. We would suspect a
hardware issue, then use the hardware test tree to decide
what to do next if the conclusion was that the machine froze.
If the machine answers a "ping", then we need to set up
for the next time, to gather more information. If the machine
"pings", then the Event Viewer logging system will be working,
and there should be an event recorded in there. For example,
in the old days, there'd be thousands of bogus ATI messages
in there from the crusty CCC drivers. I could also get a
synopsys from the Reliability Monitor, which would save on
having to check the entire Event Viewer.
I'm not going to go out on a limb, and say TightVNC,
Terminal Services related remote-in, or anything else
is going to work when there is some video issue. They
probably require something to decorate the display,
DWM and Explorer working and so on. I'm not set up
that way either - I don't have a lot of remote-in
applications primed and ready to go. I haven't even
downloaded Teamviewer. There's nothing in my reliability
results here, to lead me to suspect I need any of that
stuff. Not a good usage of time.
Microsoft claimed that 30% of some class of problem, was
caused by NVidia drivers. As long as there is a log entry
generated, that's a start. (A log entry that can be logged,
because the kernel, the task scheduler, and loads of those
rubbish services are still running.)