"babel17" <"babel17not me"@optonline.net> wrote in message
news:KsrUh.41$LM1.27@newsfe12.lga...
> How would I find which application was trying to access the same memory
> address?
I'm not sure. Process Explorer from www.sysinternals.com has a facility to
show the owning process of a window, however I'm not convinced this will
work in this scenario as I don't believe this is an error message displayed
by the application. You could also try Process Monitor (available from the
same site).
This may not be the cause of the problem. My guess is this is not a dodgy
RAM issue though - MemTest86 would confirm or deny this though.
> No new devices, so no new drivers.
Device drivers may not mean additional physical devices. A lot of software
uses code that runs as a device driver as this is the only way of getting
third party code to run in kernel mode.
"Ed Metcalfe" <edmetcalfe@hotmail.com> wrote in message
news:%23pULyV4fHHA.208@TK2MSFTNGP05.phx.gbl...
>
> "babel17" <"babel17not me"@optonline.net> wrote in message
> news:KsrUh.41$LM1.27@newsfe12.lga...
>> How would I find which application was trying to access the same memory
>> address?
>
> I'm not sure. Process Explorer from www.sysinternals.com has a facility to
> show the owning process of a window, however I'm not convinced this will
> work in this scenario as I don't believe this is an error message
> displayed by the application. You could also try Process Monitor
> (available from the same site).
>
> This may not be the cause of the problem. My guess is this is not a dodgy
> RAM issue though - MemTest86 would confirm or deny this though.
>
>
>> No new devices, so no new drivers.
>
> Device drivers may not mean additional physical devices. A lot of software
> uses code that runs as a device driver as this is the only way of getting
> third party code to run in kernel mode.
>
> Ed Metcalfe.
>
Ed Metcalfe wrote:
> "Ed Metcalfe" <edmetcalfe@hotmail.com> wrote in message
> news:%23pULyV4fHHA.208@TK2MSFTNGP05.phx.gbl...
>> "babel17" <"babel17not me"@optonline.net> wrote in message
>> news:KsrUh.41$LM1.27@newsfe12.lga...
>>> How would I find which application was trying to access the same memory
>>> address?
>> I'm not sure. Process Explorer from www.sysinternals.com has a facility to
>> show the owning process of a window, however I'm not convinced this will
>> work in this scenario as I don't believe this is an error message
>> displayed by the application. You could also try Process Monitor
>> (available from the same site).
>>
>> This may not be the cause of the problem. My guess is this is not a dodgy
>> RAM issue though - MemTest86 would confirm or deny this though.
>>
>>
>>> No new devices, so no new drivers.
>> Device drivers may not mean additional physical devices. A lot of software
>> uses code that runs as a device driver as this is the only way of getting
>> third party code to run in kernel mode.
>>
>> Ed Metcalfe.
>>
>
> This may be worth a look:
>
> http://support.microsoft.com/default...b;en-us;899811
>
>
Thanks, Ed.
It appears on http://support.microsoft.com/default...b;en-us;899811
that Microsoft is implying that they wish to fine tune this hotfix.
I may hold off until they do, as the problem is bearable.
Thank you very much for the reference to this URL.
babel17 wrote:
> Stan Brown wrote:
>> Sat, 14 Apr 2007 17:24:56 -0400 from babel17 <"babel17not
>> me"@optonline.net>:
>>> Here is a problem I have been having for some time.
>>>
>>> "The instruction at "0x0***454d" referenced memory at "0x0***454d".
>>> The memory could not be "read".
>>
>> Since this happens repeatedly, you should *immediately* do a strong
>> memory scan of your computer. It appears you may have some bad RAM. If
>> you do, then anything that happens to hit that particular spot in RAM
>> on its way to your disk will be written wrong, permanently. This is a
>> very bad thing.
>>
>>> Now all I have to do is click "OK" and the message dissappears, so
>>> it is not causing a major problem.
>>
>> I would not be so sanguine.
>>
>>> Anyone have any ideas why this message appears and what I can do to
>>> avoid it?
>>
>> Not "avoid", but fix the problem. Get a friend with a known good
>> computer to visit www.memtest.org and burn you a bootable CD of that
>> free software. Then boot it in your computer. (It doesn't run from
>> Windows; you must reboot. If necessary, get the friend to show you how
>> to boot from CD instead of hard drive.)
>>
>> If you have bad RAM, it should show up within a few minutes of running
>> the memory test. If it doesn't find any problem after running for at
>> least an hour (or two complete passes), then it's not bad RAM but you
>> should probably do a repair install of Windows since IE is misbehaving.
>>
>> If you do have bad RAM, the good news is that it's easy to replace
>> (even on most laptops) and not terribly expensive. Any computer-savvy
>> friend can help you.
>>
>>
> Stan:
>
> I went to the website you referred to.
>
> For someone with little technical computer knowledge, which of the
> following versions should I download . . .
>
> Download - Pre-Compiled Bootable ISO (.gz)
> Download - Pre-Compiled Bootable ISO (.zip)
>
>
> Download - Pre-Compiled Bootable Binary (.gz)
> Download - Pre-Compiled Bootable Binary (.zip)
>
> Thanks.
>
> Babel.
>
>
I'm not sure what a "binary" or an "ISO" are, nor which one I should
download to make a bootable CD to test my computer's memory.
"babel17" <"babel17not me"@optonline.net> wrote in message
news:9oxUh.96$LM1.74@newsfe12.lga...
> babel17 wrote:
>> Stan Brown wrote:
>>> Sat, 14 Apr 2007 17:24:56 -0400 from babel17 <"babel17not
>>> me"@optonline.net>:
>>>> Here is a problem I have been having for some time.
>>>>
>>>> "The instruction at "0x0***454d" referenced memory at "0x0***454d".
>>>> The memory could not be "read".
>>>
>>> Since this happens repeatedly, you should *immediately* do a strong
>>> memory scan of your computer. It appears you may have some bad RAM. If
>>> you do, then anything that happens to hit that particular spot in RAM on
>>> its way to your disk will be written wrong, permanently. This is a very
>>> bad thing.
>>>
>>>> Now all I have to do is click "OK" and the message dissappears, so
>>>> it is not causing a major problem.
>>>
>>> I would not be so sanguine.
>>>
>>>> Anyone have any ideas why this message appears and what I can do to
>>>> avoid it?
>>>
>>> Not "avoid", but fix the problem. Get a friend with a known good
>>> computer to visit www.memtest.org and burn you a bootable CD of that
>>> free software. Then boot it in your computer. (It doesn't run from
>>> Windows; you must reboot. If necessary, get the friend to show you how
>>> to boot from CD instead of hard drive.)
>>>
>>> If you have bad RAM, it should show up within a few minutes of running
>>> the memory test. If it doesn't find any problem after running for at
>>> least an hour (or two complete passes), then it's not bad RAM but you
>>> should probably do a repair install of Windows since IE is misbehaving.
>>>
>>> If you do have bad RAM, the good news is that it's easy to replace (even
>>> on most laptops) and not terribly expensive. Any computer-savvy friend
>>> can help you.
>>>
>>>
>> Stan:
>>
>> I went to the website you referred to.
>>
>> For someone with little technical computer knowledge, which of the
>> following versions should I download . . .
>>
>> Download - Pre-Compiled Bootable ISO (.gz)
>> Download - Pre-Compiled Bootable ISO (.zip)
>>
>>
>> Download - Pre-Compiled Bootable Binary (.gz)
>> Download - Pre-Compiled Bootable Binary (.zip)
>>
>> Thanks.
>>
>> Babel.
>>
>>
> I'm not sure what a "binary" or an "ISO" are, nor which one I should
> download to make a bootable CD to test my computer's memory.
>
> Babel
>
> --
> Kindly remove "notme" to reply.
ISO. You make a bootable CD by burning an ISO image to it.
Jim
Jim wrote:
> "babel17" <"babel17not me"@optonline.net> wrote in message
> news:9oxUh.96$LM1.74@newsfe12.lga...
>> babel17 wrote:
>>> Stan Brown wrote:
>>>> Sat, 14 Apr 2007 17:24:56 -0400 from babel17 <"babel17not
>>>> me"@optonline.net>:
>>>>> Here is a problem I have been having for some time.
>>>>>
>>>>> "The instruction at "0x0***454d" referenced memory at "0x0***454d".
>>>>> The memory could not be "read".
>>>> Since this happens repeatedly, you should *immediately* do a strong
>>>> memory scan of your computer. It appears you may have some bad RAM. If
>>>> you do, then anything that happens to hit that particular spot in RAM on
>>>> its way to your disk will be written wrong, permanently. This is a very
>>>> bad thing.
>>>>
>>>>> Now all I have to do is click "OK" and the message dissappears, so
>>>>> it is not causing a major problem.
>>>> I would not be so sanguine.
>>>>
>>>>> Anyone have any ideas why this message appears and what I can do to
>>>>> avoid it?
>>>> Not "avoid", but fix the problem. Get a friend with a known good
>>>> computer to visit www.memtest.org and burn you a bootable CD of that
>>>> free software. Then boot it in your computer. (It doesn't run from
>>>> Windows; you must reboot. If necessary, get the friend to show you how
>>>> to boot from CD instead of hard drive.)
>>>>
>>>> If you have bad RAM, it should show up within a few minutes of running
>>>> the memory test. If it doesn't find any problem after running for at
>>>> least an hour (or two complete passes), then it's not bad RAM but you
>>>> should probably do a repair install of Windows since IE is misbehaving.
>>>>
>>>> If you do have bad RAM, the good news is that it's easy to replace (even
>>>> on most laptops) and not terribly expensive. Any computer-savvy friend
>>>> can help you.
>>>>
>>>>
>>> Stan:
>>>
>>> I went to the website you referred to.
>>>
>>> For someone with little technical computer knowledge, which of the
>>> following versions should I download . . .
>>>
>>> Download - Pre-Compiled Bootable ISO (.gz)
>>> Download - Pre-Compiled Bootable ISO (.zip)
>>>
>>>
>>> Download - Pre-Compiled Bootable Binary (.gz)
>>> Download - Pre-Compiled Bootable Binary (.zip)
>>>
>>> Thanks.
>>>
>>> Babel.
>>>
>>>
>> I'm not sure what a "binary" or an "ISO" are, nor which one I should
>> download to make a bootable CD to test my computer's memory.
>>
>> Babel
>>
>> --
>> Kindly remove "notme" to reply.
> ISO. You make a bootable CD by burning an ISO image to it.
> Jim
>
>
OK - downloaded & unzipped.
Do I have this right ? - I burn it to a CD then reboot with the CD in
the CD drive (that's what they mean by "bootable CD") ?
Mon, 16 Apr 2007 17:26:12 -0400 from babel17 <"babel17not
me"@optonline.net>:
> >>> Stan Brown wrote:
> >>>> Not "avoid", but fix the problem. Get a friend with a known good
> >>>> computer to visit www.memtest.org and burn you a bootable CD of that
> >>>> free software. Then boot it in your computer. (It doesn't run from
> >>>> Windows; you must reboot. If necessary, get the friend to show you how
> >>>> to boot from CD instead of hard drive.)
> >>>>
> >>>> If you have bad RAM, it should show up within a few minutes of running
> >>>> the memory test. If it doesn't find any problem after running for at
> >>>> least an hour (or two complete passes), then it's not bad RAM but you
> >>>> should probably do a repair install of Windows since IE is misbehaving.
> >>>>
> >>>> If you do have bad RAM, the good news is that it's easy to replace (even
> >>>> on most laptops) and not terribly expensive. Any computer-savvy friend
> >>>> can help you.
>
> OK - downloaded & unzipped.
>
> Do I have this right ? - I burn it to a CD then reboot with the CD in
> the CD drive (that's what they mean by "bootable CD") ?
Be sure in your CD burning software that you select "bootable CD" as
an option or an output type.
And you're doing this on another computer, not the bad one, right?
Stan Brown wrote:
> Mon, 16 Apr 2007 17:26:12 -0400 from babel17 <"babel17not
> me"@optonline.net>:
>
>>>>> Stan Brown wrote:
>>>>>> Not "avoid", but fix the problem. Get a friend with a known good
>>>>>> computer to visit www.memtest.org and burn you a bootable CD of that
>>>>>> free software. Then boot it in your computer. (It doesn't run from
>>>>>> Windows; you must reboot. If necessary, get the friend to show you how
>>>>>> to boot from CD instead of hard drive.)
>>>>>>
>>>>>> If you have bad RAM, it should show up within a few minutes of running
>>>>>> the memory test. If it doesn't find any problem after running for at
>>>>>> least an hour (or two complete passes), then it's not bad RAM but you
>>>>>> should probably do a repair install of Windows since IE is misbehaving.
>>>>>>
>>>>>> If you do have bad RAM, the good news is that it's easy to replace (even
>>>>>> on most laptops) and not terribly expensive. Any computer-savvy friend
>>>>>> can help you.
>> OK - downloaded & unzipped.
>>
>> Do I have this right ? - I burn it to a CD then reboot with the CD in
>> the CD drive (that's what they mean by "bootable CD") ?
>
> Be sure in your CD burning software that you select "bootable CD" as
> an option or an output type.
>
> And you're doing this on another computer, not the bad one, right?
>
Stan: I tried to select bootable CD on Nero, & it told me I had to
formate the CD, so I right-clicked the CD burner in "My Computer".
Windows(?) told me I had to enable drag-to-disk,, which I did, and
dragged the unzipped program to the CD. I then rebooted with the CD
still in the drive, but Windows booted normally, not to the memory test
program - well, not normally, I couldn't get into "My Computer"
(searchlight), so I took the CD out & rebooted again.
I guess I have to figure out how to burn a bootable CD with Nero, in
order to do this.
Tue, 17 Apr 2007 19:00:56 -0400 from babel17 <"babel17not
me"@optonline.net>:
> I guess I have to figure out how to burn a bootable CD with Nero, in
> order to do this.
Yes.
Why not ask a computer-savvy friend? This is the sort of thing she an
show you in two minutes, where it would take a lot longer to try to
explain with back-and-forth in Usenet.
Re: an error message I would like to avoid 
Linear Mode
