Re: Stop 0A BSOD

Hi Franz. A couple of questions for you: Did you change anything in the
system's hardware or software configuration when this error began to occur?
Does the error happen consistently or semi-consistently now? Do you see any
specific device driver files called out in the BSOD message, and if so, do
they change with each crash?

If you haven't changed anything in the system and it just began crashing
randomly, you may have experienced some sort of a hardware failure. I
recently had this happen in XP Pro on my personal computer, where the crash
would happen in a consistent place but called out random devices causing the
problem. It turned out that my CPU had died, and the errors disappeared
completely when I replaced the CPU. (In my case, I received a large variety
of STOP codes, including 0A, 7B, 05, 06 and D1, none of which should have
been happening where they were.)

Other devices could cause the problem, as well as system RAM. If you
suspect a particular device in the system, try swapping it out with an
identical device (such as a video card). If the problem seems to be random
and you can't pin it down to a particular device or operation, try swapping
out the RAM and/or CPU and see if that fixes the problem. The problem may
also reside with the system's mainboard (such as problems with the PCI Bus,
IDE or USB controllers, etc.) or with the power supply (such as when one of
the voltage lines starts putting out too low a voltage for the system).

If the problems started happening after a recent software upgrade such as
installing a new device driver, try uninstalling or rolling back the driver
or software to see if the problem disappears. If it does, you should
contact the vendor and inform them of the problem.

Hope this helps. =)

--
Matt Kellner (mattkell@xxxxxxxxxxxxxxxxxxxx)
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers no rights.
===============================

"Franz Leu" <franz.leu@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OvdZYqJfFHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
> Hi group
>
> I have a system that runs perfect for some time and suddenly I get a BSOD:
> IRQL_NOT_LESS_OR_EQUAL
> Stop 0x0A (0x00000165, 0x00000002, 0x00000000, 0x804F2724)
> It's based on XPe SP2.
> Does somebody have a hint how to track down this error?
>
> Thanks and best regards
> Franz


.

Relevant Pages

  • Re: Quad core CPUs loaded at only 50% when running a CPU and mmap intensive multi-threaded task
    ... Well, I just bought this new box, so there isn't a kernel version that I know that worked on this hardware. ... However on my previous box I have never seen such a problem (that the CPU is loaded only 50% with clamd) and I've been ... # Device Drivers ...
    (Linux-Kernel)
  • Re: How to develop a random number generation device
    ... single shared CPU; much less, in fact, since irrevelant interrupts, ... probably through shared memory and semaphores. ... switches are a reliability issue - processors don't have problems with them. ... If you shift the complexity to hardware, you'd get hardware that is expensive and buggy. ...
    (sci.electronics.design)
  • Re: Starting Windows 2000 hangs on new install.
    ... There might also be other mobo updated drivers. ... I've heard it said that winme is less 'hardware picky' than win2k ... > || Kevin. ... trying to return the CPU, but I'd need to show that it is faulty ...
    (microsoft.public.win2000.setup)
  • Re: Starting Windows 2000 hangs on new install.
    ... I mention BT merely as an example of my experience with a piece of hardware ... > CPU, but I'd need to show that it is faulty first. ... If you recently purchased mobo or cpu are you able to ... > || Kevin. ...
    (microsoft.public.win2000.setup)
  • RE: 70% CPU Usage Due to Hardware Interrupt Conflicts
    ... >> the CPU (also as measured by Windows Task Manager). ... >> apparent hardware conflicts, but a process management tool (Process Manager ... >> IRQ 10: ...
    (microsoft.public.windowsxp.general)