Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.hardware (
More info?)
PS 1000008e is same causes as 0000008e
--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
"David Candy" <.> wrote in message news:eKDaZ22aFHA.2768@tk2msftngp13.phx.gbl...
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.
Parameters
The following parameters are displayed on the blue screen.
Parameter Description
1 The exception code that was not handled
2 The address at which the exception occurred
3 The trap frame
4 Reserved
Cause
This is a very common bug check. To interpret it, you must identify which exception was generated.
Common exception codes include:
a.. 0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.
b.. 0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system. • 0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.
For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows DDK.
Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. Make sure you have enough disk space. If a driver is identified in the bug check 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 plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.
If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.
If exception code 0x80000002 occurs, the trap frame will supply additional information.
If the specific cause of the exception is unknown, the following should be considered:
Hardware incompatibility. First, make sure that any new hardware installed is listed on the Microsoft Windows Hardware Compatibility List (HCL).
Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk. Check for and delete any unneeded temporary files, Internet cache files, application backup files, and .chk files containing saved file fragments from disk scans. You can also use another hard disk with more free space for the installation. BIOS problems can be resolved by upgrading the system BIOS version.
Try all the following with existing dump files but you can also turn on the
Driver Verifier (type verifier in Start Run and follow the wizard). This is
strict checking of all drivers (so it makes computer slower). This may give
different error messages and pinpoint one driver that is not crashing but
causing another driver to crash. If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).
Get your XP CD and install Windows Support Tools.
Type in start run after installing and rebooting
pstat > "%userprofile%\desktop\driverlist.txt"
The last table in this file is a list of loaded drivers. Other things apart
from hardware uses drivers. Post the list of drivers (the last table only -
REPEAT THE LAST TABLE O N L Y ) or match the fault address to the driver.
If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx
)
Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Load the crash dump file into windbg (File - Load Crash Dump and it's in
c:\windows\minidump) and READ WHAT IT SAYS (you may need to tell it where
the symbol files are), then
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)
If a minidump doesn't help use a kernel dump, if that doesn't help create a
full dump.
You can look up specific details here
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/
ddtools/BCIntro_ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp
If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/windiag.asp
If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to
http://oca.microsoft.com
Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters aren't that useful for searching.
--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
"Jerry Wong" <jerrywkwong_nospam@netvigator.com> wrote in message news:#E8yJx2aFHA.2380@tk2msftngp13.phx.gbl...
> ¨Æ¥óÃþ«¬: ¸ê°T
> ¨Æ¥ó¨Ó·½: Save Dump
> ¨Æ¥óÃþ§O¥Ø¿ý: µL
> ¨Æ¥óÃѧO½X: 1001
> ¤é´Á: 7/6/2005
> ®É¶¡: 10:14:34
> ¨Ï¥ÎªÌ: N/A
> error:
> 0x1000008e (0xc0000005, 0xbf8a0ff6, 0xf33f815c, 0x00000000)¡C error dump:
> C:\WINDOWS\Minidump\Mini060705-01.dmp¡C
>
> use what software?
>
>
> --
> Jerry Wong
>
>
http://www.geocities.com/jerrywong.geo
>
> §Ú·q¬È C©MµØ¨º³Ð³y·É®ü§ò¦a¤§¤Ñ¤Wªº¯«¡C(®³1:9)
> I fear the LORD, the God of heaven, which hath made the sea and the dry
> land. (Jonah 1:9)
>
>
Facebook
Twitter
Instagram