Application error, The instruction at * referenced memory at *. The memory could not be read.
5 replies, posted
So, this happened about the same time I installed AMD drivers but I uninstalled the drivers to trouble shoot and I get this error. Unsure if coincidence or if it fucked something up big time because I had to hard reset the computer, but SFC and chk disk and scanning memory for problems and using msconfig yields no results. The memory is clean. Removing page memory fails to help. I've searched far and wide for a solution and I come to you all for help.
Basically, when I start up the computer, werfault.exe returns an application error. The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
Then it says that rundll32.exe has this error. The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
Then it says that RazerOverlay.exe has hit this error. The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
basically, I get hit with this error a bunch of times. Werfault.exe usually is showing up every other time. I disabled it but it still produces errors(?)
I can't even install fucking 3DS max which is why I'm so mad. The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
I can't uninstall a lot of programs. The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
Its the same fucking error. Every time. The same instruction. The same memory.
The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
The instruction at 0x00000000680B68B6 referenced memory at 0x0000000000000214. The memory could not be read.
Any of you guys know what to do? I searched this exact error up online and google literally returned ZERO results.
[editline]21st December 2016[/editline]
It should be noted that I believe it to be application side because 3DS installer runs if I rush to chrome and start it up before the first onslaught of errors happen. But because it takes longer to install than it takes for the errors to pop up I don't get anything installed. I have no idea where to start and I would appriciate help. Thank you in advance.
Have you done any of the normal troubleshooting steps?
- Perform a full virus scan in safe mode
- run: sfc /scannow
[QUOTE=Richard Simmons;51561139]Have you done any of the normal troubleshooting steps?
- Perform a full virus scan in safe mode
- run: sfc /scannow[/QUOTE]
Already done, check the details.
I did the obligatory google search and solutions. I did all the common sense stuff.
[editline]21st December 2016[/editline]
Most at least
I feel like my wording is coming off as dickish or demanding I apologize, that is not the case.
Hopefully I'm not too late on this. I'll assume this is not GPU drivers related but more of a timing coincidence.
If multiple applications break, my first guess would be corrupt memory.
What I would try is get something like Hiren's boot CD (it's free though it's kinda grey legally). There you have a bunch of diagnostic tools, the most important being:
- Memtest 86+ (you can also get it standalone)
- Mini Windows XP
Memtest will test your ram. If it runs and red appears on your screen, you've more or less found the culprit. Just in case you can try reseating the ram to see if that helps.
If Memtest doesn't do anything, you can run Mini XP to see if the OS boots normally. If it does, the next thing I would check is the hard drive. Usually I run Victoria and then just run a test to sequentially read the whole drive. If there's sectors that don't respond, you might have a bad part of the drive, though honestly that's a lot less likely.
If neither of those do anything, my next guess would be some form of spyware or corrupt Windows installation. I'd run something like Kaspersky's Tdsskiller and if that doesn't yield anything, perhaps ComboFix (disclaimer: may brick your installation).
Going back to the GPU drivers being a possible culprit, I would try running the computer with the GPU removed or disabled in BIOS (assuming you have an onboard GPU) and see what happens then.
This will be either malware, a broken antivirus or similar aggressive hooking application, or a botched windows update. Graphics drivers tend to contain modules that are loaded into every process, so a broken driver install/uninstall could feasibly cause it
Best bet is system restore. If you can't, you'll have to pick at the registry from safe mode to try and stop it attempting to load whatever is crashing everything
[QUOTE=Darkimmortal;51591530]This will be either malware, a broken antivirus or similar aggressive hooking application, or a botched windows update. Graphics drivers tend to contain modules that are loaded into every process, so a broken driver install/uninstall could feasibly cause it
Best bet is system restore. If you can't, you'll have to pick at the registry from safe mode to try and stop it attempting to load whatever is crashing everything[/QUOTE]
Honestly, I think it would be very ill advised to have someone 'pick at registry' if they don't know what theyre doing. Its just a pretty good way of botching windows all together. In fact, picking at the registry would be just time consuming waste of time especially if you're just looking for something that is booting up with windows on bootup or login.
I would recommend yet another useful tool from sysinternals, [URL="https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx"]Autoruns[/URL]. Again, if you don't know what you're doing you can still screw up windows.
[editline]28th December 2016[/editline]
Besides using a restore point, or troubleshooting this using various means. THe easiest solution would to be backing up what data you can and reinstalling windows.
Sorry, you need to Log In to post a reply to this thread.