Troubleshooting Stop Messages : Common Stop Messages (part 2)

5. Stop 0x3B or SYSTEM_SERVICE_EXCEPTION

The Stop 0x3B message indicates that an exception happened while executing a routine that transitions from nonprivileged code to privileged code.

5.1. Interpreting the Message

This Stop message has three parameters:

5.2. Resolving the Problem

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code. To resolve the problem, update to the latest driver for your video card. If you currently have the latest version installed, try rolling back to an earlier version.

Note:

MORE INFO For more information about Stop 0x3B messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x0000003B and 0x3B.

6. Stop 0x3F 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 because the system is 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.

6.1. Interpreting the Message

Depending on the configuration of your system, the value of the first parameter might vary. The following are possible values for the first parameter and the information returned:

• 0x0A PTE type: 0x00 = system expansion, 0x01 = nonpaged pool expansion

• 0x0B Requested size

• 0x0C Total free system PTEs

• 0x0D Total system PTEs

6.2. Resolving the Problem

The following suggestions are specific to Stop 0x3F errors. For additional troubleshooting suggestions that apply to all Stop errors.

• Stop 0x3F messages can occur after you install faulty drivers or system services. If a driver 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 may not be 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.

A related Stop message, 0xD8: DRIVER_USED_EXCESSIVE_PTES.

Note:

MORE INFO For more information about Stop 0x3F messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x0000003F and 0x3F.

7. Stop 0x50 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, and video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.

7.1. Interpreting the Message

This Stop message has four parameters:

7.2. Resolving the Problem

The following suggestions are specific to Stop 0x50 errors. For additional troubleshooting suggestions that apply to all Stop errors.

• If you added new hardware recently, remove and replace the hardware to determine whether it is causing or contributing to the problem. 

• Stop 0x50 messages can also occur after you install faulty drivers or system services. If the driver 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 whether 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.

• Check your hard disk for problems. 

Note:

MORE INFO For more information about Stop 0x50 messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x00000050 and 0x50. Specifically, refer to Knowledge Base article 938239.

8. Stop 0x77 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.

8.1. Interpreting the Message

This Stop message has four parameters. The following set of definitions applies only if the first and third parameters are both zero:

Otherwise, the following definitions apply:

Frequently, you can determine the cause of this error from the second parameter, the I/O status code. Some common status codes include the following:

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

• 0xC000009C, or STATUS_DEVICE_DATA_ERROR, generally 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 hard disk configuration.

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

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

8.2. Resolving the Problem

The following suggestions are specific to Stop 0x77 errors. For additional troubleshooting suggestions that apply to all Stop errors.

• 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, an error that is 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. Additionally, use ChkDsk to check the disk for problems. 

• Another cause of Stop 0x77 messages is defective, malfunctioning, or failed memory hardware, such as memory modules, L2 SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace the hardware to determine whether it is causing or contributing to the problem. 

• The problem might also be due to cracks, scratched traces, or defective features 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 the following section, "Stop 0x7A or KERNEL_DATA_INPAGE_ERROR."

Note:

MORE INFO For more information about Stop 0x77 messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x00000077 and 0x77.

9. Stop 0x7A 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.

9.1. Interpreting the Message

This Stop message has four parameters:

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

• 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, defective disk cabling, or two devices attempting to use the same resources.

9.2. Resolving the Problem

The following suggestions are specific to Stop 0x7A errors. For additional troubleshooting suggestions that apply to all Stop errors.

• 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. 

• Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory hardware, such as memory modules, L2 SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace the hardware to determine whether it is causing or contributing to the problem. 

• 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.

• The problem might also be due to cracks, scratched traces, or defective features 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.

Note:

MORE INFO For more information about Stop 0x7A messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x0000007A and 0x7A.