VC++ 6.0 Crash on Compile
by Chris "Dark" Evans · in Technical Issues · 03/18/2003 (3:15 pm) · 7 replies
Hey guys, this is a new problem for me. I'm not a newb or anything. About a month ago I started getting random BSoD's (Blue Screen of Death) in Windows XP. I though, "what the hell?" I figured it was my hard drive, so I went and bought another one, but I'm cheap and decided to run through again and check EVERYTHING so I could hopefully return the new drive I just bought. I finally figured out that it was my cooling system, my processor was getting up to around 180 degrees F, then it'd crash.
Anyway, during this time I couldn't compile. Obviously it was too much and would heat up my CPU faster than normal. That's one of the things that lead me to believe it was my hard drive. It didn't crash while idling, or while surfing, only during compiling or some other high resource program. I thought it was writing to bad sectors when it compiled because I would get page file errors, and other errors.
I fixed it though, and everything else has worked fine since except VC++ still won't compile anything. I get an error (XP's version of an Illegal Operation). It says, "Microsoft Devepoper Studio has encountered a probleem and needs to close. We are sorry for the inconvenience." When I click details, I get this:
AppName: msdev.exe AppVer: 6.0.8168.2 ModName: mspdb60.dll
ModVer: 6.0.8168.0 Offset: 00012ea4
I figured, "Hmmm, that's odd. That file must be corrupt." So, I uninstalled and reinstalled my entire visual studio. I reinstalled SP5. I tried to compile again, but it gives me the same error!
So... I reinstalled windows XP w/SP1. I needed SP1 anyway. Then I tried compiling, same error. So again I uninstalled and made damn sure that file was gone so there was no chance of it lingering around and being corrupt. I reinstalled it, and of course, I still get the error.
The only thing I can think of doing now is formatting and starting from scratch. That's REALLY not what I want to do. I've got a 40 gig hard drive with around 15 gigs of stuff I'd need to back up (that's not including the 20 or so gigs of crap that I don't need).
If anyone has any advice to what's going on, and maybe how I could fix it, I'd REALLY appreciate it.
My Specs are:
AMD Athlon 1900+ 1.59GHZ
40 GB IBM Hard Drive
256 MB PC133 SDRAM
A NIC, a GeForce 2, and an SB Live
I've also got a DVD drive and a few other small hard drives in there.
Thanks for reading all that!
- Dark
Anyway, during this time I couldn't compile. Obviously it was too much and would heat up my CPU faster than normal. That's one of the things that lead me to believe it was my hard drive. It didn't crash while idling, or while surfing, only during compiling or some other high resource program. I thought it was writing to bad sectors when it compiled because I would get page file errors, and other errors.
I fixed it though, and everything else has worked fine since except VC++ still won't compile anything. I get an error (XP's version of an Illegal Operation). It says, "Microsoft Devepoper Studio has encountered a probleem and needs to close. We are sorry for the inconvenience." When I click details, I get this:
AppName: msdev.exe AppVer: 6.0.8168.2 ModName: mspdb60.dll
ModVer: 6.0.8168.0 Offset: 00012ea4
I figured, "Hmmm, that's odd. That file must be corrupt." So, I uninstalled and reinstalled my entire visual studio. I reinstalled SP5. I tried to compile again, but it gives me the same error!
So... I reinstalled windows XP w/SP1. I needed SP1 anyway. Then I tried compiling, same error. So again I uninstalled and made damn sure that file was gone so there was no chance of it lingering around and being corrupt. I reinstalled it, and of course, I still get the error.
The only thing I can think of doing now is formatting and starting from scratch. That's REALLY not what I want to do. I've got a 40 gig hard drive with around 15 gigs of stuff I'd need to back up (that's not including the 20 or so gigs of crap that I don't need).
If anyone has any advice to what's going on, and maybe how I could fix it, I'd REALLY appreciate it.
My Specs are:
AMD Athlon 1900+ 1.59GHZ
40 GB IBM Hard Drive
256 MB PC133 SDRAM
A NIC, a GeForce 2, and an SB Live
I've also got a DVD drive and a few other small hard drives in there.
Thanks for reading all that!
- Dark
#2
03/19/2003 (6:38 pm)
It doesn't matter what I try to compile, it could be a "hello world" app and it would still crash. It's got to be a corrupted file somewhere. Any ideas on how I'd find it?
#3
03/19/2003 (7:01 pm)
that's pretty odd.
#4
After trying to figure what was wrong (practically taking my computers in pieces and putting them back in), Changed the fans, power supply (Thought it was a power problem), but the problem still persisted.
However, I managed to solve the problem when I always reboot the computer on the first boot. Somehow the problem went away and my compter was stable. :-O
I don't know why, but it WORKS :P
Maybe you can try sometime like that...
03/19/2003 (8:13 pm)
I'm running nearly an identical configuration with your computer. Though I don't suffer from the blue screen you see - in the first boot, my computer always crashes after the first 5 minutes of using it.After trying to figure what was wrong (practically taking my computers in pieces and putting them back in), Changed the fans, power supply (Thought it was a power problem), but the problem still persisted.
However, I managed to solve the problem when I always reboot the computer on the first boot. Somehow the problem went away and my compter was stable. :-O
I don't know why, but it WORKS :P
Maybe you can try sometime like that...
#5
03/20/2003 (5:12 am)
The next step I would take is to stick a different memory DIMM in (borrow one if you have to...most high level geeks have a stick or two of PC133 they can spare). I find that the NT based OS's tend to be a great deal more sensitive to bad memory and it often looks like a HD failure.
#6
03/20/2003 (5:20 am)
I agree with Matt, sounds like a memory issue.
Torque Owner Jarrod Roberson
when the processor is overheating like that it can cause all kinds of things to get corrupted on writes to the disk.
also I assume you bought a bigger copper heat sink and fan right?