- #1
- 90
- 3
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Windows XP Unexpected Error
- Thread starter Euler2718
- Start date
Answers and Replies
- #2
Borg
Science Advisor
Gold Member
- 1,970
- 2,843
The address is likely a memory address that can change. It might be a bad memory cell but that's a guess.
What were some of the links that you found and what have you tried so far?
What were some of the links that you found and what have you tried so far?
- #3
- 90
- 3
The address is likely a memory address that can change. It might be a bad memory cell but that's a guess.
What were some of the links that you found and what have you tried so far?
The only thing I could find that was semi-relevant was https://forums.techguy.org/threads/...as-occurred-exception-code-3221225477.911567/ . It doesn't apepar that individual had much luck in his tries though. This computer doesn't have Virgin Media though. I haven't tried anything because I'm not sure what to try.
- #4
Borg
Science Advisor
Gold Member
- 1,970
- 2,843
Give this one a shot - http://answers.microsoft.com/en-us/...hat-this/5ee54a58-6ad7-4601-980a-ff008668ea6b. It's related to a user that is having issues while logging in. I don't know when your error occurred but, if it's a memory card issue like I suspect, it may help narrow it down. I'll have to refresh my memory for how to check a memory card for bad sectors.
BTW, when did the error occur?
BTW, when did the error occur?
- #5
Borg
Science Advisor
Gold Member
- 1,970
- 2,843
See if you've been having any problems described here - How to Diagnose, Check, and Test for Bad Memory.
- #6
- 3,388
- 945
It could be due to newly installed software which is defective, did the machine have any new software installed before this started happening?
It might also be a side effect of some kind of ad-ware that wasn't intentionally installed.
Try booting it in 'safe mode', this will start the machine in a configuration that has minimal number of background processes running.
If the problem goes away, then it's occurring because of some background process that isn't necessary.
So then you have to look at the processes which start up with a normal boot and figure out what one is the problem is by process of elimination.
If you boot in safe mode and the problem still is there, then it;s more likely a hardware issue.
It might also be a side effect of some kind of ad-ware that wasn't intentionally installed.
Try booting it in 'safe mode', this will start the machine in a configuration that has minimal number of background processes running.
If the problem goes away, then it's occurring because of some background process that isn't necessary.
So then you have to look at the processes which start up with a normal boot and figure out what one is the problem is by process of elimination.
If you boot in safe mode and the problem still is there, then it;s more likely a hardware issue.
- #7
- 90
- 3
Give this one a shot - http://answers.microsoft.com/en-us/...hat-this/5ee54a58-6ad7-4601-980a-ff008668ea6b. It's related to a user that is having issues while logging in. I don't know when your error occurred but, if it's a memory card issue like I suspect, it may help narrow it down. I'll have to refresh my memory for how to check a memory card for bad sectors.
BTW, when did the error occur?
It happened a little after logging in.
See if you've been having any problems described here - How to Diagnose, Check, and Test for Bad Memory.
I'm starting to believe this could be the path to follow.
It could be due to newly installed software which is defective, did the machine have any new software installed before this started happening?
It might also be a side effect of some kind of ad-ware that you didn't intentionally install.
Try booting it in 'safe mode', this will start the machine in a configuration that has minimal number of background processes running.
If the problem goes away, then it's occurring because of some background process that isn't necessary.
So then you have to look at the processes which start up with a normal boot and figure out what one is the problem is by process of elimination.
There isn't any new software on the PC, nor should there be any ad ware. The PC is used very basically and doesn't travel on any shady sites or download much. I'll try the safemode though, just to be safe.
- #8
jedishrfu
Mentor
- 13,285
- 7,192
For old machines, its good to blow away the dust inside the case with a can of compressed air. Also try to reseat the cards one at a time then fire it up.
- #9
Tom.G
Science Advisor
- 4,190
- 2,901
The Exception Code shown at the bottom of the screen shot is the Decimal representation of Hex C0000005:
//
// MessageId: STATUS_ACCESS_VIOLATION
//
// MessageText:
//
// The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
//
#define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC0000005L) // winnt
As noted by jedishrfu, cleaning and reseating the memory cards is a good first step.
If random errors keep popping up during normal use, from a Command Prompt run "SFC /scannow". This compares the critical operating system files with the original files on the Windows CD and replaces any corrupted files. It doesn't tell you if anything was replaced, so all you can do is use the machine and hope it is 'cured'.
Windows, up thru at least XP, has a quirk that if disk space in the Swap File runs out it will silently fail with no indication why. So if the hard disk is mostly full, make some room on it.
If you're still getting random errors, get a copy of Memtest86 or Memtest86+ and let it run overnight with all of its tests enabled.
If Memtest86 reports repeated errors at a few memory addresses, it's probably failed memory.
If errors at scattered addresses and/or random bits are reported,
the Power Supply or the Motherboard are prime suspects. Motherboards, and especially Power Supplies, have a limited life. Power Supplies are suspect after 3000 to 5000 hours of operation or five years age; Motherboards 'often' last three times as long, or longer.
If Memtest86 reports are no errors,
it may be corrupted software, but Power Supply and Motherboard are still possibilities.
//
// MessageId: STATUS_ACCESS_VIOLATION
//
// MessageText:
//
// The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
//
#define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC0000005L) // winnt
As noted by jedishrfu, cleaning and reseating the memory cards is a good first step.
If random errors keep popping up during normal use, from a Command Prompt run "SFC /scannow". This compares the critical operating system files with the original files on the Windows CD and replaces any corrupted files. It doesn't tell you if anything was replaced, so all you can do is use the machine and hope it is 'cured'.
Windows, up thru at least XP, has a quirk that if disk space in the Swap File runs out it will silently fail with no indication why. So if the hard disk is mostly full, make some room on it.
If you're still getting random errors, get a copy of Memtest86 or Memtest86+ and let it run overnight with all of its tests enabled.
If Memtest86 reports repeated errors at a few memory addresses, it's probably failed memory.
If errors at scattered addresses and/or random bits are reported,
the Power Supply or the Motherboard are prime suspects. Motherboards, and especially Power Supplies, have a limited life. Power Supplies are suspect after 3000 to 5000 hours of operation or five years age; Motherboards 'often' last three times as long, or longer.
If Memtest86 reports are no errors,
it may be corrupted software, but Power Supply and Motherboard are still possibilities.
Share:
