Common Cause of "Error
performing inpage operation" Explained
Microsoft Knowledge Base Article: 141117 - When
copying files from a diskette on a Windows NT computer,
you may occasionally experience an "Error performing
inpage operation". Error Messages Caused
by Incorrect Serial Port Configuration
Microsoft Knowledge Base Article: 112584 - If
you configure a serial port incorrectly in the
Ports option of Control Panel, there are several
error messages that may appear in Event Viewer
after you restart the computer.
Error Message: Memory
Could Not Be Read...
Microsoft Knowledge Base Article: 262490 - When
you log on to the local console of your Windows
2000-based computer, you may receive the following
error message:
Explanation of "Status
Buffer Overflow" Error
Microsoft Knowledge Base Article: 193839 - Certain
conditions, which can report a network error to
the event log, are caused by a non-destructive
SMB message also known a "Status Message." Most
commonly the error reported in the event log is
network error event 2012.
FIX: "Limited
Virtual Memory" Error Message When You Start Your
Computer
Microsoft Knowledge Base Article: 257758
- When you set the paging file (Pagefile.sys)
on your computer to a size that is lower than
the recommended size of 12 megabytes (MB) plus
the amount of random access memory (RAM), a temporary
paging file (Temppf.sys) may be created, you may
receive the following error message after you
log on: Limited Virtual Memory. Your system is running without
a properly sized paging file. Please use the virtual
memory option of the System applet in the Control
Panel to create a paging file, or to increase
the initial size of your paging file.
Possible Resolutions
to STOP 0x0A, 0x01E, and 0x50 Errors Q183169
-
Microsoft Knowledge Base Article Windows NT computers,
and those built on NT technology, may stop responding
(hang - with one or more of the following STOP
error messages:
STOP Errors When
Running MITAC 6133 Laptop on Battery Power
Microsoft Knowledge Base Article: 250975 - When
you try to run a MITAC 6133 laptop using battery
power, you may receive the following STOP error
messages:
STOP 0xC0000244 When
Security Log Full
If the CrashOnAuditFail registry key is set to
1 and the Security Event log is full on a computer
running Windows NT, the following blue screen
error message may be displayed: STOP:
C0000244 {Audit Failed} An attempt to generate
a security audit failed.
STOP 0x0000000A Errors
A "Stop: 0x0000000a"
Error Occurs After You Install an HP ScanJet 5100c
or 5200c Scanner
Microsoft Knowledge Base Article: 315377 - After
you install a Hewlett-Packard (HP) ScanJet 5100c
or 5200c scanner, you may receive the following
Stop error when you restart your computer:
A "STOP 0xA" Error
Message Occurs When You Use Routing and Remote
Access with NAT and VPN
Microsoft Knowledge Base Article: 318437 - If
you use the Routing and Remote Access feature
of Windows 2000 and you also use virtual private
networking (VPN) and network address translation
(NAT) functionality on the same computer, you
may receive the following error message:
Backup Exec 8.0 May
Cause "Stop 0x0000000A" or Sporadic Reboots
Microsoft Knowledge Base Article: 266196 - Veritas
Backup Exec 8.0 may cause a "Stop 0x0000000A"
error message or sporadic reboots. The stop code
may resemble the following example:
Eject Request May
Cause "Stop 0xA" Error Message
Microsoft Knowledge Base Article: 254611 - When
you request that a device be ejected using the
Add/Remove Hardware tool in Control Panel, you
may receive a "Stop 0xA" error message.
Hotfix from Q259545
causes "Stop 0x0000000A" Error Message in Disk.sys
File
Microsoft Knowledge Base Article: 276409 - After
two or more Fibre Channel adapters are installed
but only one is connected to a single set of disks,
no problems occur. However, after another set
of disks is attached to the second adapter, you
may receive Stop 0xA error message.
"Stop 0x0000000A"
Error Message and Computer Stops Responding When
You Use Dial-up RAS Connection
Microsoft Knowledge Base Article: 321420 - When
you use a dial-up remote access service (RAS)
connection to browse the Internet or to connect
to a corporate network, your computer may stop
responding (hang) and return a Stop error (an
error on a blue screen) similar to the following...
Stop 0x0a Error in
nt!ExpBoostOwnerThread() Occurs on a Large Terminal
Server Installation
Microsoft Knowledge Base Article: 321613 - In
a large Windows Terminal Services installation,
a Windows 2000-based computer under heavy stress
may stop unexpectedly with the following error
message: STOP : 0x0000000a (0x00000063, 0x0000001c,
0x00000000, 0x80415026) The first argument is
typically a low address (for example, 0 + 0x63
= 0x63). The fourth argument is always an address
in the nt!ExpBoostOwnerThread()
function
STOP: 0x0000000A
When You Dual Boot with Windows NT 4.0 on the
Same Partition
Microsoft Knowledge Base Article: 227301 - If
you install Windows 2000 on a partition where
an existing version of Windows NT 4.0 is already
installed, when you boot into the previously installed
version of Windows NT you may receive the following
error message on a blue screen:
"Stop 0xA" Trying
to Reuse a Freed File Handle
Microsoft Knowledge Base Article: 258541 - A Windows
2000-based server that is handling a large amount
of file input/ouput (I/O) operations may generate
a "Stop 0xA" error message. This problem may be
more likely to occur on multiple-processor computers.
"Stop 0x0000000A"
Stop Code on Stressed Servers
Microsoft Knowledge Base Article: 286362 - A stressed
Windows 2000-based server may display the following
stop code on a blue screen: Stop 0x0000000A (0x00000060, 0x0000001c, 0x00000001,
0x8042a04a)
STOP Errors 0x00000023
and 0x0000000A in Fastfat.sys When a Program Queries
the File System
Microsoft Knowledge Base Article: 289205 - When
a program queries for a file name or for volume
information, Windows 2000 may exhibit the following
STOP errors in Fastfat.sys:
Troubleshooting "Stop
0x0A" Messages in Windows NT or Windows 2000
Microsoft Knowledge Base Article: 165863 - This
article discusses how to troubleshoot the following
"Stop" error message in Windows NT or Windows
2000:
STOP 0x000000Ax Errors
"STOP 0x000000A5"
When Installing Windows 2000
Microsoft Knowledge Base Article: 256841 - When
you are installing Windows 2000, you may receive
the following error message: STOP: 0x000000A5 (<Parameter1>, <Parameter2>,
<Parameter3>,<Parameter4>)
The ACPI Bios in this system is not fully compliant
to the specification.Please read the readme.txt
for possible workarounds, or contact your system
vendor for an updated bios.
STOP 0x000000Bx Errors
Err Msg: Stop 0x000000B4
The Video Driver Failed to Initialize
Microsoft Knowledge Base Article: 240369 - After
you install Windows 2000, the following error
message may be displayed when you start your computer:
"STOP 0x000000B4"
or Black Screen During GUI-Mode Setup on Micron
Powerdigm XSU
Microsoft Knowledge Base Article: 250271 - You
may experience either of the following symptoms
at the beginning of GUI-mode Setup:
"Stop 0xB8 ATTEMPTED_SWITCH_FROM_DPC"
Error Message When You Use a Parallel Port Zip
Drive
Microsoft Knowledge Base Article: 281428 - When
your computer tries to access a parallel port
Iomega Zip drive, you may receive the following
error message on a blue screen: STOP:
0x000000B8 (0x00000000,0x00000000,0x00000000,0x00000000)
ATTEMPTED_SWITCH_FROM_DPC address 0xf729a248 in
ppa.sys
Stop 0x000000B8 Error
Occurs in a Windows 2000 Cluster
The cluster node performs a random bugcheck and
you receive either of the following error messages:
STOP 0x00000b8 ATTEMPTED_SWITCH_FROM_DPC
(b8) A wait operation, attach process, or yield
was attempted from a DPC routine. This is an illegal
operation and the stack track will lead to the
offending code and original DPC routine
STOP 0x000000Cx Errors
How to Debug "Stop 0x2C" or "Stop 0x0000002C" Error Messages
Microsoft Knowledge Base Article: 265879 - This
article describes how to debug Stop 2C error and
BAD_POOL_CALLER messages.
"Stop 0xC2 BAD_POOL_CALLER"
Error Message on Print Server
Microsoft Knowledge Base Article: 258069 - A Windows
2000-based print server may randomly stop responding
(hang) with a "Stop" error message on a blue screen.
The stop code is 0xC2, and the first parameter
is always 0x00000007.
"STOP 0x000000c2"
Error Message Appears on a Blue Screen After You
Install IomegaWare
Microsoft Knowledge Base Article: 309155 - After
you install IomegaWare 2.0 version software on
your computer, you may receive the following error
message on a blue screen:
A
"Stop 0x000000C2" Error Occurs When You Try to
Close a File on a Network Share
Microsoft Knowledge Base Article 328776 - When
you try to close a file that is located on a network
share, you may receive the following error message
(or one that is similar) on a blue screen: STOP
0x000000C2 (0x00000007, 0x00000fd3, 0x88289700,
0x00000000)
"Stop 0x000000cb"
Uninstalling SMS 2.0 on Windows 2000
Microsoft Knowledge Base Article: 254813 - When
you attempt to uninstall Microsoft Systems Management
Server (SMS) 2.0 on a computer that is running
Windows 2000, the computer may stop responding
(hang) and the following error message may be
displayed on a blue screen:
Error Message:
STOP 0x000000C5 DRIVER_CORRUPTED_EXPOOL
Microsoft Knowledge Base Article: 291810 - You
may receive the following STOP error message on
a blue screen STOP 0x000000C5
(parameter 1, parameter 2, parameter
3, parameter 4) DRIVER_CORRUPTED_EXPOOL
where parameter 1 is the memory that is
referenced, parameter 2 is the internal
request level (IRQL), parameter 3 may be
a value of 0 (a read operation) or 1 (a write
operation), and parameter 4 is the address
that referenced memory.
"STOP 0x000000CE"
Error Message in Raspppoe.sys During Upgrade from
Windows NT 4.0 to Windows 2000
Microsoft Knowledge Base Article: 296946 - When
you upgrade from Microsoft Windows NT 4.0 to Windows
2000 you may receive the following error message:
You Receive a "Stop
0x000000CE" Error Message During Shutdown
Microsoft Knowledge Base Article 327643 - While
your computer is shutting down, you may receive
a "Stop 0x000000CE" error message. Mrxsmb.sys
is listed as the problem driver.
STOP 0x000000Dx Errors
"Stop 0x000000D1"
Error Message in Tcpip.sys
Microsoft Knowledge Base Article: 260956 - Under
certain circumstances when you are using TCP/IP
for network communication, your computer may stop
responding (hang) and display the following error
message on a blue screen:
"Stop 0xC00002D1"
Caused by Change to System File
Microsoft Knowledge Base Article: 216352 - If
you accidentally delete or change a protected
Windows 2000 system file, you may receive a "Stop
0xC00002D1" error message on a blue screen. When
you restart the computer, the original file is
replaced automatically and Windows should op
STOP 0x000000D1 in
Ino_fltr.sys with Inoculan
Microsoft Knowledge Base Article: 247421 - When
you save a file to a floppy disk or copy a file
to a floppy disk on a computer running Windows 2000,
you may receive the following error message:
"Stop 0x000000D1"
Error in Atmlane.sys
Microsoft Knowledge Base Article
Q294442 - When you are using Asynchronous Transfer
Mode (ATM - Network services in Windows 2000,
you may receive the following stop message:
Error Message Reports
STOP 0x000000D1 in Serial.sys When Serial Device
or Driver Verifier Is in Use
Microsoft Knowledge Base Article: 276545 - When
you use a serial device or run the Driver Verifier
tool on a Windows 2000-based system, a STOP 0x00000D1
error in the Serial.sys driver may occur.
"Stop 0x000000D1"
Error Message in Tcpip.sys
Microsoft Knowledge Base Article: 260956 - Under
certain circumstances when you are using TCP/IP
for network communication, your computer may stop
responding (hang) and display the following error
message on a blue screen:
Stop
0xD1 in Tcpip.sys During Session Setup or in the
Middle of a Data Stream
Microsoft Knowledge Base Article: 255594
- During session Setup or in the middle of a data
stream, a Windows 2000 server may stop responding
(hang - and the following error message may be
displayed:
STOP 0x000000d6 with
Xircom CEM56-100
Microsoft Knowledge Base Article: 228440 - You
may receive the following error message on a blue
screen:
"STOP
0x000000D8 DRIVER_USED_EXCESSIVE_PTES" Error Message
on Server with Heavy I/O Load
Microsoft Knowledge Base Article: 311551 - On
a server that experiences a heavy input/output
(I/O) load, you may receive the following error
message on a blue screen: ***
STOP 0x000000D8 DRIVER_USED_EXCESSIVE_PTES
NOTE: This problem is more likely to occur on
heavily loaded Microsoft Exchange or Microsoft
SQL Server systems or domain controllers with
a large Active Directory.
How to Troubleshoot
"STOP 0x0000003F" and "STOP 0x000000D8" Error
Messages in Windows 2000
Microsoft Knowledge Base Article: 256004 - Your
Windows 2000-based computer may generate one of
the following error messages on a blue screen:
The
BLACKDRV.SYS file Causes the Stop Error Message:
0X000000D1(0XBE70D600, 0X00000000,0X00000000,0XBE92F13C
Q269279 - Microsoft Knowledge Base Article When
you copy large files over the network, your computer
can restart if Startup And Recovery is set to
Automatically Reboot under the
STOP 0x000000Ex Errors
"STOP 0x000000E2"
Error Message Occurs on a Blue Screen
Microsoft Knowledge Base Article: 273636 - When
you use Windows 2000, you may receive the following
error message on a blue screen: STOP 0x000000E2 (00000000, 00000000, 00000000,
00000000) MANUALLY_INITIATED_CRASH A Stop 0xE2
error message indicates that you manually initiated
the crash. However, if the Driver Verifier Manager
tool is enabled and there is an issue with either
an enabled driver or one of the monitored settings,
then a Stop 0x000000E2 error message is generated.
You
Receive a "Stop 0x000000E3" Error Message in Windows
2000
Microsoft Knowledge Base Article: 307232 - You
may receive a "Stop 0x000000E3" error message
on a blue screen.
Error Message: STOP
0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
Microsoft Knowledge Base Article: 293078 - You
may receive the following error message on a blue
screen: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
STOP 0x00000018 Errors
How to Troubleshoot
a STOP 0x00000018 REFERENCE_BY_POINTER Error Message
Microsoft Knowledge Base Article: 282503 - This
article describes how to troubleshoot the following
error message: STOP
0x00000018 (parameter 1, parameter 2, parameter
3, parameter 4) REFERENCE_BY_POINTER
STOP 0x0000001A
Errors
How
to Troubleshoot a STOP 0x0000001A MEMORY_MANAGEMENT
Error Message
Microsoft Knowledge Base Article: 282504 - If
you are running Windows 2000, you may receive
the following error message: STOP
0x0000001A (parameter, parameter, parameter, parameter)
MEMORY_MANAGEMENT
STOP 0x0000001E Errors
DirectCD 3.01 Prevents
Starting in Safe Mode in Windows 2000
Microsoft Knowledge Base Article: 261807 - After
installing Adaptec's DirectCD version 3.01 on
Microsoft Windows 2000, you may receive the following
error message when you attempt to start in Safe
Mode: STOP:
0x0000001e KMODE_EXCEPTION_NOT_HANDLED
This occurs because Adaptec's
driver CDR4VSD.SYS installed by DirectCD version
3.01 is not compatible with Safe Mode.
A
"Stop 0x0000001E" Error Occurs in Win32k.sys in
Windows 2000
Microsoft Knowledge Base Article: 811363 - You
may receive the following error message on a blue
screen when Windows 2000 is working on a graphics
operation: Stop 0x0000001E
(0xC0000005, 0xA0023BE5, 0x00000000, 0x0000004C)
Error
Message: STOP 0x00000001e KMODE_EXCEPTION_NOT_HANDLED
in Win2k.sys
Microsoft Knowledge Base Article: 294728 - When
you restart your computer, you may receive the
following error message: STOP
0x0000001e KMODE_EXCEPTION_NOT_HANDLED in win2k.sys
How to Troubleshoot
"Stop 0x0000001E" with First Parameter of 0xC0000044
Microsoft Knowledge Base Article: 264223
- A computer that is running Windows NT 4.0 or
Windows 2000 may receive the following error message
on a blue screen:
Open Handles Cause
STOP 0x0000001E or STOP 0x00000024
Microsoft Knowledge Base Article: 195857 - While
shutting down an application the system may stop
with a STOP 0x0000001E or STOP 0x00000024 error
message. In the case of the STOP 0x0000001E the
first parameter will always be C0000005.
Printing in Outlook
98 on Windows NT/2000 4.0 Causes STOP 0x00000001E
Microsoft Knowledge Base Article: 234326 - When
you attempt to use the print function in Microsoft
Outlook 98 on a computer running Windows NT, your
computer may stop responding (hang) and display
the following error message:
STOP 0x1E in Usbhub.sys
with Surprise Removal of Plug and Play USB Hub
Microsoft Knowledge Base Article: 260830 - When
you unplug a Plug and Play Universal Serial Bus
(USB) hub (a surprise removal) several times,
the following error message may be displayed:
"Stop 0x0000001e"
in Win32k.sys When You Quit a Program
Microsoft Knowledge Base Article: 269593 - When
you quit a program, you may receive the following
error message on a blue screen:
Stop 0x0000001E in
Win32k.sys When Using Animated Mouse Pointers
Microsoft Knowledge Base Article: 278999 - When
you are using animated mouse pointers in Windows
2000 with Terminal Services enabled, you may get
receive the following error message on a blue
screen when you log off: Stop 0x0000001E (0xc0000005,
0xa009ddf0, 0x00000000, 0x0000003c)
"Stop
0x0000001e" on Windows 2000 Server
Microsoft Knowledge Base Article: 279640 - When
you are running Windows 2000 Server with or without
Service Pack 1 (SP1 -, you may receive one of
the following stop codes:
"Stop
0x0000001E KMODE_EXCEPTION_NOT_HANDLED" Error
Message May Be Displayed When You Use the Diskperf
Utility
Microsoft Knowledge Base Article: 300224 - After
you have installed Terminal Services on Windows
2000 or you have upgraded from Microsoft Windows
NT 4.0 Terminal Server to Windows 2000, you may
receive the following error message on a blue
screen:
"Stop 0x0000001E"
Error Message After Changing Color Depth
Microsoft Knowledge Base Article: 260982 - When
you change the color depth from High Color (16-bit)
to True Color (24-bit) on your Windows 2000-based
computer while the DVD player is open, you may
receive a "Stop 0x0000001E" error message on a
blue screen.
Stop 0x1e Error Message
Adding Port to Triple Lanstreamer PCI Network
Adapter
Microsoft Knowledge Base Article: 217078 - When
you attempt to add a port to a Triple Lanstreamer
PCI network adapter, you may receive the following
error message on a blue screen:
"Stop: 0x0000001E"
Error Message During Setup
Microsoft Knowledge Base Article: 161703 - Windows
NT generates a bug check code on a blue screen
when a problem is encountered. These codes can
assist you in troubleshooting the problem. For
additional information about bug check codes,
see Microsoft Knowledge Base Article-ID: Q103059 - Descriptions
of Bug Codes for Windows NT. This article
describes only the following bug check code: STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
"Stop
0x0000001E" Error Message in Ntoskrnl.exe
Microsoft Knowledge Base Article: 294690 - When
you use a Windows 2000-based computer, you may
receive the following error message on a blue
screen while Windows processes a loop back packet:
"Stop
0x0000001E" Error Message Printing with Hewlett-Packard
DesignJet Printer Driver from a Terminal Services
Client
Microsoft Knowledge Base Article: 301330 - When
you print from a Terminal Server or Terminal Services
client, you may receive a "Stop 0x0000001E" error
message on a blue screen. This issue can occur
if you are using the Hewlett-Packard DesignJet
driver (HPGL2/RTL - version 4.4 for Windows
Stop
0x0000001E Error Message When You Print from a
Windows 2000 Terminal Services Client
Microsoft Knowledge Base Article: 261322 - When
you try to print from an RDP client in a Windows
2000 Terminal Services session, you may receive
the following error message on a blue screen on
the server: Stop 0x0000001e
(0xc0000005, 0xa00372aa, 0x00000000, 0x00000034)
Stop
0x0000001E in Win32k.sys When Using Animated Mouse
Pointers
Microsoft Knowledge Base Article: 278999 - When
you are using animated mouse pointers in Windows
2000 with Terminal Services enabled, you may get
receive the following error message on a blue
screen when you log off:
"Stop
0x0000001e" on Windows 2000 Server
Microsoft Knowledge Base Article: 279640 - When
you are running Windows 2000 Server with or without
Service Pack 1 (SP1), you may receive one of the
following stop codes:
"Stop 0x1E" or "Stop
0x50" with Terminal Services Client Print Session
Microsoft Knowledge Base Article: 279343 - A Windows
2000-based Terminal Services server may generate
a "Stop 0x1E" or "Stop 0x50" error message during
a Terminal Services client print session. This
may be caused by selecting a particular font in
the document that is being printed.
STOP 0x00000023 Errors
How to Troubleshoot
a "Stop 0x00000023 FAT_FILE_SYSTEM" Message
Microsoft Knowledge Base Article: 290182 - A Windows
2000-based computer that uses the FAT file system
may generate the following error message: STOP
0x00000023 (Parameter1, Parameter2, Parameter3,
Parameter4) FAT_FILE_SYSTEM
STOP Errors 0x00000023
and 0x0000000A in Fastfat.sys When a Program Queries
the File System
Microsoft Knowledge Base Article: 289205 - When
a program queries for a file name or for volume
information, Windows 2000 may exhibit the following
STOP errors in Fastfat.sys:
STOP 0x00000024 Errors
Troubleshooting Stop
0x24 or NTFS_FILE_SYSTEM Error Messages
Microsoft Knowledge Base Article: 228888 - When
you run Windows 2000, you may receive either of
the following error messages:
Open Handles Cause
STOP 0x0000001E or STOP 0x00000024
Microsoft Knowledge Base Article: 195857 - While
shutting down an application the system may stop
with a STOP 0x0000001E or STOP 0x00000024 error
message. In the case of the STOP 0x0000001E the
first parameter will always be C0000005.
STOP 0x00000027 Errors
"Stop 0x00000027
RDR_FILE_SYSTEM" Error Message During Shutdown
Microsoft Knowledge Base Article: 261939
- When you shut down a Windows 2000-based computer,
the following error message may be displayed:
STOP 0x0000002D Errors
How to Troubleshoot
a Stop 0x0000002D SCSI_DISK_DRIVER_INTERNAL Error
Message
Microsoft Knowledge Base Article: 290188 - This
article describes how to troubleshoot the following
error message:
STOP 0x0000002D (parameter 1, parameter 2, parameter
3, parameter 4)
SCSI_DISK_DRIVER_INTERNAL
STOP 0x0000002E
Errors
Troubleshooting "STOP
0x0000002E" or "DATA_BUS_ERROR" Error Message
Microsoft Knowledge Base Article: 218132 - Your
Windows 2000-based computer may stop with the
following error message: STOP:
0x0000002E (parameter1, parameter2,
parameter3, parameter4) DATA_BUS_ERROR
This stop message indicates that a parity
error has been detected in system memory.
STOP 0x0000002F Errors
How to Troubleshoot
a STOP 0x0000002F INSTRUCTION_BUS_ERROR Error
Message
Microsoft Knowledge Base Article: 290192 - This
article describes how to troubleshoot the following
error message:
STOP 0x0000002F (parameter 1, parameter 2, parameter
3, parameter 4)
INSTRUCTION_BUS_ERROR
STOP 0x0000003E Errors
How to Troubleshoot
"STOP 0x0000003E MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED"
Error Messages
Microsoft Knowledge Base Article: 290196 - When
you are using a multiple-processor computer that
is running Windows 2000, you may receive the following
error message: STOP 0x0000003E (Parameter1, Parameter2,
Parameter3, Parameter4) MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
STOP 0x0000003F Errors
How to Troubleshoot
"STOP 0x0000003F" and "STOP 0x000000D8" Error
Messages in Windows 2000
Microsoft Knowledge Base Article: 256004 - Your
Windows 2000-based computer may generate one of
the following error messages on a blue screen:
STOP 0x00000037 Errors
How to Troubleshoot
a STOP 0x00000037 FLOPPY_INTERNAL_ERROR Error
Message
Microsoft Knowledge Base Article: 290193 - This
article describes how to troubleshoot the following
error message:
STOP 0x00000037 (parameter 1, parameter 2, parameter
3, parameter 4)
FLOPPY_INTERNAL_ERROR
STOP 0x00000041 Errors
Error Message: STOP
0x00000041 MUST_SUCCEED_POOL_EMPTY
Microsoft Knowledge Base Article: 291591 - You
may receive the following error message on a blue
screen: STOP
0x00000041 MUST_SUCCEED_POOL_EMPTY (0x1000,0x440,0x2E,0x1)
(updated 3/21/2001)
STOP
0x00000044
Errors
"Stop
0x00000044 Multiple_IRP_Complete_Requests" Error
Message During a Shutdown or Standby Operation
Microsoft Knowledge Base Article
Q294876 - In Windows 2000, when you perform a
shutdown, hibernation, or standby operation, you
may receive the following error message:
STOP 0x00000048 Errors
How to Troubleshoot
a "STOP 0x00000048 CANCEL_STATE_IN_COMPLETED_IRP"
Error Message
Microsoft Knowledge Base Article: 291593 - Your
Windows 2000-based computer may generate the following
error message on a blue screen: STOP
0x00000048 CANCEL_STATE_IN_COMPLETED_IRP (0xe2709504,0x0,0x0,0x0)
"Stop
0x48" Occurs When You Stop the Computer Browser
Service
Microsoft Knowledge Base Article 331484 - Under
a race condition, you may receive a "Stop 0x48"
error message when you stop the Computer Browser
service.
STOP 0x0000004C
Errors
How
to Troubleshoot STOP 0x0000004C FATAL_UNHANDLED_HARD_ERROR
Microsoft Knowledge Base Article: 291801 - This
article describes how to troubleshoot the following
error message that you may receive on a blue screen:
STOP 0x0000004E Errors
How to Troubleshoot
a "STOP 0x0000004E PFN_LIST_CORRUPT" Error Message
Microsoft Knowledge Base Article: 291806 - When
you use a Windows 2000-based computer, you may
receive the following error message on a blue
screen: STOP 0x0000004E PFN_LIST_CORRUPT (Parameter1, Parameter2,
Parameter3, Parameter4)
STOP 0x00000050 Errors
Damaged
Font Causes STOP 0x00000050 Error Message in the
Win32k.sys File in Windows 2000
Microsoft Knowledge Base Article: 319965 - When
you are using your Windows 2000-based computer,
you may receive a STOP 0x00000050 error message
in the Win32k.sys file.
Stop
Error Occurs When You Start the Computer for the
First Time
You may receive the following Stop error message
when you start the computer the first time: Stop
0x00000050 (0xE1626822,0x00000001,0x804EFF46,0x00000002)
The problem occurs when a registry value is set
to NULL, but it is supposed to be a double-null
terminated string. When the computer is initialized,
it references the null string and the Stop error
that is described in the "Symptoms" section occurs
"Stop
0x00000050" Error Message During Copy from OS/2
Clients
Microsoft Knowledge Base Article: 281546 - When
you copy files from an OS/2-based client computer
to a Windows 2000-based computer, you may receive
the following error message: STOP
0x00000050 (0xXXXXXXXX 0x00000000 0xXXXXXXXX 0x00000001
in Srv.sys
"Stop
0x00000050" Error Message When You Are Using a
CD-ROM
Microsoft Knowledge Base Article: 302827 - When
you are using a CD-ROM, you may receive a "Stop
0x00000050" error message.
"Stop 0x50" Error
Message While Installing Windows NT 4.0
Microsoft Knowledge Base Article: 171003 - While
you are installing Windows NT 4.0, your computer
may stop responding (hang) while displaying the
following error message on a blue screen:
"Stop 0x00000050"
in Ntfs.sys Under Stress Accessing Freed FCB
Microsoft Knowledge Base Article: 252192 - A Windows
2000-based computer that is under stress in Ntfs.sys
may display the following error message on a blue
screen;
STOP 0x50 in Usbhub.sys
with Surprise Removal of Plug and Play USB Hub
Microsoft Knowledge Base Article: 261199 - When
you unplug a Plug and Play Universal Serial Bus
(USB) hub (a surprise removal) several times,
the following error message may be displayed:
Stop 0x00000050 in
Udfs.sys Viewing Files on DVD
Microsoft Knowledge Base Article: 282870 - When
you are using Windows Explorer to view files on
a DVD, you may receive the following error message
on a blue screen: Stop
0x00000050 (0xd1e3ffd7, 0x00000000, 0xbef54b74,
0x00000000)
"Stop 0x00000050"
in Ntfs.sys Under Stress Accessing Freed FCB
Microsoft Knowledge Base Article: 252192 - A Windows
2000-based computer that is under stress in Ntfs.sys
may display the following error message on a blue
screen:
Stop 0x50 Error Message
Printing to Windows NT 4.0 Print Server
Microsoft Knowledge Base Article: 199118 - When
you attempt to print to a Microsoft Windows NT
4.0 print server, you may receive the following
error message:
"Stop 0x1E" or "Stop
0x50" with Terminal Services Client Print Session
Microsoft Knowledge Base Article: 279343 - A Windows
2000-based Terminal Services server may generate
a "Stop 0x1E" or "Stop 0x50" error message during
a Terminal Services client print session. This
may be caused by selecting a particular font in
the document that is being printed.
"Stop 0x50" in ObReferenceObjectByPointer
with Terminal Services in Windows 2000
Microsoft Knowledge Base Article: 295462 - Under
certain conditions, a heavily loaded Windows 2000-based
server that is using Terminal Services may experience
a "Stop 0x50" (fffffff0,0,8044d24d,0) error in
ObReferenceObjectByPointer.
"Stop 0x50 in Win32k.sys"
Error Message
Microsoft Knowledge Base Article: 281132 - When
you are running Terminal Services with multiple
clients (for example, you may have Citrix clients
with Citrix Serverfarm), you may receive multiple
error messages on blue screens that are related
to Win32k.sys. The following error message may
be displayed: STOP:
0x00000050 (0xf7f7f7fb, 0x00000000, 0xa0033dd0,
0x00000000) PAGE_FAULT_IN_NONPAGED_AREA address
0xa0033dd0 in Win32K.sys
"Stop
0x00000050" Error Message When USB Device Is Connected
Microsoft Knowledge Base Article: 291284 - If
you connect a Universal Serial Bus (USB - device
to the USB port, your computer may stop responding
(hang - with the following error message:
Stop
0x50 Error Message When You Rename a Large Number
of Files on Windows 2000
Microsoft Knowledge Base Article: 323256
- After a you create and then rename a large number
of files, you may receive a stop 0x00000050 error
message on a blue screen. If special pool memory
is turned on (as is described in Q188831), you
may receive a stop 0x000000CD error message
"Stop
0x00000050" Error Message When You View Files
on a DVD
Microsoft Knowledge Base Article: 290321 - When
you are use Windows Explorer to view files on
a DVD, you may receive the following error message
on a blue screen:
STOP 0x00000051 Errors
How to Troubleshoot
a "STOP 0x00000051 REGISTRY ERROR" Error Message
Microsoft Knowledge Base Article: 282501 - When
you use a computer that is running Windows 2000,
you may receive the following error message: STOP
0x00000051 (parameter,parameter,parameter,parameter)
REGISTRY ERROR
STOP 0x00000058 Errors
How to Recover From
a STOP 0x00000058 FTDISK_INTERNAL_ERROR
Microsoft Knowledge Base Article: 128630 - The
following STOP error message appears when you
start Windows NT:
Stop 0x58 Error Message
Booting to a Shadow Drive from a Broken Basic
Mirror
Microsoft Knowledge Base Article: 224199 - Unlike
previous versions of Microsoft Windows NT, Windows
2000 provides the ability to upgrade a Windows
NT server that has the operating system disk software
mirrored without first breaking the mirror.
STOP 0x0000005D Errors
How to Troubleshoot
a "STOP 0x0000005D UNSUPPORTED_PROCESSOR" Error
Message
Microsoft Knowledge Base Article: 282500 - While
you are using a computer that is running Windows
2000, you may receive the following error message:
STOP: 0x0000005D (parameter, parameter, parameter, parameter)
UNSUPPORTED_PROCESSOR
STOP 0x00000058
Errors
Stop
0x58 Error Message Booting to a Shadow Drive from
a Broken Basic Mirror
Microsoft Knowledge Base Article: 224199 -
Unlike previous versions of Microsoft Windows
NT, Windows 2000 provides the ability to upgrade
a Windows NT server that has the operating system
disk software mirrored without first breaking
the mirror.
STOP 0x00000073 Errors
How to Troubleshoot
a STOP 0x00000073 CONFIG_LIST_FAILED Error Message
Microsoft Knowledge Base Article: 291808 - This
article describes how to troubleshoot the following
error message that you may receive on a blue screen:
STOP Ox00000073 (parameter 1, parameter 2, parameter 3,
parameter 4) CONFIG_LIST_FAILED
How to Troubleshoot
a STOP 0x00000075 CANNOT_WRITE_CONFIGURATION Error
Message
Microsoft Knowledge Base Article: 291809 - This
article describes how to troubleshoot the following
error message that you may receive on a blue screen:
STOP Ox00000075 (parameter 1, parameter 2, parameter 3,
parameter 4) CANNOT_WRITE_CONFIGURATION
STOP 0x00000076 Errors
Troubleshooting
"STOP 0x00000076 - PROCESS_HAS_LOCKED_PAGES" Error
Messages in Windows 2000
Microsoft Knowledge Base Article: 256010 - A Windows
2000-based computer may display one of the following
error messages on a blue screen:
STOP 0x0000007B Errors
Installing
Windows 2000 from a USB CD-ROM Drive May Cause
a "Stop 0x7B" Error
Microsoft Knowledge Base Article If you are using
a Universal Serial Bus (USB - CD-ROM drive to
install Windows 2000 on certain legacy-free computers,
you may receive a "Stop 0x0000007B" Inaccessible_boot_device
error message while booting from the installation
CD. Because many legacy-free computers do not
have a standard CD-ROM drive or floppydisk drive,
the USB CD-ROM drive may be the only method for
installing or recovering Windows
"STOP 0x0000007B"
Error After Moving Windows 2000 System Disk to
Another System
Microsoft Knowledge Base Article: 271965 - After
you move the system (boot) disk to a backup computer,
you may receive the following message on your
Windows 2000 computer when you try to start the
backup computer: ***STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE
"Stop 0x0000007B"
Error Message Is Generated While Converting Basic
Disk to Dynamic
Microsoft Knowledge Base Article: 280724 - After
you choose to convert the basic disk that contains
your Windows 2000 boot partition to dynamic, you
receive the following error message during the
required reboot: STOP
0x0000007B Inaccessible boot device. If more than
two partitions were on the drive, rebooting the
system may allow you to get past this error, but
Disk Management may now report the disk as "Dynamic
Unreadable".
STOP 0x7B Error Message
or Unformatted Partitions After You Apply Windows
2000 Service Pack 1
Microsoft Knowledge Base Article: 271274 - When
you restart your computer after you install Windows
2000 Service Pack 1 (SP1), you may experience
one of the following symptoms: While your computer
is restarting, you may receive the following error
message on a blue screen, and your computer may
stop responding (hang): STOP
0x0000007B INACCESSIBLE_BOOT_DEVICE Or, your computer
restarts, partitions on physical hard disks may
be either missing or appear in the Disk Management
tool as 7.88 gigabytes (GB) in size and "Healthy".
However, within the drive, one or more of the
partitions may be listed as being unformatted
or damaged. Also, if you try to open the partition
in Windows Explorer, you receive a message that
indicates the drive is not formatted and you are
then prompted to format the drive.
"STOP
0x0000007B: INACCESSIBLE_BOOT_DEVICE" Error Message
When You Start Your Computer
Microsoft Knowledge Base Article: 287043 -
When you start your computer after you install
a new motherboard, you may receive the following
error message on a blue screen: STOP:
0x0000007B: ( parameter1 , parameter2 , parameter3
, parameter4 ) INACCESSIBLE_BOOT_DEVICE
STOP 0x7B Installing
Windows 2000 Professional to Mirror Volume
Microsoft Knowledge Base Article: 235287 - When
you install Windows 2000 Professional to a volume
that was Mirrored using Windows 2000 Server, you
receive the following error message:
STOP:
0x0000007b Is Generated When You Boot to a Mirrored
Dynamic Disk
Microsoft Knowledge Base Article: 308640 - If
you are using software mirroring on Dynamic Disks
for your boot partition, the computer may generate
the following error message during a normal shutdown
and restart process:
Windows Hangs at
"Loading Machine Info" with HighPoint UltraDMA
ATA/66 Controller
Microsoft Knowledge Base Article: 243018 - If
you start your computer using a Windows 2000 CD-ROM
to install Windows and you have installed a HighPoint
UltraDMA ATA/66 hard disk controller, the computer
may stop responding (hang) while the following
information is displayed: Loading
Machine Information. You cannot press F6
to install a secondary controller driver. If you
upgrade from Windows NT 4.0 or Windows 95/98,
you may receive the following error message: Stop
0x0000007b INACCESSIBLE_BOOT_DEVICE This
issue occurs because there is not a Windows 2000
compatible driver for the HighPoint UltraDMA ATA/66
hard disk controller
Using Sysprep May
Result in "Stop 0x7b (Inaccessible Boot Device)"
on Some Computers
Microsoft Knowledge Base Article: 257813 - When
you use Sysprep (including versions 1.0, 1.1,
and later versions) to create images for computers,
some computers may generate a "Stop 0x7b" error
message upon reboot after the mini-Setup wizard
finishes.
How to Troubleshoot
a STOP 0x0000007D INSTALL_MORE_MEMORY Error Message
Microsoft Knowledge Base Article: 292942 - This
article describes how to troubleshoot the following
error message that you may receive on a blue screen:
STOP 0x0000007D INSTALL_MORE_MEMORY (0xe2709504,0x0,0x0,0x0)
"STOP
0x0000007B" with Unattended Setup Using the ExtendOemPartition
Keyword and Installing the Loopback Adapter
Microsoft Knowledge Base Article: 295759 - If
you use the ExtendOemPartition option in an unattended
Setup script and the script is also being used
to install the Microsoft Loopback adapter, the
computer may stop responding (hang - after the
final reboot.
STOP 0x0000007F Errors
General Causes of
STOP 0x0000007F Errors
Microsoft Knowledge Base Article: 137539 - You
may receive the following error message while
running Windows NT:
Stop 0x0000007F When
You Restart Your Computer with MCD Tape Changers
Microsoft Knowledge Base Article: 252182 - After
you restart your computer with tapes in the tape
changer library, you may receive the following
error message on a blue screen at the end of the
auto inventory sequence:
"Stop 0x0000007F
Unexpected_kernel_mode_trap x08" After Installing
Novell Client on Windows 2000 Professional
Microsoft Knowledge Base Article: 264045 - You
may receive the following error message on a Compaq
Deskpro 6000 computer that is running Windows
2000 Professional when you install the Novell
client version 4.7:
STOP 0x00000080 Errors
How to Troubleshoot
a STOP 0x00000080 NMI_HARDWARE_FAILURE Error Message
Microsoft Knowledge Base Article: 292945 - This
article describes how to troubleshoot the following
error message that you may receive on a blue screen:
STOP 0x00000080 NMI_HARWARE_FAILURE (0xe2709504,0x0,0x0,0x0)
STOP 0x0000008B Errors
How to Troubleshoot
a STOP 0x0000008B MBR_CHECKSUM_MISMATCH Error
Message
Microsoft Knowledge Base Article: 292982 - This
article describes how to troubleshoot the following
error message that you may receive on a blue screen:
STOP 0x0000008B MBR_CHECKSUM_MISMATCH (0x0,0x0,0x0,0x0)
STOP 0x00000092 Errors
How to Troubleshoot
a STOP 0x00000092 UP_DRIVER_ON_MP_SYSTEM Error
Message
Microsoft Knowledge Base Article: 292983 - This
article describes how to troubleshoot the following
error message that you may receive on a blue screen:
STOP 0x00000092 UP_DRIVER_ON_MP_SYSTEM (0x0,0x0,0x0,0x0)
STOP 0x00000097 Errors
How to Troubleshoot
a STOP 0x00000097 BOUND_IMAGE_UNSUPPORTED Error
Message
Microsoft Knowledge Base Article: 292984 - This
article describes how to troubleshoot the following
error message that you may receive on a blue screen:
STOP 0x00000097 BOUND_IMAGE_UNSUPPORTED (0x0,0x0,0x0,0x0)
STOP 0x0000009F Errors
Cluster
Server May Generate "STOP 0x9F" During Shutdown
Microsoft Knowledge Base Article: 297219 - When
you shut down or restart a Windows 2000-based
cluster server, the following error message may
be displayed:
"STOP 0x9f" in Ntoskrnl.exe
When Shutting Down or Restarting Computer
Microsoft Knowledge Base Article: 245835 - After
you install Intuit Quicken 2000, you may receive
the following error message when you shut down
or restart your computer: STOP 0x0000009f Driver_Power_State_Failure
"STOP 0x9f" in Symevent.sys
When Shutting Down or Restarting Computer
Microsoft Knowledge Base Article: 239415 - After
you install Norton CrashGuard 4.0 or 4.01 for
Microsoft Windows 95/Microsoft Windows 98/Microsoft
Windows NT in Windows 2000, the following error
message may be displayed when you shut down or
restart your computer.
Troubleshooting STOP
0x9F Error Messages in Windows 2000
Microsoft Knowledge Base Article: 246243 - You
may receive a "STOP 0x0000009F DRIVER_POWER_STATE_FAILURE"
error message in Windows 2000.
STOP 0x000002xx Errors
Error
Message Cites STOP 0xc000021a Event and STATUS_SYSTEM_PROCESS_TERMINATED
Microsoft Knowledge Base Article: 295087
- While a program is running, the following error
message may appear:
How to Troubleshoot
a STOP 0xC0000218 Error Message
Microsoft Knowledge Base Article: 156640 - A computer
running Windows NT Server displays the following
STOP error message:
STOP: C0000221 Unknown
Hard Error or STOP: C0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
Microsoft Knowledge Base Article: 101096 - Err
Msg: STOP: C0000221 Unknown Hard Error or STOP:
C0000221 STATUS_IMAGE_CHECKSUM_MISMATCH This error
can appear in many different formats, ranging
from a blue system error screen to a dialog box.
The type of format depends on how much of the
operating system was loaded when the corrupted
file was detected. If you receive this error message,
the file listed along with the error is corrupted.
You need to either obtain a new copy of the file
or reinstall Windows NT or Windows 2000. If reinstallation
fails to solve the problem, then a hardware or
network problem may exist.
STOP 0xC0000244 When
Security Log Full
Microsoft Knowledge Base Article: 232564 - If
the CrashOnAuditFail registry key is set to 1
and the Security Event log is full on a computer
running Windows NT, the following blue screen
error message may be displayed:
Err Msg: STOP: C000026C
Unable to Load Device Driver...
Microsoft Knowledge Base Article: 160495 - When
you install Windows NT, start Windows NT from
the hard disk, or start Windows NT from the three
Setup floppy disks during a repair process, you
may receive one of the following error messages:
|
