Information

Tiny URL

Enter a long URL to make tiny:

Stop 0X0000007F UNEXPECTED_KERNEL_MODE_TRAP

Posted by Nizamudeen 0 comments
This is the BSOD image for 0X0000007F 

Cause: 
 This error message can occur if either of the following conditions exists:
  • Your computer has hardware or software problems (hardware failure is the most common cause).
  • You try to over clock the speed of your computer's processor (for example, you set a 150 MhZ processor to run at 187 MhZ).
The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal. The most common causes of a STOP 0x7F are:
  • Low-level hardware corruption, such as corrupt memory (RAM)
  • Mismatched memory modules
  • A malfunctioning motherboard

Resolution:

To resolve this issue, use the appropriate method:
  • If either software or hardware can cause a particular trap, a debug is required to determine which is the cause. If you suspect a hardware problem, try the following hardware troubleshooting steps:
    1. Test the RAM in the computer by running the diagnostic software that is provided by the computer manufacturer. Replace any RAM that is reported as bad. Also, make sure that all the RAM in the computer is the same speed.
    2. Try removing or swapping out controllers, cards, or other peripherals.
    3. Try a different motherboard on the computer.
  • If you are over clocking the speed of your processor, set it back to the speed at which it is designed to run.
  • Check with the hardware vendor for any updated hardware drivers or BIOS updates, or both.

Stop 0x0000002C - "PORT_DRIVER_INTERNAL"

Posted by Nizamudeen 29 comments

Cause of STOP 0x0000002C Errors

STOP 0x0000002C errors are likely caused by hardware or device driver issues.
If STOP 0x0000002C isn't the exact STOP code you're seeing or PORT_DRIVER_INTERNAL isn't the exact message, please check my Complete List of STOP Error Codes  and reference the troubleshooting information for the STOP message that you are seeing.

Resolution

Note: The STOP 0x0000002C STOP code is rare so there's little troubleshooting information available that's specific to the error.
However, since most STOP errors have similar causes, there are some basic troubleshooting steps to help fix STOP 0x0000002C issues:
  1. Restart your computer if you haven't already done so.

    The STOP 0x0000002C blue screen error may not occur again after rebooting.
  2. These extensive troubleshooting steps aren't specific to the STOP 0x0000002C error but since most STOP errors are so similar, they should help resolve it.
Please let me know if you've fixed the STOP 0x0000002C blue screen of death using a method that I don't have above. I'd like to keep this page updated with the most accurate STOP 0x0000002C error troubleshooting information as possible.

Stop 0X0000002B PANIC_STACK_SWITCH

Posted by Nizamudeen 0 comments
This is the BSOD image for 0X0000002B 


Explanation:
 
This is a Windows 2000 Executive character-mode STOP message. It indicates a panic switch to the kernel stack because of stack overflow. This error might be caused by the kernel-mode driver using too much stack space. Or a data corruption has occurred in the kernel.

User Action:
 
If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.

Stop 0x0000003F - NO_MORE_SYSTEM_PTES

Posted by Nizamudeen 0 comments

Causes:

When an SNA client computer has a TCP/IP socket connection to an SNA Server, the server periodically sends a Keep Alive message to the client to speed up the detection of a lost client LAN session. SNA Server TCP/IP Keep Alive messages do not complete because the client's TCP receive window size dropped to zero. The SNA Server keeps on queuing new Keep Alive messages (even though earlier keep alive messages haven't completed) until the SNA Server runs out of system PTEs. 

Resolution:
Microsoft has modified the files, SNADMOD.DLL and SNAIP.DLL, so that SNA Server does not queue a new Keep Alive until the previous one has completed. Thus, the connection is aborted after a configurable timeout. The timeout is specified in the following registry parameter: 

The KeepAliveLimit specifies how many WatchDogTimeouts SNA Server waits before aborting the connection. The default watchdogtimeout value is 60 seconds, though this is also configurable under: 
If a second keepalive is sent to a client box, SNA Server now logs Event 700 to indicate this (logged only when detailed problem analysis logging is enabled). If the limit is exhausted, then SNA Server logs a 701 event at a high severity to indicate this. The client's IP address is logged in these new events.
The registry value, HardClse, controls how the connection is aborted. If the value is "yes", the connection is reset immediately and no effort is made to close the connection gracefully. The default value is "no". HardClse is found in the following subtree: 


Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR (0x07A)

Posted by Nizamudeen 2 comments
This is the BSOD image for Stop 0x0000007A
Causes : 

** A page of kernel data was not found in the pagefile and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.
 
Solution :

** Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems.
** Run chkdsk /r or chkdsk /f to detect and resolve any file system structural damage.
** Run any system diagnostics that are supplied by your computer manufacturer, especially a HDD check. System
**If all Hardware fully functional reinstall Operating .

Stop 0x0000002E or DATA_BUS_ERROR

Posted by Nizamudeen 0 comments
Causes :

This indicates a system memory parity error, typically caused by 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). It also can indicate hard disk damage caused by viruses or other problems.

Solution: 

** Look for other hardware issues. Remove any newly installed Hardware. 
** Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM and HDD check.
** Perform a Driver Rollback if incase a driver has been updated for a particular components

Stop 0x00000023 (or) 0x00000024 - NTFS_FILE_SYSTEM

Posted by Nizamudeen 0 comments

This is the BSOD image for  0x00000024
Causes :  
A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted.

Solution :  
Right click My Computer and click Manage.

Once the Computer Management screen come up look for Event Viewer, System.
Do this on a regular basis as well. You will have to restart your system before the disk scan begins on a system partition.
If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r.
Solution 1:

Insert your Windows XP CD, bootup as normal and choose Boot from CD when the option appears.
Once booted from the CD, select Console Recovery. Run Chkdsk.

Solution 2:
(This may seem long winded but it could help you.)

If you do not have the Windows Xp discs then:

Make sure everything is switched off. Your computer system switched off. Physically take out your hard disk that has Windows XP installed on it and attach it to a second desktop (make sure it is a slave by altering the jumper settings in the back. Look at the hard disks instructions on how to do this.)
If you don't have a second desktop take it to a friend who has a desktop and attach it to theirs.

When you have attached it, boot up the computer that it has been attached to and then run Chkdsk on that drive. Use these commands.

Chkdsk /p (performs an exhaustive check of the drive and corrects any errors.) /r ( Locates bad sectors and recovers readable information.)

Example: chkdsk c: /p /r
The C: is the C drive that Windows XP is installed on.
If you can get into your system then get into a DOS prompt and run the same chkdsk command.

This hopefully will help you to recover a failing system. The other alternative is to do a complete re-install of the operating system.

Stop 0x00000050 " PAGE_FAULT_IN_NONPAGED_AREA "

Posted by Nizamudeen 0 comments
This is the BSOD image for 0x00000050

Causes : 

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.


Solution : 

* Look for other hardware issues. Remove any newly installed Hardware.
* Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check.
* Perform a Driver Rollback if incase a driver has been updated for a particular component.

Stop 0x0000001E - KMODE_EXCEPTION_NOT_HANDLED 0x1E

Posted by Nizamudeen 0 comments
 
This is the BSOD image for 0x0000001E

Causes : 

A "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message indicates that an error condition was detected by the kernel and Windows was unable to continue running because of this error condition.

The types of problems that can cause a "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message are very similar to the problems that cause a "STOP 0x0000000A" error message, such as bad pointers, invalid addresses and other types of access violations. The STOP 0x0000001E bug check identifies an error that occurred in a section of code where no error handling routines exist.



Resolution : 

* Try to replace the driver that is identified in the STOP error message, either with a known good copy from your installation media, or with an updated version from the manufacturer.
* Disable the driver that is identified in the STOP error message or any newly installed drivers.
* Verify that any new hardware or software is properly installed. Disconnect the new hardware or replace it to see if this resolves the issue.
* If you have a video driver that was not supplied with the operating system, try switching to the standard VGA driver or a driver that is compatible with the operating system.
* Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check. If this is a new installation of the hardware or software, contact the manufacturer for any requires updates for drivers or firmware.
* Disable all filter drivers, such as remote control software, antivirus programs, backup programs, and so on.

STOP 0X0000000A IRQL_NOT_LESS_OR_EQUAL

Posted by Nizamudeen 0 comments
 This will be the BSOD Screen for 0x0000000A
Caused : 

This behavior can occur if there is incompatible hardware or an incompatible device driver on your computer.

Resolution : 

* Restart the computer and see if you receive an option to revert back to a previous operating system.
(Choose this option if it is displayed)
*If it is displayedWhen your computer starts Windows 98 or Windows Me, uninstall any antivirus software and boot manager software (such as Roxio GoBack), and then "clean boot" your computer by using the information in one of the following Microsoft Knowledge Base articles:


(http://support.microsoft.com/kb/267288/EN-US/ ) How to Perform a Clean Boot in Windows Millennium Edition
(http://support.microsoft.com/kb/192926/EN-US/ ) How to Perform Clean-Boot Troubleshooting for Windows 98

* If you do not receive the option to revert to a previous operating system, Remove any unnecessary hardware from the computer. Disconnect any Universal Serial Bus (USB) devices and printers, and remove the network adapter, sound card, serial adapters, and so on.

* If you continue to receive this error message, you may need to flash the BIOS on the computer's motherboard. Refer to the manufacturer of your computer or the Web site for the motherboard for information about how to do this

Stop 0x0000000A in Windows 2000

Posted by Nizamudeen 0 comments
A stressed Windows 2000-based server may display the following stop code on a blue screen:

Stop 0x0000000A (0x00000060, 0x0000001c, 0x00000001, 0x8042a04a)
 
Caused : This problem is caused by a small timing problem that can cause a null pointer to be referenced.

Resolution :
To resolve this problem, obtain the latest service pack for Windows 2000.

How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

Subscribe to: Posts (Atom)