Re: Stop 0x0000000a error debug analysis
- From: "Peter Foldes" <okf22@xxxxxxxxxxx>
- Date: Wed, 3 Jun 2009 00:05:24 -0400
Martin
See the following
http://msdn.microsoft.com/en-gb/library/ms793589.aspx
--
Peter
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
"Martin Whybrow" <aholeintheground@xxxxxxxxxxxx> wrote in message news:7AhVl.7197$Qt2.6675@xxxxxxxxxxxxxxxx
"Gerry" <gerry@xxxxxxxxxx> wrote in message news:unXaTv04JHA.1716@xxxxxxxxxxxxxxxxxxxxxxxMartinI did some more digging in the minidumps and found 1 or 2 that pointed to tdi.sys as the failure with the same bugcheck values, so it looks like a networking problem. I then found a reference to using verifier.exe, I started this (in safe mode) and set it to verify all drivers; when I rebooted, the BSOD appeared but this time the dump file analysis pointed to wlcom51b.sys which is the Compaq USB Wireless LAN adapter; I disabled the WLAN in safe mode, rebooted and no more BSOD. Unfortunately I'm now seeing the 'you must activate Windows before you can log on' message and, as I don't have a working network, it looks like I'm going to have to do this over the phone; I suspect I may come unstuck here as I used my XP SP2 disks to do the repair but the COA is, I believe, for XP with no service packs, so I don't know if it can be activated.
Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793589.aspx
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or
software. Use the General Troubleshooting of STOP Messages checklist
above. Technically, this error condition means that a kernel-mode
process or driver tried to access a memory location to which it did not
have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was
too high. (A kernel-mode process can access only other processes that
have an IRQL lower than, or equal to, its own.)
Source: http://aumha.org/a/stop.htm
You receive a "Stop 0x0000000A" error message in Windows XP
http://support.microsoft.com/kb/314063/
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
martin.whybrow@xxxxxxxxxxxx wrote:My Compaq EVO N410c is giving the STOP 0x0000000a error every time I
boot
normally to Windows; it runs perfectly in safe mode. The machine is
running
XP Pro SP2. I have run a full repair installation, but it's still the
same.
I've run a windbg trace (on another PC) on the minidump file and the
summary
is: Probably caused by : ntoskrnl.exe ( nt!KiInsertTimerTable+2f ).
I've posted the full trace below (note the path to ntoskrnl.exe points
to an
SP2 version as the machine used for doing the trace is running SP3).
Loading Dump File [a:\Mini060109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\XP_SP2_System_Files_For_Debugging
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Mon Jun 1 02:45:01.914 2009 (GMT+1)
System Uptime: 0 days 0:01:05.479
Loading Kernel Symbols
...............................................................
..............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {62005e3f, 2, 0, 804dc42a}
Probably caused by : ntoskrnl.exe ( nt!KiInsertTimerTable+2f )
Followup: MachineOwner
---------
Can anyone enlighten me as to what this error could be? I doubt the
RAM is
faulty as, as mentioned above, it's rock solid in safe mode.
Martin
Apologies for using google groups, Outlook Express has decided it
didn't want to send my message (another problem to be fixed).
Martin
--
martin<dot here>whybrow<at here>ntlworld<dot here>com
.
- References:
- Stop 0x0000000a error debug analysis
- From: martin . whybrow
- Re: Stop 0x0000000a error debug analysis
- From: Gerry
- Re: Stop 0x0000000a error debug analysis
- From: Martin Whybrow
- Stop 0x0000000a error debug analysis
- Prev by Date: Re: Help - Process of removal of a program from XP system
- Next by Date: "The application failed to initialize properly (0xc0000006). Click on OK to terminate the application" II
- Previous by thread: Re: Stop 0x0000000a error debug analysis
- Next by thread: Standby selection shuts down windows computer
- Index(es):
Relevant Pages
|
