Help please: ntoskrnl.exe

Ran windows debugging tools and got this... Any idea on the next steps i should be taking?


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini051409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\windows\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu May 14 07:51:21.366 2009 (GMT-4)
System Uptime: 0 days 0:34:59.273
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 40000080, {8a4bb130, 89b6c378, 805512b8, 2}

Unable to load image NDIS.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NDIS.sys
Probably caused by : ntoskrnl.exe ( nt!_woutput+414 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_ID_DRIVER (40000080)
This is the NDIS Driver Bugcheck for Windows 2000 and Windows XP.
For Windows Server 2003 and later, see 0x7C, BUGCODE_NDIS_DRIVER.
DESCRIPTION
The meaning of the bug check parameters cannot be determined by examining the
parameters alone. You must also examine the text of a DbgPrint message.
For details, see either the debugger documentation or the DDK documentation.
Arguments:
Arg1: 8a4bb130
Arg2: 89b6c378
Arg3: 805512b8
Arg4: 00000002

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x40000080

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 00000000 to 804f9f43

STACK_TEXT:
80551638 00000000 00000000 00000000 00000000 nt!_woutput+0x414


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!_woutput+414
804f9f43 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!_woutput+414

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

FAILURE_BUCKET_ID: 0x40000080_nt!_woutput+414

BUCKET_ID: 0x40000080_nt!_woutput+414

Followup: MachineOwner
---------


Rhiannon Schaeffer, Business Analyst
Weidenhammer
935 Berkshire Blvd
Wyomissing, PA 19610
610-378-1149 ext 8431
rschaeffer@hammer.net

Visit our solutions at www.hammer.net

 

Seems it is a boot.ini problem, or a problem with the ntoskrnl file itself. Check Windows Update first, then have a look here:
http://www.computerhope.com/issues/ch000631.htm
Could run chkdsk from a command prompt within Windows, but doubt if that would be adequate.
If you resolve the issue make sure to run Windows Update again.