• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

stupid annoying error

Red Squirrel

Red Squirrel

No Lifer
I randomly get this annoying error (usually when I'm shutting down but not always)

stupid_error.jpg


It's usually for asus probe, but sometimes explorer, or another app. The last system I got this on ended up self destructing itself so I'm very scared the same thing will happen to this system.

The ram is fine, I memtested a bunch of times. Even the system that self destructed itself - the ram was fine.

so wtf is this error about anyway? and why is the word read in quotes, it just makes it look more stupid because it's so badly written. This error really pisses me off. it's worse then the illegal operation back in the win98 days.


Oh and I seem to get this error more often when I'm using VMware.
 
Looks like poorly written software to me. I used to use AsusProbe and it would crap out every now and then with similar errors. And the message isn't poorly written, it's just produced at a very low level.

Out of curiousity, what happens when you click 'cancel'? Do you have a development environment with a debugger installed? Back when I used to work with Delphi, it would let me step in and debug stuff that had pointers go awry. I don't remember, but it might also have been set up to handle this in other programs as well.
 
Have you scanned the system for spyware & viruses ?

I use the ASUS PC Probe program all the time & it works perfectly.
 
High security around here no spyware or any such crap. I'm a tech and own my own company so this has me stumped. I know it's not the software because it did not do it before, and the error always happends on random software. And it scares me since my last system that started acting weird would BSOD then reboot and the C drive would be gone, and I built this new system because I did not have time to start troubleshooting a weird issue like that on my main machine, and now it's haunting me again.

And wether I click ok or cancel does not do anything, it just closes.
 
so wtf is this error about anyway? and why is the word read in quotes, it just makes it look more stupid because it's so badly written. This error really pisses me off. it's worse then the illegal operation back in the win98 days.
Click to expand...
It says that the instruction at 0x0040329c dereferenced a pointer (tried to read a value from memory, in this case) but the pointer was invalid (it pointed to location 0x0000002 - that's below the application's memory space). No idea why "read" is in quotes - it's Microsoft's fault 😉. Without debug symbols, you're highly unlikely to be able to glean any useful information from the message. If you had symbols and source, you could at least see what function was crashing and what it was trying to do. It could be caused by all sorts of things - from bad hardware to an unexpected option in the program's config file... there's not really any way to tell.
 
hmm and by bad hardware is this limited pretty much to ram? Since it is memory related after all. I did a few memtests overnight over the past few weeks and they returned clean. (in most cases if there's errors they'll show up within the hour, sometimes instantly)

I was thinking cooling, but my CPU (athlon 64) is at 32 and mobo at 26, and it goes even lower when all the fans are on.

One thing I forgot to mention I have dual channel memory (two 512 sticks in the proper slots) and I've heard people getting stability issues with dual channel but figured it was BS since dual channel should actually make it faster. So could it in fact be true that it causes issues?
 
hmm and by bad hardware is this limited pretty much to ram? Since it is memory related after all.
Click to expand...
No, it's not necessarily memory-related. I'd be very surprised if bad ram or hardware memory-related issues would cause it to crash at exactly the same place every time though.
 
Originally posted by: RedSquirrel
hmm and by bad hardware is this limited pretty much to ram? Since it is memory related after all. I did a few memtests overnight over the past few weeks and they returned clean. (in most cases if there's errors they'll show up within the hour, sometimes instantly)

One thing I forgot to mention I have dual channel memory (two 512 sticks in the proper slots) and I've heard people getting stability issues with dual channel but figured it was BS since dual channel should actually make it faster. So could it in fact be true that it causes issues?
Click to expand...

If running dual channel was an issue, it would of probably shown up in memtest.

The next step I would take is to run a chkdsk on your drive.

from cmd promt......chkdsk /r

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top