what does this memory error mean?

"The instruction at 0x00932723 referenced memory at 0x1091009c. The memory
could not be read. "

I ran two ram checks/tests and there no problems with the ram. Already tried
google. Anyone else ever seen this error and solved the problem? Any advice
appreciated. Thanks!

"d" <d@invalide.aol.com> wrote in message news:dPBlh.15834$h_1.1222@bignews6.bellsouth.net.. .
> "The instruction at 0x00932723 referenced memory at 0x1091009c. The memory
> could not be read. "
>
> I ran two ram checks/tests and there no problems with the ram. Already tried
> google. Anyone else ever seen this error and solved the problem? Any advice
> appreciated. Thanks!

It likely means there's a bug in the software you were trying to run.

-- Bob Day
http://bobday.vze.com

"Bob Day" <xxxxxx@yyyyyy.com> wrote in message
news:VYBlh.801$NO5.636@trndny01...
> "d" <d@invalide.aol.com> wrote in message
news:dPBlh.15834$h_1.1222@bignews6.bellsouth.net.. .
> > "The instruction at 0x00932723 referenced memory at 0x1091009c. The
memory
> > could not be read. "
> >
> > I ran two ram checks/tests and there no problems with the ram. Already
tried
> > google. Anyone else ever seen this error and solved the problem? Any
advice
> > appreciated. Thanks!
>
> It likely means there's a bug in the software you were trying to run.


Yes.
That would be true if the error only occurs while running one particular
application

OTOH: If that error occurs while running different apps...then it probably
is a RAM problem
(even if it did pass a RAM test)



--
Posted via a free Usenet account from http://www.teranews.com

d wrote:
>
> "The instruction at 0x00932723 referenced memory at 0x1091009c.
> The memory could not be read. "
>
> I ran two ram checks/tests and there no problems with the ram.
> Already tried google. Anyone else ever seen this error and solved
> the problem? Any advice appreciated. Thanks!

Do you have over 256 MB of memory? What sort of memory test? The
built in bios scan won't test it. Find memtest86.

You failed to set follow-ups to a newsgroup you normally read. So
I did.

--
Merry Christmas, Happy Hanukah, Happy New Year
Joyeux Noel, Bonne Annee.
Chuck F (cbfalconer at maineline dot net)
<http://cbfalconer.home.att.net>

"philo" <philo@privacy.net> wrote in message
news:4596e484$0$18577$88260bb3@free.teranews.com.. .
>
> "Bob Day" <xxxxxx@yyyyyy.com> wrote in message
> news:VYBlh.801$NO5.636@trndny01...
>> "d" <d@invalide.aol.com> wrote in message
> news:dPBlh.15834$h_1.1222@bignews6.bellsouth.net.. .
>> > "The instruction at 0x00932723 referenced memory at 0x1091009c. The
> memory
>> > could not be read. "
>> >
>> > I ran two ram checks/tests and there no problems with the ram.
>>
>> It likely means there's a bug in the software you were trying to run.
>
> Yes.
> That would be true if the error only occurs while running one
> particular
> application
>
> OTOH: If that error occurs while running different apps...then it
> probably
> is a RAM problem
> (even if it did pass a RAM test)


Unless the OP is running DOS, there is no way he is running just one
program in memory. Also, the OP provided no clue as to WHICH "ram
checks/tests" he used to supposedly test his memory. If the OP tested
using memtest86 (from http://www.memtest86.com/ and NOT the one from
http://www.memtest.org/) then it very probably is NOT the memory
hardware. Could be the OS, a driver, something he has load on Windows
startup, some add-on or plug-in to whatever program(s) he is running,
some always-running program, like a firewall or anti-virus software, a
proxy used by different similar-function programs, and the list goes on.
Absolutely no history is indicated. Did it happen always, or just
recently, or after some hardware or software change?

Thanks for turning a simple little question into a debate fest guys.

There is nothing wrong with my ram. And my post was simple and short because
if you have not seen this error and solved it yourself, I am certain you
cannot help me. . . . which the replies have proven so far :) You guys
don't know the answer NOT because I haven't give you guys enough info, ok?
Even if I answer all your questions, you still won't know the answer :)

The worrisome thing so far is that now serveral people have told me they get
this error when they do just common internet browsing. I am getting it when
I run a dedicated server program. But the error could very well happen when
the server program is not even up! So I can't really buy the statement that
it's some program I'm running. However, more gamers than browsers have told
me they got it with their pc games. So that is why I am doing all the steps
below.

And I'm certain one of these steps below will solve my problem. I got them
from Google research, and curiously not these newsgroups (wink).

--------0------------0-----------0-------
Run Regedit from run box. Look at the following locations in the registry
and change the

values from 0 to 1:

hkey_local_machine-system-currentcontrolset-control-session manager-memory
management

and look for

DisablePagingExecutive waarde = 1
LargeSystemCache = 1

You can always go back and put the values back to zero if you are skeptical
about this one.


---------0---------------0----------

Doubt this next one will do anything for you in regards to this specific
memory problem, but you might as well try it to rule it out. I did, and it
showed no errors.

Go to Run box again and run sfc /scannow. Make sure you have your Windows CD
in the cdrom. This checks all your system files to make sure they are not
corruopt. You will probably have to hit the Retry button about 40 times
because it stops and asks you each
time it finds a file that has a problem or doesn't match the original and is
not stored on your computer. You can read more about scan fc here:

http://www.updatexp.com/scannow-sfc.html


------0----------------0-----------

If you have installed Java or bought a computer with Jave on it, you should
try this one. I honestly don't know what this one could do with me running a
server, but you might as well try it. They actually had a screenshot of the
exact error I was getting, so that's why I tried it. And, of course, I never
noticed this problem before I installed Java. I did Solution #2 on this
webpage:

http://www.java.com/en/download/help/ikernel.xml



-------0-----------------0----------

And this next tip is a work-around, but I know for sure it works. Most of
the people who have complained about this error would not even have known
about it had they turned off their error reporting system.

So go into Control Panel > System > Advanced tab > and

select button Error Reporting. Then uncheck everything except the first one
that says Disable Error Reporting. Out of sight out of mind for those who
had the error when they were internet browsing. For me, my server might
still crash, but we shall see soon enough.


---------0--------------------0----


Ok, this step makes me a little concerned about the guy's knowledge who
suggested it. And I really don't think its my problem, even though I did
upgrade from 512mb to 1 gig of ram. I started runing the server after the
upgrade, so I just can't put much weight on this. But alot of ram gurus will
tell you to do something similar to this when you get a memory error after
you upgraded ram. And it certainly won't hurt you to try it. Note though
that for me I could not make the setting 2 times bigger as this guy suggests
to do. I could only set the maximum for 17000mb because that is all Windows
would let me do, but that is still pretty big. I also believe you are
supposed to delete your old
pagesys file before you do any of these steps, but he does not say that
below.


The instructions:



Try recreating the virtual memory.

For XP system...
1. Right-click on My Computer and select Properties.
2. Click the Advanced Tab and select Settings under the Perfomance Options.
3. Click on the Advanced Tab and select Change under Virtual Memory.
4. Click No Paging File and clisk Set.
5. Click OK, OK, OK and tell the system to restart.
6. Let the system reboot...It will be slower than usual.
7. Right-click on My Computer and select Properties.
8. Click the Advanced Tab and select Settings under the Perfomance Options.
9. Click on the Advanced Tab and select Change under Virtual Memory.
10. Click Custom Size and set the Initial Size to (1.5 times your Physical
Memory.)
11. Set Maximum to (2 times your Physical Memory.)
12. Click OK, OK, OK. No reboot required.

This problem stems from system images. When a manufacturer creates an image
and then changes the memory but does not update the image, memory errors can
occur. This can even happen when you upgrade your own system memory. Always
recreate the Virtual memory after modifying physical memory. It should
prevent these types of errors.

d <d@invalide.aol.com> wrote

> Thanks for turning a simple little question into a debate fest guys.

You clearly wouldnt know what a real debate
fest was if it bit you on your lard arse.

> There is nothing wrong with my ram.

Unless you spell out how you decided that, anyone with
a clue isnt prepared to accept your assertion on that.

> And my post was simple and short because if you have not seen this error and solved it yourself, I
> am certain you cannot help me. . . .

More fool you. Some of us can fix ANY problem
with a careful analysis of the detail seen.

> which the replies have proven so far :)

Wrong again.

> You guys don't know the answer NOT because I haven't give you guys enough info, ok? Even if I
> answer all your questions, you still won't know the answer :)

Using that mindlessly silly line, some problems can never be resolved.

Wrong.

> The worrisome thing so far is that now serveral people have told me they get this error when they
> do just common internet browsing. I am getting it when I run a dedicated server program.

Then you should have said that, its vital information.

> But the error could very well happen when the server program is not even up!

You clearly havent actually got a fucking clue about anything at all.

> So I can't really buy the statement that it's some program I'm running.

That was just one POSSIBILTY that can produce that error message.

> However, more gamers than browsers have told me they got it with their pc games. So that is why I
> am doing all the steps below.

It is in fact not a particular uncommon error message
and it can be caused by a number of things.

Effective diagnosis involves systematically testing the
possibilitys that can produce that particular error message.

Not stamping your foot when someone doesnt give you an instant
diagnosis with the pathetically inadequate information you provided.

> And I'm certain one of these steps below will solve my problem.

And it remains to be seen if your certainty turns out to be valid.

> I got them from Google research, and curiously not these newsgroups (wink).

You previously claimed

>> Already tried google.

You were either lying then, or are lying now.

> --------0------------0-----------0-------
> Run Regedit from run box. Look at the following locations in the registry and change the

> values from 0 to 1:

> hkey_local_machine-system-currentcontrolset-control-session
> manager-memory management

> and look for

> DisablePagingExecutive waarde = 1
> LargeSystemCache = 1

> You can always go back and put the values back to zero if you are skeptical about this one.

Mindlessly silly, it wont be that.

> ---------0---------------0----------

> Doubt this next one will do anything for you in regards to this
> specific memory problem, but you might as well try it to rule it out.
> I did, and it showed no errors.

> Go to Run box again and run sfc /scannow. Make sure you have your
> Windows CD in the cdrom. This checks all your system files to make
> sure they are not corruopt. You will probably have to hit the Retry
> button about 40 times because it stops and asks you each time it finds a file that has a problem
> or doesn't match the original and is not stored on your computer. You can read more about scan fc
> here:

> http://www.updatexp.com/scannow-sfc.html

Very unlikely indeed to be the problem if it isnt reproducible.

Only worth trying when the other more obvious possibilitys have been eliminated.

> ------0----------------0-----------

> If you have installed Java or bought a computer with Jave on it, you should try this one. I
> honestly don't know what this one could do with me running a server, but you might as well try it.
> They actually had a screenshot of the exact error I was getting, so that's why I tried it. And, of
> course, I never noticed this problem before I installed Java. I did Solution #2 on this webpage:

> http://www.java.com/en/download/help/ikernel.xml

> -------0-----------------0----------

> And this next tip is a work-around, but I know for sure it works.
> Most of the people who have complained about this error would not
> even have known about it had they turned off their error reporting system.

> So go into Control Panel > System > Advanced tab > and

> select button Error Reporting. Then uncheck everything except the
> first one that says Disable Error Reporting. Out of sight out of mind
> for those who had the error when they were internet browsing. For me, my server might still crash,
> but we shall see soon enough.

Mindlessly silly.

> ---------0--------------------0----

> Ok, this step makes me a little concerned about the guy's knowledge
> who suggested it. And I really don't think its my problem, even
> though I did upgrade from 512mb to 1 gig of ram. I started runing the
> server after the upgrade, so I just can't put much weight on this.
> But alot of ram gurus will tell you to do something similar to this
> when you get a memory error after you upgraded ram. And it certainly
> won't hurt you to try it. Note though that for me I could not make the setting 2 times bigger as
> this guy suggests to do. I could only set the maximum for 17000mb because that is all Windows
> would let me do, but that is still pretty big. I also believe you are supposed to delete your old
> pagesys file before you do any of these steps, but he does not say that below.

> The instructions:

> Try recreating the virtual memory.

> For XP system...
> 1. Right-click on My Computer and select Properties.
> 2. Click the Advanced Tab and select Settings under the Perfomance Options. 3. Click on the
> Advanced Tab and select Change under Virtual Memory.
> 4. Click No Paging File and clisk Set.
> 5. Click OK, OK, OK and tell the system to restart.
> 6. Let the system reboot...It will be slower than usual.
> 7. Right-click on My Computer and select Properties.
> 8. Click the Advanced Tab and select Settings under the Perfomance Options. 9. Click on the
> Advanced Tab and select Change under Virtual Memory.
> 10. Click Custom Size and set the Initial Size to (1.5 times your Physical Memory.)
> 11. Set Maximum to (2 times your Physical Memory.)
> 12. Click OK, OK, OK. No reboot required.

Mindlessly silly.

> This problem stems from system images. When a manufacturer creates an image and then changes the
> memory but does not update the image, memory errors can occur.

Not a fucking clue.

> This can even happen when you upgrade your own system memory. Always recreate the Virtual memory
> after modifying
> physical memory. It should prevent these types of errors.

Not a fucking clue.


How about you try spelling out how you have decided that your memory is fine ?

Most likely you do have a memory problem and need to test that possibility more
carefully by running memtest86+ overnight and the Prime95 system thrashing test.

"Rod Speed" <rod.speed.aaa@gmail.com> wrote in message
news:4voua0F1co3ouU1@mid.individual.net...
<d@invalide.aol.com> wrote a bunch of mindless bable .>


Ahh the ever-amusing maturity of pc gamers LMAO! I've clearly wasted enough
time here. Although I've now learned how to use my filters to weed certain
people out, I won't be back in this thread. CYA dudes.

For anyone else who had a similar problem and stumbled across my post--the
only one that actually told you how to solve the problem--the server has not
crashed in 4 hours, so it looks like one of those steps solved the problem.

There is also one more thing I did that I want to make sure you try. Google
"User Profile Hive Cleanup Service," dload it and install it. Although no
error showed in my System Event viewer, I did have an Event ID 1517
"warning" that suggested I had an application mixup with some service
running in the background. It kept some memory from becoming free. So it
certainly won't hurt you to run the UPHC service.

On Sat, 30 Dec 2006 21:13:50 -0600, "d" <d@invalide.aol.com>
wrote:

>Thanks for turning a simple little question into a debate fest guys.
>
>There is nothing wrong with my ram. And my post was simple and short because
>if you have not seen this error and solved it yourself, I am certain you
>cannot help me. . . . which the replies have proven so far :)

You did not give a full set of information such as whether
this is the ONLY error and exact same error every time.
This makes your opening post quite inadequate, your laziness
in not bothering to fully detail the scenario is the
problem, leaving others to start guessing until they draw
out more information from you - remember that you are the
only one that can actually see the system, know anything
about it but what was provided in your post.

>You guys
>don't know the answer NOT because I haven't give you guys enough info, ok?

You seem to be taking a backwards attitude about this,
perhaps an apology for wasting their time would be in order
- it is your burden to supply the information.

>Even if I answer all your questions, you still won't know the answer :)

Erroneous presumption. Fact is, most people don't have this
error. Only through Q & A to find out what is unique about
your system, would the uniqueness causing the problem be
found.

The general approach is to look at the instruction and
memory addresses and keep track of them- the next time an
error happens, compare these addresses. Were any in common?
Look at the unique jobs running, and the memory dump files
(presuming you DO have it set to make them).

>
>The worrisome thing so far is that now serveral people have told me they get
>this error when they do just common internet browsing. I am getting it when
>I run a dedicated server program. But the error could very well happen when
>the server program is not even up! So I can't really buy the statement that
>it's some program I'm running.

They weren't trying to make you "buy" anything, this is not
a challenge to convince you of anything whatsoever. You
have hardware and software (OS is software). If it's not
the memory itself, could be the memory subsystem, perhaps
even caused by a 3rd factor like heat or power, but any way
you look at it the ultimate end is memory, or software
(programs running). Recognize that it doesn't have to be
some narrow interpretation of something you click to open
for software to be running. Being able to click at all
means you have some software running.



>However, more gamers than browsers have told
>me they got it with their pc games. So that is why I am doing all the steps
>below.
>
>And I'm certain one of these steps below will solve my problem. I got them
>from Google research, and curiously not these newsgroups (wink).

Funny that we don't have these problems, so whatever fault
you have allowed, is not solved because you fail to provide
information, then you wink as if you know something. What
do you know? That your ego caused a problem and prevented
quick resolution of it.

Rest of the random windows urban myths snipped out, because
you didn't find any solution, just tried random things and
are hoping the problem is fixed without any idea.

d <d@invalide.aol.com> wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote d <d@invalide.aol.com> wrote

> Ahh the ever-amusing maturity of pc gamers LMAO!

Guess which pathetic little drug crazed prat has just
got egg all over its pathetic little face, as always ?

> I've clearly wasted enough time here.

Yep, you've clearly got your head completely up your arse.

> Although I've now learned how to use my filters to weed certain people out, I won't be back in
> this thread. CYA dudes.

Dont let the door hit you on the arse on the way out, dud.

> For anyone else who had a similar problem and stumbled across my post--the only one that actually
> told you how to solve the problem--the server has not crashed in 4 hours, so it looks like one of
> those steps solved the problem.

We'll see...

> There is also one more thing I did that I want to make sure you try.
> Google "User Profile Hive Cleanup Service," dload it and install it.
> Although no error showed in my System Event viewer, I did have an
> Event ID 1517 "warning" that suggested I had an application mixup
> with some service running in the background. It kept some memory from
> becoming free. So it certainly won't hurt you to run the UPHC service.

Pathetic, really.

In article <qyJlh.13282$U12.9197@bignews1.bellsouth.net>, d says...
> "Rod Speed" <rod.speed.aaa@gmail.com> wrote in message
> news:4voua0F1co3ouU1@mid.individual.net...
> <d@invalide.aol.com> wrote a bunch of mindless bable .>
>
>
> Ahh the ever-amusing maturity of pc gamers LMAO! I've clearly wasted enough
> time here. Although I've now learned how to use my filters to weed certain
> people out, I won't be back in this thread. CYA dudes.

FUCK YOU THEN. You're posting in a PC system builders group. If you
actually gave us the full story instead of bits then perhaps we'd be
able to help better.


--
Conor

"You're not married,you haven't got a girlfriend and you've never seen
Star Trek? Good Lord!" - Patrick Stewart

In article <EVFlh.17503$cB6.1686@bignews7.bellsouth.net>, d says...
> Thanks for turning a simple little question into a debate fest guys.
>
> There is nothing wrong with my ram. And my post was simple and short because
> if you have not seen this error and solved it yourself, I am certain you
> cannot help me. . . . which the replies have proven so far :) You guys
> don't know the answer NOT because I haven't give you guys enough info, ok?
> Even if I answer all your questions, you still won't know the answer :)
>
I think you'll find we can point you in the right direction. For
example, you claim the RAM is OK but have you run MEMTEST on it?

Usually when you get errors like this it's because the program is
accessing memory you'll commonly not use either because of its size or
because of the number of others running.

FOR EXAMPLE: I had a similar error that showed up in Battlefield 2. It
only ever showed up when I was running that game because it was the
only program that would use more than 1GB of RAM and therefore was the
only one accessing the second 1GB DIMM. Take the DIMM out, the fault
went away. Swap over the DIMM and the error message appeared on other
programs at a different address.


--
Conor

"You're not married,you haven't got a girlfriend and you've never seen
Star Trek? Good Lord!" - Patrick Stewart

d wrote:

> "The instruction at 0x00932723 referenced memory at 0x1091009c. The memory
> could not be read. "
>
> I ran two ram checks/tests and there no problems with the ram. Already
> tried google. Anyone else ever seen this error and solved the problem? Any
> advice appreciated. Thanks!

Even though you seem to be a proper dickwad, I will try to answer your
question.

Firstly, I must say if you have never seen a memory address exception before
you must be a total neophyte. It is a common exception. All it is saying
is that some code executing at 0x00932723 tried to reference an invalid
data memory address. In most cases this is because of a problem with the
code itself and doesn't mean your RAM is stuffed.

There are myriad ways to generate invalid memory references in software,
some of them are: using de-allocated (stale) memory pointers, not checking
return values, not checking for array bounds limits, mis-managing a COM
object's lifetime any many many more.

If the cause is indeed a buggy bit of code, it may not be repeatable either
because it may not happen until the system's memory allocator has to work
hard to find free memory in the heap. This is usually when stale pointer
problems happen the most - when the heap is stressed.

You would be surprised how many applications can shit themselves when they
are running low on heap.

Even though it most likely a software problem, it can also be caused by
hardware - bad RAM or faulty addressing. If you say you have checked your
RAM with diagnostic software then it is almost certainly just a software
problem.

Pissing around with the virtual memory as you appear to have done is
pointless and just shows what an ignorant dickhead you are.

I hope that helps.

"d" <d@invalide.aol.com> wrote in message
news:EVFlh.17503$cB6.1686@bignews7.bellsouth.net.. .
> Thanks for turning a simple little question into a debate fest guys.
>
> There is nothing wrong with my ram. And my post was simple and short
> because if you have not seen this error and solved it yourself, I am
> certain you cannot help me. . . . which the replies have proven so far
> :) You guys don't know the answer NOT because I haven't give you
> guys enough info, ok? Even if I answer all your questions, you still
> won't know the answer :)


If you expected that no one could answer your problem regardless of how
much information that you provided, why the hell are you here wasting
our time? DUH!

"d" <d@invalide.aol.com> wrote in message
news:EVFlh.17503$cB6.1686@bignews7.bellsouth.net.. .
>
> --------0------------0-----------0-------
> Run Regedit from run box. Look at the following locations in the
> registry and change the
>
> values from 0 to 1:
>
> hkey_local_machine-system-currentcontrolset-control-session
> manager-memory management
>
> and look for
>
> DisablePagingExecutive waarde = 1
> LargeSystemCache = 1
>
> You can always go back and put the values back to zero if you are
> skeptical about this one.

You haven't a clue what this does, do you? It leaves more of the exec
in physical memory and less on the slow hard drive in the pagefile.
Setting it to 1 means more is in physical memory which merely means more
of your real memory got consumed. That is hardly what will cause the
RAM error as loading ANY addition software would consume the extra
amount of real memory.

> Go to Run box again and run sfc /scannow. Make sure you have your
> Windows CD in the cdrom. This checks all your system files to make
> sure they are not corruopt. You will probably have to hit the Retry
> button about 40 times because it stops and asks you each
> time it finds a file that has a problem or doesn't match the original
> and is not stored on your computer. You can read more about scan fc
> here:

You really are just shotgunning around trying to find something,
anything, that might fix your software problem. I'm surprised you
didn't mention inserting the install CD, selecting to format the old
partition, and doing a full new install of the OS would fix the problem,
too.

> If you have installed Java or bought a computer with Jave on it, you
> should try this one. I honestly don't know what this one could do with
> me running a server, but you might as well try it. They actually had a
> screenshot of the exact error I was getting, so that's why I tried it.
> And, of course, I never noticed this problem before I installed Java.
> I did Solution #2 on this webpage:

More shotgunning. Rather than narrow down what software caused the
problem, you are just stomping around hoping to step atop of whatever is
screwing up. Yeah, real pro are you ... not!

<snip - more shotgunning - and he hasn't hit the bird yet>

Reminds of the idiot that used to work on the mainframe I/O unit. When
he had a problem, his first step was to slam the suspect circuit card
against the table to see if any of the chips popped off their tops and
then take it into rework to have the chip replaced. There was a chance
that he might get the defective chip replaced. He didn't know what to
do but felt he had to show he was doing something.

""The instruction at 0x00932723 referenced memory at 0x1091009c. The
memory
could not be read. "

Yeah, that was clear. Did it occur in a program, and the same program?
Did it popup when you thought you weren't running a program (which means
it was a background program)? Did you try Safe Mode? At this point,
and since you are only here to spout your claimed intelligence in
reading other people's articles, I don't care anymore about your
problem. You really don't want help. The fact that you said "Thanks
for turning a simple little question into a debate fest guys" proves you
haven't a clue about the scope of this problem. Enjoy your flaky
machine.

"Vanguard" wrote:
>
> Unless the OP is running DOS, there is no way he is running just one
> program in memory. Also, the OP provided no clue as to WHICH "ram
> checks/tests" he used to supposedly test his memory. If the OP tested
> using memtest86 (from http://www.memtest86.com/ and NOT the one from
> http://www.memtest.org/) then it very probably is NOT the memory hardware.

Why is it that you do not trust the results from memtest86+ (if I am reading
you correctly)?

Jon

It seems to me that D asked for help, and instead got picked on and cursed
at... Fight pickers.
"d" <d@invalide.aol.com> wrote in message
news:dPBlh.15834$h_1.1222@bignews6.bellsouth.net.. .
> "The instruction at 0x00932723 referenced memory at 0x1091009c. The memory
> could not be read. "
>
> I ran two ram checks/tests and there no problems with the ram. Already
tried
> google. Anyone else ever seen this error and solved the problem? Any
advice
> appreciated. Thanks!
>
>