How to resolve a persistant 'Icc runtime: GP fault. Stack trace' error message appearing


Please can someone help me resolve a persistant 'Icc runtime: GP fault. Stack trace' message box appearing containing the error message

'Corrupted Stack. Impossible to show trace'

This is a windows 2000 server operating system.
The problem seems to happen frequently and leaves a number of message boxes on the screen if left overnight.

Any Ideas?

regards

Stoopidis
StoopidisAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
StoopidisAuthor Commented:
If you feel the points offered on this question are too low please let me know and i will increase points
0
 
StoopidisAuthor Commented:
Is this one too hard?
0
 
Charmed_EmpressCommented:
We saw this error today in our of our laptops.  The problem is due to a malware called winspsv.exe that resides in c:\winnt\system32 folder.  Look into the Registry key called hkey_local_machine\software\microsoft\windows\currentversion\run and you shall see a key called Windows Services=C:\winnt\system32\winspsv.exe.  Delete it and restart your computer in Safe Mode.  Then delete winspsv.exe from the System32 folder. Restart the computer in normal mode and retest.  I have submitted the file to Symantec for investigation.

Thank you.
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

 
jamielochheadCommented:
Hi

I tried  a simpler alternative, which seemed to work. This is simply following the above method but applying it in a different way.

1. Seach (start menu: search for files and folders) the C: drive for winspsv.exe.
2. Rename from winspsv.exe. to winspsv1.exe.
3. Reastart the machine.

This seems to have worked, but I don't guarantee it as such a solid solution as the one above, but it is easy to try and run within Windows, and after seeing many hoax virus/solutions, I am a little wary of deleting files.

Regards

Jamie Lochhead

I hope this os of help. Any further comments on this, I am sure will be useful
0
 
Charmed_EmpressCommented:
Thanks for the information. Symantec responded to me and informed me that the file is viral and it is W32.Randex.  The latest virus definition file from Norton should detect it.

Below is the information from Symantec sent to me:

We have analyzed your submission.  The following is a report of our findings for each file you have submitted:

filename: A:\winspsv.exe
machine:
result: This file is infected with W32.Randex

Developer notes:
A:\winspsv.exe is non-repairable threat.  NAV with the latest beta definition detects this.  Please delete this file and replace it if neccessary.  Please follow the instruction at the end of this email message to install the latest beta definitions.

SDGS build passed #26268 Hiroshi Shinotsuka

0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
 
StoopidisAuthor Commented:
Thanks for your comments on this......It was a bit late to help me but i didn't know how to cancel the question....plus your answer was spot on so what the hey

Stoopidis
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.