What is ini file error: app path data fail? my laptop wont start
The laptop wont start and when it starts, it some times freezes and turns off, it may also let off one long beep and two short ones before it starts then i get the ini file error:app path data fail, and it does nothing
An expert who has achieved level 2 by getting 100 points
An expert that got 5 achievements.
An expert whose answer got voted for 20 times.
An expert who has answered 20 questions.
Re: what is ini file error: app path data fail? my laptop...
REstart your computer and keep pressing F8 till you get the option to boot in safe mode. IF this works then it means a driver or some piece of hardware you added is conflicting. If it still wont boot i would think bad RAM.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Service fails to start. When trying to start a service using the Services Management Console (services.msc) an error is displayed:
Could not start the <Service Name> on the local computer
Error 193: 0xc1
All supported products and operating systems.
Check all the folders that are in the path to the executable and make sure there are no files with the same name as the first word in the folder name.
A file called "program" in your systemdrive (c:)
A file called "GFI" in your "Program Files" folder
File called "EventsManager" in your GFI folder.
When the Microsoft Service Control Manager launches a service it checks the path to the executable. If there are any files with the same name in the directory as the the first word in the directory name, it will fail with the above error.
System registry corruption leads to runtime errors and your computer crashes.Windows Registry is very complex and not easy to repair manually. Hence, athird-party Registry Cleaner and PC Optimizer software is recommended.
1. Download a Registry Cleaner and PC Optimizer software such as Reginout. 2. Click Registry Cleaner tab. 3. Click Start Scan. 4. The registry scan will start. Wait till it is finished. 5. As per the results, click Fix Now button to start repairing you registry.
Often good registry cleaners include built-in Backup & Restore centre thatlets you recover from an unforeseen situation by simply restoring the state ofyour registry.
Your computer freezes due to problemswith the computer memory. A faulty RAM may result in Blue Screen of Death(BSOD).
In such a case, remove the existing RAM and clean it using a soft cloth. Then,connect it again. The problem may not persist..
Your computer freezes because of a previously failed or incompleteinstallation. An incomplete or failed installation creates junk registryentries and thereby system crashing problem.
Repair the registry entries created by a failed setup and delete the files thatstill remain on your hard disk. Delete the contents of C:\Windows\Temp folder.
Disk Space Allocated by Unnecessary Files
Your computer freezes if the operating system has no adequate free disk spaceto perform its operations. Temporary files, temporary internet files, logfiles, browser cache and other files may occupy a large amount of your diskspace and thus generating runtime errors that crashes your system.
Using Disk Cleaner, delete the junk files from your hard disk. The steps are asbelow:
1. Click Start ' All Programs ' Accessories ' System Tools ' Disk CleanUp. 2. Follow the instructions on your screen.
Restart the PC. The hal.dll error could be a fluke.
Check for proper boot order in BIOS. You might see the hal.dll error if the boot order in BIOS is first looking at a hard drive other than your main hard drive.
Note: If you've recently changed your boot order or recently flashed your BIOS, this may be what's causing your problem.
Run Windows XP System Restore from a command prompt. If this doesn't work or you're receiving the hal.dll error message before you're able to complete this process, move on to the next step.
Repair or replace the boot.ini file. This will work if the cause of the problem is actually Windows XP's boot.ini file and not the hal.dll file, which is often times the case.
Note: If repairing the boot.ini does correct the hal.dll issue but the problem reappears after a reboot and you've recently installed Internet Explorer 8 in Windows XP, uninstall IE8. In this specific situation, IE8 could be the root cause of your hal.dll problem.
Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the hal.dll error.
Recover data from any bad sectors on your hard drive. If the physical part of your hard drive that stores any part of the hal.dll file has been damaged, you're likely to see errors like this.
Restore the hal.dll file from the Windows XP CD. If the hal.dll file is truly the cause of the problem, restoring it from the original Windows XP CD may do the trick.
Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.
Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch.
Note: While this will almost certainly resolve any hal.dll errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.
I have looked all around and no one has tried the fix that I have just tried. If your laptop freezes until it's moved slightly or you have to apply pressure around the touchpad / memory area it is neither those parts that are causing the problem. The real problem lies beneath. The problem is the southbridge intel chip. I fix Xbox 360's so I know a lot about cold solder points and it seams that HP placed the chip in an unstable area. The southbridge chip over time gets cooked under the plastic and sooner or later has cold solder joints which means it can constantly connect and disconnect its cold solder point. Every time it disconnects your laptop freezes because the flow has just stoped. The answer is to do two things. First you must find some sort of heat obsorbing pad, I had a thermal pad around which I used to fix an Xbox so I used that. I opened the laptop to the point that I could see the chip (make sure you know what your doing when opening your laptop!!!!). Then I just placed the thermal pad on top of it and closed the laptop. The other thing you should do which I can't since I do not have it, but you should use a heat gun in order to reflow the solder between the southbridge chip and the motherboard. The pads may not work entirely because they can sometimes only apply pressure and wont fully recconect the cold solder points below the chip. My laptop is working fine right now with only a couple freeze ups since it is in my lap and I have just applied the fix not to long ago but it would never work in this position before and leads me to the conclusion that it must be the chip. I did not use the heatgun method but if and when I do buy a heatgun I will definitely do so to prevent the very few freezes I still recieve. I hope this helps.
Problems with MMC is usually it is not working correctly or not working at all. Most of the time is has been caused by a corrupt MMC configuration file. All you have to do to fix this is delete or rename the old configuration file and the MMC will create a new one automatically.
The MMC configuration file is located in your Application Data folder and is associated with each User—not each computer.
An example of the path to the config files:
C:\Documents and Settings\"User"\Application Data\Microsoft\MCC (local App Data)
Check your floppy and optical (CD/DVD) drives for media. Often
times, the "NTLDR is Missing" error will appear if your PC is trying to
boot to a non-bootable floppy disk or CD/DVD.
Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive is listed first.
Check the hard drive and other drive settings in BIOS and
ensure they are correct. The BIOS configuration tells the computer how
to use a drive so incorrect settings can cause problems, including
NTLDR errors. There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.
Open your computer's case and ensure that the cable that connects the hard drive to the motherboard
is firmly in place. If this does not resolve the issue, try replacing
the cable. NTLDR error messages could be caused by loose or
malfunctioning IDE cables.
Update your motherboard's BIOS. Occasionally, an outdated BIOS version can cause the "NTLDR is Missing" error.
Perform a clean installation of Windows XP.
This type of installation will completely remove Windows XP from your
PC and install it again from scratch. While this will almost certainly
resolve any NTLDR errors, it is a time consuming process due to the
fact that all of your data must be backed up and then later restored.
If you can't gain access to your files to back them up, understand that
you will lose them all if you continue with a clean installation of
Finally, if all else has failed, including the clean
installation from the last step, you're most likely facing a hardware
issue with your hard drive. Replace the hard drive and then perform a new installation of Windows XP.
You have to rebuild the boot.ini file. That is going to require a disk and do a repair install. Or the MBR (Master boot record) is corrupt. Software like Paragon partition manage can check your MRB and see is it is pointing to the correct boot.ini file path.