the instruction at 0x75606e6a referenced memory at 0x00000008. The memory could not be "read."
Four answers:
modista
2009-02-28 13:17:43 UTC
I also have the same error and I tried the memtest recommended above but I don't know how to run it.
I also found a page giving instructions on how to repair svchost.
http://www.pchell.com/support/svchosterror.shtml
Joshua C
2009-02-26 17:44:17 UTC
When computers are running code, they have a list of instructions that they run in order. The first part is where the instruction was, where the computer was told to do something. Part of that instruction was to go to a place in your computers memory and get some information out of it. The place that it was asked to look at (that second number), is actually off limits for most programs to use. Basically, something went wrong with your program you were running.
This is like your boss at work telling you to go to the Pentagon and count how many chairs are there, and you coming back and saying "they wouldn't let me in".
Addresses that start with a lot of 0's are generally reserved for the operating system and system level data structures.
Din
2009-02-26 17:50:04 UTC
That can be a sign of memory going bad. If you get a lot of "General Protection Fault" errors or memory read/write errors then you may have a failing block of memory.
I'd recommend using a utility like Memtest86+ to check your memory for errors. If it finds any errors you'll want to replace the memory stick or risk things getting worse. Keep in mind that memory errors can give you all kinds of seemingly unrelated problems. All programs that you run and all your files that you open get loaded into memory first . That means anything can get garbled if part of it is written into a failing section of memory.
If you bought the memory retail then you should be able to get an RMA number from the manufacturer and send it back for a replacement. If it came with an OEM computer (Dell, HP, Gateway, eMachine, Compaq, etc.) then you have to go through them *if* it's still under warranty with them. If it's not under warranty then you're out of luck and need to buy a replacement stick yourself.
Eric M
2009-02-27 09:29:14 UTC
I have the same exact error message that you have and it is coming up everytime that I go to a new webpage or a popup occurs. I did just take off WiniGuard that someone inadvetantly put on my computer,but I am not sure yet.
Let me know if you find anything out on this one. I am in hell right now.
ⓘ
This content was originally posted on Y! Answers, a Q&A website that shut down in 2021.