Refrerenced memory at 0x0000000c could not be "read"?

Hello all you nice people out there in 'Sanity' land,

First - a message from my sponsor: 'For the record, I'm no computer wiz. And, I also do not know all-a-da proper terminologies either. This is stated before someone ups and decides to send any defamatory e-mail my way. Thank you.'

You may now return to your regularly non-scheduled e-mails.

Ah, hello again. Now, sledge-in-hand, let's have it. I had installed the VisualBasic Express, oh, about 2wks ago. A very short time thereafter I got an error message. It read, reads, as follows:

aspnet_state.exe. Application Error.

The instruction at 0x6a2a2fec referenced memory

at 0x0000000c could not be "read".

Click "OK" to end program

Click "Cancel" to debug.

This message would appear every time that I shut down. [Still does!] I was unable to gain any knowledge as to what caused, incurred, bought forth it's wrath, or otherwise pointed me out to this error. But, to the sum of it, I ended up dumping my hd and re-loading the OS - onto a RAW HD! Along with every program all over - again! I did not reinstall the VB EX - nor did I reinstall my Norton SW [It 'was' about my 4th, or 5th! time, of being directed to return to a RAW environment by Tech Support!]

To this very day I did not know what the problem was then. And, yes, still today - I still do not know. After everything was ree-loaded, except for the VB Express & NSW, I now have that self same problem all - over - again. I believe it may have been created through improper settings to, definity no thanks to me, Services - via Admin. Tools. I went into a panic regardless just from the sight of those words which carry such utter devastation.

Finally, I am not able to remember just which service/services that I activated or de-activated that may have brought this vengence into my home. So I went through each and every service, one-by-one, on & off, that, obviously, did no good either. It simply will not leave, go away, or be evicted.

I am at wits end here. And that is an understatement of universal proportion beyond the understandings of mortal man. No - even that don't cover to it!

I'm not one to beg. But, you got it, here I am. {Begging of course!] So, please, if the name-a-da merciful 'God' above! HELP!!!!!!!!!!!!!!!!!

Thanx could never be enough to say, or do, be there someone, anyone, anything, any pet, any in-law, rodent, fish etc etc. Out there, in the great, w-i-d-e US of A that holds this most treasured knowledge of how to find my stolen 'Precious'. I'd love to "read" it.

It's been so long...

All these lost years...

I just can't believe it...

Beaten. By Sand no less!,

GeoK




Answer this question

Refrerenced memory at 0x0000000c could not be "read"?

  • The_Drewster

    The way I fixed this problem is by reinstalling ASP.Net.
    I had exactlyt the same error message.
    though mine occured to my laptop.

    is it a web server < if it is, sorry to here that>

    the step i toke to resolved it is shown at my first post.
    if that didn't work. let me know.



  • pxgator

    post a screenshot of the error message and more description please

    When:
    Where:


  • SD Diver

    Hello,I just wanted to say THANK YOU!I have been having the same error message as others at shut down.I did what you suggested and went to services and disabled asp.net and now no more error message. AGAIN THANK YOU FOR HELPING ME DO WHAT HP COULDNT. GOD BLESS! AWAITING HIS RETURN!
  • Kartit

    I am running Windows XP, Media Edition 2005. I have all security updates in place. Somewhere around two weeks ago , I started getting a similar message. Mine appears while closing out Internet Explorer. The message I am getting is : The instruction at "0x02121f21" referenced memory at "0x01a2f238." The memory could not be "read." Along with the Click "OK" to end program. This "new" bug happens every time I close out of Internet Explorer. Is anyone else having the same issue Does anyone have any idea how to fix it I swear, nothing drives me more batty than a constant error reminding me that a program isn't working correctly!

    Thanks for your time in advance.

    Serenefive


  • Omar80

    We just installed VS2005 and we're getting this same error. Can't seem to fix it.

    I've been googling, but can't find a fix. Does anyone here have a fix

    Thanks!
    Joe


  • lisa52

    A screenshot would be very hard to provide as the error message pops up during shutdown of windows. GeoK’s post previously on this thread quotes exactly what the error popup says:

    aspnet_state.exe. Application Error.

    The instruction at 0x6a2a2fec referenced memory

    at 0x0000000c could not be "read".

    Click "OK" to end program

    Click "Cancel" to debug.

    This is a bit frustrating as we are worried about rebooting remote servers if they get stuck with an error on shutdown.

    /Per Salmi


  • Daniel Bachler

    Thank you for the infomation your post saved me lots-o-lookup...

    Your answer was right on the money...


  • Jordi73757

    I'm experiencing the same problem.
    I'm using my laptop as a development web server and needed to turn on a service that is not normally turned on by default: asp.net State service.
    (Administrative Tools - Services).

    The error happens when I shut down.
    If the service is turned off (and most users do not need this service up and running), the error disappear.

    So, unless you are using your pc as a webserver, stop that service and the error will go away.
    Doesn't solve my problem (I need to have it running....) but hope it solves yours.


  • wfsCA

    We have this same error on all our developer workstations where we run Visual Studio 2005 and ASP.NET 2.0.

    Anyone found a solution

    Most of the time we don't suffer very much because the shutdown completes after about 10 seconds delay when the error message is displayed.


  • zicovn

    Thanks but the fix above isn't really a fix at all but a workaround for people who don't need ASP.NET 1.1 registered. As soon as you register version 1.1 again, the problem comes back. Is there no way to actually FIX this problem properly Perhaps there's a hotfix or service pack that solves the issue

    Thanks,

    Nick...

  • Youcef

    I don't know why this worked for me but after trying everthing I could find on the internet, none of it worked, I ran winsockxpfix.exe and the error message went away. Do a google search for winsockxpfix.exe and download it for free.

    Hope it helps.


  • wd

    I had the same problem.

    Note: I just want to share what I learn from this experience . . . . . DOCUMENT your actions. meaning . . every time you tried something make sure you write  it down. If the action was unsuccessful . . . return it to the original state. Try to find solutions from more "Solid" sources like this one . . . not from a "Who-Knows" website

    Here is the solution:

    If you have visual studio.net follow this step

    1. go to start
    2. find Visual studio.net
    3. under visual studio.net tools click the command prompt
    4. first let us make sure you have asp.net install and how many version do you have. type
    aspnet_regiis -lv. your root should be whatever version of .Net you have.
    Note: if you don't know, one way to find out is to open visual studio.net - then - go to help menu - then click about visual studio.net . It should tell you want version of .net you have <third line down>.

    another way is to go to the admin tools and right click on the "Microsoft .net framework X.X"
    5. now you know the version we need, lets take out the rest. First we need to completely remove all aspnet versions inside your computer. on the visual studio command prompt type
    aspnet_regiis -ua.
    6. type aspnet_regiis -- the computer should tell you that there are no version installed.
    7. know type aspnet_regiis -i;

    that should fix the problem.

    For those who don't have visual studio.net

    simply use the run command and type the following:
    STOP: v.X.XXXX = the version of .net you have
    type: %windir%\Microsoft.NET\Framework\v.X.XXXX\aspnet_regiis.exe -ua
    type: %windir%\Microsoft.NET\Framework\v.X.XXXX\aspnet_regiis.exe -i

    NOTE: make sure you turn on Aspnet_state.exe in your computer. Go to the administrative tools and double click on service and find "ASP.NET State Service" double click it and click the start button. You can change the start type too if you want

    Another problem: "I CANT CREATE NEW ASP.NET PROJECTS ON VISUAL STUDIO"

    make sure you turn on the IIS and ASP.NET state service.

    that should fix it.

    problem: "I CAN'T FIND IIS IN THE SERVICE CONSOLE"

    on the run command type "control panel" <just go there what ever works>
    find add and remove program
    inside the add and remove program window click on the "Add/Remove Window'sComponet"
    if "Internet Information Service (IIS)" is not check. . . . well . . . check it.
    <NOTE: when I installed IIS in my laptop , it requires Window XP disk. . .not sure if it will be the same case to you>

    after that is done . . turn it on

    when both IIS and ASPnet_State.exe are on = problem solve
    I hope this article help you solve your problems. it toke me two days to solve this problem because mainly  because I don't keep track of my actions and sources

    if you still can't create asp.net project via visual studio.net then you you need to setup your IIS




  • sParc134758

    Hi to all!

    At firt sorry for my english

    I'he the same problem, and the solution for solve it doesn't works.

    I Don't use Visual Studio, so i tried with solution using the run command.

    I'he set the aspnet_state service in mode automatic:

    if i used my software when i shutdown the pc i haven't errors, but i try to shutdown pc without to use my software so i have the error...

    how can solve this

    Tx a lot!


  • Narcomancer

    Hey folks, I'm checking on this now, will post when I hear back.

    If you do not need asp.net for anything, Michael_Guinto's post above shows how to disable it, which will effectively work around this problem. I marked his post as an 'answer' because this workaround will work for some of you.

    If you do need asp.net and are hitting this, wait for my reply.

    Thanks

    Alex



  • Refrerenced memory at 0x0000000c could not be "read"?