Request for Help

I have a computer with bsod and I have extracted the DMP file and pasted the contents. I have no idea where to go from here, any help is appreciated. The computer boots to safe mode, it also got to the login screen after a recent system restore, but all result in the following bsod. I have run 1 pass of memtest with 0 errors and 7 of 11 expanded tests of windows boot disk with 0 errors. Thank you...



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


Loading Dump File [F:\Mini080508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\local cache* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Tue Aug 5 21:13:02.249 2008 (GMT-7)
System Uptime: 0 days 0:01:11.828
Loading Kernel Symbols
.............................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 640b54b6, f89a3acc, 0}

Unable to load image spndt.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for spndt.sys
Probably caused by : hardware

Followup: MachineOwner
---------
*** Possible invalid call from 8057d55a ( nt!NtOpenFile+0x22 )
*** Expected target 8057d362 ( nt!IoCreateFile+0x0 )

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: 640b54b6, The address that the exception occurred at
Arg3: f89a3acc, 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:
+640b54b6
640b54b6 ?? ???

TRAP_FRAME: f89a3acc -- (.trap 0xfffffffff89a3acc)
ErrCode = 00000000
eax=ed0e7d98 ebx=8057d538 ecx=ed0e7d9c edx=ed0e7d90 esi=f89a3c2c edi=f89a3b9c
eip=640b54b6 esp=f89a3b40 ebp=f89a3b7c iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
640b54b6 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8057d55f to 640b54b6

POSSIBLE_INVALID_CONTROL_TRANSFER: from 8057d55a to 8057d362

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f89a3b3c 8057d55f f89a3c5c 001f0000 f89a3c34 0x640b54b6
f89a3b7c 804dd99f f89a3c5c 001f0000 f89a3c34 nt!NtOpenFile+0x27
f89a3b7c 804e3ba3 f89a3c5c 001f0000 f89a3c34 nt!KiFastCallEntry+0xfc
f89a3c0c 805afd92 f89a3c5c 001f0000 f89a3c34 nt!ZwOpenFile+0x11
f89a3c54 ed0e7538 ed0e7d9c 001f0000 ed0e7ede nt!IoGetDeviceObjectPointer+0x40
f89a3c84 805a2995 81b10f38 81613000 00000000 spndt+0x538
f89a3d54 805b988a 00001014 00000001 00000000 nt!IopLoadDriver+0x66c
f89a3d7c 804e23b5 00001014 00000000 823c58b8 nt!IopLoadUnloadDriver+0x45
f89a3dac 80574128 ed512cf4 00000000 00000000 nt!ExpWorkerThread+0xef
f89a3ddc 804ec781 804e22f1 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .trap 0xfffffffff89a3acc ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
8057d362-8057d366 5 bytes - nt!IoCreateFile
[ 8b ff 55 8b ec:e9 68 a0 b6 6c ]
5 errors : !nt (8057d362-8057d366)

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CPU_CALL_ERROR

Followup: MachineOwner
---------
*** Possible invalid call from 8057d55a ( nt!NtOpenFile+0x22 )
*** Expected target 8057d362 ( nt!IoCreateFile+0x0 )

 

Hey Siegfried.

What laptop? Acer or Asus?

In both case, pop in the vista cd and do a repair of the OS.

That might help.



Boot your computer into safemode and download the WINDIAG tool link

 

Sorry, to clarify its a Dell Windows Media Center os desktop.

 

I'm no pro but I googled the exeception code above.
http://www.updatexp.com/0xC0000005.html


hope that helps!

 

update you demon tool stpd driver

http://www.daemon-tools.cc/dtcc/f19/sptd-sys-other-sys-problem-9327/index7.html

 

Hmmm... a Google search for spndt.sys turns up a couple pieces of malware. Can you search your drive for this file and upload it to http://www.virustotal.com/ and see if anything flags it?

 

Wow, thank you for all this help. I will be doing every one of these and post back. Thank you so much. This computer went dead and it had a bunch of important docs on it, thankfully I got them off and used the evil windows sys restore, and now it boots up. Time for a whole security overall I think. Thank you again.