 Re: Fatal Error!!! | 
06-16-2005, 12:30 PM
#8 (permalink)
|
Okay I might have the problem fixed. Here is what I found at the site for this problem. You are having a problem with this error. Just following the instructions I have listed below. If you have any problems let me know I will be on and off durning the day today. This may look overwhelming but I am sure you can get through it.
Fatal Exception Errors
What is It?
A fatal exception error occurs when your computer’s processor encounters an operation that it cannot process. In these cases, an exception to the operating system is caused, meaning it cannot proceed. This is rather drastically termed as a fatal exception, hence the term ‘fatal exception error’.
When Does it Occur?
All too often! Poor programming or sloppy code is usually the culprit, involving mathematical formulae that won’t resolve. However, faulty RAM will also cause fatal exceptions whenever data needs to be written to a bad area. Often, physical memory related errors only show up after a major upgrade, like switching to a new version of Windows; the older operating system might not have used areas of memory that the new one does, for instance. Incorrectly installed or poorly configured hardware can also throw up the message – for example, if the driver tells Windows to expect a device where there isn’t one, or allocates resources incorrectly.
Why Does it Occur?
Fatal exceptions are not directly caused by Windows – they’re actually produced by your processor when it finds an operation it can’t handle. However, Windows occasionally indirectly causes the exceptional operation error, especially in Windows 98, which is based on the older DOS operating system.
What to Look For
Typically the fatal exception error is reported in this way on a blue screen: ‘A fatal exception XY has occurred at xxxx:xxxxxxxx’. The XY part of the error is the type of processor exception that’s happened, and is the most informative, as this will give you a much better idea of how to fix it than where in the computer’s memory it happened. Write the code down and take it to
http://support.microsoft.com/?kbid=150314, where you’ll find a full list of fatal exceptions and their definitions.
How to Fix the Problem
More often than not, you’ll need to reboot after a fatal exception. Do so after noting down at least the first two digits of the error code. Now try to reproduce the error by repeating the actions you were doing just before it showed up. If you can reproduce it, note down what caused it and try to remove the offending program or driver. Use this information to search
http://support.microsoft.com for your problem and any possible solution.
Where to Go
If you cannot easily find the cause of the fatal exception, go to
http://support.microsoft.com/?kbid=192926, where you’ll find details of how to perform a clean boot in order to narrow down your search for the cause of the problem.
Case Study: Control Panel Fatal Exception fix
A fatal exception OE screen appears either when opening or closing the Control Panel or during startup, and the Control Panel error can also cause Windows to hang. A misplaced scanner file is the culprit.
Click the Start button, select Find, Files or Folders and type vhpscand.vxd into the ‘Named’ box. Click Find Now. If vhpscand.vxd turns up in the C:\Windows\System folder, it’s causing the problem and you need to move it.
Then right-click the vhpscand.vxd file and choose Cut from the drop-down menu. Browse to the folder C:\Windows\System\Iosubsys, right-click again and choose Paste. Restart your computer
This next link is for if you have to do a clean boot. Make sure you have made a back up before doing so. And follow the instructions on the page. Dang I wish I lived closer. It would make it easier to do this.
I find that it is easiest to print it out so that you don't have to keep going between screens.
http://support.microsoft.com/kb/192926/EN-US/
Let me know okay
Leah aka poorgirl
Linear Mode
