Need more accurate computer diagnostic tools to find and fix problems

Doug

Code 3: The driver for this device might be corrupted, or your system may be running low on memory or other resources

Updated: August 31, 2007

Applies To: Windows Server 2008

Device Manager displays the following message in the Device Properties dialog box, on the General tab, in the Device Status text box:

The driver for this device might be corrupted, or your system may be running low on memory or other resources. (Code 3)

Diagnosis

The driver cannot successfully load because it is corrupted, or because there is not enough memory to run the driver.

Resolution

If the driver is corrupted, uninstall the driver and then scan for new hardware to install the driver again. To scan for new hardware, click the Action menu in Device Manager, and then click Scan for hardware changes.

If the computer has insufficient memory to run the driver, you can close some applications to make memory available. To check memory and system resources, click Start, All Programs, Accessories, Systems Tools, and then click System Information. You may have to install additional random access memory (RAM).

Source: http://technet.microsoft.com/en-us/library/cc771799(v=ws.10).aspx

In the action centre, I can't find any "View reliability History", so I am not sure where to go with that.

Select, Start, Control Panel, Action Center. Click on the Arrow down to the right of Maintenance and then on View reliability history.

Maintenance is located under Security.

That is what everyone keeps saying. My original point is that is not much of an answer, but I appreciate your comments. You think this is caused by a virus?

This look like good advice that will take me awhile to go through. The yellow exclams all say code 3, which as far as I can tel,l does not mean much. In the action centre, I can't find any "View reliability History", so I am not sure where to go with that.

I think that, in your present situation, a re-install would be the best way out of your mess. You may still have some infection in there and your system is in tatters.

You can install your other software as you need it, not so much of a sojourn as trying to installl everything in one sitting.

It will also allow you to monitor hardware and performance as you go..

Re diags.. a Jeep I6 4.0 Litre is what it is, as is a GM L7. There is no standard PC, especially if ti has been running for a while. There are as many permutations as the odds of winning the lottery.

Type Device Manager in the Search box above the Start button and press ENTER. Are there any yellow question marks in Device Manager? If yes what is the Device Error code.

To see Hidden Devices (Non Plug and Play Drivers) you need to select View, Show Hidden Devices. It is necessary to do this every time you open Device Manager if you need to see them.

A further complication can be Ghosted Devices –installed but not connected!

http://www.lockergnome.com/windows/2005/04/29/display-hidden-devices-in-device-manager-xp/

Select Start, Control Panel. Action Center, Click on the Arrow down to the right of Maintenance and then on View reliability history. In the graph you will see red orbs, Click on one and it gives details and to the right is another link saying View technical details. Can you copy and paste the description in a further message. Repeating reports are more relevant than one off problems. Here are some notes about Event Viewer Reports which may help. When you have a lot of errors you need to concentrate on system errors and warnings, even if it is applications that are giving you grief. Sorting system problems first can make resolving application problems easier. Note the time the computer is last booted and deal with those at the beginning of the boot first. Correcting the earlier errors can resolve later ones.

1. Normally when an error occurs on your computer looking in Event Viewer should be your starting point for finding a solution. Most system related errors are logged and getting an exact copy of the relevant report is important. Unfortunately understanding the reports is not easy and most computer users need help with their interpretation. I have more to say later on interpretation.
2. Event Viewer comprises three main Windows logs. These are Application, Security and System. For troubleshooting purposes System is by far the most important.
3. To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window select Windows Logs and System. Place the cursor on System, right click and select Filter Current Log. Check the box before Error and click on OK and you see only Error reports. Click on the Date and Time Column Header to sort. You may need to click a second time to see the latest Report at the top.
4. A tip for posting copies of Error Reports! Run Event Viewer and double click on the error you want to copy. Click on the Copy button on the General tab to place a copy on your Clipboard and close Event Viewer. Now start your message and paste into the body of the message. Make sure this is the first paste after exiting from Event Viewer.
5. There are three types of Report, being Information, Warning and Error reports. In most situations it is Error Reports that offer the best information but occasionally Warning Reports provide useful clues.
6. All reports have date and time stamps and when troubleshooting it is important to concentrate on more recent reports. Study reports since the point when the computer was last booted and then check whether a similar report appeared in the previous session. If errors do not repeat investigation as to why they occurred is wasted effort.
7. Within individual reports the more important information is Event ID and Source as these help when looking for help on the internet. The description is equally important and copying the exact text for use as the search criteria greatly helps getting better results when using Google. Do not paraphrase descriptions when asking others for help.