Stop 0x0000000a error debug analysis

[martin.whybrow]

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).

 

[Leonard Grey]

If your computer runs fine in Safe Mode, that's usually an indication
that something you have set to start with Windows is causing a problem.

 

[The Real Truth MVP]

Leonard Grey is a troll who cannot fix your system. He is jealous of the
fact that I can. He can't prove what he says about me and my software
because it is not true. The guy is an idiot. If you tell him the sky is
purple he will believe it because he is too stupid to look up and see it for
himself.

--
The Real Truth http://pcbutts1-therealtruth.blogspot.com/
*WARNING* Do NOT follow any advice given by the people listed below.
They do NOT have the expertise or knowledge to fix your issue. Do not waste
your time.
David H Lipman, Malke, PA Bear, Beauregard T. Shagnasty, Leythos.

If your computer runs fine in Safe Mode, that's usually an indication that
something you have set to start with Windows is causing a problem.
---
Leonard Grey
Errare humanum est

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).

 

[Gerry]

Martin

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
~~~~~~~~~~~~~~~~~~~

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 Whybrow]

Martin

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
~~~~~~~~~~~~~~~~~~~

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).

I 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.
Martin

 

[Peter Foldes]

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

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
~~~~~~~~~~~~~~~~~~~

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).

I 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.
Martin