Re: Stop 0A BSOD
- From: "Franz Leu" <franz.leu@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 30 Jun 2005 12:12:01 +0200
Thanks to all of you guys for this help and great clarification. I may go to try this "debugger thing". ... some remarks in-line ..
"Matt Kellner (MS)" <mattkell@xxxxxxxxxxxxx> schrieb im Newsbeitrag news:OkAnjzOfFHA.3300@xxxxxxxxxxxxxxxxxxxxxxx
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?Nop. It happens from time to time and there are no drivers listed on the BSOD. I never saw this during development of the system. Now the unit is out for beta testing with the customer and this showed up. It runs from a CF in EWF RAM reg mode, so it's sure the customer could not change a thing.
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.)I was having a STOP 07 before during boot. This turned out to go away when I diabled USB legacy support in BIOS. Could be a problem with the USB keyboard.
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@xxxxxxxxxxxxxxxxxxxxxxxHi 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
.
- References:
- Stop 0A BSOD
- From: Franz Leu
- Re: Stop 0A BSOD
- From: Matt Kellner \(MS\)
- Stop 0A BSOD
- Prev by Date: Re: Working Image corrupting
- Next by Date: Re: Intel Extreme Graphics 82845G
- Previous by thread: Re: Stop 0A BSOD
- Next by thread: Intel Extreme Graphics 82845G
- Index(es):
Relevant Pages
|
|