Unknown Application error?

Shampoo

Shampoo

Shampoo

Associate
Joined
28 Apr 2009
Posts
785
This has been popping up a few times on a mate's PCand I don't know what it's about?

The instruction at 0x73c2e5a8 referenced memory at 0x00000000. The memory could not be read.

2vtwnfb.png
 
Start - msconfig - 'Startup' tab. Uncheck all non essential programs. Reboot. If the error doesn't come back then re-enable each in turn until you find the rogue program.

Also, update all drivers just to be on the safe side
 
Seems to be linked to csrss.exe in the task manager. Why would that be trying to update and then failing? Already ran the necessary checks to rule out it being a fake/trojan/virus etc so I'm a bit stumped by this behaviour.
 
I had an issue like this on my brothers PC, it would try to continue an update that had an error, found a entry in task manager for the software it was trying to update so it would continue on startup, removed that and killed the process and it stopped popping up.
 
Just a quick google comes up with this. - csrss.exe is a process which is registered as a Trojan. This Trojan allows attackers to access your computer from remote locations, steal passwords, Internet banking and personal data.
Try putting the windows disk in and restoring.
 
I've already been through that potential scenario. The only instance of that process is in the system32 folder where it should be and all scans are clean. It's not that. It's a legit windows process I've already scoped it out.
 
Shampoo said:
I've already been through that potential scenario. The only instance of that process is in the system32 folder where it should be and all scans are clean. It's not that. It's a legit windows process I've already scoped it out.
Click to expand...

Alright mate, I was only saying what google said. Try a system restore, normally fixes stuff like that.
 
Just found this - csrss.exe is the name of a critical system process but it is also the name of malware. Which it is depends on where it is found. The legitimate location will be in system32, elsewhere it is probably malware. It could well be an infection that isn't being picked up.
 
You must log in or register to reply here.
Back
Top Bottom