How To Fix Hal.dll Errors in Windows 7 and Windows Vista

Posted: Thursday, 21 July 2011 by Unknown in Labels: , , , , , ,
0

If you have Windows Vista or Windows 7 installed and you're seeing the hal.dll error, it most likely means that for whatever reason, your master boot record has been changed to the one only compatible with Windows XP... and it's looking for hal.dll.

Lucky, this problem is pretty easy to fix.

Resolution

1. Start System Recovery Options from the Windows Installation Disc.

2. Open Command Prompt from the System Recovery Options menu.

3. At the prompt, type the bootsect command as shown below and then press Enter:

bootsect /nt60 sys

The bootsect command as used above will overwrite the master boot record on the partition used to boot Windows to the one that's compatible with Windows Vista, Windows 7, and later Windows operating systems.

4. After running the bootsect command as shown in the last step, you should see a result that looks something like this:

C: (\\?\Volume{37a450c8-2331-11e0-9019-806e6f6e6963})

Successfully updated NTFS filesystem bootcode.

Bootcode was successfully updated on all targeted volumes.

Note: If you receive some kind of error, or this doesn't work after you try to start Windows normally again, try running "bootsect /nt60 all" instead. The only caveat here is that if you're running a dual-boot computer, you may inadvertently cause a similar, but opposite, problem with any older operating systems you boot to.

5. Close the Command Prompt window and then remove the Windows disc from your optical drive.

6. Click the Restart button from the System Recovery Options window.

7. Windows should start normally now.

8. If nothing works make a clean installation of windows.

Missing Or Corrupt Hal.dll Error Troubleshooting Windows XP

Posted: Wednesday, 20 July 2011 by Unknown in Labels: , , , , , ,
0

Hal.dll Error Message

There are few different ways that the "missing or corrupt hal.dll" error may present itself, with the first listing being the most common:

"Windows could not start because the following file is missing or corrupt:
\system32\hal.dll.
Please re-install a copy of the above file."

"\System32\Hal.dll missing or corrupt:
Please re-install a copy of the above file."

"Cannot find \Windows\System32\hal.dll"

"Cannot find hal.dll"

The "missing or corrupt hal.dll" error displays shortly after the computer is first started. Windows XP has not yet fully loaded when this error message appears.

Cause

Causes of the "missing or corrupt hal.dll" error include, naturally, a damaged hal.dll DLL file or a hal.dll file that has been deleted or moved from its intended location.

Additional causes may include a damaged or missing boot.ini file or possibly a physically damaged hard drive.

Hal.dll Error Troubleshooting

1. Restart the PC. The hal.dll error could be a fluke.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

8. 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.

9. 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.

Important: If you can't gain access to your files to back them up, you should understand that you will lose them all if you continue with a clean installation of Windows XP.

10. Test the hard drive. 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 but you'll want to test it to be sure.

If the drive fails any of your tests, replace the hard drive and then complete a "new" installation of Windows XP.

Invalid Page Fault in Module Kernel32.dll Error Resolution

Posted: by Unknown in Labels: , , , ,
0

Kernel32.dll Error Messages

There are a number of different ways that the "invalid page fault in module kernel32.dll" error may show up on your computer. Many different software programs may generate the kernel32.dll error in Windows but here are some of the more common specific error messages you may see:

"Explorer caused an invalid page fault in module Kernel32.DLL"

"Iexplore caused an invalid page fault in module Kernel32.DLL"

"Commgr32 caused an invalid page fault in module Kernel32.dll"

"Error in Kernel32.dll"

"[PROGRAM NAME] has caused an error in Kernel32.dll"

Kernel32.dll error messages may appear when Windows starts, when a program is opened, when a program is running, when a program is closed or at nearly any time during a session of Windows.

Cause of Kernel32.dll Errors

The causes of the kernel32.dll error message are as varied as the messages themselves. The kernel32.dll file is involved with memory management in Windows.

When Windows is started, kernel32.dll is loaded into a protected memory space so other programs don't attempt to use the same space in memory to run their operations.

The frequently accompanying "invalid page fault" error means that another program (or many programs) are trying to access this same space in your computer's memory.

Resolution

1. Restart your computer. The kernel32.dll error could be a fluke.

2. Reinstall the program if the "invalid page fault in module kernel32.dll" error occurs only when you use a single software program.

Chances are, the software program is most likely to blame so uninstalling and reinstalling the program may do the trick.

Be sure to install any service packs or other patches available for the program. One of these may have resolved the kernel32.dll problem that the software is causing. If necessary, you may need to stop using a particular program if it's the only cause of the problem.

3. Repair potentially damaged password list files. Try this troubleshooting step only if you're running Windows 95 or Windows 98 and if the kernel32.dll page fault is caused by "Explorer", "Commgr32", "Mprexe", "Msgsrv32", or "Iexplore".

4. Repair corrupted thumbs.db files. Often times, the "Explorer caused an invalid page fault in module Kernel32.DLL" error is caused by a corrupted thumbs.dll file in a folder of subfolder that you're trying to access.

5. Do you have DLL files saved to your desktop? If so, remove them. This can sometimes cause kernel32.dll errors.

6. Run a virus scan. Some specific computer viruses cause kernel32.dll errors as part of their damage to your computer. Quarantining the virus may resolve your issue entirely.

7. Update drivers for any hardware that might be related to the kernel32.dll error. For example, if a kernel32.dll error appears when printing to your printer, try updating the drivers for your printer.

If you suspect that drivers need updated but aren't sure where to start, update your video card drivers. Outdated video card drivers sometimes cause kernel32.dll errors.

8. Decrease the hardware acceleration on your video card. While uncommon, some computers do have problems when the hardware acceleration is set at it's default setting of full acceleration.

9. Have you overclocked your PC? If so, try resetting your hardware configuration to the default recommended by the manufacturer. Overclocking has been known to cause kernel32.dll issues.

10. Test your system memory for damage. Kernel32.dll error messages from random programs and activities in Windows could be a sign of a hardware failure with your computer's memory. One of these programs will clearly identify if you have a problem or give your memory a clean bill of health.

Replace the memory if it fails any of your tests.

11. Repair your Windows installation. If individual software reinstallations and hardware tests fail to resolve the problem, a repair installation of Windows should replace any damaged or missing files that may be causing kernel32.dll messages.

12. Perform a clean installation of Windows. This type of installation will completely remove Windows from your PC and install it again from scratch.

13. Finally, if all else has failed, including the clean installation from the last step, you're likely looking at a hardware issue with your hard drive or another piece of hardware.

If the hard drive is the likely culprit, replace the hard drive and then perform a new installation of Windows.

D3dx9_41.dll Not Found Error Resolution

Posted: by Unknown in Labels: , , , , ,
0

There are several ways that d3dx9_41.dll errors can show up on your computer. Several of the more common specific d3dx9_41.dll error messages are listed below:

"The file d3dx9_41.dll is missing"

"D3dx9_41.DLL Not Found"

"File d3dx9_41.dll not found"

Cause of D3dx9_41.dll Errors

D3dx9_41.dll issues are caused in one way or another by an issue with Microsoft DirectX.

The d3dx9_41.dll file is one of many files contained in the DirectX software collection. Since DirectX is utilized by most Windows based games and advanced graphics programs, d3dx9_41.dll errors usually show up only when using these programs.

Resolution

1. Restart your computer if you haven't yet.

The d3dx9_41.dll error might be a fluke and a simple restart could clear it up completely.

2. Install the latest version of Microsoft DirectX. Chances are, upgrading to the latest version of DirectX will fix the d3dx9_41.dll not found error.

3. Assuming the latest DirectX version from Microsoft doesn't fix the d3dx9_41.dll error you're receiving, look for a DirectX installation program on your game or application DVD or CD. Usually, if a game or other program utilizes DirectX, the software developers will include a copy of DirectX on the installation disc.

Sometimes, though not often, the DirectX version included on the disc is a better fit for the program than the latest version available online.

4. Uninstall the game or software program and then reinstall it again. Something might have happened to the files in the program that work with d3dx9_41.dll and a reinstall could do the trick.

5. Restore the d3dx9_41.dll file from the latest DirectX software package. If the above troubleshooting steps haven't worked to solve your d3dx9_41.dll error, try extracting the d3dx9_41.dll individually from the DirectX downloadable package.

6. Update the drivers for your video card. While it's not the most common solution, in some situations updating the drivers for the video card in your computer could correct this DirectX issue.

Important Registry Tricks For Security

Posted: Tuesday, 19 July 2011 by Unknown in Labels: , , , , , , ,
0

## Manually Disable Regedit Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.


HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System
NOTE: If you do not have System, right click on Polices, click on New and Key, then type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value. Type DisableRegistryTools and press Enter.

6. Right click on DisableRegistryTools and click on Modify.
7. To Disable Regedit and Allow Silent Mode: Type 1 and ok
8. To Disable Regedit and Prevent Silent Mode: Type 2 and ok

## Manually Disable CMD Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System

Note:If you do not have System in the left pane, then right click on Windows and click on New and Key, then type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value. Type DisableCMD and press Enter.

6. Right click on DisableCMD and click on Modify
7. To Disable Command Prompt Only and Allow Scripts: Type 2 and ok.
8. To Disable Command Prompt and Scripts: Type 1 and ok.

## Manually Disable TaskMgr Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System

NOTE: If you do not have System, then right click on Polices and click on New and Key. Type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value and type DisableTaskMgr and press Enter.

6. Right click on DisableTaskMgr and click on Modify.
7. Type 1 and click on OK.

## Manually Disable Autoplay Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\No​DriveTypeAutorun

NOTE: If you do not have System, then right click on Polices and click on New and Key. Type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value and
type No​DriveTypeAutorun and press Enter.

6. Right-click NoDriveTypeAutorun, and then click Modify.
7. In the Value data box, type 0xFF to disable all types of drives.
8. Click OK, and then exit Registry Editor.
9. Restart the computer.

## Manually Disable Run Command in Start Menu Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\No​Run

NOTE: If you do not have System, then right click on Polices and click on New and Key. Type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value and
type No​Run and press Enter.

6. Right-click NoRun, and then click Modify.
7. In the Value data box, type 0 to disable run / 1 to eanble run.
8. Click OK, and then exit Registry Editor.
9. Restart the computer.

Note: Other DWORD values: DisableLocalMachineRun, DisableLocalMachineRunOnce, DisableCurrentUserRun, DisableCurrentUserRunOnce.