You need to be more specific. Which driver do you think is causing it? when and where the message come from? Have you checked the compatibility of the device with your system?
2006-10-10 08:51:47
·
answer #1
·
answered by netwalker01 3
·
1⤊
0⤋
Tip #1: Ignore the Fluff
Stop screens generally contain a lot of information, most of it confusing. What's really important, however, are:
The symbolic name of the error, for example DRIVER_IRQL_NOT_LESS_OR_EQUAL.
The hexadecimal number of the error prefixed by "0x"; for example, "0x000000D1", which can be remembered as "0xD1" for short.
The name of any driver specifically mentioned as relating to the error.
The rest you can usually ignore unless you are a Microsoft support technician versed in the arcane lore of interpreting Stop screens. I usually start with the name or number and look up the error in one of the many resources available, which I'll discuss in a moment. But first make sure you write down this information, so that you can look it up later.
Tip #2: What Did I Do?
Before I start running to Google to look for information about the error, I first try to pause and think, "What have I done recently that could have caused this problem?" Since most Stop screens are caused by flaky drivers or hardware problems, I ask myself questions like these:
Have I installed any new devices recently? Were they on the HCL?
Have I updated any device drivers since the last time I rebooted?
Could I have kicked the machine with my foot and possibly unseated some card from its socket?
Has the machine's hard drive been making funny noises lately?
Did I install any new service packs, hotfixes, or other applications in the last few days?
Did I make any changes to the configuration of the operating system or my BIOS settings recently?
If you ask yourself questions like these, you may think of something that may have caused the Stop error to occur, and armed with that fact and the information you've copied down, you're ready to proceed with troubleshooting the error.
Tip #3: Check Your Event Log
Next, I usually simply try rebooting the machine if it isn't already configured to reboot itself when a Stop error occurs. To configure auto-reboot after a Stop error, select Control Panel -> System -> Advanced -> Startup and Recovery -> Settings. This opens the Startup and Recovery screen (Figure 1), where you can configure boot options and what you want to happen when a system failure occurs.
Figure 1. Startup and Recovery screen in Windows XP.
In Windows XP, when the operating system encounters an exception it can't handle, the following actions occur:
An event describing the error is written to the System log in the Event console.
An administrative alert is sent over the network if the Alerter and Messenger services are running (these are disabled by default).
A small memory dump of key information (including the Stop error info) is performed into the %SystemRoot%\Minidump directory.
The system automatically restarts.
2006-10-10 15:51:29
·
answer #2
·
answered by god knows and sees else Yahoo 6
·
1⤊
1⤋
could be a pop up trying to get you to download something you don't need,,,if your computer is working fine ignore it,,and scan your computer with an anti spyware remover like spybot search and destroy.
2006-10-10 15:55:08
·
answer #3
·
answered by Anonymous
·
0⤊
1⤋