BLUE SCREEN STOP ERROR 1000008E, {c0000005, 80534de3, a964f848, 0}

0x1000008e

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/bccodes_59k7.asp

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:

0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.

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.
******************************

check the memory chip you installed . try changing it or removing it & working in your old setup . Bluscreen generly means hardware problem . So it is the memory chip you need to replace first

hi thanks for that - I tried to get the

0xC0000005: STATUS_ACCESS_VIOLATION web link
A memory access violation occurred.


from ms but you got it here, I want to try fix this rather than than playing around with the hardware,


1 The exception code that was not handled          - 0xC0000005: STATUS_ACCESS_VIOLATION
2 The address at which the exception occurred    - 80534de3
3 The trap frame                                               - a964f848
4 Reserved
##############################################################
I have checked system info in system tools

I checked the conflicts and this is what is loaded, is there anything here causing a problem????


System Information report written at: 02/25/04 12:48:48
System Name: DEAN
[Conflicts/Sharing]

Resource      Device      
I/O Port 0x00000000-0x00000CF7      PCI bus      
I/O Port 0x00000000-0x00000CF7      Direct memory access controller      
            
I/O Port 0x000003C0-0x000003DF      ATI RS200/RS200M Accelerated Graphics Port      
I/O Port 0x000003C0-0x000003DF      IGP 340M      
            
IRQ 10      IGP 340M      
IRQ 10      ALi PCI to USB Open Host Controller      
IRQ 10      Conexant 56K ACLink Modem      
IRQ 10      National Semiconductor Corp. DP83815/816 10/100 MacPhyter PCI Adapter      
            
Memory Address 0xD0300000-0xD03FFFFF      ATI RS200/RS200M Accelerated Graphics Port      
Memory Address 0xD0300000-0xD03FFFFF      IGP 340M      
            
IRQ 11      O2Micro OZ6912 CardBus Controller      
IRQ 11      Texas Instruments OHCI Compliant IEEE 1394 Host Controller      
            
Memory Address 0xD8000000-0xDFFFFFFF      ATI RS200/RS200M Accelerated Graphics Port      
Memory Address 0xD8000000-0xDFFFFFFF      IGP 340M      
            
I/O Port 0x00009000-0x00009FFF      ATI RS200/RS200M Accelerated Graphics Port      
I/O Port 0x00009000-0x00009FFF      IGP 340M      
            
Memory Address 0xD0000-0xD3FFF      PCI bus      
Memory Address 0xD0000-0xD3FFF      PCI bus      
            
Memory Address 0xA0000-0xBFFFF      PCI bus      
Memory Address 0xA0000-0xBFFFF      ATI RS200/RS200M Accelerated Graphics Port      
Memory Address 0xA0000-0xBFFFF      IGP 340M      
            
I/O Port 0x000003B0-0x000003BB      ATI RS200/RS200M Accelerated Graphics Port      
I/O Port 0x000003B0-0x000003BB      IGP 340M      
##############################################################            

I have downloaded all updated drivers including bios update from hp, I will give it a test trying to install vs.net (uses a few cd's) to see if it helps

Scene this problem before,

For me it was a bad stick or RAM.  Can you try this in another PC?

it seems that the bios update seems to have helped here, i also updated all hardware drivers from HP. so far so good and I installed a few cd's yesterday without blue screen.