After moving to a new Internet Explorer based employee time management system, I started noticing a slew of reports coming in where IE was crashing when trying to access any of the menus within the browser. The error always presented itself as: “Microsoft Visual C++ Runtime Library. Runtime Error!..” 
Archive for July 4th, 2010
Go Digging for the Exception
Posted by William Diaz on July 4, 2010
Posted in Troubleshooting, Troubleshooting Tools | Tagged: Crash, Dump, IE, Process Explorer, WinDbg | Leave a Comment »
.Net Cleanup & Setup Verification Tools
Posted by William Diaz on July 4, 2010
I have found a need to use these tools a few times in the past so I thought I would mention them.
The .NET Framework setup verification tool is designed to automatically perform a set of steps to verify the installation state of one or more versions of the .NET Framework on a computer. It will verify the presence of files, directories, registry keys and values for the .NET Framework. It will also verify that simple applications that use the .NET Framework can be run correctly.
Read about and obtain from here: http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
The updated version of the cleanup tool contains options to clean up the .NET Framework 1.0, 1.1, 2.0, 3.0 and 3.5 separately and all versions simultaneously in a single step. The cleanup tool contains logic so that if it is run on an OS version that includes the .NET Framework as an OS component, it will not offer the option to clean it up. This means that running the cleanup tool on Windows XP Media Center Edition or Tablet PC Edition will not offer the option to clean up the .NET Framework 1.0, running it on Windows Server 2003 will not offer the option to clean up the .NET Framework 1.1 and running it on Windows Vista will not offer the option to clean up the .NET Framework 2.0 or the .NET Framework 3.0.
See here: http://blogs.msdn.com/b/astebner/archive/2006/05/30/611355.aspx
Posted in Troubleshooting, Troubleshooting Tools | Leave a Comment »
Identifying Unknown Hardware
Posted by William Diaz on July 4, 2010
To see missing drivers for any hardware component just open the System Information utility from Start > Run and type msinfo32. You can also do this remotely with any computer within your network by using the View > Remote Computer option.
Expand the Components heading in the navigation tree and select Problem Devices: Read the rest of this entry »
Posted in Troubleshooting, Troubleshooting Tools | Tagged: Hardware | Leave a Comment »
Windows Explored 