Hi, i have been searching the net for around 2-3 hours about this error but so far have no solution.

The exact 2 errors i am getting occur when windows first loads about 75% of the time it is booted.

*** STOP: (0X0000008E, 0X806EF134, 0XF8A88670, 0X00000000)

And

*** STOP: (0X0000008E, 0X806EF134, 0XB1F63B0C, 0X00000000)

Any help fixing these errors would be good.

Ash~

and the rest of the error message is?

I cant get the whole thing the next time it decides to do it but i do get this error when the system is booted afterwards.

BCCode : 1000008e BCP1 : C0000005 BCP2 : 806EF134 BCP3 : F8A88670
BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 768_1

Ash~

Windows XP and Service Pack 3 is about all you can get from that.
A couple of options.

Start your machine in safe mode, then shut down and restart to rebuild the driver cache. See if that improves it.

Stop things from starting up by using msconfig, then turn them back on one by one until the failures start to happen again.

Ok i have turned on the laptop to do what you have reccomended and i got the error screen. It reads.

__________________________________________________ ____

A problem has been detected and windows has been shut down to prevent damage to your computer.

If this is the first time you have seen this stop error screen, restart your computer. If this screen sppears again, follow these steps:

Check to be sure you have adequate disk space. If a driver is identified in the stop message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press f8 to select advanced startup options, and then select safe mode.

Technical Information:

*** STOP: 0x0000008E (0xC0000005, 0x806EF134, 0xF8A84670, 0x00000000)

Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance.

__________________________________________________ __

And thats what is displayed on the blue screen, i will await a reply before tring the other methods you have given me.

Thanks Alot, Ash~

The lack of specific error messages suggests that it is a memory problem. unclip any memory you have installed and clean the socket and pins, just a wipe over with a tissue will do. then reinstall it.
Download Memtest86 and run tests on the memory as well.

Have you installed anything new BTW?

other than that go through the "Safe Mode" start - shutdown - restart cycle and the MsConfig elimination process.

Well this is actually an error on a friends laptop and i have no expierence with them, this being a desktop pc i could easy remove RAM.

Do you think they should take it to a shop in order to do this?

I will run memtest on the laptop when i next see them do i need to burn it to a bootable disk?

Thanks for your help, Ash~

depends on how much you want to be involved.

It's either an easy fix, OS re-installation or replace the laptop if it's a motherboard failure. You need the history to decide.

It could be a driver conflict also, has your friend installed any new devices or updated any software recently? It's most likely a SW issue. I doubt the laptop hardware is failing, if it was a PC the ram it seems like would be the problem.

Ok well how can i identify which drivers are causing the problem?

When windows boots i get an error and i get:

The following files were included in the error:
C:\DOCUME~1\jason\LOCALS~1\Temp\WER6789.dir00\Mini 0011109-10.dmp
C:\DOCUME~1\jason\LOCALS~1\Temp\WER6789.dir00\sysd ata.xml

Can anyone suggest what to do?

Ash~

http://support.microsoft.com/kb/315263

Ok i have the windows debugging tool.

Am i trying to open the dumpfile to show you guys on here?

As i cant locate it to open it, i have tried cleaning the ram and had no success.

Thanks so far

Ash~

You might be over-writing or deleting the dump files because they are in the temp directory on your machine. Some "cleanup" tools will remove them on restart.

RC on My Computer -> choose Properties -> click Startup and Recovery -> change the "Small Dump Directory"

Ok here is what i get when i open the dump file.

_________________________________________


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


Loading Dump File [C:\Documents and Settings\jason\Desktop\Mini012509-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 = 0x8055b1c0
Debug session time: Sun Jan 25 13:14:24.071 2009 (GMT+0)
System Uptime: 0 days 0:00:49.651
************************************************** *******************
* 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
.....
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
Unable to load image fltmgr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 806ef134, f8a8c670, 0}

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

*** WARNING: Unable to verify timestamp for SRTSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP.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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 : SRTSP.SYS ( SRTSP+15e69 )

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


Ash~

Bloody Nortons is all I can say!

http://www.file.net/process/srtsp.sys.html

When i try and run the scan i get a page cannot be displayed so i cant run it.

Ash~

don't be running their scanner, it will only probably offer to lighten your credit card at the end of it.

Use msconfig to turn off the Symantec AutoProtect "feature"

or download CCleaner and remove it from the registry.

or even better, uninstall the whole of the Nortons "security" system and install a GOOD AV scanner.

Ok well the computer it is on has AVG will that be sufficiant enough to cover the loss of norton?

Ash~

yep

Think of it not as losing Nortons,

think of it more as gaining 300Mb of memory