Computer Technicians Quick Reference Guide

Useful DOS Commands:

Networking

ipconfig - Windows IP Configuration

ipconfig will tell you the IP settings for the current computer such as what your current IP is and
what subnet/gateway

you are on. It is great for troubleshooting. Here are the two most useful commands for ipconfig and
usage:

ipconfig /all Views detailed information about the installed network devices.

ipconfig /release - This will release any IP information that the computer was given and make
your IP address 0.0.0.0

ipconfig /renew - This will ask any DHCP servers (usually your modem/router) for a new IP
address.

ping - Check a connection or computer

Ping is used to check the health of a connection. The ping command will tell you whether a network
device is responding

and how fast it is running. The ping tool can also be used to convert a web address into an IP (eg.
www.google.com =

74.125.19.99). Usage:

ping www.google.com - Pings a webserver to see if it can be reached or is responding. I

personally use this to see if the

computer I am on can reach the internet.

ping 192.168.0.1 - Pings a local address, often a modem, router or another computer.

netstat - Displays current TCP/IP connections

netstat - Will display what connections are currently active on the system. Useful for spotting
programs calling back to

base such as spyware.

File Management
type - Open text files

Similar to Unixs cat command, this command will display the contents of a text file in DOS as read-
only. Usage:

type c:\sometextfile.txt

attrib - Make hidden files visible

Attrib can change the attributes of a file, such as whether its a system file or its hidden. This is
especially useful to

technicians because critical files such as the boot.ini is a hidden system file:

attrib -H c:\boot.ini - To unhide the boot.ini

attrib -S c:\boot.ini - To make remove its system file attribute

For more options with this command, type attrib /? find - Advanced file search

The find command is a very powerful one with many options such as the ability to search for
something, but exclude

certain files. The following command will find all files with .pdf in their name on C:\

dir c:\ /s /b | find ".pdf"

For more information in this command and its usage, type find /?

move - Move files

Normal usage of the move command would be:

move file.txt c:\TextFiles\

However, you can also use it to move only certain files. For example, if I wanted to get all the PDFs
out of a folder and

move them to another location, but leave all other file types alone, I would do:

move *.pdf c:\WorkPDFs\

tree - View the tree structure

Type tree to see the folder and file structure of the folder you are currently in. You can also use this
command to make

prints of the directory structure by sending the information to a text file with the following
command tree > textfile.txt

System
systeminfo - Displays information about the system

systeminfo - Will display information about the system such as the name, version, uptime,
specifications and patches

installed (XP Pro only by default).

tasklist / taskkill - Shows what programs are running on the computer and can kill them

tasklist - Will display all the processes running and their memory usage.

taskkill - Will kill a process (XP Pro only by default). Usage would be: taskkill firefox.exe

sfc - Launches Windows system file checker utility

sfc /scannow - This command will start scanning your computer for any damaged or missing
windows system files.

Useful to run after a virus, adware or spyware attack has damaged core files. Have an XP CD handy
for this one.

chkdsk - Can check a disk and attempt to recover data in bad sectors.

chkdsk /f /r - This will check a disk for errors and try and fixes information from bad sectors

chkdsk /x - Forces the volume to dismount first.

For further information/usage on any of these commands, you can bring up the help for each one of
them by typing:

command /?
STOP Messages:

Stop 0x0000000A: IRQL_NOT_LESS_OR_EQUAL - This Windows stop error indicates that a kernal
mode process or driver

tried to access a memory location that it did not have permission to access, or at a IRQL that was
too high (a kernal

mode process can only access a IRQL that is lower than or equal to its own IRQL).

This stop message usually means that there is incompatible or faulty hardware. In personal
experience its usually bad

ram.

Stop 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL - Note the "Driver" part at the start off
the message, this isnt

the same as the error message above - This Windows stop error indicates that the computer tried to
access memory

using a kernal process which had a IRQL that was too high (as kernal processes can only access
IRQLs that it is either

equal to or IRQLs that less than it). This is usually caused by incorrect or incompatible drivers.

Stop 0x00000024: NTFS_FILE_SYSTEM - This Windows stop error typically indicates that a
problem occured with the file

NTFS.sys such is the driver that allows the operating system to read and write to NTFS formatted
harddrives. This can

often be caused by harddrive problems.

Stop 0x000000ED: UNMOUNTABLE_BOOT_VOLUME - This Windows stop error is caused by a

Input/Output sub-system

tried to use the boot volume but failed. This error can occur during an upgrade to Windows XP
Professional on

computers that use faster ATA harddrives or have controllers with the wrong cabling. This can
sometimes be caused by a
failing hard drive.

Stop 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA - This Windows stop error indicates that

information that the

operating system was looking for was not found in memory (ram). This occurs when the system
looks for information in

the ram that doesnt exist. This is usually caused by defective RAM (including Ram on your
motherboard, L2 cache and

video card ram).

Stop 0x0000002E: DATA_BUS_ERROR - This Windows stop error indicates an error in the system
memory. It is caused

when the system tries to access a memory address that doesnt exist. This usually is caused by
defective or failed RAM

(including those on your motherboard, Level 2 case or the memory on your video card). This can
also indicate hard drive

damage caused by viruses or other computer problems.

Stop 0x0000007B: INACCESSIBLE_BOOT_DEVICE - This Windows stop error indicates that

Windows XP Professional is

unable to access the boot volume or system partition of your harddrive during startup.

Installing incorrect drivers for your harddrives or updating the storage adapter hardware usually
causes this error. It is

also possible that the boot volume or system partition was damaged either by hardware failure or a
virus infection.

Stop 0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER - This Windows stop error indicates

that there is a problem with

a device driver (such as the video card driver) that is causing the system to pause indefinitely. This
problem is usually

causes when the video card driver is waiting for the video card hardware to become idle but never
does. This usually

indicates that there is a hardware problem with the video device or the video card driver is faulty.
Stop 0x0000008e: PAGE_FAULT_IN_NON_PAGED_AREA - This is typically caused by faulty RAM
or the RAM

configuration you are running is incompatible with Windows XP.

Stop 0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS - This problem is primarily limited to

Windows 2000 as is

caused by a bad driver called "falstaff.sys". This can be stopped by updating this driver from the
vendor at

http://www.in-system.com

Stop: 0x000000F4 (000000000003, 0xFFFFFADF50, 0xFFFFFADF50EC32A8, etc)

Finally, I took out the CMOS battery (the small round battery on your motherboard), rebooted, then
re-installed it, and rebooted the machine again. It fixed the problem! So this STOP error is related to
either a low CMOS battery or simply having to take it out and put it back in. Next time you add
some new hardware to your computer, you have get this error because the components do not get
configured properly during the install. Removing and reinstalling ensures that the device can
reconfigure correctly with the new hardware.

Other strange errors Ive gotten include The location that you specified does not contain stored
information relating to the File and Settings Transfer Wizard.

IRQL_NOT_LESS_OR_EQUAL (0x000000A)

I just formatted my hard drives and reinstalled Windows. At first, I had tons of problems getting
Windows to install (very random BSODs), and after running Memtest86 on each stick of RAM, I
found a bad stick. So while I'm waiting for an RMA on that....I continued with the Windows
install using 2 sticks of good RAM (I ran Memtest on each of them for about 2 hours). Windows
installed fine, and I've had pretty good luck getting all my software and external devices
reinstalled. However, I'm getting this error a few times a week:

DRIVER_CORRUPTED_EXPOOL ( Stop : 0x000000c5 (0x00000004, 0x00000002,

0x00000001, 0x805446DE)

Was there any software or hardware changes made prior to this issue?

This error stands for DRIVER_CORRUPTED_EXPOOL. This indicates that the system
attempted to access invalid memory at a process IRQL that was too high. It could also be due to
bad drivers. If the issue is caused by any driver, then you need to update it from the
manufacturers website.

You may try these:

Step 1: Unplug all the external devices if any and check if you are able to start the computer.

Step 2: Check if you are able to start the computer in safe mode.

A description of the Safe Mode Boot options in Windows

XP http://support.microsoft.com/kb/315222

Step 3: If you are able to start the computer in safe mode, determine whether a third-party
program or utility is causing the issue

Follow the steps from How to configure Windows XP to start in a "clean boot"
statehttp://support.microsoft.com/kb/310353

Note: Ensure to start the computer normally by following the steps under Steps to configure
Windows to use a Normal startup state.

INVALID_SOFTWARE_INTERRUPT" ( STOP 0x00000007)

The STOP 0x00000007 error may also be abbreviated as STOP 0x7 but the full STOP code will always
be what's displayed on the blue screen STOP message.

If Windows is able to start after the STOP 0x 7 errors, you may be prompted with a Windows has
recovered from an unexpected shutdown message that shows:

STOP 0x00000007 errors are likely caused by hardware or device driver issues.

If STOP 0x00000007 isn't the exact STOP code you're seeing or

INVALID_SOFTWARE_INTERRUPT isn't the exact message, please check my Complete List
of STOP Error Codes and reference the troubleshooting information for the STOP message that
you are seeing.

Important Data Locations:

Outlook Express Emails

C:\Documents and Settings\User Account\Local Settings\Application Data\Identities\{Random

Numbers and

Letters}\Microsoft\Outlook Express Address Book

C:\Documents and Settings\User Account\Application Data\Microsoft\Address Book\User
Account.wab

Microsoft Outlook

C:\Documents and Settings\User Account\Local Settings\Application Data\Microsoft\Outlook

Microsoft Outlook .nk2 Auto-Complete File

C:\Documents and Settings\User Account \Application Data\Microsoft\Outlook Favorites

C:\Documents and Settings\User Account\Favorites My Documents

C:\Documents and Settings\User Account\My Documents Desktop

C:\Documents and Settings\User Account\Desktop

Quickbooks Accounting Package Database - Default Location

C:\Program Files\Intuit\QuickBooks\databasename.qbw

MYOB Accounting Package Database - Default Location

C:\MYOB {version number}\databasename.myo

google chrome can't connect to proxy server and

i can't change lan settings. What do I do?

On Windows XP, click Start, or on Windows Vista or Windows 7, click start, and then click
Run.
In the Run text box, copy (CTRL+C) and paste (CTRL+V) or type the following:
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v
ProxyEnable /t REG_DWORD /d 0 /f
Click OK.
On Windows XP, click Start , or on Windows Vista or Windows 7, click start, and then click
Run.
In the Run text box, copy (CTRL+C) and paste (CTRL+V) or type the following:
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v
ProxyServer /f
Click OK.
 QUICK GUIDE OF ALL HARDWARE ERROR TROUBLE SHOUTING
Trick and simple trouble shouting!!!

FIRST SOLUTION:
This is the message I get when I start up my computer.

NTLDR Is Missing - The NTLDR is missing error displays very shortly after the computer is first started,
immediately after the Power On Self Test (POST) is complete. Windows XP has only initially begun to load
when the NTLDR error message appears.

Causes:

This problem may occur if the basic input/output system (BIOS) on your computer is outdated, or if
one or more of the following Windows boot files are missing or damaged:

Ntldr
Ntdetect.com
Boot.ini

Method 2: Use the Recovery Console

1. Use the Windows xp Setup disks to restart the computer, or use the Windows 2000 CD-ROM
to restart the computer.
2. At the Welcome to Setup screen, press R to repair the Windows xp installation.
3. Press C to repair the Windows xp installation by using the Recovery Console.
4. Type the number that corresponds to the Windows installation that you want to repair, and
then press ENTER. For example, type 1, and then press ENTER. For more information, click
the following article number to view the article in the Microsoft Knowledge Base:

229716 Description of the Windows Recovery Console

5. Type the Administrator password, and then press ENTER.

6. Type map, and then press ENTER. Note the drive letter that is assigned to the CD-ROM drive
that contains the Windows xp CD-ROM.
7. Type the following commands, pressing ENTER after you type each one, where drive is the
drive letter that you typed in step 4 of Method 2: Use the Recovery Console, of this article:

copy drive:\i386\ntldr c:\

copy drive:\i386\ntdetect.com c:\

hit enter then restart your computer hmm done

SECOND SOLUTION:
You need iso files like FIXNTLDR.ISO for the fixed the problem OF YOUR COMPUTER

DOWNLOAD :

Step 2. If you have a working Windows machine download my fix:

(32 BIT Floppy fixntldr.exe |CD-R fixntldriso.zip | USB ntldrusb.zip)

(64 bit WinXP Floppy 64ntflop.exe | CD-R 64ntiso.zip | Files 64ntfile.zip)

You need device like : USB FDD / CD blank

To USB FDD so many tutorial in YouTube so view them.
To CD blank use to nero smart to burn it the file like FIXNTLDR.ISO then run the cd into booting
Change into bios setting to 1st boot priority
Then see the following the start back up data ok !!!

Using the boot disk in the computer with the "NTLDR is missing" error.

Start back up the broken computer with the floppy/cd-r/usb inside it/plugged into it. Once your
computer gets past the BIOS screen your computer should try to access the boot disk and you
should see a black screen with white letters (What if I don't see this screen?). that says:

1ST TRY THIS seleccione esto primero

2ND TRY THIS essayez ceci en deuzieme
3RD TRY THIS wahlen Sie diesen Third
4TH TRY THIS selezioni questo fourth
5TH TRY THIS selecione este fifth
6TH TRY THIS seleccione este sexto
7TH TRY THIS essayez ceci en septieme
8TH TRY THIS wahlen Sie dieses achte
9TH TRY THIS selezioni questo nono
10TH TRY THIS selecione este decimo

Choose 1ST TRY THIS seleccione esto primero < for BYPASS section of error so you see the
LOADING then copy the file into CD then paste into the primary drive like C:/

3rd SOLUTION

NTLDR Is Missing - when ntldr is missing was not found windows xp / 7 in hard disk the
problem is Ram, why? Because the ram are the write and read all booting and windows so many
way the ram is the problem of your computer.. check the software name:
http://www.memtest.org/
 -Error-
This is the message I get when I start up my computer.

Reboot and select proper boot device or

insert boot media in selected - the main problem of this error is a part of HDD or as noon
hard disk so need check all body part like SATA POWER and SATA CONNECTOR or HARD
DISK or maybe SATA SLOT onboard.

HOW TO RESOLVE:
1st to do change one the SATA CONNECTOR check into computer if not respond change the
other SATA POWER then check if not respond again check the HDD then check again if HDD change
HDD then try again the 1st step ok

How to Repair Boot Errors

Remove the non-system disk from your boot device. For example, remove the non-
system disk from the floppy drive or the CD-ROM drive.

Change your computer's boot sequence. Make sure that your computer's first boot
sequence is the CD-ROM Drive.

Insert the Windows XP or Windows 2000 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.

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
must access from the Recovery Console.

When you are prompted, type the Administrator password. If the administrator
password is blank, just press ENTER.

Enter in the following commands: COPY X:\i386\NTLDR C:\ COPY

X:\i386\NTDETECT.COM C:\ [where X=CD ROM Drive].
Enter also the following to check also the boot.ini:
type c:\Boot.ini

If the following message appear "The system cannot find the file or directory specified"
your Boot.ini file maybe missing or damaged. You can replace Boot.ini by creating another
and save to a disk and copy it just like the instruction in number 8 by doing:

COPY X:\Boot.ini c:\

 -Error-
Disk boot failure
This is the message I get when I start up my computer.

- When starting the computer system, a 'disk boot failure - insert system disk' error can occur
for several reasons, including either hardware or software changes. It may also occur if there is a
CD or a diskette in the drive while starting the computer. An incorrect boot sequence, a newly
installed hard drive, an unplugged hard drive or a damaged disk may result in the the disk boot
failure insert system disk error. It is possible to fix the disk boot failure error by restoring the
boot sector in the case of corrupt system files. If the disk is damaged, partitioning the disk and
reinstalling the operating system will solve the problem.

Cause:

This issue could be caused by any of the below possibilities.

1. Boot options are not set properly in CMOS

2. Non bootable disc or USB in computer
3. Remove added hardware and check connections
4. Hard drive is bad

How to resolve:

Boot options are not set properly in CMOS

Verify that the boot options within CMOS Setup are set properly. Below is an example of
how we recommend the boot options be set.

1. Floppy drive
2. CD-ROM drive
3. Hard Drive
4. Other/Network

Non-bootable floppy diskette or disc or USB in computer

Verify that there is no floppy diskette or disc in the computer. If the boot options are set
improperly the computer could be trying to boot from the disc drive instead of the hard
drive.In addition to verifying there is no disc in the computer make sure that no USB jump
drive, external hard drive, or memory stick is inside any memory card reader. If you're
wanting to boot from a floppy diskette, CD, DVD, or USB drive and are getting this error
message and have verified that your CMOS settings are in the proper order as explained in
the above paragraph the diskette or disc you're using is either bad or does not have the
proper files on it to make it bootable.
 -Error-
Unmountable Boot Volume Error
This is the message I get when I start up my computer.

One unfortunately common problem is data corruption on a hard drive and the dreaded
Unmountable Boot Volume error. Many people feel they are forced to format the drive and start
from scratch in this situation. However, frequently there is a better way of save your installation, as
long as you have the installation media available. Directions for both XP and Windows 7 included.

If you receive the unmountable boot volume error and have an installation disk, you still have a
chance to save your system.

This error is frequently caused by unfortunate wear and tear corruption of the data on the hard
drive. By using the following utilities, you often can repair the damaged hard drive and prevent a
complete reinstallation of your system.

Windows XP Directions:

1. Insert your XP installation disc into an optical drive and boot up your computer.
2. When you see a welcome screen, hit the R key on your keyboard. This will enter you into
recovery mode with a DOS prompt.
3. Now type chkdsk /p and hit Enter. This will launch a utility which will check for errors on your
hard drive.
4. After the process is done, type fixboot and hit Enter to repair any damaged boot files which may
have become corrupted. When asked to say yes or no, type the Y key on your keyboard.
5. Type exit and press the Enter key to reboot your computer.

Windows 7 Directions:

1. Boot from the Windows 7 DVD.

2. Select Repair my computer.
3. Select Command Prompt
4. From the command prompt enter the following command: Chkdsk /R C: where C is your boot
drive.
5. Answer Y to check the disk the next time that the system restarts.
6. Reboot the system. After the reboot, Windows will check the hard disk and try to repair the
damaged area.
7. If you still get the error after this process, repeat the process but try rebuilding the master boot
record at the command prompt with the following command: bootrec /fixboot and then rebooting

If your system can be saved, you should now be able to boot back into Windows without a problem!

- See more at: http://www.tech-

recipes.com/rx/2605/fixing_the_dreaded_unmountable_boot_volume_error/#sthash.wVX6e9N9.dp
uf
 -Error-

Read disk error

In rare circumstances setting the BIOS back to defaults can fix the issue. You can usually get to
the BIOS by pressing Del or F2 etc during boot. There should be an option to reset to defaults,
look for an option similar to the one in the picture below. Failing that, you can remove the BIOS
battery for a few minutes to reset. If youre unable to access CMOS because it is password
protected, you can easily reset it from Windows by using CMOS De-Animator.
2nd solution:

Palit cable sata or IDE okay