BIOS/UEFI Bios Beeps/stop errors/ network ect...

Status
Not open for further replies.

Dutcho

VIP POOF
VIP Member
Joined
May 27, 2001
Messages
20,834
Likes
83
#1
Ment to do this ages ago, I know I can never remember them....


Below is a table of the most common AMI, Phoenix and Award BIOS beep codes.

AMI (American Megatrends International) BIOS Beep Codes.
AMI BIOS uses beeps of the same length and pitch. The error is displayed as a number of beeps. For example, 4 beeps indicated a timer failure.
BEEP CODE MEANING POSSIBLE CAUSE
1 Beep (No video) Memory refresh failure Bad memory
2 Beeps Memory parity error Bad memory
3 Beeps Base 64K mem failure Bad memory
4 Beeps Timer not operational Bad motherboard
5 Beeps Processor error Bad processor
6 Beeps 8042 Gate A20 failure Bad CPU or Motherboard
7 Beeps Processor exception Bad processor
8 Beeps Video memory error Bad video card or memory
9 Beeps ROM checksum error Bad BIOS
10 Beeps CMOS checksum error Bad motherboard
11 Beeps Cache memory bad Bad CPU or motherboard



Award BIOS Beep Codes
Award BIOS uses beeps of varying duration. A long beep will typically last for 2 seconds while a short beep will last only 1 second. Award BIOS also uses beeps of different frequency to indicate critical errors. If an Award BIOS detects that the CPU is overheating it may play a high pitched repeating beep while the computer is running.
BEEP CODE MEANING POSSIBLE CAUSE
1 Long, 2 Short Video adapter failure Bad video adapter
Repeating (Endless loop) Memory error Bad memory or bad connection
1 Long, 3 Short Video adapter failure Bad video adapter or memory
High freq. beeps (while running) CPU is overheating CPU fan failure
Repeating High, Low beeps CPU failure Bad processor



Phoenix BIOS Beep Codes
Phoenix BIOS uses beep code patterns to indicate problems. In the table below the '-' indicates a brief pause between beeps.
Example: 1 - 1 - 2 would sound like BEEP <pause> BEEP <pause> BEEP BEEP

BEEP CODE MEANING POSSIBLE CAUSE
1 - 1 - 2 CPU / motherboard failure Bad CPU / motherboard
1 - 1 - 3 CMOS read/write failure Bad motherboard
1 - 1 - 4 BIOS ROM failure Bad BIOS chip
1 - 2 - 1 Timer failure Bad motherboard
1 - 2 - 2 DMA failure Bad motherboard
1 - 2 - 3 DMA failure Bad motherboard
1 - 3 - 1 Memory refresh failure Bad memory
1 - 3 - 2 64K memory failure Bad memory
1 - 3 - 3 64K memory failure Bad memory
1 - 3 - 4 64K memory failure Bad memory
1 - 4 - 1 Address line failure Bad memory
1 - 4 - 2 Parity error Bad memory
1 - 4 - 3 Timer failure Bad motherboard
1 - 4 - 4 NMI port failure Bad motherboard
2 - 1 - 1 64K memory failure Bad memory
2 - 1 - 2 64K memory failure Bad memory
2 - 1 - 3 64K memory failure Bad memory
2 - 1 - 4 64K memory failure Bad memory
2 - 2 - 1 64K memory failure Bad memory
2 - 2 - 2 64K memory failure Bad memory
2 - 2 - 3 64K memory failure Bad memory
2 - 2 - 4 64K memory failure Bad memory
2 - 3 - 1 64K memory failure Bad memory
2 - 3 - 2 64K memory failure Bad memory
2 - 3 - 3 64K memory failure Bad memory
2 - 3 - 4 64K memory failure Bad memory
2 - 4 - 1 64K memory failure Bad memory
2 - 4 - 2 64K memory failure Bad memory
2 - 4 - 4 64K memory failure Bad memory
2 - 4 - 4 64K memory failure Bad memory
3 - 1 - 1 Slave DMA failure Bad motherboard
3 - 1 - 2 Master DMA failure Bad motherboard
3 - 1 - 3 Interrupt controller failure Bad motherboard
3 - 1 -4 Slave IC failure Bad motherboard
3 - 2 -2 Interrupt Controller failure Bad motherboard
3 - 2 - 3 <RESERVED>
3 - 2 - 4 Keyboard control failure Bad motherboard
3 - 3 - 1 CMOS batter failure Bad CMOS battery
3 - 3 - 2 CMOS configuration error Incorrect setting
3 - 3 - 3 <RESERVED>
3 - 3 - 4 Video memory failure Bad video card or memory
3 - 4 - 1 Video init failure Bad video card or memory
4 - 2 - 1 Timer failure Bad motherboard
4 - 2 - 2 CMOS shutdown failure Bad motherboard
4 - 2 - 3 Gate A20 failure Bad motherboard
4 - 2 - 4 Unexpected interrupt Bad processor
4 - 3 - 1 RAM test failure Bad memory
4 - 3 - 3 Timer failure Bad motherboard
4 - 3 - 4 RTC failure Bad motherboard
4 - 4 - 1 Serial port failure Bad motherboard
4 - 4 - 2 Parallel port failure Bad motherboard
4 - 4 - 3 Coprocessor failure Bad motherboard or CPU.
9 - 2 - 1 Video adapter incompatibility Use a different brand of video card
Useful sites
Bios - BIOS Central




How to get SYSTEM Privileges in Windows, Thanks to Nizzex


If you open your task manager (ctrl + alt + del) and look at the processes, you will notice that different processes are being run by different users. Some of these processes will be the user you are logged in as, some are local services, network services, and some are run by the system. Now try ending a process run by the system… You will get an error saying access denied. What does this mean? It means that even though you may be admin, you are not the most privileged user on your computer, the system is. Once we become the system, we will be able to access ANY folder, registry entry, etc, but you will be also be able to kill any system task which can be antivirus, VNC, deepfreeze, etc.

How do we do it?
Alright, the windows task manager ends programs and processes, but what most people don’t know is that it can also start them. It starts the new processes under the user who it is being run by. You can see this by looking at the taskmgr.exe process; it is being run by you. So in order to start processes as system we must start the task manager as system, and once we do that we can start a new explorer.exe process which will give us full access to ANYTHING. In order to start the task manager under system we must use the windows scheduler. The scheduler is a built in windows program that allows you to run any program at any time.

1. Hit Start -> Run
2. Type “at XX:XX /interactive taskmgr” in the box (without the quotes) where XX:XX is the time one minute ahead of the clock, but in military time. So lets say that it is 4:15 pm. You would type 16:16
3. When 4:16 comes around the task manager will open. What is different? it is now being run by the system, you can check this in the process tab.
4. Kill the explorer process
5. Click File -> New Task and in the box type explorer.exe
6. Your windows should now start loading up again
7. Once it does, look at the user who is logged in at the start menu… SYSTEM… look at explorer.exe in the task manager.. SYSTEM

You now have full access to the computer to do whatever the hell you want.
 
Last edited by a moderator:

damage

Inactive User
Joined
Aug 9, 2001
Messages
9,419
Likes
1
#2
Windows Stop Errors explained thanks to dutcho
Windows Stop Errors

Windows Stop Errors or Blue screen of death, (BSOD) are generated when windows experiences a fault from which it cannot recover. They are a feature of all Microsoft NT based operating systems e.g. NT, Windows 2000 and Windows XP.
The purpose of the stop error is to help you to troubleshoot problems with your system. The stop error is usually written in hex, for example 0x0000000A this can also be shortened to 0xA.

Causes of Stop Errors

Many things can cause stop errors, hardware and software, fortunately the Stop error describes the error and can be used to determine the cause. The probability of these errors also increases when you overclock your PC.
Below is a list of Stop errors, it is in no way a definitive list but hopefully deals with the more common stop errors.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

When people see this error, they see the IRQ part and assume that this must be caused by an IRQ conflict. This is not the case. It is caused when a kernel mode process or, more commonly, a driver attempts to access memory that it shouldn’t. If you receive this error, you should be thinking about the drivers you have installed. Are they certified to work by Microsoft?

0x0000007B: INACCESSIBLE_BOOT_DEVICE

This one is more self-explanatory. Windows cannot boot from the selected device. You will need to check that the drivers for your hard disk controller are loaded if you’re are using an onboard or external raid controller or if you are using a SCSI card. If you cannot boot the PC, move the hard disk to a standard IDE controller, boot and then install the correct drivers.

0x000000C2: BAD_POOL_CALLER

Again a kernel mode process or driver performed an illegal memory operation. Check for any recently installed drivers, which could be causing the problem.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

A hardware or software component attempted to access a memory address which does not exist or the data it was attempting to access does not exist. This can also be caused by defective memory and can also be caused by pushing the memory too far when overclocking.

0x00000076: PROCESS_HAS_LOCKED_PAGES and
0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS

This is also caused by drivers. A driver uses allocated memory but doesn’t free up the memory correctly after its operation.

0xC0000218: UNKNOWN_HARD_ERROR

A registry hive could not be loaded. You will need to restore the registry. This can happen if the registry data on your hard disk gets corrupted or if when loading the registry into memory it gets corrupted. This is usually hardware related.

0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

This Stop message indicates that a kernel-mode process tried to execute an incorrect or unknown processor instruction. This error handler is a default error handler that catches errors not associated with other specific error handlers. This can be caused by drivers or possibly a hardware problem.

What to do after a stop error?

There are several options after you receive a stop error, depending on which operating system you use and how well prepared you are. A lot of the time you may be able to let the pc reboot as normal and everything will be fine, sometimes it won’t. When you receive a stop error, switch off your pc when it reboots and consider your options. These are the options:

Last known good configuration (NT/Windows 2000/Windows XP)

This is a “one shot” method. If immediately after you receive the stop error you select last known good configuration from the advanced start up options, windows will use a copy of the registry from the previous reboot. This only works once, if you reboot without it the old version of the registry will be overwritten with the version you were using when the blue screen occurred. The disadvantage to this is that any applications or drivers you have installed since the last reboot will be lost.

intresting site with some more info [DLMURL]http://aumha.org/win5/kbestop.php[/DLMURL]
 
Last edited by a moderator:

Dutcho

VIP POOF
VIP Member
Joined
May 27, 2001
Messages
20,834
Likes
83
#3
Run Commands.

dxdiag = direct x diagnostic tool

msconfig = sort out startup problems

ipconfig/all - gives you details of you network card inc ip address

regedit
+
regedit32

for modifying registry - please backup and take extra care when dealing with reg settings......

cmd
opens a command prompt window on Win2K/XP systems.
Then type
help
displays a list of all the 'old style'/DOS like commands you can use, such as xcopy, ren etc etc.


For more information on a specific command, type HELP command-name
ASSOC Displays or modifies file extension associations.
AT Schedules commands and programs to run on a computer.
ATTRIB Displays or changes file attributes.
BREAK Sets or clears extended CTRL+C checking.
CACLS Displays or modifies access control lists (ACLs) of files.
CALL Calls one batch program from another.
CD Displays the name of or changes the current directory.
CHCP Displays or sets the active code page number.
CHDIR Displays the name of or changes the current directory.
CHKDSK Checks a disk and displays a status report.
CHKNTFS Displays or modifies the checking of disk at boot time.
CLS Clears the screen.
CMD Starts a new instance of the Windows command interpreter.

COLOR Sets the default console foreground and background colors.

COMP Compares the contents of two files or sets of files.
COMPACT Displays or alters the compression of files on NTFS partitions.

CONVERT Converts FAT volumes to NTFS. You cannot convert the
current drive.

COPY Copies one or more files to another location.
DATE Displays or sets the date.
DEL Deletes one or more files.
DIR Displays a list of files and subdirectories in a directory.
DISKCOMP Compares the contents of two floppy disks.
DISKCOPY Copies the contents of one floppy disk to another.
DOSKEY Edits command lines, recalls Windows commands, and creates macros.

ECHO Displays messages, or turns command echoing on or off.
ENDLOCAL Ends localization of environment changes in a batch file.
ERASE Deletes one or more files.
EXIT Quits the CMD.EXE program (command interpreter).
FC Compares two files or sets of files, and displays the differences between them.

FIND Searches for a text string in a file or files.
FINDSTR Searches for strings in files.
FOR Runs a specified command for each file in a set of files.
FORMAT Formats a disk for use with Windows.
FTYPE Displays or modifies file types used in file extension associations.

GOTO Directs the Windows command interpreter to a labeled line in a batch program.

GRAFTABL Enables Windows to display an extended character set in graphics mode.

HELP Provides Help information for Windows commands.
IF Performs conditional processing in batch programs.
LABEL Creates, changes, or deletes the volume label of a disk.
MD Creates a directory.
MKDIR Creates a directory.
MODE Configures a system device.
MORE Displays output one screen at a time.
MOVE Moves one or more files from one directory to another directory.
PATH Displays or sets a search path for executable files.
PAUSE Suspends processing of a batch file and displays a message.
POPD Restores the previous value of the current directory saved by PUSHD.
PRINT Prints a text file.
PROMPT Changes the Windows command prompt.
PUSHD Saves the current directory then changes it.
RD Removes a directory.
RECOVER Recovers readable information from a bad or defective disk.
REM Records comments (remarks) in batch files or CONFIG.SYS.
REN Renames a file or files.
RENAME Renames a file or files.
REPLACE Replaces files.
RMDIR Removes a directory.
SET Displays, sets, or removes Windows environment variables.
SETLOCAL Begins localization of environment changes in a batch file.
SHIFT Shifts the position of replaceable parameters in batch files.
SORT Sorts input.
START Starts a separate window to run a specified program or command.
SUBST Associates a path with a drive letter.
TIME Displays or sets the system time.
TITLE Sets the window title for a CMD.EXE session.
TREE Graphically displays the directory structure of a drive or path.
TYPE Displays the contents of a text file.
VER Displays the Windows version.
VERIFY Tells Windows whether to verify that your files are written
correctly to a disk.
VOL Displays a disk volume label and serial number.
XCOPY Copies files and directory trees.


heres one for 98-ME

winipcfg

this shows u all ur stuff that u would find in the ipconfig/all in the dos mode and puts it in a nice GUI regarding network peripherals and boradband

heres one for 98-ME

winipcfg

this shows u all ur stuff that u would find in the ipconfig/all in the dos mode and puts it in a nice GUI regarding network peripherals and boradband

ping -n 999 -w 1 (cmd -ping 999 times with a 1second time out)
net send ip/hostname (cmd -fun/annoying messages)
services.msc (run -stop/start services)

this is XP PRO only.

Group Policy Editor
type "gpedit.msc" at the run prompt.
allows you to set all sorts of options from the desktop setting to security.

IF your PC gets a little confused and windows stop responding - or if you want quicker access to control panel apps - try the following commands to access control panel settings.

Open a Run window and type -

Control panel tool Command
-----------------------------------------------------------------
Accessibility Options control access.cpl
Add New Hardware control sysdm.cpl add new hardware
Add/Remove Programs control appwiz.cpl
Date/Time Properties control timedate.cpl
Display Properties control desk.cpl
FindFast control findfast.cpl
Fonts Folder control fonts
Internet Properties control inetcpl.cpl
Joystick Properties control joy.cpl
Keyboard Properties control main.cpl keyboard
Microsoft Exchange control mlcfg32.cpl
Microsoft Mail Post Office control wgpocpl.cpl
Modem Properties control modem.cpl
Mouse Properties control main.cpl
Multimedia Properties control mmsys.cpl
Network Properties control netcpl.cpl
NOTE: In Windows NT 4.0, Network
properties is Ncpa.cpl, not Netcpl.cpl
Password Properties control password.cpl
PC Card control main.cpl pc card (PCMCIA)
Power Management (Windows 95) control main.cpl power
Power Management (Windows 98) control powercfg.cpl
Printers Folder control printers
Regional Settings control intl.cpl
Scanners and Cameras control sticpl.cpl
Sound Properties control mmsys.cpl sounds
System Properties control sysdm.cpl

Users control Ncpa.cpl users

for win 95/98 and ME control inetcpl.cpl users
 

Dutcho

VIP POOF
VIP Member
Joined
May 27, 2001
Messages
20,834
Likes
83
#4
Try this if you want to diable windows messenger
RunDll32 advpack.dll,LaunchINFSection %windir%\INF\msmsgs.inf,BLC.Remove

here is a fun one

go to run and type in cmd and hit enter

and then hopefully if ur network supports it then type

net send * [message]

it will send the message to all the computers on ur network! lolz

but problem is, you can get into truouble. so u can replace the * with the computer u wanna send it to. to findout the computer name u wanna send it to u wither type net view on ur computer, or go to ur mates computer and type hostname to see their computer name

and then type

net send [computer] [message]


Netstat command expanded
I use this method to manualy look for programs connected or trying to connect to the internet.

type;

-------------------------------------------------------------------------
'Netstat' for a basic look at internet connections in URL format.

'Netstat -a' for detailed view of internet connections in URL format.

'Netstat -n' for a more compacted view of net conns in IP address format.

'Netstat -o' to view in URL format with PID number.
-------------------------------------------------------------------------

and you can use combinations, like my favourite 'Netstat -n -o' to list net connections in IP address format with PID number displayed aswell.


PID Number
PID stands for Program ID. This is an ID number windows issues a program when it is executed (running).

Using the above netstat command combo, we can see what program is tring to connect to the net.

1. Open CMD and type 'netstat -n -o' and you wil notice at the end of every ip address is a PID number.

2. Now bring up Task Manager (Ctrl + Alt + Del) & press the Processes Tab.

3. You need to view the PID column, so if you cant see it goto View > Select Columns & tick PID. Press ok.

4. Now you can go back to the DOS window, look at a connection and mentaly note down the PID number and then look for it in the PID column in Task Manager to see what program is making that connection.



Accessibility Controls access.cpl
Add Hardware Wizard hdwwiz.cpl
Add/Remove Programs appwiz.cpl
Administrative Tools control admintools
Automatic Updates wuaucpl.cpl
Bluetooth Transfer Wizard fsquirt
Calculator calc
Certificate Manager certmgr.msc
Character Map charmap
Check Disk Utility chkdsk
Clipboard Viewer clipbrd
Command Prompt cmd
Component Services dcomcnfg
Computer Management compmgmt.msc
timedate.cpl ddeshare
Device Manager devmgmt.msc
Direct X Control Panel (If Installed)* directx.cpl
Direct X Troubleshooter dxdiag
Disk Cleanup Utility cleanmgr
Disk Defragment dfrg.msc
Disk Management diskmgmt.msc
Disk Partition Manager diskpart
Display Properties control desktop
Display Properties desk.cpl
Display Properties (w/Appearance Tab Preselected) control color
Dr. Watson System Troubleshooting Utility drwtsn32
Driver Verifier Utility verifier
Event Viewer eventvwr.msc
File Signature Verification Tool sigverif
Findfast findfast.cpl
Folders Properties control folders
Fonts control fonts
Fonts Folder fonts
Free Cell Card Game freecell
Game Controllers joy.cpl
Group Policy Editor (XP Prof) gpedit.msc
Hearts Card Game mshearts
Iexpress Wizard iexpress
Indexing Service ciadv.msc
Internet Properties inetcpl.cpl
IP Configuration (Display Connection Configuration) ipconfig /all
IP Configuration (Display DNS Cache Contents) ipconfig /displaydns
IP Configuration (Delete DNS Cache Contents) ipconfig /flushdns
IP Configuration (Release All Connections) ipconfig /release
IP Configuration (Renew All Connections) ipconfig /renew
IP Configuration (Refreshes DHCP & Re-Registers DNS) ipconfig /registerdns
IP Configuration (Display DHCP Class ID) ipconfig /showclassid
IP Configuration (Modifies DHCP Class ID) ipconfig /setclassid
Java Control Panel (If Installed) jpicpl32.cpl
Java Control Panel (If Installed) javaws
Keyboard Properties control keyboard
Local Security Settings secpol.msc
Local Users and Groups lusrmgr.msc
Logs You Out Of Windows logoff
Microsoft Chat winchat
Minesweeper Game winmine
Mouse Properties control mouse
Mouse Properties main.cpl
Network Connections control netconnections
Network Connections ncpa.cpl
Network Setup Wizard netsetup.cpl
Notepad notepad
Nview Desktop Manager (If Installed) nvtuicpl.cpl
Object Packager packager
ODBC Data Source Administrator odbccp32.cpl
On Screen Keyboard osk
Opens AC3 Filter (If Installed) ac3filter.cpl
Password Properties password.cpl
Performance Monitor perfmon.msc
Performance Monitor perfmon
Phone and Modem Options telephon.cpl
Power Configuration powercfg.cpl
Printers and Faxes control printers
Printers Folder printers
Private Character Editor eudcedit
Quicktime (If Installed) QuickTime.cpl
Regional Settings intl.cpl
Registry Editor regedit
Registry Editor regedit32
Remote Desktop mstsc
Removable Storage ntmsmgr.msc
Removable Storage Operator Requests ntmsoprq.msc
Resultant Set of Policy (XP Prof) rsop.msc
Scanners and Cameras sticpl.cpl
Scheduled Tasks control schedtasks
Security Center wscui.cpl
Services services.msc
Shared Folders fsmgmt.msc
Shuts Down Windows shutdown
Sounds and Audio mmsys.cpl
Spider Solitare Card Game spider
SQL Client Configuration cliconfg
System Configuration Editor sysedit
System Configuration Utility msconfig
System File Checker Utility (Scan Immediately) sfc /scannow
System File Checker Utility (Scan Once At Next Boot) sfc /scanonce
System File Checker Utility (Scan On Every Boot) sfc /scanboot
System File Checker Utility (Return to Default Setting) sfc /revert
System File Checker Utility (Purge File Cache) sfc /purgecache
System File Checker Utility (Set Cache Size to size x) sfc /cachesize=x
System Properties sysdm.cpl
Task Manager taskmgr
Telnet Client telnet
User Account Management nusrmgr.cpl
Utility Manager utilman
Windows Firewall firewall.cpl
Windows Magnifier magnify
Windows Management Infrastructure wmimgmt.msc
Windows System Security Tool syskey
Windows Update Launches wupdmgr
Windows XP Tour Wizard tourstart
Wordpad write
 

Dutcho

VIP POOF
VIP Member
Joined
May 27, 2001
Messages
20,834
Likes
83
#5
;Remove Alexa Spyware (comes built in Windows by default)
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Extensions\{c95fe080-8f5d-11d2-a20b-00aa003c157a}]

;-Enable Remote-Desktop
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Terminal Server]

"fDenyTSConnections"=dword:00000000



;Fix for DSO Exploit that Spybot complains about
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Internet Settings\Zones\0]
"1004"=dword:00000003

[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\Advanced]
"Start_LargeMFUIcons"=dword:00000000

;Make the Windows XP registration with Microsoft unnecessary
[HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\Cu rrentVersion]
"RegDone"="1"

;Disables Preview of Movie file formats (allowing you to move/rename/delete without errors)
[-HKEY_CLASSES_ROOT\.avi\ShellEx]
[-HKEY_CLASSES_ROOT\.mpg\ShellEx]
[-HKEY_CLASSES_ROOT\.mpe\ShellEx]
[-HKEY_CLASSES_ROOT\.mpeg\ShellEx]

;Set IE cache to 20MB, 7 days history
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Internet Settings\5.0\Cache\Content]
"PerUserItem"=dword:00000000
"CachePrefix"=""
"CacheLimit"=dword:00005000

; Messenger
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Messenger]
"Start"=dword:00000002

;This adds the "Open Command Window Here" on the right click menu for folders
[HKEY_CLASSES_ROOT\Directory\shell\cmd]
@="Open Command Window Here"
[HKEY_CLASSES_ROOT\Directory\shell\cmd\command]
@="cmd.exe /k \"cd %L\""
[HKEY_CLASSES_ROOT\Drive\shell\cmd]
@="Open Command Window Here"
[HKEY_CLASSES_ROOT\Drive\shell\cmd\command]
@="cmd.exe /k \"cd %L\""
 

Dutcho

VIP POOF
VIP Member
Joined
May 27, 2001
Messages
20,834
Likes
83
#6
cleanmgr = Disk cleanup utility.
wab = Windows address book
winver = Displays version of windows
wupdmgr = Launches windows update manager
 

The Dentist

VIP Member
VIP Member
Joined
Apr 2, 2006
Messages
8,316
Likes
168
#7
Windows XP Blue Screen of Death STOP Codes

Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL


The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.

Possible Resolutions:

A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.

A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.

If you encounter a Stop 0xA message while upgrading to Windows XPl, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.

Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED

The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause Stop 0x1E messages share similarities with those that generate Stop 0xA errors in that they can be due to invalid memory and access violations. This default Windows XP error handler typically intercepts these problems if error-handling routines are not present in the code itself.

Possible Resolutions:

Stop 0x1E messages typically occur after installing faulty drivers or system services, or they can indicate hardware problems, such as memory and IRQ conflicts. If a Stop message lists a driver by name, disable, remove, or roll it back to correct the problem. If disabling or removing applications and drivers resolves the issue, contact the hardware manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.

If the Stop message mentions the file Win32k.sys, the source of the error might be a third-party "remote control" program. If such software is installed, you might be able to disable it by starting the system in safe mode. If not, use Recovery Console to manually delete the system service file that is causing the problem.

Problems can result from system firmware incompatibilities. Many Advanced Configuration and Power Interface (ACPI) issues can be resolved by updating to the latest firmware.

Other possible causes include insufficient disk space while installing applications or performing certain functions that require more memory. You can free up space by deleting unneeded files. Use Disk Cleanup to increase available disk space. From Recovery Console, remove temporary files (those with .tmp file extensions), Internet cache files, application backup files, and .tmp files generated by Chkdsk.exe or Autochk.exe. You can also choose to install additional applications to another hard disk with more free space or move data files, paging files, and so on.

The problem might be due to a memory leak caused by an application or service that is not releasing memory correctly. Poolmon (Poolmon.exe) helps you to isolate the components that are causing kernel memory leaks. For more information about troubleshooting memory leaks, see Microsoft Knowledgebase articles Q177415, "How to Use Poolmon to Troubleshoot Kernel Mode Memory Leaks," and Q298102, "Finding Pool Tags Used by Third Party Files Without Using the Debugger."

Stop 0x00000024 or NTFS_FILE_SYSTEM

The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.

Possible Resolutions:

Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Autochk in the Application log.

Verify that the tools you use to continually monitor your system, such as virus scanners, backup programs, or disk defragmenters are compatible with Windows XP. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests.
To test hard disk or volume integrity

Method 1:

1. In the Run dialog box, in the Open box type:
cmd

2. Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:
chkdsk drive: /f

Method 2:

1. Double-click My Computer, and then select the hard disk you want to check.
2. On the File menu, click Properties.
3. Click the Tools tab.
4. In the Error-checking box, click Check Now.
5. In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.

If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.

If you are not using the NTFS file system, and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2), Microsoft® Windows® 98, or Microsoft® Windows® Millennium Edition (Me) installed. Do not use tools meant for other operating systems on Windows XP partitions!

Nonpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel.

Stop 0x0000002E or DATA_BUS_ERROR

The Stop 0x2E message indicates a system memory parity error. The cause is typically failed or defective RAM (including motherboard, Level 2 cache, or video memory), incompatible or mismatched memory hardware, or when a device driver attempts to access an address in the 0x8xxxxxxx range that does not exist (does not map to a physical address). A Stop 0x2E message can also indicate hard disk damage caused by viruses or other problems.

Possible Resolutions:

Stop 0x2E is typically due to defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.

Stop 0x2E messages can also occur after installing faulty drivers or system services. If a file name is given, you need to disable, remove, or roll back that driver. Disable the service or application and confirm that this resolves the error. If so, contact the hardware manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.

Hard disk corruption can also cause this Stop message.

The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.

Stop 0x0000003F or NO_MORE_SYSTEM_PTES

The Stop 0x3F message indicates one or more of the following problems:

The system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions.

A faulty device driver is not managing memory properly.

An application, such as a backup program, is improperly allocating large amounts of kernel memory.

Possible Resolutions:

Stop 0x3F messages can occur after installing faulty drivers or system services. If a file name is given, you need to disable, remove, or roll back that driver. Disable the service or application and confirm that this resolves the error. If so, contact the hardware manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.

The system might not actually be out of PTEs, but a contiguous memory block of sufficient size is not available to satisfy a driver or application request. Check for the availability of updated driver or application files and consult the hardware or program documentation for minimum system requirements.

Another cause is excessive demands for system PTE by applications. This situation is more common in server
Caution

o Do not edit the registry unless you have no alternative. The registry editor bypasses standard safeguards, allowing settings that can damage your system, or even require you to reinstall Windows. If you must edit the registry, back it up first...

To increase the number of PTEs allocated in the registry
1. In the Run dialog box, and in the Open box, type: regedit

2. In the registry editor, navigate to the subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\
Session Manager\Memory Management.

3. Double-click on PagedPoolSize and SystemPages to view the value for each entry.

4. If PagedPoolSize is not zero, assign a value of 0.

5. If SystemPages is not zero, assign a value of 40000 for systems with 128 MB (or less) of memory, or 110000 for systems with 128 MB to 256 MB of memory. For systems with more memory, do not increase the SystemPages value above 110000 without contacting Microsoft technical support.

6. Click OK, and then close the registry editor.

7. Restart your computer.

Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA

The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.

Possible Resolutions:

If you added new hardware recently, remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed.

Stop 0x50 messages can also occur after installing faulty drivers or system services. If the file name is listed, you need to disable, remove, or roll back that driver. If not, disable the recently installed service or application to determine if this resolves the error. If this does not resolve the problem, contact the hardware manufacturer for updates. Using updated drivers and software is especially important for network interface cards, video adapters, backup programs, multimedia applications, antivirus scanners, and CD mastering tools. If an updated driver is not available, attempt to use a driver from a similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem.

Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR

The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection.
Possible Resolutions:

Stop 0x77 messages can be caused by bad sectors in the virtual memory paging file or a disk controller error. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, which is an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.

Another cause of Stop 0x77 messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.

The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.

Problems that cause Stop 0x77 messages can also cause Stop 0x7A messages. For more information about Stop 0x7A messages, see "Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR" later in this list.

Stop 0x00000079 or MISMATCHED_HAL

The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the kernel type for the computer do not match. This error most often occurs when ACPI firmware settings are changed. For example, you might install Windows XP on an x86-based computer with the firmware ACPI enable option enabled and later decide to disable it. This error can also result when mismatched single and multi-processor configuration files are copied to the system.

Possible Resolutions:

A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or Hal.dll files. This can occur after manual repairs that involve copying incorrect files to the system. This error also occurs when using mismatched files, such as copying a multiprocessor HAL on to a system using a single-processor kernel (or vice versa). The kernel and HAL files for single-processor and multiprocessor systems are stored on the Windows XP Professional operating system CD using two different file names. For example, the single and multi-processor versions of the kernel, named Ntoskrnl.exe and Ntkrnlmp.exe respectively. Setup copies either Ntoskrnl.exe or Ntkrnlmp.exe to your system as Ntoskrnl.exe. In Recovery Console, you can use the Copy command to copy the correct HAL or kernel files from the CD to the appropriate folder on the hard disk.

If you experience Stop 0x79 messages after changing firmware settings, restore the original settings used during Windows XP Professional Setup.

Because systems that use the ACPI HAL ignore IRQ assignments stored in firmware, you can only manually change IRQ settings for non-ACPI (Standard PC HAL) systems. Some x86-based provide the option to toggle ACPI functionality. To disable or re-enable ACPI, you must change firmware settings and reinstall Windows XP. Because of the numerous registry and system file changes required, you must run Setup again (an upgrade installation does not work).

Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR

The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.

Frequently, the cause of this error can be determined from the second parameter, the I/O status code. Some common status codes are:

0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.

0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks (sectors) on the hard disk.

0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.

0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.

0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination, defective storage controller hardware, or defective disk cabling, or two devices attempting to use the same resources.

Possible Resolutions:

Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix.

Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.

Check the hardware manufacturer's Web site for updates to disk adapter firmware or drivers that improve compatibility. Verify that your disks and controller support the same set of advanced features, such as higher transfer rates. If necessary, select a slower transfer rate if an update is not yet available. Consult your hardware or device documentation for more information.

IMPORTANT
o You can install disk controller drivers not present on the Windows XP Professional operating system CD by responding to the following prompt shortly after starting Setup:

o Press F6 if you need to install a third party SCSI or RAID driver.

o Press F6, and when prompted, provide the appropriate storage controller driver (ATA or SCSI) supplied by the manufacturer.

The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.

Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. For more information about Stop 0x77 messages, see "Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR" earlier in this list.

Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE

The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.

The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:

Disks or storage controllers that are failing, defective, or improperly configured.

Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.

Possible Resolutions:

During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.

Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.

Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.

Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.

Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about 0xED Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this list.

Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP

The Stop 0x7F message indicates that one of three types of problems occurred in kernel-mode:

A condition that the kernel is not allowed to have or intercept (also known as a bound trap).

Software problems.

Hardware failures.

Possible Resolutions:

Stop 0x7F messages are typically due to defective, malfunctioning, or failed memory hardware. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.

Running the CPU beyond the rated specification, known as "overclocking," can cause Stop 0x7F or other error messages due to heat buildup. When diagnosing problems on overclocked systems, first restore all clock and bus speed settings to the manufacturer recommended values to determine if this resolves the issues.

The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.

Stop 0x7F messages can occur after installing incompatible applications, drivers, or system services. Contact the software manufacturer about possible Windows XP specific updates. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.

Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE

The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state.

Possible Resolutions:

Stop 0x9F messages can occur after installing faulty applications or drivers or system services. If a file is listed by name and you can associate it with an application, uninstall the application. For drivers, disable, remove, or roll back that driver to to determine if this resolves the error. If it does, contact the hardware manufacturer for a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.

For information about troubleshooting standby and hibernate mode issues, see KB article Q266169, "How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000."

Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY

The Stop 0xBE message indicates that a driver attempted to write to read-only memory.

Possible Resolutions:

A Stop 0xBE message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

Stop 0xC2 or BAD_POOL_CALLER

The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:

By allocating a memory pool size of zero bytes.
By allocating a memory pool that does not exist.
By attempting to free a memory pool that is already free.
By allocating or freeing a memory pool at an IRQL that was too high.

This Stop message is typically due to a faulty driver or software.

Possible Resolutions:

A Stop 0xC2 messages might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

A Stop 0xC2 messages might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.

If you encounter a Stop 0xC2 message while upgrading to Windows XP, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.

Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT
_CANCELLING_PENDING_OPERATIONS


This Stop messages indicates that a driver failed to cancel pending operations before exiting.

Possible Resolutions:

Stop 0xCE messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL

The Stop 0xD1 messages indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.

Possible Resolutions:

Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER

A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.

Possible Resolutions:

Stop 0xD1 messages can occur after installing faulty drivers (especially video drivers) or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME

The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error might also occur during an upgrade to Windows XP Professional on systems that use higher throughput ATA disks or controllers with incorrect cabling. In some cases, your system might appear to work normally after you restart.

Possible Resolutions:

If using higher throughput ATA disks and controllers, those capable of data transfer rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 megabytes per second, but is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.

Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.

Problems that cause 0xED errors might also cause Stop 0x7B errors. For more information about 0x7B Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" earlier in this appendix.

Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.

Possible Resolutions:

You can use Driver Rollback or System Restore from safe mode, to restore a previous driver. You can also use Windows XP Professional recovery features such as the Last Known Good Configuration startup option, Backup, or Automated System Recovery to restore a previous working configuration. After restoring from backup media, you might need to reapply service packs or hotfixes, depending on when the backups were made.

If the Stop message names the specific file, try replacing it manually with a fresh copy from the Windows XP Professional operating system CD using safe mode or Recovery Console. For systems using the FAT16 or FAT32 file system, you have the option of using a Windows 98 or Windows Millennium Edition Emergency Boot Disk to access the hard disk.
If the original file from the operating system CD has a file name that ends with an underscore (_) character, you cannot use the file until it is uncompressed. The Recovery Console's Copy command is ideal for copying compressed files because it detects and expands them. If you do not specify a destination file name, you must rename the expanded file with the correct extension before using it. From safe mode or Recovery Console, you can use the Expand command to uncompress and copy a file to a destination location. In Recovery Console, the expanded file is given the correct name after being copied to the destination location. For more information about the Copy or Expand commands, see Windows XP Help and Support Center. environments. Windows XP Professional provides a registry entry, SystemPages, that you can use to increase the number of PTEs allocated.
 
Status
Not open for further replies.
TEST
Top