Help Corrupt Registry, Computer Crashes
Well my computer keeps crashing and it says mcd42.dll is missing and the "blue screen of death" appears when running certain apps. I went to use the free registry fixers but all it does is delete stuff, half of them dont work case it says missing mfc42.dll, and i have to buy them. Is there a manual way to fix the registry?
0
Comments
I searched for this file on my computer and it shows up as being used by quite a few programs and has copies in various places around the HD. Which program(s) are causing the BSOD?
Good luck.
I found this file to be a part of all of the following programs on my computer, sometimes showing a different version of the file and different file size:
Logitech Mouseware
MediaFace II (CD label app)
Nero
3DMark2001 SE
Super Video Joiner
I also found a reference to problems being caused by the Xupiter spyware program. A trip over to the Spyware/Virus/Trojan Discussion Forum might be worthwhile.
If I were in your shoes I would probably try reinstalling any program which gave me an error message regarding that file. Failing that, I'd likely try a Windows Repair Install. Neither of those options would be a large amount of fun, but might end up being easier in the long run than trying to fix things piecemeal.
Trogan's suggestion to run Memtest is a good one, too.
As for IE running, you can be chock full of spyware and still have that. Also, what device were you referring to when you said "i think i did install something device related"? A borked driver might be causing the problem.
Can you post the error you're getting on the BSOD?
NVTcp.sys - adress AADF3582 base at AAD62000, DataStrip 4253b85b *b's may be D's
Google documents numerous problems such as this. You may want to try an updated driver, or try a somewhat older version if you have the latest one now.
Read post #6 and after in this thread at [H]ard|Forum. The suggested fix was a rollback to an earlier set of drivers.
Your chipset drivers are another hardware item which figure prominently in everything you do. As for only recently starting, see if one of the .dll files you mentioned is included in the driver package. If it got corrupted it would explain all of your troubles.
A word of caution: Be sure you know what you're doing, a complete chipset driver removal is not for the meek. If you can ghost your boot partition to another drive it would be highly advisable to do so.
I bet if we took a poll to see how many people had a problem and traced it to a suddenly malfunctioning driver which had worked just fine for ages we would end up with quite a long list. If you have everything backed up, what have you got to lose by trying it?
Was it the same message on the most recent BSOD?
Good luck!