• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

A whole night's worth of work wasted, i hate windows so much....

A

Azndude51

Platinum Member
I spent all night reinstalling windows, installing all my programs, drivers, games, changing the settings, etc. After the last installation I had to restart and guess what? I get the BSOD before windows XP pro can completely load.

It says, "STOP: c0000135 {Unable to locate component} This application failed to start because msvcrt.dll was not found. Re-installing the application may fix the problem."

I tried safe mode and that doesn't work either, I don't know what to do. I've tried looking up info about msvcrt.dll but the stuff I found doesn't really help. I guess I'm going to have to try reinstalling again tonight unless you guys can help me get it working.



EDIT: Thanks for the help so far, here is my updated problem. I have 3 HDs, one is IDE and the other two are SATA (160GB and 250). I booted from the Windows install disk and told Windows to format and install on the 160GB. After it formatted and copied the installation files, the PC restarts, but I get get an error message like the one found here. Using method two, I am able to load windows and complete the rest of the installation. When I finally got into Windows, I found the problem, Windows was installed in the correct hard drive, but that drive has the letter E. All the system files are on the E drive and my two other hard drives are listed as C and D, they have non system files on them like music and movies that were there on my previous insatllation

EDIT2: I reinstalled again with only 1 DVD drive and my main HD plugged in, I got the correct drive letter this time. However, when I went to install the nforce drivers, my computer crashed and I was unable to start windows again. I finally reinstalled for a final time and installed older nforce drivers instead with no problems. Everything works fine now.
 
Msvcrt.dll is just the Visual C++ runtime library. You can download the latest version from a number of places on the web. Strange that it caused a BSOD.
 
Msvcrt.dll is just the Visual C++ runtime library. You can download the latest version from a number of places on the web. Strange that it caused a BSOD.
Click to expand...

I would guess that a critical component like svchost.exe or something requires it.
 
Originally posted by: Robor
Tried 'Last Known Good Configuration' and the Repair option?
Click to expand...

I've tried every option under the F8 menu. They all lead to either a system restart or BSOD after the Windows loading screen.


Originally posted by: NogginBoink
What was the last thing that you installed before the fatal reboot?
Click to expand...

Actually, I think it was a Windows Update, one of those that requires you to restart. :|

Originally posted by: ForumMaster
[L=download it from here. take you hdd and insert the file through a different computer. try and let's see.[/quote]

The problem is that I don't have any other computers around that have SATA. The only friends of mine that do have SATA on their mobos are still away at college, I got out for the summer earlier than they do.
Click to expand...
 
Originally posted by: Markbnj
Msvcrt.dll is just the Visual C++ runtime library. You can download the latest version from a number of places on the web. Strange that it caused a BSOD.
Click to expand...

Yeah, download it or copy it from a working XP box. Put it on floppy or CD and just boot to the repair console and replace the bad file. I have a feeling that if you do that you're going to get another file and another. Probably best to make sure your hardware is good and reload.
 
Do a search for BartPE.. Compile and burn it (or even throw it onto a memory stick) along with the needed files that windows is upset about.

In the future use Nlite to create an unattended install with all the updates, drivers, and your apps of choice.. Then when Windows pulls a hissy fit you won't waste too much time redoing everything to spec.

http://www.msfn.org/board/index.php?showtopic=28005

http://www.nliteos.com/download.html
The above is just a download link if you want to skip the guide.
 
Download and burn Kanotix. Its a linux livecd that has excellent hardware detection and the captive-ntfs driver (full write support, I've heard a 0% chance of anything bad happening) so you can go online, download the dll or whatever, and write the file to your windows folder in your hard drive.

Torrent Link if you're interested.
 
Before you guys replied, I already reinstalled again and ran into more problems 🙁 I ended up getting some drive path error and Windows wouldn't start at all, I didn't feel like trouble shooting, so I started the install again... The 3rd time went through w/out a hitch, then while installing my Nvidia nforce drivers (the most recent and compatible, I've use it before the first reinstall) my system restarted and I ended up getting nothing but a black screen after the BIOS loads all the hardware and stuff. Now I'm waiting for the 4th reinstall to complete... If I ever get my system running I will definitely do the unattended install thing. I've never had this much trouble trying to get windows to work and I've installed XP at least 10 times on various PCs, so I'm not that much of a nub.
 
Sounds like hardware problems.

My (not) favorite problem to look at first is to test the memory. Try memtest86. Use a boot cdrom or floppy an let it run for a few hours. The longer the better. (a stable computer should be able to easily go a week straight of running tests with no errors)

Otherwise likely problems are overheating (make sure that the heatsink is clean) PSU overheating/damaged, screwed up IDE cables and so on and so forth.

Could be what caused your problems you thought you had to reinstall to fix.
 
Originally posted by: drag
Sounds like hardware problems.
Click to expand...

Sure does

I learned the hard way YEARS ago that blue screens are not fixed with a format/reinstall.

It really seems like memory.

Good luck, but don't spend any more time thinking it's the O/S's fault.
 
I have experienced this before !!! I've ended up doing THREE important logical things..

1) go to BIOS and strip everything down to minimum ( all CACHE = OFF, DMA=OFF, etc)
2) use an old low-speed CDROM for installing winXP disc ( for some reason , low speed CDROM reads winXP cd more precisely although slower )
3) use minimal RAM during install process ( my guess is so winXP will avoid using 'cache from cd - to - ram' during install which is a problem if ur RAM is not 100% good)

and I would also do "system restore" at every third party software install or upgrade. Then if your PC refused to BOOT at any point, do use BART-PE or any LIVE-CD to bootup your machine.. BUT follow the BART-PE documentation on how to "restore" the previously saved "system restore". The documentation is very clear about :
1) how to delete the damaged last configuration files
2) how to copy the recently saved "system restore point" into the active directory

hope that helps !!
 
Originally posted by: drag
Sounds like hardware problems.

My (not) favorite problem to look at first is to test the memory. Try memtest86. Use a boot cdrom or floppy an let it run for a few hours. The longer the better. (a stable computer should be able to easily go a week straight of running tests with no errors)

Otherwise likely problems are overheating (make sure that the heatsink is clean) PSU overheating/damaged, screwed up IDE cables and so on and so forth.

Could be what caused your problems you thought you had to reinstall to fix.
Click to expand...

If I can't get it working by the time I go to bed, I'll do the memory test overnight. I don't think its the overheating, I already checked all my fans and have them all running full blast.



Originally posted by: logicmaster2003
I have experienced this before !!! I've ended up doing THREE important logical things..

1) go to BIOS and strip everything down to minimum ( all CACHE = OFF, DMA=OFF, etc)
2) use an old low-speed CDROM for installing winXP disc ( for some reason , low speed CDROM reads winXP cd more precisely although slower )
3) use minimal RAM during install process ( my guess is so winXP will avoid using 'cache from cd - to - ram' during install which is a problem if ur RAM is not 100% good)

and I would also do "system restore" at every third party software install or upgrade. Then if your PC refused to BOOT at any point, do use BART-PE or any LIVE-CD to bootup your machine.. BUT follow the BART-PE documentation on how to "restore" the previously saved "system restore". The documentation is very clear about :
1) how to delete the damaged last configuration files
2) how to copy the recently saved "system restore point" into the active directory

hope that helps !!
Click to expand...


I did the BIOS stuff you suggested, but I don't have an extra low speed CD-ROM handy. It would've been nice to know that I could've loaded a restore point w/out being in windows because I did have a restore point before almost every program/driver I installed. However, it's obviously too late for that now I will use have BART-PE ready if I ever get XP installed correctly.
 
If you don't like XP's drive letter allocation, the safest thing to do is to disconnect ALL the drives and memory card readers, install only your intended c: drive and your CD drive, and do the XP install. THEN add the additional drives.

After Windows XP has allocated drive letters for all those other "drives", THEN it will give a drive letter to your new System drive where you are intalling Windows XP. Hence the "E:" drive letter.
 
that is very true.. on what RebateMoner said above... thats in addition to what I suggested to run the install with everything in minimal mode. If yoour motherboard have a built-in VGA port.. its a PLUS to install winXP using that (with ur AGP or PCI-E card disconnected).. then after a successful install.. then u can do "system restore" before adding-in the rest of the cards one-by-one ( video card, extra harddrive, usb scanner / etc).
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top