Showing posts with label Windows error. Show all posts
Showing posts with label Windows error. Show all posts

Keyboard error - 301

Keyboard error - 301
"Every time I start my computer I get a 301 keyboard error. What does this mean and how can I fix it?" Thanks for the question, Im trying to answer it.

Script errors in Internet Explorer


For internet explorer users is not a new trouble having script errors.


Error 651 - Windows

Error 651 on Windows usually can appear when you try to access the internet using broadband connection, through Wan Miniport PPPoE, then fails citing Error 651. Try to replace the driver raspppoe.sys in Windows/System32/Drivers directory with a new one. Here’s how you do it. Rename the raspppoe.sys to raspppoe.old or any other name as per your choice. Download the file from http://shell.windows.com/fileassoc/0409/xml/redir.asp?EXT=zip and save it in Windows/System32/Drivers directory. For more help, visit answers.microsoft.com

How to fix windows system32 config system error

When you try to start or restart your Windows XP-based computer, you may receive one of the following error messages: Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SOFTWARE Stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or alternate System error: Lsass.exe When trying to update a password the return status indicates that the value provided as the current password is not correct. Recover a corrupted registry that prevents Windows XP from starting The procedure that this article describes uses Recovery Console and System Restore. This article also lists all the required steps in specific order to make sure that the process is fully completed. When you finish this procedure, the system returns to a state very close to the state before the problem occurred. If you have ever run NTBackup and completed a system state backup, you do not have to follow the procedures in parts two and three. You can go to part four. Part one In part one, you start the Recovery Console, create a temporary folder, back up the existing registry files to a new location, delete the registry files at their existing location, and then copy the registry files from the repair folder to the System32\Config folder. When you have finished this procedure, a registry is created that you can use to start Windows XP. This registry was created and saved during the initial setup of Windows XP. Therefore any changes and settings that occurred after the Setup program was finished are lost. To complete part one, follow these steps: Insert the Windows XP startup disk into the floppy disk drive, or insert the Windows XP CD-ROM into the CD-ROM drive, and then restart the computer. Click to select any options that are required to start the computer from the CD-ROM drive if you are prompted to do so. When the "Welcome to Setup" screen appears, press R to start the Recovery Console. If you have a dual-boot or multiple-boot computer, select the installation that you want to access from the Recovery Console. When you are prompted to do so, type the Administrator password. If the administrator password is blank, just press ENTER. At the Recovery Console command prompt, type the following lines, pressing ENTER after you type each line: md tmp copy c:\windows\system32\config\system c:\windows\tmp\system.bak copy c:\windows\system32\config\software c:\windows\tmp\software.bak copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak copy c:\windows\system32\config\security c:\windows\tmp\security.bak copy c:\windows\system32\config\default c:\windows\tmp\default.bak delete c:\windows\system32\config\system delete c:\windows\system32\config\software delete c:\windows\system32\config\sam delete c:\windows\system32\config\security delete c:\windows\system32\config\default copy c:\windows\repair\system c:\windows\system32\config\system copy c:\windows\repair\software c:\windows\system32\config\software copy c:\windows\repair\sam c:\windows\system32\config\sam copy c:\windows\repair\security c:\windows\system32\config\security copy c:\windows\repair\default c:\windows\system32\config\default Type exit to quit Recovery Console. Your computer will restart. Note This procedure assumes that Windows XP is installed to the C:\Windows folder. Make sure to change C:\Windows to the appropriate windows_folder if it is a different location. If you have access to another computer, to save time, you can copy the text in step five, and then create a text file called "Regcopy1.txt" (for example). To use this file, run the following command when you start in Recovery Console: batch regcopy1.txt With the batch command in Recovery Console, you can process all the commands in a text file sequentially. When you use the batch command, you do not have to manually type as many commands. Part two To complete the procedure described in this section, you must be logged on as an administrator, or an administrative user (a user who has an account in the Administrators group). If you are using Windows XP Home Edition, you can log on as an administrative user. If you log on as an administrator, you must first start Windows XP Home Edition in Safe mode. To start the Windows XP Home Edition computer in Safe mode, follow these steps. Note Print these instructions before you continue. You cannot view these instructions after you restart the computer in Safe Mode. If you use the NTFS file system, also print the instructions from Knowledge Base article KB309531. Step 7 contains a reference to the article. Click Start, click Shut Down (or click Turn Off Computer), click Restart, and then click OK (or click Restart). Press the F8 key. On a computer that is configured to start to multiple operating systems, you can press F8 when you see the Startup menu. Use the arrow keys to select the appropriate Safe mode option, and then press ENTER. If you have a dual-boot or multiple-boot system, use the arrow keys to select the installation that you want to access, and then press ENTER. In part two, you copy the registry files from their backed up location by using System Restore. This folder is not available in Recovery Console and is generally not visible during typical usage. Before you start this procedure, you must change several settings to make the folder visible: Start Windows Explorer. On the Tools menu, click Folder options. Click the View tab. Under Hidden files and folders, click to select Show hidden files and folders, and then click to clear the Hide protected operating system files (Recommended) check box. Click Yes when the dialog box that confirms that you want to display these files appears. Double-click the drive where you installed Windows XP to display a list of the folders. If is important to click the correct drive. Open the System Volume Information folder. This folder is unavailable and appears dimmed because it is set as a super-hidden folder. For more information, please visit support.microsoft.com

Stop error code 0x0000000A - Windows

You receive a Stop error message with the following format during or after the installation of Windows XP: Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL *** Address x has base at x - filename In this Stop error message, each parameter is a hexadecimal number that refers to a specific issue: Parameter 1 - An address that was referenced incorrectly. Parameter 2 - An IRQL that was required to access the memory. Parameter 3 - The type of access, where 0 is a read operation and 1 is a write operation. Parameter 4 - The address of the instruction that referenced memory in parameter 1. For example: STOP 0x0000000A (0xBFD14AAC, 0x000000FF, 0x00000000, 0x8000F67C) IRQL_NOT_LESS_OR_EQUAL ***Address 8000f67c has base at 80001000 - hal.dll This Stop error message usually occurs during installation when there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). Typically, this error occurs when a driver uses an incorrect memory address. Other possible causes of this error include an incompatible device driver, a general hardware problem, or incompatible software. When this Stop error message occurs, first try to resolve the issue by using the Windows Error Reporting tool that is automatically displayed when any error occurs. The Reporting tool sends an error report to Microsoft, and reports a fix or a workaround back to you immediately. If no fix or workaround is available, or if the fix or workaround reported by the tool does not resolve the error, then follow the methods in the "Advanced Troubleshooting" section. For more information please visit support.microsoft.com

Runtime Error - WIndows XP

Runtime errors in Windows XP or another version of Windows It can be caused by invalid and corrupted registry entries is one of the most common causes for this type of problem. Common Runtime Errors: Disk Full Bad Record Number Subscript Out Of Range Illegal Use Of Null Out Of Memory Device Unavailable