In this case the operating system has been crashing from time to time.
In this case Windows Server 2003 was crashing during boot.
In this case Windows Explorer was not responding sporadically for about 10 seconds.
In this case the system completely stopped responding and I used a feature of the operating system to force ...
The system crashed when I clicked on the "Stop Debugging" button in Visual Studio.
This exception occurs when you run the !clrstack command after the .loadby sos clr command.
This exception occurs when you try to save changes in the Control Panel\System and Security\File History\Exclude Folders.
This exception occurs when the CommandString parameter for the !for_each_module contains the !address command.
This case shows us that there is some code that can run without error for years and then one day ends up with a failure.
When you try one of these scenarios: 1. Create Scheduled Backups (TF401009 and TF400997). 2. Reconfigure Scheduled Backups (TF401009 and TF400997). 3. Restore Databases (TF400997).
Every time when I ran Code Analysis on the project from the Visual Studio 2010 it’s always worked fine, but one day when I ran it right away after the project has been loaded the Visual Studio crashed.
A few days after my brother installed Windows 8 Developer Preview he told me that when he clicks on the "File Types" in Control Panel Indexing Options->Advanced, both dialogues (Indexing Options and Advanced Options) disappear in a few seconds.
Once when I was doing debugging using WinDbg, it suddenly stopped responding. After a while I ran another instance and began investigation.