Stop Error 0x8e

This is a copy of the dump i pulled off of a laptop I"m working on. I can tell you it has passed all hardware diagnostics (memory and harddrive) and has passed a dskchk with no problems or bad sectors. I can't seem to find a specific driver that seems to be faulting in this case but I'm fairly certain it is driver causing problems. Any help would be appreciated!
Loading Dump File [X:\NOC\mswanson\CBarbee Dump\Mini041310-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols;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: Tue Apr 13 18:53:27.750 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:22.437
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 1000008E, {c0000005, 80637421, b5a8f988, 0}

Probably caused by : ntoskrnl.exe ( nt!RtlReserveChunkLZNT1+b8 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 80637421, The address that the exception occurred at
Arg3: b5a8f988, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!RtlReserveChunkLZNT1+b8
80637421 8b4304          mov     eax,dword ptr [ebx+4]

TRAP_FRAME:  b5a8f988 -- (.trap 0xffffffffb5a8f988)
ErrCode = 00000000
eax=00000f00 ebx=00000f00 ecx=89de92d0 edx=00000003 esi=e1035758 edi=00000079
eip=80637421 esp=b5a8f9fc ebp=b5a8fa44 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!RtlReserveChunkLZNT1+0xb8:
80637421 8b4304          mov     eax,dword ptr [ebx+4] ds:0023:00000f04=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  services.exe

LAST_CONTROL_TRANSFER:  from 80637332 to 80637421

STACK_TEXT:  
b5a8fa44 80637332 e1035758 006f0079 e1035758 nt!RtlReserveChunkLZNT1+0xb8
b5a8fa58 8063b7c6 e1035758 006f0079 e1035758 nt!RtlDescribeChunkLZNT1+0x95
b5a8fa74 80638c65 e1035758 006f0079 e1035758 nt!SepAuditFailed+0x7e
b5a8fa90 80638f23 e1035758 00296090 cee7836c nt!SepAdtOpenObjectAuditAlarm+0x59
b5a8faac 80638fc0 e1035758 00296090 d6c57094 nt!SepAdtOpenObjectAuditAlarm+0x317
b5a8fae8 806397fe e1035758 00303bc8 cd644bcc nt!SepAdtOpenObjectAuditAlarm+0x3b4
b5a8fb2c 80639971 e59b0000 00000400 00000003 nt!SeAuditProcessCreation+0x1b
b5a8fb5c 80626072 e1035758 000001b8 e1035758 nt!SeAuditProcessExit+0xd
b5a8fccc 8062196a 00010003 b5a8fd64 b5a8fce8 nt!NtMapUserPhysicalPages+0x27d
b5a8fcdc 8054163c 00000005 b5a8fd64 8050047d nt!PpBiosResourcesToNtResources+0xa1
b5a8fce8 8050047d badb0d00 b5a8fd60 000a001f nt!RtlIpv4StringToAddressExW+0xbd
b5a8fd64 7c90e514 badb0d00 0007fe50 00000000 nt!IopfCompleteRequest+0x71
WARNING: Frame IP not in any known module. Following frames may be wrong.
b5a8fd68 badb0d00 0007fe50 00000000 00000000 0x7c90e514
b5a8fd6c 0007fe50 00000000 00000000 00000000 0xbadb0d00
b5a8fd70 00000000 00000000 00000000 00000000 0x7fe50


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!RtlReserveChunkLZNT1+b8
80637421 8b4304          mov     eax,dword ptr [ebx+4]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!RtlReserveChunkLZNT1+b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b1e9e60

FAILURE_BUCKET_ID:  0x8E_nt!RtlReserveChunkLZNT1+b8

BUCKET_ID:  0x8E_nt!RtlReserveChunkLZNT1+b8

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

Open in new window

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

edbedbCommented:
It appears that the ntoskrnl.exe is missing or corrupted. Replace it with a known good copy of it. It belongs in the windows\system32 folder.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.