Hi - - am looking for some help. i am no PC expert

My son's PC has died with a blue screen stop msg ox0000008E. the exception code is 0xC0000005, 0xEEBD5D03.

have done a little research on this site and some guys have been really helpful, but am now struggling.

the PC is a 3.0ghz Packard Bell. 1.0g Ram running XP SP2

The system seems to boot up OK but then after around a minute goes to blue screen with the above error msg. have followed similar msgs on this site and run CHKDSK but it says that it is looks ok but hasnt tested it.

I can just about get the thing working in safe mode but have no idea what to do next.

have heard that it could be hardware so will spend the next hour removing RAM chips one by one and see what happens. he tells me that he had a problem when he clicked on a link sent to him in MSN but can't give any more details than that.
we have not changed any hardware / drivers etc

any help gratefully received

thanks

The 8E error points at RAM problems. It's pretty unique for a STOP code in that it only points at RAM problems when you look it up! So there's a good start.

There are a couple of ways to diag it.

You don't say which PB model it is, but if it has two sticks of RAM you can try removing one of the sticks to see if the problem persists, and then swapping with the other stick likewise.

The other way is to download a RAM test utility and run that.

I agree with the above poster. If oyu have more than one stick of RAM iin the computer, remove one and try booting again. If you still get problems, replace the stick you removed, and remove the otehr. Ifyou only have one stick of RAM in the computer, take it out and put in another (f you have one).

First Im no expert but what i read a error in ram ,not necessarily bad ram .But i could be wrong and for sure swap ram or test ram try memtest86 program .
http://msdn.microsoft.com/library/de...933845.xml.asp

From another site . i found this info and i quote!
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

When it comes to BIOS or firmware updates, I'm always of the mind that if it has been OK for x number of years, if it suddenly starts doing it now....

Guys

thanks for the help. have tried removing the memory chips 512mb each (one at a time) and it makes no difference. have even moved them to different slots to no avail.

the PC boots up OK, gets to the point where it puts the ICONS on the screen. it then comes up with a 'restore active desktop' question. (it makes no difference if you accept this or not). you then get the standard windows error msg that windows has recovered from a serious error (and asks whether you want to report it or not).

it does nothing for 20 seconds (and looks fine) but then the blue screen returns and the whole thing dies.

how do I get a memory tester? do i buy one or get one from the web? free ?

as before any help gratefully received - I'm stuck on this one !

Download and install this first:

http://tinyurl.com/y9598x

Then download and run this (and let it create the default folder):

http://tinyurl.com/y5zohv

Use the program called Imagewriter (installed in the first link) to create a bootable disk using the file extracted in the second link.

Then restart the broken machine with the disk in the drive and run the RAM tests.

thanks for that

have run both RAM and hard drive tests and both have come up clear. the RAM test took hours!

any other ideas? could it be related to the link i mentioned earlier? has anybody got any other ideas? -- HELP!!

the page i linked earlier ,
has some tips i think if you follow them you just might fix your problem.

copy/paste fro that link == * 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 Driver Kit.
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 in the Microsoft Windows Marketplace Tested Products List.

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.

true ,but after reading all the post in this thread ,no where does it say that this computer has been working great for years ,and also nowhere does the user say if any new hardware has been added to the computer lately .