Re: Suddenly getting various system errors.

Tech-Archive recommends: Fix windows errors by optimizing your registry

Gerry - Thank you for through explaination. It is still under warranty, but
only if it is a hardware issue.

I have researched these messages (I admit I don't fully understand the
complete meaning of each one), but I don't understand why my dirvers or bios
would work one day and not the next, then work again after rebooting. So far
not one of these messages have reocurred.

I have already run "sigverif.exe". The only thing to come up were some
Symantec files, not any hardware drivers. I don't know why Symantec has
drivers, but I'm afraid my A/V program would stop working without them.

I also ran the memory tester, but stopped it after 6 passes because the
instructions said if it passed the first test, the memory was probably ok. I
since read that I should let it run much longer, and plan to do that as soon
as I have a chance.

I haven't tried SFC yet, but as I said about the drivers, if a file is bad,
I would expect continuous failures.

I'm leaning towards thinking there is a memory problem, and I hope a longer
test will verify that.





"Gerry" wrote:

Jeff

Hunt the needle in the haystack!

Background information on Stop Error message 0x8E
http://msdn2.microsoft.com/en-us/library/ms794023.aspx

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler
didn't catch. These are nearly always hardware compatibility issues
(which sometimes means a driver issue or a need for a BIOS upgrade).
Source: http://aumha.org/a/stop.htm

Background information on Stop Error message 0xD1
http://msdn2.microsoft.com/en-us/library/ms795930.aspx

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process
IRQL that was too high. The most typical cause is a bad device driver
(one that uses improper addresses). It can also be caused by caused by
faulty or mismatched RAM, or a damaged pagefile.
Source: http://aumha.org/a/stop.htm

Background information on Stop Error message 0x19
http://msdn2.microsoft.com/en-us/library/ms793223.aspx

0x00000019: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device
driver issues are probably the mstt common, but this can have diverse
causes including bad sectors or other disk write issues, and problems
with some routers. (By theory, RAM problems would be suspect for memory
pool issues, but I haven't been able to confirm this as a cause.)
Source: http://aumha.org/a/stop.htm

The first question you need to ask yourself is what hardware / software
changes did you make immediately prior to the first error occuring.

Even though you have dismissed overheating remove any dust bunnies from
inside the computer casing using an Air Duster and check all fans are
running.

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

tTy Start, Run, type "sfc /scannow" without quotes and hit Enter.

Description of Windows XP and Windows Server 2003 System
File Checker (Sfc.exe)
http://support.microsoft.com/default.aspx?scid=kb;en-us;310747

You will need your CD.

Check for motherboard updates to drivers and the BIOS. Third party not
Microsoft.

Is the computer still under warranty?

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

.

Relevant Pages

  • Re: PAGE_FAULT_IN_NONPAGE_AREA
    ... In Device Manager the Network Card appears under Network Adapter. ... Don't forget the problem could be hardware not software. ... Background information on Stop Error message ... Requested data was not in memory. ...
    (microsoft.public.windowsxp.general)
  • Re: blue screen
    ... Background information on Stop Error message ... Requested data was not in memory. ... Typically due to a bad driver, or faulty or incompatible hardware ...
    (microsoft.public.windowsxp.general)
  • RE: Hardware or software?
    ... > quite a few where this turned out to be memory failing. ... > issue of exclamation marked properties in device manager, ... I don't know whether this is a software or a hardware problem. ... I tried to reinstall the drivers from the ...
    (microsoft.public.windowsxp.general)
  • Re: City of Heroes crashing...
    ... Hardware issues can cause freezing, black screens and other ... your drivers should always be kept up to date. ... | and does several memory dumps and yes we've had the occasional blue screen. ...
    (microsoft.public.windowsxp.games)
  • Re: blue screen
    ... Background information on Stop Error message ... Requested data was not in memory. ... hardware problems (e.g., incorrect SCSI termination or a flawed PCI ...
    (microsoft.public.windowsxp.general)