BSOD caused by driver hal.dll

Similar Questions

• Bluescreens and hal.dll

  I get frequent bluescreens for months.  Sometimes two or three a day.  Recently, I reformatted my computer and reinstalled Windows, which did not help in the slightest.  They occur at any time, is not serious if I am playing games or if the computer is sitting idle.

  System Specs:
  Windows Vista Home Premium 32-bit
  NVIDIA NForce 680i SLI
  NVIDIA GeForce 9800 GTX
  Intel Core 2 Quad Q6700 2.66 GHz
  4 GB OF RAM

  Below information gathered from the program BlueScreenView.  It's just the past three breaks down, because they are always the same.

  Thank you!

  DETAILS OF THE ACCIDENT

  ==================================================
  Dump file: Mini062210 - 01.dmp
  Crash time: 22/06/2010 10:27:17
  Bug Check String:
  Bug check code: 0 x 00000124
  Parameter 1: 0x00000000
  Parameter 2: 0x8956b020
  Parameter 3: 0xb2000040
  Parameter 4: 0 x 00000800
  Caused by the driver: hal.dll
  Caused by the address: hal.dll + 69dd
  Description of the file: Hardware Abstraction Layer DLL
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.0.6002.18005 (lh_sp2rtm.090410 - 1830)
  ==================================================

  ==================================================
  Dump file: Mini062010 - 01.dmp
  Crash time: 20/06/2010-18:49:14
  Bug Check String:
  Bug check code: 0 x 00000124
  Parameter 1: 0x00000000
  Parameter 2: 0x86e4a3f0
  Parameter 3: 0xb2000040
  Parameter 4: 0 x 00000800
  Caused by the driver: hal.dll
  Caused by the address: hal.dll + 69dd
  Description of the file: Hardware Abstraction Layer DLL
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.0.6002.18005 (lh_sp2rtm.090410 - 1830)
  ==================================================

  ==================================================
  Dump file: Mini061910 - 03.dmp
  Crash time: 19/06/2010 21:24:05
  Bug Check String:
  Bug check code: 0 x 00000124
  Parameter 1: 0x00000000
  Parameter 2: 0xaae3d3f0
  Parameter 3: 0xb2000040
  Parameter 4: 0 x 00000800
  Caused by the driver: hal.dll
  Caused by the address: hal.dll + 69dd
  Description of the file: Hardware Abstraction Layer DLL
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.0.6002.18005 (lh_sp2rtm.090410 - 1830)
  ==================================================

  MODULE OF THE PILOT/DETAILS:
  ==================================================
  File name: hal.dll
  Stack address: hal.dll + 69dd
  Address: 0x82bae000
  Address: 0x82be1000
  Size: 0 x 00033000
  Time stamp: 0x49e018d9
  Channel time: 2009-04-11 14:13:13
  Product name: Microsoft® Windows® Operating System
  Description of the file: Hardware Abstraction Layer DLL
  File version: 6.0.6002.18005 (lh_sp2rtm.090410 - 1830)
  Company: Microsoft Corporation
  Full path: C:\Windows\system32\hal.dll
  ==================================================

  All except a depressed that you downloaded came from bugs 0 x 124. Unfortunately, the pshed.dll file (error on hardware detection specific platform) on your system doesn't have a published public symbols, is not possible to get the data structures necessary to extract more details landfills.  If you can download c:\windows\system32\pshed.dll from your system to SkyDrive, which can help get the symbols which can lead to additional details.  That said, you don't seem to be a hardware problem, probably processor or motherboard.  Try some of what follows, but you may wind up checking in some hardware replacement.  Make sure that the cooling and ventilation system. Test the RAM, reinsert the processor and RAM if you can.  If the BIOS is the most recent, consider to return to a previous version and see if that helps.  Otherwise, update the BIOS.  Also check the BIOS settings; Perhaps, note the current settings, reset the default settings of the BIOS and then to adjust these parameters are needed to settle, you know.  Check the voltage, etc. and ensure/verify the motherboard CPU compatibility.  If you are overclocking, stop.

  I suggest to change your return to its 2660 MHz CPU frequency expected, his current 3500 MHz. (ratio OC 1.31 for your valued at 2.66 GHz Q6700 .)

• blue screen caused by driver ntoskrnl.exe

  original title: BSOD caused by driver ntoskrnl.exe

  I received several BSOD for some time now, usually 1 day a week, I'll take 4-5 in a row.  They always come when I'm starting, often after installing something (a different application each time).  Uninstalling these does not help.  It never happened when already in a windows session.  I have updated all drivers listed on the HP (model 8540p) website.  Here is an example of a landfill; Each dump is the same with exception to Param 4 (and, of course, the time and filename)

  Bug Check String	Bug check code	Param 1	Param 2	Param 3	Parameter 4	Caused by the driver	Caused by address
  IRQL_NOT_LESS_OR_EQUAL	0x0000000A	0	2	0	fffff800'032937 d 5	Ntoskrnl.exe	Ntoskrnl.exe + 80640

  The other 'setting 4"of are
  fffff800'032877 d 5
  fffff800'032df7d5
  fffff800'0328e7d5
  fffff800'0328a7d5
  fffff800'0329c7d5
  fffff800'032cd7d5
  fffff800'032937 d 5

  Edit: format for moving things to adapt to changes.  Last digit of Param 1-3 are listed.  Figures are all zeros.

  .rar is fine.

  With the Windows Debugger (WinDbg) the minidump files show the driver who caused the accident is the CipcCdp.sys:

  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck A, {0, 2, 0, fffff800032d97d5}

  Failed to load image \SystemRoot\system32\DRIVERS\CipcCdp.sys, 0n2 error Win32
  WARNING: Unable to verify timestamp for CipcCdp.sys
  ERROR: Module load completed but symbols can be loaded for CipcCdp.sys
  Probably caused by: CipcCdp.sys (CipcCdp + 1bfa)

  The CipcCdp.sys, which is dated July 21, 2010, seems to be a driver for Cisco IP Communicator.

  Can you try to update or, if necessary, uninstall the Cisco IP Communicator software and see if the BSOD solve.

  Same driver, causing the crash even in the following link:

  http://www.SevenForums.com/crashes-debugging/149525-IRQL_NOT_LESS_OR_EQUAL-b-c-i-connected-2-monitors.html

  The Cisco IP Communicator software is unable to uninstall itself so if you are still experiencing a BSOD after update or uninstall please provide the files minidump resulting.

• Satellite P300D-20U - BSOD 0 x 00000124 caused by hal.dll

  Hi guys.

  After my BSOD's long-term thinking, I got the main reason which probably caused it. It is hal.dll (bluescreenviewer told me). As far as I know, it's a driver of the motherboard.

  Where can I update it? Or what should I do?

  Why you again open thread on the same topic?
  You have already posted this here:
  http://forums.computers.Toshiba-Europe.com/forums/message.jspa?MessageID=189835

  You must decide which thread you want to track

• BSOD Vista caused by Ntkrnlpa.exe Ntfs.Sys, random hal.dll, etc..

  A friend of mine gave me this computer about 2 or 3 months without a hard drive, thanks to a little research because I am not a professional of any kind, I knew that, because of the lack of a disk hard computer did not have an operating system. Having had an old computer just sitting with a 60 GB hard drive I connected on the computer I have now. After buying a new installation of Windows Vista Service Pack 2 disc, just well installed on the hard drive (which has been formatted to remove the old operating system, and all other things potentially buggy) and the computer has given new life. Following these time immediately, I downloaded and installed Microsoft security Essentials to protect my computer and a few other things to Rainmeter, steam, and that's it. Not even which in fact through the first day, however it has begun its random cycle without blue screening end who, after looking hard and troubleshooting, I've yet to find a solution for. Especially, it occurs whenever trying to read a chart highlighting / demanding the game, but also random triggers when nothing works and it's just sitting here. Ironically, I am writing this issue on the same computer in the hope I can find a fix to the Microsoft community.

  He still run Windows Vista Service Pack 2 (32-bit) and my computer is a PC of Compaq Presario SR5710Y so that you know what the material consists of.

  Here's my last 4 crashes

  Mini042815 - 04.dmp 28/04/2015-18:59:23 0x864e3aa8 0x8471ad78 0x000000e3 RESOURCE_NOT_OWNED 0x00000000 0 x 00000002 Ntfs.sys Ntfs.sys + 12012 NT File System Driver

  Mini042815 - 03.dmp 28/04/2015-18:23:07 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0 x 00000004 0x00000002 0 x 00000000 0x822d9abf ntkrnlpa.exe ntkrnlpa.exe + 4de7d NT Kernel & System

  Mini042815 - 02.dmp 28/04/2015-18:14:28 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x006301be 0x00000002 0 x 00000001 0x822dab50 ntkrnlpa.exe ntkrnlpa.exe + 4de7d NT Kernel & System

  Mini042815 - 01.dmp 0x0000001a MEMORY_MANAGEMENT 15/04/2015-18:12:40 x 0 00005003 0xc0802000 00000197 0 x 0 x 77635101 hal.dll hal.dll + 770c Hardware Abstraction Layer DLL

  DJ

  If he continued to hang after re-installing windows, but before installing other programs, there is probably material.  I'd start with memtest

  2-Memtest. (You can learn more about running memtest here)

• Blue Screen Error Code Caused by hal.dll and ntkrnlpa.exe 9F.

  original title: BSOD error Code Caused by hal.dll and ntkrnlpa.exe 9F.

  Currently, I'm having a problem on a Fujitsu T1010 with Windows Vista x 84 installed tablet. At a random time that I use my computer, I get a generic blue screen with information DRIVER_POWER_STATE_FAILURE. The error code is 0x0000009F (0 x 00000003, 0x86f692e0, 0x86f692e0, 0x865a6598). BlueScreenView.exe, I see that the root causes are hal.dll + 997f and ntkrnlpa.exe + f5b28. So far, I've had 14 accidents. I run the driver verifier and the causes are hal.dll + 726c and ntkrnlpa.exe + 2ea5a7 windrvr6.sys + 0. Any help is appreciated! Thank you.

  Timothy

  Hello

  References to Vista also apply to Windows 7.
  
  Updated drivers, BIOS and software control (if any) is a good idea.

  This is my generic how updates of appropriate driver:

  For drivers, visit manufacturer of emergency system and of the manufacturer of the device that are the most common.
  Control Panel - device - Graphics Manager - note the brand and complete model
  your video card - double - tab of the driver - write version information. Now, click on update
  Driver (this can do nothing as MS is far behind the certification of drivers) - then right-click.
  Uninstall - REBOOT it will refresh the driver stack.

  Repeat this for network - card (NIC), Wifi network, sound, mouse, and keyboard if 3rd party
  with their own software and drivers and all other main drivers that you have.

  Now in the system manufacturer (Dell, HP, Toshiba as examples) site (in a restaurant), peripheral
  Site of the manufacturer (Realtek, Intel, Nvidia, ATI, for example) and get their latest versions. (Look for
  BIOS, Chipset and software updates on the site of the manufacturer of the system here.)

  Download - SAVE - go to where you put them - right click - RUN AD ADMIN - reset after each
  installation.

  Always check in the Device Manager - drivers tab to be sure the version you actually install
  presents itself. This is because some restore drivers before the most recent is installed (sound card drivers
  in particular that) so to install a driver - reboot - check that it is installed and repeat as
  necessary.

  Repeat to the manufacturers - BTW on device at the DO NOT RUN THEIR SCANNER - manually check by model.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  How to install a device driver in Vista Device Manager
  http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

  If you update the drivers manually, then it's a good idea to disable the facilities of driver in the Windows updates,
  This leaves ONE of Windows updates, but it will not install the drivers who are generally older and cause
  questions. If updates offers a new driver and then hide it (right click on it) and then go look for new ones
  manually if you wish.

  How to disable automatic driver Installation in Windows Vista - drivers
  http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
  http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

  Hope these helps.

  Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

• Is it possible possible to recover my data from my drive hard after receipt of this error message is the reference to hal.dll

  This error message is on a Windows XP Home Edition.

  «Windows has not start because the following file is missing or corrupt: Windows root\system32\hal.dll»

  This occurred after the use of the Norton Symantec solution to get rid of malware Tidserv activity.  After trying to restart my computer after the removal of the malware, assuming she was kidnapped, I got this error message.  I had backed up my important files on an external hard drive some time ago, but I still want to recover from this if possible.  It is an old Dell Dimension 3000 series and I don't have the CD that came with that installation.

  Thank you

  You could use another method to start your computer (like a Knoppix/Ubuntu or Hiren boot CD) and copy them to your personal data to an external device, you can move/slave your HARD drive to another system and see if you can copy the data off that way.

  This could work, but for me this looks like a lot of trouble and I only take it only after having exhausted all other methods of fixing what you have.

  Assuming you want to fix what you have (or at least make an effort to do so)...

  Despite what the message said, interpret it as meaning that XP just cannot find the file or XP is told to find the file in the right place.  This means not the file is missing or damaged - XP just cannot find it.

  There are two things to do that don't require to have an installation CD:

  run a chkdsk/r from the XP Recovery Console
  you rebuild the file c:\boot.ini from the XP Recovery Console

  Start with the chkdsk command, and here's how:

  The question was preceded by a loss of power, aborted reboot or abnormal termination? (This includes the plug pulling, buttons power and removing the battery).

  These can cause corruption in the file system that must be fixed before you do anything else.

  If none of these events occurred (or even if they have not taken place), you must verify the integrity of your file system before anything else (especially "try" things).

  There is zero logic to begin to try to begin to try to modify or copy files to a hard drive that has a corrupted file system, so this must first be fixed using the XP chkdsk program and run chkdsk on your hard drives may solve your problem completely.

  Use the XP Recovery Console to check the file system on your HARD drive and fix the problems and then try to start your system - this may be all you need to do.  Or, you are welcome to just start trying things that might work.

  Boot into the Recovery Console Windows using an XP bootable installation CD.

  If you have no XP bootable media (or aren't sure you have) create a bootable XP Recovery CD of Console and do not forget.

  This is not the same as recovery disks that might have come with the acquisition of the system store.

  You can make a bootable Recovery Console CD by downloading an ISO file and burn it to a CD.

  The ISO bootable image file you need to download is called:

  xp_rec_con. ISO

  Download the ISO from here:

  http://www.mediafire.com/?ueyyzfymmig

  Use a new CD and this simple and free program to burn your ISO file and create your bootable CD:

  http://www.ImgBurn.com/

  When you install ImgBurn, DO NOT install the Ask toolbar.

  Here are some instructions for ImgBurn:

  http://Forum.ImgBurn.com/index.php?showtopic=61

  It would be a good idea to test your bootable CD on a computer running.

  You may need to adjust the computer BIOS settings to use the CD-ROM drive as the first device to boot instead of the hard drive.  These adjustments are made before Windows tries to load.  If you miss it, you will need to restart the system again.

  When you start on the CD, follow the instructions:

  Press any key to boot from CD...

  Installing Windows... going to pronounce.

  Press 'R' to enter the Recovery Console.

  Select the installation that you want to access (usually 1: C:\WINDOWS)

  You may be asked to enter the password (usually empty).

  You should be in the folder C:\WINDOWS.  It's the same as the

  C:\Windows folder that you see in Solution Explorer.

  The Recovery Console allows base as file commands: copy, rename, replace, delete, chkdsk, fixboot, fixmbr, cd, etc.

  For a list of the commands in the Recovery Console, type help at the prompt of commands or read on here XP Recovery Console:

  http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

  A good idea before you start things must first verify the integrity of your file system by using the chkdsk command.

  In the command prompt window, run the chkdsk command on the drive where Windows is installed to try to fix any problems on the afflicted player.

  Running chkdsk is fine, even if he finds no problem.  It won't hurt anything to run it.

  Assuming your boot drive is C, run the following command:

  CHKDSK C: /r

  Let chkdsk finish to correct the problems, he could find.

  It may take a long time for chkdsk complete or they seem to be "stuck".  Be patient.  If the HARD drive led blinks always, chkdsk is something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.

  You must run chkdsk/r again until it finds no error to correct.

  Remove the CD, and then type "exit" to exit the RC and restart the computer.

  You have not to set the BIOS to boot the disk HARD since the CD won't be.

• missing hal.dll message after removing the hard drive

  Original title:Ok, I had the same problem on my hard drive missing hal.dll. My question is what windows xp writes the cmos on my computer?

  OK, I had the same problem on my hard drive missing hal.dll. My question is what windows xp writes the cmos on my computer? The reason why I ask, is that I physically removed the hard drive from the computer and then start the computer I get the same message hal.dll lack. Since the hard drive is not installed, the only place where this message comes's cmos or bios of the computer.
  I know it seems odd, but I couldn't believe it when I saw it after removing the hard drive. It used to be with older computers and Windows 95 or 98 when you took a hard drive that wasn't working and installed with one that works from a different computer, you could swap out and boot the computer and make a few changes to some drivers if you.

  So what is windows xp write to the memory cmos on my computer?

  > Ok, I had the same problem on my hard drive missing hal.dll.

  The same as what? If you reference another thread, please include a link to it.

  > My question is what windows xp writes the cmos on my computer?

  It is not write anything for her at all.

  > Lack of the reason why I ask this is that I physically removed the hard drive from the computer and then start the computer I get the same message hal.dll.

  I think that you're wrong. I would like to say two things happening:

  1. you have more than one hard drive and the problematic drive was not removed, or

  2. you deleted something other than a hard drive.

  Do you have a CD in your CD drive by chance?

  What is the brand and model of your PC? Are you able to get into the BIOS?

• system32\hal.dll. missing. computer will not start. Help, please. I don't have an xp cd. XP is installed on the hard drive

  Hello
  My laptop is not at all start. It is just coming up with the error message "windows root>\system32\hal.dll. missing. Please reinstall a copy of the above file.
  Everything I can find on the web so far tells me to reinstall via an XP CD. My version of xp was preinstalled, because it's a computer dell laptop.
  Can someone help me?

  Hello
  Please take a look at this article and follow the steps in troubleshooting bottom of the page.

  http://support.Microsoft.com/kb/314477

  I hope this helps. Just reply to the results.

• BSOD caused by the discache.sys driver

  Hello

  I had a couple of BSOD happen recently and would like help to understand what exactly is the cause of the errors. So far, I found that Nirsoft has a tool to view the errors blue screen (http://www.nirsoft.net/utils/blue_screen_view.html). I looked at the bug check Code and found advice to uninstall and reinstall the drivers for my video card manufacturer's Web site.

  Here are a few screenshots of the BSOD error details:

  http://imgur.com/a/XLk8J

  Recently, a BSOD caused my previous unreadable ssd not recognized / BIOS and Device Manager. I didn't have a chance, try to access it from other computers, then these BSOD is rather worrying. I'd appreciate any help and advice you have.

  Thank you!

  These accidents are called BCC116 and are associated with your video subsystem.  Please follow the instructions of this wiki

• Cannot start the computer (error hal.dll)

  Hi, I use Windows xp and when it loads, it says:
  Windows could not start because the following file is missing or corrupt:
  \System32\hal.dll
  Please reinstall a copy of the top of the queue.

  I have the original Windows xp cd and when I boot from the cd the blue screen comes up saying "Windows Setup".
  It automatically start doing something and then he stuck to "ACPI Plug & Play bus driver. Stucks HE there for a while and when it ends, I got an error message that says: "file acpi.sys cause unexpected error (32768) to 5964 in d:\xpsprtm\base\boot\setup\setup.c line."

  And when I press any button it just restarts the computer and it makes a loop in this way.
  And by the way, safe mode and all the other modes do not work, I get the same error for hal.dll, and I can't reach the office.

  Help, please!

  UPDATE: this time I received the error "acpi.sys file caused...". "now, I got that it's corrupted.

  It is extremely unlikely that the hal.dll file is missing or damaged.

  It is extremely likely that XP just cannot find the file.

  I have no idea what you have tried so far things - have you tried to do a repair installation?

  For this error, I first start in the XP Recovery Console (by pressing 'R' of your bootable CD) and run chkdsk /r on your system and then see how things appear after that, but try this notice from the Support Engineer and see how it works.

  If you can't get into the Recovery Console any CD you or you are not sure what type of bootable media you have, you should make a bootable CD from the Console of the Recovery XP (no XP media required) and do not forget what you have.

  Since the Microsoft Answers forum does not have any kind of information system request when a new question is asked, we know absolutely nothing about your system.  Not knowing the basic information a problem prolongs the frustration and the agony of these issues.

  Thank you MS Answers, allowing the resolution of simple problems as frustrating and a lot of time as possible.

  Provide information on your system, the better you can:

  What is your system brand and model?

  What is your Version of XP and the Service Pack?

  Your system's disks IDE or SATA drives?

  Describe your current antivirus and software anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc..

  The question was preceded by a loss of power, aborted reboot or abnormal termination?  (this includes the plug pulling, buttons power, remove the battery, etc.)

  The afflicted system has a working CD/DVD (internal or external) drive?

  If the system works, what do you think might have changed since the last time it did not work properly?

• Missing hal.dll – is driving me crazy!

  Thus, a colleague brought me a XP computer that wouldn't start. The message I get is about either being damaged or missing hal.dll.

  So I jumped on the internet for a solution, but none have worked so far, and I got to a point where I'm about to throw it out the window! We want to avoid reinstalling Windows like we don't have a copy of most of the software installed more!

  I've tried so far...

  Using the recovery console on the XP disc to develop hal.dl_ - unsuccessfully

  You use the recovery disk XP console to run CHKDSK /rconnect - unsuccessfully

  Using the recovery console on the XP disc to develop ntoskrnl.ex_ - unsuccessfully

  You use the recovery disk XP console to run bootcfg /rebuild - without success (picked up one more installation of XP in RECYCLER but not start not completely)

  Install another copy of Windows on the HARD drive in a separate file, then copying the file hal.dll everywhere and by removing the new facility - without success

  Anyone has any suggestions more? He makes me crazy!

  I backed up all my data, but I have all my installation discs. Nothing I can do about that really,

  Looks like you're stuck trying to solve what you have.

  Personally, I would like to burn a live cd like ubuntu, download the boot.ini file that I created for you, then place at the root of c drive using the live cd. Restart and see what you get now the error. At least you would spend the boot.ini issue cause you know that you have a good boot.ini file. You can then start the hal.dll if it does not start. but, when you're dealing with a problem that could be one of the two files, you don't really know which way to go. Remove a cause, then focus on the other. At least that's the way I do things. Process of elimination until I get to the root of the problem.

• Windows xp pro sp3 will not start corrupted boot.ini and hal.dll - please help

  I installed Norton 360 offred via internet was last updated.  It immediately launched all applications previously disabled at STARTUP in msconfig.  And shortly after he started to gives me the blue screen "to the death".  This done in two days, and I was desperately trying to solve the problem by turning off almost all applications critical to running Windows XP Pro SP3, Norton and Office 2007 Home and student.  I even went and tried to edit the Boot.ini file in startup and recovery under the Advanced tab in the workstation properties.  Now all I get is an error message Windows cannot start because the hal.dll file is missing or damaged.  I replaced it by copying a modified version of the boot sequence, while the hard drive of my laptop was enslaved to my desktp PC, but nothing helped.  I can't even the Recovery Console to start on my laptop.  I need HELP, please.

  These profile errors are usually caused by one of the following:

  1-profile corruption.  The user profile is damaged and that Windows cannot load.  To resolve this issue, create a new user profile and move your files to the new profile.   See here for more information:

  How to copy data from a corrupted to a new profile in Windows XP user profile

  2 drives or corruption of the file system.  Run chkdks /f on the volume C:.  Please note that there is ALWAYS a risk of data loss when chkdsk is run on a volume, ideally, you should have a backup of your files before running chkdsk.

  3 - virus or malware activity.  Some of these parasites can revoke your permissions on the folder of your profile, check the permissions on "C:\Documents and Settings\Andre" and make sure you have a full control on the folder.  Check this box until you try #1 or 2 above.

  Some of these parasites can also revoke your permissions in key areas of the registry and create real Dany on the machine that can prevent you to run some of your software.  Use Regedit to load your old profile hive (NTUSER. (DAT) in your profile folder (C:\Documents and Settings\Andre\NTUSER. (DAT) and make sure you have full control over the key.  In the advanced security settings to ensure that the child objects are inherit permissions from the parent and put a check mark on "replace entries permissions for all child objects...". "Click on apply and OK your way out.  See here for easy to follow instructions for loading and editing of remote registry hives: http://www.rwin.ch/xp-live/regedit.htm make sure you unload the hive when you're done, otherwise the changes will not be saved.

  These parasites can also revoke permission on the other key of registry and system files, you can use SubInACL to restore your permissions on these key objects, see here for more information:

  Solve installation errors using the SubInACL tool to repair the file and registry permissions

  John

• Root Windows satellite 5200 701 system32/hal.dll missing

  My Toshiba s5200 701 crashed today.

  Windows displays this error:

  + windows didn't start because the following file is missing or corrupt: windows root system32 / hal.dll +.
  + Please re install. +

  First of all, this Toshiba is a European model and I live in the USA.
  Second, the model is old.
  Third, I don't have the XP CD reinstal the OS.

  I don't know if it's worth buying a new professional XP for this computer.

  All ideas, suggestions. Please notify.

  Jose

  Hello

  I read on issues such as
  You need to reinstall the OS, but it would also be possible that this error is related to the defective HARD and/or RAM disk.
  Many uses had this error again after the new installation of the OS and in individual cases the RAM or the HARD drive has been affected as well.

  What to say; It s your decision what you want to do... I recommend reinstall Win XP once more to verify if this question relates only to lack hal.dll in the system32 folder.
  However the Win XP license is cheap, because Win 7 is on the market and no one wants to use 'old' OS which will be more in the coming years...

• Error Hal.dll not found or currupted

  Hello

  Just, I restarted my laptop and was greeted with this message. Then I tried to re - install windows xp family and the same error.

  I don't have my cd of XP Home so I used my version of the Home Office. Does this matter at all or what could be the problem.

  Help, please
  Joe

  If you get an error about a missing or corrupt hal.dll file, it could simply be the BOOT. INI file in the root of the C: drive that is misconfigured

  Insert and boot from your Windows XP CD.

  At the first R = repair option, press the R key

  Press the number that corresponds to the correct location of the Windows installation you want to repair. In general, this will be #1
  Type bootcfg/list to display these entries in the TRUNK. INI file

  Type bootcfg /rebuild to fix

  Exit at the exit of the CD ROM and type

  There are also quite a few pages explaining what to do:

  http://www.experts-exchange.com/Operating_Systems/Q_20885225.html

  Good luck