这些天很少见，但有时您在使用计算机时仍然会遇到神秘的错误消息。隐秘错误是不能真正解释自己的错误。
如果幸运的话，您会得到一个可以查找的错误参考编号，但在“无法读取引用内存中的指令”错误的情况下，您(Referenced Memory Could)就(Instruction)没有这样的运气了。
这种特殊的错误可能随时发生，通常没有任何明确的原因。因此，如果您在 PC 上愉快地做自己的事情，但突然遇到软件崩溃和此错误，本指南将引导您走上恢复之路。
这个错误到底是什么？(What Is This Error Exactly?)
错误的实际文本是不言自明的。RAM中的信息存储在特定地址。当有问题的软件需要存储在特定地址的信息时，它会要求它。有时，无论出于何种原因，这个过程都会出错。这个错误告诉我们地址由于某种原因无效。
是什么导致错误？(What Causes The Error?)
现在我们来解决真正的问题。虽然我们知道涉及到无效的内存地址，但我们不知道为什么(why )内存地址无效。
这是这个特殊错误引起如此多悲伤的原因之一。它可以是硬件、软件或月相。好消息是，通过一些推论和逻辑，追踪导致你的记忆错误问题的小精灵是可能的。
做一些侦探工作(Doing Some Detective Work)
在我们查看可以解决此错误的特定修复之前，您需要做一些准备。毕竟，简单地尝试一切更有可能导致新问题，并且不一定会指出问题的真正原因。
您要做的最重要的事情是注意错误发生的时间和方式。问自己这些问题：
- (Did)它是在硬件或软件更改后开始发生的吗 ？
- 它只发生在一个特定的应用程序中吗？
- 不管你在做什么，它都会发生吗？
- 它是随机发生的，还是以设定的时间间隔发生的？
如果您可以收集一些间接证据，它可能会提供有关哪些修复更有可能起作用的线索。例如，如果只有一个特定的程序出现此错误，那么您最好访问他们的技术支持页面，而不是随意摆弄自己的计算机。
在我们讨论使此错误成为遥远记忆的各种方法时，请牢记错误上下文的细节。
最明智的修复(The Most Sensible Fixes)
由于无效内存地址造成轻微破坏的原因有很多，因此收集最明智的修复是有意义的。其中有很多，因此从最有可能与您的特定错误相关的那些开始是要走的路。
如果您执行的修复对您的计算机进行了更改，请记住如果它没有消除问题，请撤消它。如果你不这样做，那么你就是在引入新的变量，这使得消除可能性变得更加困难。系统化！
The Easiest Fix: Ignore It!
这是迄今为止解决问题的最简单方法，但只有在问题的原因不是系统性的情况下，忽略错误才有效。计算机和使它们有用的软件非常复杂。有时事情只会出错一次或很少出错。
因此，如果您一次又一次地看到此错误，请不要担心。如果您每隔几周或几个月就看到一次，那么它也可能不值得努力解决。
如果内存错误正在中断关键任务工作或经常发生以致严重损害您的用户体验，那么您当然应该研究其他解决方案。关键是不要对可能非常罕见或什至可能是一次性的错误感到害怕。
请更多（虚拟）RAM(More (Virtual) RAM Please)
虚拟内存是硬盘驱动器的保留部分，当您的物理RAM(RAM)芯片已满时，它充当溢出。通常，当需要大量内存的应用程序用完RAM并且无处放置附加信息时，它就会丢失。当一个程序要求返回它的信息时，它不存在。这(Which)会导致崩溃或严重故障。
(Memory)现代操作系统中的内存管理确实非常好，并且高质量的软件产品也可以在可用RAM的情况下有效地工作。所以在大多数情况下，甚至不需要虚拟内存。但是，内存管理不善或系统虚拟内存分配过小的程序可能会导致内存错误。
当然，您可以添加更多物理RAM，但一种快速（而且免费！）的解决方案是优化您的虚拟内存分页文件。只需(Just)遵循本指南(this guide)，您的应用程序就会有足够的呼吸空间。
关闭后台应用程序(Close Background Applications)
解决相同问题的另一个角度是减少需要大量内存的应用程序的数量。
您的互联网浏览器是这里最大的罪魁祸首。您在Google Chrome(Google Chrome)等浏览器中打开的每个(Every)选项卡都会占用大量内存(RAM)。有人加载游戏并将浏览器或办公套件软件在后台打开是很正常的。如果您的内存不足，关闭一些选项卡或保存您的工作并关闭您的生产力应用程序可能会有很大帮助。
也许您没有在后台运行的程序，至少不是您知道的程序。最好检查计算机空闲时使用了多少内存。这样做再简单不过了。
在 Windows 10、8 或 7 中，只需press CRTL+ALT+DEL ，然后单击任务管理器。(click Task Manager.)
如果您的任务管理器(Task Manager)如下所示：
然后单击更多详细信息(click More Details)将其展开。
现在，在“进程(Processes)”选项卡下，单击“内存”(Memory )列以按内存使用情况排列进程。查找正在使用大量内存的任何进程。如果它们不重要，您可以通过右键单击进程并选择结束任务(End Task)来结束它们。
请注意，如果您不知道流程是什么，则应首先使用 Google 搜索。如果可能非常重要！
时光倒流(Turn Back Time)
就今天仍在使用的操作系统而言，Windows 的最后几个版本实际上可以追溯到 Windows 7，具有一些非常全面的(Windows)恢复功能。(Windows 7)具体来说，您可以使用系统(System Restore)还原来回滚最近所做的重大更改。
这些可以是Windows更新、驱动程序安装或新软件包。如果您的内存错误在发生足以保证系统还原点的大事之后开始弹出，那么回到该点之前查看问题是否解决不会有什么坏处。
在Windows 10中，您可以通过执行以下操作将计算机恢复到较早的位置：
- 首先，在开始菜单中 搜索恢复。(Recovery )
- 单击恢复。(Recovery. )然后单击打开系统还原(Open System Restore)。
如果在您怀疑导致错误的更改之前创建了任何还原点，您可以在此处选择它们，然后按照Windows本身的说明完成还原过程。
如果事情真的很糟糕，您应该考虑重置 Windows以将其恢复到原始状态。
驱逐软件罪魁祸首(Evict a Software Culprit)
如果没有合适的还原点并且您有理由怀疑最近安装或更新的程序是导致内存错误的原因，那么只需使用“添加或删除程序(Add or Remove Programs)”功能将其卸载即可。您可以在“控制面板(Control Panel)”中找到它，或者只需在“开始”菜单(Start Menu)中搜索即可。
检查系统文件损坏(Check For System File Corruption)
如果一个更常见的解决方案没有消除内存错误，您可以使用一组特殊命令检查系统文件是否损坏。
您需要从命令提示符运行(Command Prompt)系统文件检查器(System File Checker)。如果您以前从未使用过基于文本的Windows(Windows)界面，这听起来可能令人生畏，但如果您遵循这个简单的指南(this simple guide)，那么修复过程就是轻而易举的事。其实，时不时用checker来抢先解决各种问题是一个好习惯。
使用 Cleaner Utilities 删除剩余的软件垃圾(Use Cleaner Utilities to Remove Leftover Software Junk)
在完美世界中，您删除、升级或更新的软件应自行清理。有许多实用程序专门用于删除标准卸载程序失败的这种杂物。
例如，DDU是一种流行的实用程序，可以清除系统中的GPU驱动程序。当任何与图形相关的东西引起问题时，它很有用。Java也是一个普通的来宾，它不会以它找到它的方式离开您的计算机。以至于有一个官方的 Java 删除指南(official Java removal guide)。
在使用任何类型的清理实用程序之前，请务必使用VirusTotal等服务扫描软件中的恶意软件，并阅读一些第三方评论以确保其合法有效。
更新一切(Update Everything)
有时内存错误（以及任何其他错误）可能是更新不匹配的结果。您的Windows安装可能会自动更新，但如果您的软件包和硬件驱动程序尚未更新以匹配新的代码库，则可能会导致不稳定。
首先，您需要仔细检查是否已安装Windows 更新。(Windows updates)接下来，您将要检查显示错误的程序是否也已更新。您还需要下载显卡和主板等硬件的最新驱动程序。
检查您的硬件健康状况(Check Your Hardware Health)
如果基于软件的解决方案似乎不起作用，则内存错误可能有更严重的原因。虽然没有人想听到他们的计算机硬件本身可能出现问题，但您必须消除这种可能性。
毫不奇怪，第一个嫌疑人是您的 RAM 本身。系统地检查您的 RAM 是否存在问题需要时间，但任何人都可以做到。请参阅此出色(excellent guide)的内存检查指南。
即使您已经运行了上面讨论的系统文件检查器，您也可能希望使用CHKDSK检查硬盘驱动器的物理运行状况，以防万一出现坏扇区或其他物理问题。
向客户支持提出投诉(File a Complaint With Customer Support)
当“无法读取引用内存的指令”错误显然是软件有问题的结果时，可能只有一个可行的行动方案——联系开发人员。
错误(Bugs)发生，如果游戏或软件包不断因此错误而崩溃，那么您可能无能为力。因此，向客户支持部门发送电子邮件，访问官方论坛并获得一些建议，以了解您是否遗漏了一些明显的东西，或者它是否真的是Matrix中的一个小故障。
阅读此常见错误(Getting a Read On This Common Error)
这是一长串修复程序，但没有理由让这个内存读取错误破坏您的工作或娱乐。
保持冷静的头脑，从你的清单中越过不可能的事情，很快你就会恢复正常。
Fix “Instruction at Referenced Memory Could Not Be Read” Errors
It’s rare thеse days, but somеtіmes you can still run into a crуptic error message while using your computеr. Cryptic errors are ones that don’t really explain themselves.
If you are lucky, you’ll get an error reference number you can look up, but in the case of the “Instruction at Referenced Memory Could Not Be Read” error, you have no such luck.
This particular error can strike at any time, often without any clear cause. So if you’re happily doing your thing on a PC and suddenly experience a software crash along with this error, this guide will set you on the path to recovery.
What Is This Error Exactly?
The actual text of the error is pretty self-explanatory. Information in RAM is stored at a specific address. When the software in question needs information stored at a particular address, it asks for it. Sometimes, for whatever reason, this process goes wrong. This error tells us that the address is invalid for some reason.
What Causes The Error?
Now we get to the real problem. Although we know that an invalid memory address is involved, we have no idea why the memory address was invalid.
This is one of the reasons this particular error causes so much grief. It could be hardware, software or the phase of the moon. The good news is that, with a bit of deduction and logic, tracking down the gremlin responsible for your memory error woes is possible.
Doing Some Detective Work
Before we look at the specific fixes that can address this error, you need to do a little preparation. After all, simply trying everything is more likely to cause new problems and won’t necessarily point you towards the true cause of the issue.
The most important thing you have to do is note when and how the error happens. Ask yourself these questions:
- Did it start happening after a hardware or software change?
- Does it only happen with one particular application?
- Does it happen regardless of what you are doing?
- Does it happen randomly, or at set intervals?
If you can gather some circumstantial evidence, it might provide a clue as to which fixes are more likely to work. If only one particular program gets this error, for example, then you are better off hitting up their technical support page than messing around with your own computer willy-nilly.
Keep the specifics of your error’s context in mind as we go over the various ways to make this error nothing but a distant memory.
The Most Sensible Fixes
Since there are so many possible reasons for an invalid memory address to cause a bit of mild havoc, it makes sense to round up the most sensible fixes. There are quite a few of them, so starting with the ones most likely to be related to your specific error is the way to go.
If you perform a fix that makes a change to your computer, remember to undo it if it didn’t take the problem away. If you don’t, then you’re introducing new variables that making eliminating possibilities harder. Be systematic!
The Easiest Fix: Ignore It!
This is by far the easiest way to fix the problem, but ignoring the error only works if the cause of the issue is not systematic. Computers and the software that makes them useful is very complicated. Sometimes things go wrong just once or very rarely.
So if you see this error once and never again, don’t fret about it. If you see it once every few weeks or months, it’s also probably not worth the effort of addressing.
If the memory error is disrupting mission-critical work or happens so often that it substantially hurts your user experience, then of course you should investigate other solutions. The point is not to freak out about what might be a very rare or perhaps even once-off bug.
More (Virtual) RAM Please
Virtual memory is a reserved part of your hard drive that acts as an overflow for when your physical RAM chips are full. Often when memory-hungry apps run out of RAM and have nowhere to put the additional information, it gets lost. When a program asks for its information back, it’s not there. Which leads to a crash or serious malfunction.
Memory management in modern operating systems is very good indeed and quality software products are also made to work efficiently with available RAM. So in most cases virtual memory is never even needed. However, programs with poor memory management or a too-small virtual memory allocation for your system can lead to memory errors.
You can add more physical RAM of course, but a quick (and free!) solution is to optimize your virtual memory paging file. Just follow this guide and your applications will have enough room to breathe.
Close Background Applications
Another angle from which to tackle the same problem is reducing the amount of memory-hungry applications.
Your internet browser is the biggest culprit here. Every tab you open up in a browser like Google Chrome eats up a big chunk of RAM. It’s pretty normal for someone to load up a game and leave the browser or office suite software open in the background. If you’re short on memory, closing some tabs or saving your work and closing your productivity apps can be a big help.
Perhaps you don’t have programs running in the background, at least not ones you know of. It’s a good idea to check how much of your computer’s memory is in use when it’s idle. Doing this could not be easier.
In Windows 10, 8 or 7 simply press CRTL+ALT+DEL and then click Task Manager.
If your Task Manager looks like this:
Then click More Details to expand it.
Now, under the Processes tab, click on the Memory column to arrange processes by memory use. Look for any processes that are using a large amount of memory. If they aren’t critical, you can end them by right-clicking on a process and selecting End Task.
Just be warned that if you don’t know what a process is, you should Google it first. If might be pretty important!
Turn Back Time
The last few versions of Windows, effectively back to Windows 7 in terms of which operating systems are still in use today, have some pretty comprehensive recovery features. Specifically you can use System Restore to roll back major changes that have been made recently.
These can be Windows updates, driver installations or new software packages. If your memory error started popping up after something big enough to warrant a system restore point happened, it can’t hurt to go back to before that point to see if the issue clears up.
In Windows 10 you can restore your computer to an earlier point by doing the following:
- First, search for Recovery in the Start Menu.
- Click on Recovery. Then click Open System Restore.
If any restore points were created before the changes you suspect have brought on the error, you can select them here and then follow the instructions from Windows itself to complete the restoration process.
If things are really dire, you should consider resetting Windows in order to restore it to a pristine state.
Evict a Software Culprit
If there is no restore point that’s appropriate and you have reason to suspect that a recently installed or updated program is the cause of your memory errors, then simply uninstall it using the Add or Remove Programs function. You’ll find it in the Control Panel or by simply searching for it in the Start Menu.
Check For System File Corruption
If the memory error isn’t being eliminated by one of the more common solutions, you can check your system files for corruption by using a set of special commands.
You need to run the System File Checker from the Command Prompt. That might sound intimidating if you’ve never worked with the text-based Windows interface before, but if you follow this simple guide getting that repair process going is a doddle. In fact, it’s a good habit to use the checker from time to time to preempt a variety of problems.
Use Cleaner Utilities to Remove Leftover Software Junk
In a perfect world software you remove, upgrade or update should clean up after itself. There are many utilities out there that specialize in removing this crud where the standard uninstallers fail.
For example, DDU is a popular utility that scrubs your system clean of GPU drivers. It’s useful when anything graphics-related is causing issues. Java is also a common guest that just won’t leave your computer the way it found it. So much so that there’s an official Java removal guide.
Before you use any sort of cleanup utility, be sure to scan the software for malware with a service like VirusTotal and read some third-party reviews to make sure it’s legitimate and effective.
Update Everything
Sometimes memory errors (and any other error really) can be the result of update mismatches. Your Windows installation might have updates automatically, but if your software packages and hardware drivers have not been updated to match the new codebase, it may be a recipe for instability.
First, you’ll want to double check that Windows updates have been installed. Next you’ll want to check that the program exhibiting the error has also been updated. You’ll also want to download the latest drivers for hardware like your graphics card and motherboard.
Check Your Hardware Health
If software-based solutions don’t seem to be doing the trick, the memory error might have a more serious cause. While no one wants to hear that their computer hardware itself might be on the fritz, it’s a possibility that you will have to eliminate.
Unsurprisingly, suspect number one is your RAM itself. Systematically checking your RAM for problems takes time, but anyone can do it. See this excellent guide to checking for bad memory.
Even if you’ve run the system file checker discussed above, you may want to check the physical health of your hard drive with CHKDSK just in case there are bad sectors or other physical issues with it.
File a Complaint With Customer Support
When a “instruction at referenced memory could not be read” error is clearly the result of a buggy piece of software, there may be only one course of action that will work – contacting the developers.
Bugs happen and if the game or software package is constantly crashing with this error, it might not be something that you can do anything about. So pop an email to customer support, hit up the official forums and get some advice on whether you’re missing something obvious or if it really is a glitch in the Matrix.
Getting a Read On This Common Error
That was a long list of fixes, but there’s no reason to let this memory read error derail your work or play.
Keep a cool head, cross the impossibilities from your list and soon you should be back to normalcy.
