Event Viewer Sez:

For system:
Error code 1000008e, parameter1 c0000005, parameter2 805b6bee, parameter3 b7a325e0, parameter4 00000000.

0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 38 30 35 62 36 62 65 65 805b6bee
0040: 2c 20 62 37 61 33 32 35 , b7a325
0048: 65 30 2c 20 30 30 30 30 e0, 0000
0050: 30 30 30 30 0000

For application:
Faulting application winword.exe, version 10.0.4030.0, faulting module winword.exe, version 10.0.4030.0, fault address 0x0003af79.

0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 69 6e ure win
0018: 77 6f 72 64 2e 65 78 65 word.exe
0020: 20 31 30 2e 30 2e 34 30 10.0.40
0028: 33 30 2e 30 20 69 6e 20 30.0 in
0030: 77 69 6e 77 6f 72 64 2e winword.
0038: 65 78 65 20 31 30 2e 30 exe 10.0
0040: 2e 34 30 33 30 2e 30 20 .4030.0
0048: 61 74 20 6f 66 66 73 65 at offse
0050: 74 20 30 30 30 33 61 66 t 0003af
0058: 37 39 0d 0a 79..

Those were just the most recent errors.

Have you tried opening the last dump log?

Which is where? Sorry.

If you changed to a full dump it should be C:WINDOWS/MEMORY DMP

Or else search for .DMP

This is my latest minidump:


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


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

Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Wed Feb 11 11:00:43.187 2009 (GMT-5)
System Uptime: 0 days 1:40:35.752
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded 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, 805b6bee, b7a325e0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for ikhfile.sys
*** ERROR: Module load completed but symbols could not be loaded for ikhfile.sys
*** WARNING: Unable to verify timestamp for Fastfat.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fastfat.SYS
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Probably caused by : ikhfile.sys ( ikhfile+f07 )

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

Probably caused by : ikhfile.sys ( ikhfile+f07 )

Ikhfile.sys is related to the software Spyware Doctor.

I'd suggest removing this software.

Do you have a suggestion about what to replace Spyware Doctor with?

I recommend a good anti virus (I use AVG) and a firewall (I just use the Windows firewall) Comodo is free if you want more.

I run Spybot regularly and also spyware blaster.

As long as you stay aware of where you go and what you do you should need nothing else.