From: Bill 43 on 19 May 2010 23:51 I keep getting this error in Win XP SP3: unhandled exception c0000005 at address 01261040 Please advise. I read an M/S support bulletin on the exception, but it was at a different address. I don't have the program that was addressed in that bulletin. Thank you -- Bill 43
From: Greg Russell on 20 May 2010 00:32 In news:172506A5-3BC8-4B24-B5D2-FBDB66E44CF4(a)microsoft.com, Bill 43 <Bill43(a)discussions.microsoft.com> typed: > I keep getting this error in Win XP SP3: unhandled exception c0000005 > at address 01261040. Please advise. Is the address 01261040 always the same? The machine may have some failing memory. Download, burn and boot http://memtest86.org to run an exhaustive test of the memory in the machine.
From: Bill 43 on 20 May 2010 01:15 I'll have to be more careful in checking the address to determine, however, I will run memtest, thank you -- Bill 43 "Greg Russell" wrote: > In news:172506A5-3BC8-4B24-B5D2-FBDB66E44CF4(a)microsoft.com, > Bill 43 <Bill43(a)discussions.microsoft.com> typed: > > > I keep getting this error in Win XP SP3: unhandled exception c0000005 > > at address 01261040. Please advise. > > Is the address 01261040 always the same? The machine may have some failing > memory. > > Download, burn and boot http://memtest86.org to run an exhaustive test of > the memory in the machine. > > > > > . >
From: Jose on 20 May 2010 07:56 On May 20, 1:15 am, Bill 43 <Bil...(a)discussions.microsoft.com> wrote: > I'll have to be more careful in checking the address to determine, however, I > will run memtest, thank you > -- > Bill 43 > > > > "Greg Russell" wrote: > > Innews:172506A5-3BC8-4B24-B5D2-FBDB66E44CF4(a)microsoft.com, > > Bill 43 <Bil...(a)discussions.microsoft.com> typed: > > > > I keep getting this error in Win XP SP3: unhandled exception c0000005 > > > at address 01261040. Please advise. > > > Is the address 01261040 always the same? The machine may have some failing > > memory. > > > Download, burn and boothttp://memtest86.orgto run an exhaustive test of > > the memory in the machine. > > > . Can you pinpoint the activity or actions that generate the error message? I did not see how that supplied link gets you a RAM tester, but if you want to run a memory test this will work: Run a test of your RAM with memtest86+ (I know it is boring and will cost you a CD). Memtest86+ is a more up to date version of the old memtest86 program and they are not the same. The memtest86+ will not run under Windows, so you will need to download the ISO file and create a bootable CD, boot on that and then run the memtest86+ program. If even a single error is reported that is a failure and should make you suspicious of your RAM. If you have multiple sticks of RAM you may need to run the test on them one at a time and change them out to isolate the failure to a particular single stick. Always keep at least the first bank of RAM occupied so the test will find something to do and there is enough to boot your system. Sometimes, reseating the RAM in the slots will relieve the error but a failure is still cause for suspicion. The file and instructions are here: http://www.memtest.org/ If someone says to run memtest86, you can say that you know memtest86+ supercedes memtest86 and here's why: http://en.wikipedia.org/wiki/Memtest86
|
Pages: 1 Prev: .net framework install problem Next: Vertical bar on the left of my folders has diappeared |