Grrr... VS Debug Error window won't go away...

[Thothie]

Well, ever since I installed three seperate versions of Visual Studio, in a desperate effort to compile MSC, I keep getting this new error window from various programs:


Not just the HLDS - but all sorts of proggies bring this up every now and again. What's worse, is the program it's complaining about keeps running just fine - suggesting nothing fatal is wrong. But if I leave the puter alone, the error windows add up and cause problems themselves. Clicking either button terminates the program and does nothing else.

I've uninstalled all versions of Visual Studio save for VS2003, required to code MSC. I've also stripped it down to next to nothing, and I still get this buggar.

...any idea what this belongs to and how to get rid of it? It seems to have integrated into a system DLL someplace, as it doesn't launch any proggies I don't recognize when it generates this erroneous error.

 

[The Man In Black]

Hmm. Have you tried searching the intern0rt? I looked around and could only find application specific instances of that error (Internet explorer, Everquest), but some of the things may be useful.

 

[Thothie]

Yes, believe it or not, I have searched the internets - this has been going on for a few weeks. Ya know I'm down to grasping at straws when I ask here.

 

[Tao]

Hmm, did you upgrade your ram?
I got this message all the time when I added another damaged ram stick.

 

[Kokris666]

I hate that damn bug >:O

 

[Thothie]

Hmm, did you upgrade your ram?
I got this message all the time when I added another damaged ram stick.

Well, replacing my RAM would be easier than reinstalling Windows - but not cheaper. I'll have to go DL memstat or somesuch and run a test...

...This system is so damned customized it takes me like 6 months to get it back up to par after a Windows reinstall, so I'd almost rather that be it...

Meh, never even saw this error until I installed the VS suites - and I think it *used* to activate the VS C++ remote debugger when I clicked cancel, but since I uninstalled VS6 and VS2005 at the same time - I dunno which one it belonged to.

 

[Gaz]

I got that alot when I had VS installed, if you still have one version installed, I expect theres an option in there to turn this off.

 

[Blasto121]

get this CCleaner

run the registry cleaner part if that doesn't work...

Get this! Ultimate Boot Disk

this will allow you to test your ram and other things.

 

[Thothie]

Well, actually, I finally got the chance to run Memtest86 on her, and yup, there is one tiny bad address in the memory. Still, I've never gotten this error before VS - and the debugger is (or was) a VS proggie. Meh, seriously time to upgrade anyways. I need to figure which DIMM is the problem child though, as I was planning to hand this mobo, cpu, and memory off to a friend who doesn't game (figure 512MB will suite her fine).

I got a lot of boot disks and registry cleaners... I'll see about maybe uninstalling VS 2003, and running all the cleaners again after the new year. I won't have the cash to upgrade until a bit after that.