Share via

Microsoft Visual C++ Debug Library Error

Anonymous
2010-06-26T20:14:51+00:00

I have had my computer for several years and am low on hard drive space, however; I just received, for the first time, an error "Microsoft Visual C++ Debug Library debug error". The file is a System32 file and in the explanation it indicates "Run-time check failure #2 - stack around the variable 'Cache Manager' was corupt".

I have read other posts and nothing quite fits what I'm dealing with. Does anyone know where this came from and how do I get it fixed?

Windows for home | Previous Windows versions | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

7 answers

Sort by: Most helpful
  1. Anonymous
    2010-06-27T14:03:41+00:00

    First make space on your hard drive. Windows will not work correctly and will throw all sorts of errors and get file system corruption if your hard drive is too full. Get a USB external hard drive and copy all your data files to it - music, pictures, videos. Then delete the files from your internal hard drive. Next uninstall any unused/unneeded programs from Add/Remove Programs. Of course you should also make sure that the computer is virus/malware-free and do maintenance on it. Once you have put the drive back into shape by doing the foregoing, post back with the results.

    http://www.elephantboycomputers.com/page2.html#Backing\_Up

    http://www.elephantboycomputers.com/page2.html#Maintenance

    http://www.elephantboycomputers.com/page2.html#Removing\_Malware


    MS-MVP - Elephant Boy Computers - Don't Panic!

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2010-10-03T05:54:38+00:00

    AWESOME!

    Pete, you are the man!  First time in four months I haven't had the Debug Library running!

    NSXgirl, if you try this, here are a few tips:  1) Write down the full program line from the Debug screen.  2) Create a restore point...just in case!  3) When you run "Autoruns", use the "Find" feature to locate your program.  4) Simply uncheck the box, exit, and restart.  My computer fired up with NO error messages!

    Oh, btw, the program that was causing all my trouble was installed on June 24th, the same day I dowloaded and installed some Windows updates.  Now I'm positive the updates and the error were related.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2010-10-03T03:17:25+00:00

    Go tohttp://technet.microsoft.com/en-us/sysinternals/bb963902.aspx and run Autoruns and click on the Everything Tab.  Look for the system 32 file in question and when you find it uncheck the box to stop it from starting at startup.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2010-06-29T07:42:10+00:00

    Same thing happened to me. Calling support to tell them to have me restore is not an option. Hope someone comes up with a solution. I would think these updates would be tested before they are rolled out.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2010-06-27T16:35:17+00:00

    Did you just install two .NET updates? KB982524? I'm getting the same error message, which I've never seen before, after the updates were downloaded and installed by Automatic Update. They installed on my computer on 06/24, and despite attempts to uninstall them, are still causing the same error messages. And I have over 70% of my HDD space free, so it's not a matter of a congested drive.

    Do the error messages start as soon as the desktop starts to load? Let me know if you fnd something that works. Oh, btw, I tried System Restore and took it back over a week and it still throws the same errors. Damn updates!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments