Panayiotis Christodoulou How do I run Microsoft ScanDisk? How do I run Microsoft Defrag? How do I restore Windows back to an earlier copy? How to erase my hard drive and start over? How to fix an invalid page fault? How to fix a fatal exception error? How to fix a general protection fault? How to enter the BIOS or CMOS setup? Windows runtime errors How to get to an MS-DOS prompt or Windows command line How to use the Window command line (DOS) To run ScanDisk and check your hard drive for errors follow the steps below for your version of Windows. Before running scan disk on the computer, keep in mind that it can take several hours to complete depending on the size of your hard drives, and any errors that may exist with the drive. Microsoft Windows XP, 2000, Vista, and 7 users Keep in mind that these versions can be a networking operating system and it's possible that the privileges to run Scandisk may have revoked by the system administrator. To run 3candisk we recommend you follow the recommend steps. Double-click My Computer Highlight a local hard drive by clicking on it once Right-click the highlighted local drive Click Properties Click the Tools tab and click check now to check the drive for errors. The computer needs to restart to run ScanDisk without getting interrupted. Although not required we suggest having ScanDisk automatically find and fix any errors found. Windows 2000, XP, Vista, 7, and 8 Defrag To run Defrag, we recommend you follow the steps below. Double-click My Computer or open Explorer. Highlight the local hard disk C: drive by clicking on it once. Right-click the highlighted local drive Click Properties Click the Tools tab and click the Defragment now button. Tip: Windows also supports running Defrag from the Windows command line. For a syntax and full listing of defrag options in the command line see our defrag command page. Users who are running Microsoft Windows XP or later can use System Restore to roll back the state of their system files and settings. This action can help to fix poor performance or software errors and does not erase any of your data, like pictures or music. However, it may delete settings or drivers implemented after the restore point was created. Windows 8 users Navigate to the Start Screen and type restore, which should bring up a search box. Click Create a restore point. In the System Properties window that appears, under System Protection, click the System Restore... button. After processing, a window appears with two buttons at the bottom; click Next >. The following screen usually suggests a recent restore point and your last critical update. ◦ If you know the date your problem started, check the box next to Show more restore points. Make your selections and click Next. Then, confirm your restore point and click Finish. Windows Vista and 7 users Click Start. In the Start search box, type System Restore and press enter. After processing, a window appears with two buttons at the bottom; click Next >. The following screen usually suggests a recent restore point and your last critical update. ◦ If you know the date your problem started, check the box next to Show more restore points. Make your selections and click Next. Then, confirm your restore point and clickFinish. Notice: Remember that following the steps below will erase all of the information on your hard drive and make it like new. Once the steps below have been completed, you will not be able to reverse the steps if you want to recover possible lost data. Erasing the hard drive and reinstalling Windows Windows 8 Press the Windows key plus the "C" key to open the Charms menu. Select the Search option and type reinstall in the Search text field (do not pressEnter). Select the Settings option. On the left side of the screen, select Remove everything and reinstall Windows. On the "Reset your PC" screen, click Next. On the "Do you want to fully clean your drive" screen, select Just remove my filesto do a quick deletion or select Fully clean the drive to have all files erased. On the "Ready to reset your PC" screen, click Reset. The hard drive will be erased and Windows 8 will be reinstalled. Windows 7 and Vista Insert the Windows 7/Vista installation CD in the CD-ROM drive and restart the computer. When you see the message "Press any key to boot from CD", press a key on the keyboard. Press the Enter key at the Windows Setup welcome screen. When prompted, press any key on your keyboard. On the "Install Windows" page, select your preferred language and other preferences, then click Next. On the License Agreement page, accept the terms and agreements and click Next. On the Installation Type screen, choose the Custom option. Select the Drive Options (advanced) option. For Disk 0, delete all partitions. When all partitions have been deleted, you should see a single entry named "Unallocated space". Click on Disk 0 and select Next. The Windows installation process will start by creating a new partition, formatting the partition, and installing Windows on the hard drive. The formatting process will erase the hard drive before installing Windows. An interruption that occurs when a software program attempts to access an invalid page in memory in Microsoft Windows. Page faults are caused by a software issue or confliction, driver issue, or a hardware related issue. Remove all TSRs Disable or unload any TSRs or background programs currently running before running the program causing the GPF. Delete all program temporary files Delete all temporary files that may still be residing on the hard drive from currently or previously running programs. Run ScanDisk and Defrag Run ScanDisk and run Defrag on the hard drive as it could be possible your hard drive may have an issue causing the swap file or data files to become corrupt or invalid. Update software or check for software patches If you are experiencing invalid page faults in only one program, verify that the software program is compatible with the operating system you are running the program within. Also, verify with the manufacturer or vendor of the software program that there are no available patches or updates for the program that may help or resolve your issue. Recently installed software or hardware If you have recently installed new software or hardware, uninstall or reinstall that software or hardware to verify it is not causing your issue. Bad Memory, invalid bits, or physically damaged memory Bad memory can cause Illegal Operations. If you have recently added memory to the computer it is recommended that it first be removed to verify that you are not experiencing conflictions with the recently installed memory. If no memory has been recently added to the computer it is recommended you follow all other steps found on this page before replacing the memory within the computer. In computer programming, an exception is an issue that occurs because of a confliction or abnormality in the code. An exception causes the program to stop or abort. Microsoft Windows and software use exceptions, which allow Windows or other software to communicate in layers and communicate errors or exceptions. If a program is given an exception that is invalid or unknown, you'll encounter a fatal exception. Fatal exceptions are also commonly referred to as a Fatal 0E. When a fatal exception is encountered, the error will be in the below format. A fatal exception <YZ> has occurred at xxxx:xxxxxxxx In the above example, the YZ represents the actual processor exception, this can range from 00 to 0F. Each of these processor exceptions are explained under Extended information. After the processor exception is the enhanced instruction pointer to the code segment and the 32-bit address. This is exactly where the error exception has occurred. Search for the error Often the easiest and fastest method to locate the cause of a fatal exception is to search for the error. However, for some users, it may be difficult to know exactly what to search for because of the cryptic fatal exception messages. Below are tips on how to search for these errors. 1. As mentioned above, the fatal exception has a two character code. For example, if the "0E" is present, use this as part of your search. 2. Next, the error message should contain a pointer (e.g. "0028:c001e36"). Although this may be found in a search, it is usually unique to your computer. If you're not finding any search results, exclude this from your search. 3. Finally, many fatal exception error messages also contain a file that generated the error, which is almost always a VXD file. If the fatal exception error contains a reference to a .VXD file, definitely include this as part of your search. The VXD file may also be listed as "VXD VWIN32", which is "vwin32.vxd". Revert Windows back to an earlier copy If this has just started occurring and you're running Windows XP or later, restore Windows back to an earlier copy. Update software or check for software patches If you are experiencing invalid error exception in only one program, verify that the software program is compatible with the operating system on the computer. Also, check with the manufacturer or vendor of the software program to see if there are any available patches or updates for the program that may help to resolve your issue. It is also important that you have all the latest Windows updates. Hardware drivers If fatal exceptions happen when using a hardware device (e.g. when you print), the drivers related to that device are either conflicting with another device, corrupt, or have other errors. Video drivers are also notorious for causing fatal exception error messages. Because your video card is being used all the time, it's difficult to know for certain if it's the cause of the error. Therefore we always recommend having the latest video drivers on your computer. Visit the manufacturer's website and get the latest software and drivers from them. See the computer drivers page for a listing of hardware companies. Recently installed software or hardware If you have recently installed new software or hardware, uninstall or reinstall that software or hardware to verify it is not causing your issue. With a hardware device, instead of installing the software or drivers that came with the device, visit the manufacturer's website and get the latest software or drivers from them. See the computer drivers page for a listing of hardware companies. Below is a listing of the more commonly experienced processor exceptions ranging from 00 to 0F. 00 = Divide Fault Occurs if division by zero is attempted or if the result of the operation does not fit in the destination operand. 02=NMI interrupt Interrupt 2 is reserved for the hardware Non-MaskableInterrupt condition. No exceptions trap through interrupt 2. 04=Overflow trap Occurs after an INTRO instruction has executed and the OF bit is set to 1. 05=Bounds Check fault The array Index is out of range 06=Invalid Opcode fault This error can be caused by one of the below conditions. Processor attempting to decode a bit pattern that does not correspond to any legal computer instruction. Processor attempts to execute an instruction that contains invalid operands. Processor attempts to execute a protected-mode instruction while running in virtual 8086 mode. Processor attempts to execute a LOCK prefix with an instruction that cannot be locked. 07=Copressor not available fault. This error can occur if no math coprocessor is present. This error can also occur when the math coprocessor is used and a task switch is executed. 08=Double Fault. This error occurs when processing an exception triggers a second exception. 09(OD)=Copressor Segment Overrun. Floating point operand is outside the segment. 10(0Ah/0A)=Invalid Task State Segment Fault Can be caused by a number of possibilities as Task State Segment contains a number of descriptors. 11(0Bh)=Not Present Fault The not present interrupt allows the operating system to implement virtual memory through the segmentation mechanism. 0B fault occurs when this segment is not available. 12(0Ch)=Stack Fault Occurs when instruction refers to memory beyond the limit of the stack segment. 13(Odh)=General Protection Fault Caused by any condition that is not covered by any of the other processor exceptions. The exception indicates that this program has been corrupted in memory, resulting in the immediate termination of the program. 14(Oeh)=Page Fault Occurs when a paging protection rule is violated (when the retrieve fails, data retrieved is invalid or the code that issued the fault broke the protection rule for the processor). 16(10h)=Coprocessor error fault Occurs when an unmasked floating-point exception has signaled a previous instruction. 17(11h)=Alignment Check Fault Only used on 80486 computers. Caused when code executing at ring privilege 3 attempts to access a word operand that is not divisible by four, or a long real or temp real whose address is not divisible by eight. Note: It is not upcoming to randomly experience a General Protection Fault (GPF), you should not need to troubleshoot GPF errors unless they are occurring frequently. Short for General Protection Fault, GPF is an error message generated Windows indicating that a program has attempted to access a portion of memory that is either invalid or already in use. This error often forces the user to exit the application or reboot their system. As an integral part of Windows, GPF message cannot be disabled. Remove all TSRs Disable or unload any TSRs or programs currently running before running the program causing the GPF. Delete all program temporary files Delete all temporary files that may still be residing on the hard drive from currently or previously running programs. Run ScanDisk and Defrag Run ScanDisk and run Defrag on the hard drive as it could be possible your hard drive may have an issue causing the swap file or data files to become corrupt or invalid. Verify your computer has more than 200 MB available If your computer is running low on hard drive space, your Windows swap file will be unable to increase in size when needed. This situation can cause programs to be swapped between memory and the hard drive more frequently, which can lead to more GPFs. Recently installed software or hardware If you have recently installed new software or hardware uninstall or reinstall that software or hardware to verify it is not causing your issue. Disable external cache If your CPU utilizes external cache disable it temporarily to verify if it is causing your GPF error messages. If this option is available it can be disabled through CMOS Setup. If this resolves your issue it is recommended that you contact the manufacturer of your computer, motherboard manufacturer, or CPU manufacturer for additional recommendations. Disable Power Management and screen savers If you are receiving GPFs when the computer is inactive for extended periods, disable Power Management and screen savers to ensure that they are not causing your issue. Operating System issue Windows related files can cause a General Protection fault. For example, a General Protection Fault with Explorer and KRNL386.EXE. Reinstall Windows to resolve the issue with Windows related files. Because of the wide variety of computer and BIOS manufacturers over the evolution of computers, there are numerous ways to enter the BIOS or CMOS Setup. Below is a listing of most of these methods, as well as other recommendations for entering the BIOS setup. New computers Computers manufactured in the last few years allow you to enter the BIOS setup using one of the five keys shown below during the boot process. ◦ ◦ ◦ ◦ ◦ F1 F2 * F10 ** DEL ESC * If pressing F2 opens a diagnostics tool, your setup key is likely F10 ** F10 is also used for the boot menu. If F10 opens a boot menu, your setup key is likely F2. Setup keys are to be pressed as the computer is booting up. Most users will see a message similar to the example below upon startup. Some older computers may also display a flashing block to indicate when to press the F1 or F2 keys. Once you have successfully entered the CMOS setup, you should see a screen similar to the example below. Your CMOS setup may look a little different, depending on the manufacturer, but should still have most of the same options in the menu on the left or along the bottom of the screen. How do I change and save changes in CMOS setup? Once in CMOS setup, the method for changing the settings often depends on the BIOS manufacturer. You may use the arrow keys along with the Enter key to select categories and change their values. Some manufacturers may have you press the Page up and Page down keys to change the values. I cannot change the values to a setting I want to use. If you are trying to change the clock, speed, or other settings and do not have the option available, it is because it is not supported by the motherboard. If you believe it should be supported, you may need a BIOS update. Tip: If changes you made appear to revert back to default settings or the date and time setting in the BIOS keeps falling behind, you may need to replace the CMOS battery. How do I save the changes? If any changes are made, you need to save those changes, which is typically done by pressing the F10 key on the keyboard. If F10 does not work, look at the bottom or top of the screen for the key that is used to save the settings. Note: If you're getting a runtime error with a runtime error code and error message (e.g. "Runtime error 75 path/file access error"), skip to the runtime error listing for a listing of runtime error codes and errors. Microsoft Windows Runtime errors can be caused by a lot of different problems with the computer. Follow the steps below to help find and fix all Runtime errors. Confliction with TSR or other running program If you are encountering a runtime error message while in Windows or above ensure that the issue is not being caused by a third-party program or TSR by end tasking all open programs. If after "end tasking" all TSRs you continue to experience the same issue under Windows 95 or Windows 98, check autoexec.bat and config.sys for any programs being loaded that may be causing your issue. Then, temporally disable these programs by renaming the files. Follow the instructions below for more information. Boot to an MS-DOS prompt. Once at the MS-DOS prompt, type: cd\ <press enter> ren autoexec.bat autoexec.ch <press enter> ren config.sys config.ch <press enter> Once completed, reboot the computer. Software issue If your issue persists the program, utility, or game causing the runtime error may have issues. Verify through the developer's website that all updates or patches that may be available have been downloaded and applied. If no patches or updates are available, uninstall, and reinstall the program that is causing the issue. If you are having a runtime error in your operating system, reinstall the operating system. Add-on, plug-in, or other extra software Many runtime errors are also caused by other add-ons, plug-ins, or other extra software that has been installed onto the computer and is associated with the program generating the error. If you have any additional software associated with the program causing the error, update or uninstall it, and see if that resolves the issue. Computer virus Because computer viruses and malware can tamper with the system settings or memory it can cause a runtime error. If you are currently running a virus protection program on your computer ensure it has the latest updated patch or .dat file. If you do not have a computer virus protection program it is recommended one be purchased or that a demo be temporarily downloaded to scan your computer hard drive for viruses. Memory issue Finally, if you have followed all of the above recommendations and are still getting runtime errors, you may be encountering a hardware or memory related issue. We recommend that you first contact the developer of the program causing the issue for any possible solutions. If no solutions are found, we recommend you contact the computer or motherboard manufacturer for additional recommendations or service. Runtime error listings Below is a listing of Microsoft Windows and Windows software runtime error codes and related Runtime error messages. Each error has additional information on the cause of the Runtime error and how to fix the problem. Get to a Command Prompt in Windows 10 Click Start. Type cmd and press enter. Notice: For some commands and options to work in the Windows Vista and 7 command line you must run the command line as administrator. To do this, right-click on the cmd icon and choose Run as administrator. Get to a Command Prompt in Windows 8 From the Start screen type cmd and press enter. or Move the mouse cursor to the very bottomleft corner of the screen and right-click or press Windows key + X. In the power user task menu, select either Command Prompt or Command Prompt (Admin). Get to a Command Prompt in Windows Vista and 7 Click Start. Type cmd and press enter. Notice: For some commands and options to work in the Windows Vista and 7 command line you must run the command line as administrator. To do this, right-click on the cmd icon and choose Run as administrator. This document covers the basic in navigating and using the Microsoft Windows command line. On this page, you'll learn how to move around in the command line, find files, manipulate files, and other important commands. Keep in mind that there are over 100 different commands that have been used in MS-DOS and the Windows command line. If you are interested in learning every command, see our Microsoft DOS and command prompt help page, which gives a description and example for every command. Understanding the prompt After following the above steps, the Windows command line should be shown (similar to the example below). Typically Windows starts you at your user directory. In the example below, the user is Mrhope, so our prompt is C:\Users\Windows>. This prompt tells us we are in the C: drive (the default drive letter of the hard drive) and currently in the Mrhope directory, which is a subdirectory of the Users directory. Key tips MS-DOS and the Windows command line are not case sensitive. The files and directories shown in Windows are also found in the command line. When working with a file or directory with a space, surround it in quotes. For example, My Documents would be "My Documents." Filenames can have a long file name of 255 characters and a 3 character file extension. When a file or directory is deleted in the command line, it is not moved into the Recycle Bin. If you need help with any of command type /? after the command. For example, dir /? would give the options available for the dir command. Listing the files Let's learn your first command. Type dir at the prompt to list files in the current directory. You should get an output similar to the example image below. Without using any dir options this is how dir output appears. As can be seen, you are given lots of useful information including the creation date and time, directories (<DIR>), and the name of the directory or file. In the example below, there are 0 files listed and 14 directories as indicated by the status at the bottom of the output. Every command in the command line has options, which are additional switches and commands that can be added after the command. For example, with the dir command you can type dir /p to list the files and directories in the current directory one page at a time. This switch is useful to see all the files and directories in a directory that has dozens or hundreds of files. Each of the command options and switches is listed on our DOS command page. For example, if you want to see all the options for dir see our dir command page for a full listing. The dir command can also be used to search for specific files and directories by using wildcards. For example, if you only wanted to list files or directories that begin with the letter "A" you could type dir a* to list only the AppData directory, in this above example. Moving into a directory Now that we've seen a list of directories (shown below) in the current directory move into one of those directories. To move into a directory, we use the cd command, so to move into the Desktop type cd desktop and press enter. Once you've moved into a new directory the prompt should change, so in our example, the prompt is now C:\Users\Mrhope\Desktop>. Now in this desktop directory, see what files are found in this directory by typing the dir command again. Understand the files Now in the Desktop directory in this example (as shown above), we now have 23 files and 7 directories. As can be seen in the above example, there are many different file types. In Windows, you are familiar with files having icons that help represent the file type. In the command line, the same thing is accomplished by the file extensions. For example, "forum posts.txt" is a text file because it has a .txt file extension, Time.mp3 is an MP3 music file, and minecraft.exe is an executable file. For most users, you'll only be concerned with executable files, which as mentioned above is a file that ends with .exe and are also files that end with .com and .bat. When the name of these files are typed into the command line, the program runs, which is the same as double-clicking a file in Windows. For example, if we wanted to run minecraft.exe typing "minecraft" at the prompt runs that program. If you want to view the contents of a file, most versions of the command line use the edit command. For example, if we wanted to look at the log file hijackthis.log we would typeedit hijackthis.log at the prompt. For 64-bit versions of Windows that do not support this command you can use the start command, for example, type start notepad hijackthis.log to open the file in Notepad. Further information about opening and editing a file from the command line can also be found on the link below. Moving back a directory You learned earlier the cd command can move into a directory. This command also allows you to go back a directory by typing cd.. at the prompt. When this command is typed you'll be moved out of the Desktop directory and back into the user directory. If you wanted to move back to the root directory typing cd\ takes you to the C:\> prompt. If you know the name of the directory you want to move into, you can also type cd\ and the directory name. For example, to move into C:\Windows> type cd\windows at the prompt. Creating a directory Now with your basic understanding of navigating the command line let's start creating new directories. To create a directory in the current directory use the mkdir command. For example, create a directory called "test" by typing mkdir test at the prompt. If created successfully you should be returned to the prompt with no error message. After the directory has been created, move into that directory with the cd command. Switching drives In some circumstances, you may want to copy or list files on another drive. To switch drives in the Windows command line, type the letter of the drive followed by a colon. For example, if your CD-ROM drive was the D drive you would type d: and press enter. Creating a new file You can create a new file from the command line using the edit command, copy con command, or using the start command to open a file. With the edit command edit myfile.txt <press enter> If available, this should open the edit editor. Once you have typed the information for the file myfile.txt, click File and choose exit. If you do not have a mouse, see the edit command page. When clicking exit, the computer will prompt you if you want to save the file, click Yes and the file will be created. With copy con command copy con myfile.txt <press enter> Upon executing the above command, the cursor moves down one line to a blank line, allowing you to create the new file line by line. Once you are ready to create the file, press Enter to get to a blank line, press and hold Ctrl, press Z, and then let go of both keys. This returns a ^Z. Once this has been entered, press Enter to save the file and exit it. With the start command start notepad myfile.txt <press enter> The Windows Notepad and any text editor can also be started to create a file from the command line. Entering the above command would use the start command to run Notepad and create the myfile.txt. Once the file was saved in notepad that file would be created in the same directory as the command. Creating a new batch file In the new test directory let's create your first file. In most circumstances, you never need to create any file at the command line, but it is still good to understand how files are created. In this example, we are creating a batch file. A batch file is a file that ends with .bat and is a file that can help automate frequently used commands in the command line. We are calling this batch file "example", so type edit example.bat at the prompt. As mentioned in the document on creating a file, if the edit command does not work with your version of Windows, use the start command to open the batch file in Notepad. To perform this action, you type start notepad example.bat into the prompt. Both of the above commands open a new blank example.bat window. In the file, type the below three lines, which clear the screen with the cls command and then run the dir command. @echo off cls dir After these three lines have been typed into the file save and exit the file. If you are in the edit command click File (or press Alt+F) and then Save. After the file has been saved and you are back into the command prompt, typing dir should display the example.bat in the test directory. Now run the batch file to get a better understanding of what a batch file does. To run the batch file type example at the prompt, which executes the batch file and clears the screen and then runs the dir command to display the directory listing of the test directory. Moving and copying a file Now that we've created a file let's move it into an alternate directory. To help make things easier, create another directory for the files. So, type mkdir dir2 to create a new directory in the test directory called dir2. After the new directory has been created, use the move command to move the example.bat file into that directory. To do this type move example.bat dir2 at the prompt, if done successfully you should get a message indicated the file was moved. You could also substitute the move command for the copy command to copy the file instead of moving it. Rename a file After the file has been moved into the dir2 directory, move into that directory with the cd command to rename the file. In the dir2 directory use the rename command to rename the example file into an alternate name. Type rename example.bat first.bat at the prompt to rename the file to first.bat. Now when using the dir command you should see the first.bat as the only file. Deleting a file Now that we've had our fun with our new file, delete the file with the del command. Typedel first.bat to delete the first.bat file. If successful, you are returned to the prompt with no errors and the dir command shows no files in the current directory. Renaming a directory Go back one directory to get back into the test directory by using the cd.. command mentioned earlier. Now rename our del2 directory to something else using the same rename command we used earlier. At the prompt, type rename dir2 hope to rename the directory to hope. After this command has been completed, type dir and you should now see one directory called hope. Removing a directory While still in the test directory, remove the hope directory by using the rmdir command. At the prompt, type rmdir hope to remove the hope directory. Closing or exiting the command line window After you are done with the Windows command line, you can type exit to close the window. All command list at: http://www.computerhope.com/msdos.htm