Google

Tuesday, February 12, 2008

BDV-961581-BDV

A Quick Guide to Troubleshoot BSOD (Blue Screen)

1. 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to faulty or incompatible hardware or software. 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.

2. 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
The Win XP kernel detected an illegal or unknown processor instruction. The problems that cause this Stop message 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.

3. 0x00000023: FAT_FILE_SYSTEM
A problem occurred within a read or write to a FAT16 or FAT32 file system drive. There may be a physical problem with the disk, or an interrupt request packet (IRP) may not be able to be successfully completed or may be corrupted. I suggest running ChkDsk or ScanDisk as a first effort to address it. Disable all file system filter drivers such backup utilities, virus scanners, or firewall software. Check the file properties of FASTFAT.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

4. 0x00000024: NTFS_FILE_SYSTEM
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, 0x00000023, exists for File Allocation Table file systems, FAT16 and FAT32.)

5. 0x0000002E: DATA_BUS_ERROR
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). This Stop message also can indicate hard disk damage caused by viruses or other problems.

6. 0x0000003F: NO_MORE_SYSTEM_PTES
Indicates one or more of the following problems: (1) The system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions. (2) A faulty device driver is not managing memory properly. (3) An application, such as a backup program, is improperly allocating large amounts of kernel memory.

7. 0x0000004E: PFN_LIST_CORRUPT
This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM.

8. 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message.

9. 0x00000076: PROCESS_HAS_LOCKED_PAGES
This error message is caused by a driver not cleaning up completely after an I/O operation. The General Discussion article below contains a method to track the problem if it recurs, and identify the problem driver. (The third parameter of the error message shows the number of locked pages.)

  • General Discussion {Q256010} Win 2000 (After reading the article, click here to download a Registry patch to make the recommended change.)

10. 0x00000077: KERNEL_STACK_INPAGE_ERROR
A page of kernel data requested from the pagefile could not be found or read into memory. This message also can indicate disk hardware failure, disk data corruption, or possible virus infection.

11. 0x00000079: MISMATCHED_HAL
The Hardware Abstraction Layer (HAL) and the kernel type for the computer do not match. This most often occurs when ACPI firmware settings are changed. For example, you might install Win 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.

12. 0x0000007A: KERNEL_DATA_INPAGE_ERROR
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.

13. 0x0000007B: INACCESSIBLE_BOOT_DEVICE
Win XP lost access to the system partition or boot volume during the startup process. Typical causes: Installing incorrect device drivers when installing or upgrading storage adapter hardware, or a virus.

14. 0x0000007E: SPECIFIED_MODULE_NOT_FOUND

15. 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
One of three types of problems occurred in kernel-mode: (1) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). (2) Software problems. (3) Hardware failures.

16. 0x0000009A: STATUS_INSUFFICIENT_RESOURCES
The Windows kernel has allocated all of its allotted paged-pool memory.

17. 0x0000009F: DRIVER_POWER_STATE_FAILURE
A driver is in an inconsistent or invalid power state. Typically occurs during events that involve power state transitions, such as shutting down, or moving into or out of standby or hibernate mode.

18. 0x000000A5
The cause of this message is always errors in the ACPI BIOS. Nothing can be done at an operating system level to fix the problem. See the article above for more details.

  • 0x000000A5 {Q256841} Win 2000, Win XP (when installing Win 2000 or later)

19. 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
A driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware.

20. 0x000000C2: BAD_POOL_CALLER
A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.

21. 0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
This is related to Stop Code 0x76. It appears instead of 0x76 if diagnostic tracking is enabled as described in the General Discussion article below. Note the name of the problem driver on the blue error screen.

22. 0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
A driver failed to cancel pending operations before exiting. Commonly occurs after installing faulty drivers or system services.

23. 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses).

24. 0x000000D8: DRIVER_USED_EXCESSIVE_PTES
Typically occurs if your computer runs out of Page Table Entries (PTEs) due to a driver that requests large amounts of kernel memory.

25. 0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
A device driver problem has caused the system to pause indefinitely (hang). Typically, this 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.

26. 0x000000ED: UNMOUNTABLE_BOOT_VOLUME
The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error also might occur during an upgrade to Win XP 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.

27. 0x000000F2: HARDWARE_INTERRUPT_STORM
This error message appers if the kernel detects an interrupt storm i.e., when a level-interrupt-triggered device fails to release an IRQ. Usually, this is caused by a bad device driver. (See the link above for more details.)

28. 0xC0000218: UNKNOWN_HARD_ERROR
A necessary Registry hive file couldn’t be loaded. The file may be corrupt or missing (requiring either an Emergency Repair Disk or a Windows reinstallation). The Registry files may have been corrupted because of hard disk corruption or some other hardware problem. A driver may have corrupted the Registry data while loading into memory, or the memory where the Registry is loading may have a parity error (turn off the external cache and check the physical RAM).

29. 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
This occurs when Win XP switches into kernel mode and a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised and security can no longer be guaranteed. Because Win XP can’t run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can cause the system to stop responding. This Stop message also can occur when the computer is restarted after a system administrator has modified permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders.

30. 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
Indicates driver problems, system file problems, disk corruption problems (such as a damaged pagefile), or faulty memory hardware.

31. 0xC000026C
Usually indicates device driver problems.


Posted by how to at 9:10 PM 0 comments

Labels:

Monday, February 11, 2008

Domains, Servers, Databases, Directories... What does it all mean?


I like to use analogies when trying to explain concepts that are new to people. For many, the terminology of Lotus Notes/Domino includes words they've never used before. I know analogies are never perfect, but they can help lead to a general understanding. So with that in mind, I'm going to try and explain Lotus Notes and Domino by relating it to the physical world we work in.

Similar to how your company has office buildings where everyone works, Domino has what are called a domains. Your company might have a single building (domain), or they may have many. Sometimes you may work in a different building than your normally do, just as sometimes you may access information in a different Domino domain.

Inside those office building you have many rooms/offices where people work. Inside your Domino domain there are many servers. Often rooms have specific functions such as the boardroom, the copy center, or the cafeteria. Servers may also have specific functions. You may access your email on one, a shared TeamRoom on another, and a Project Management database on yet another.

Where are documents stored in each of these offices? In filing cabinets. On a Domino server these "filing cabinets" are represented by databases. Similar to how in each office you may find documents unique to a specific person, each Notes database might have documents for a specific person, for example your email. However, your company might also have a common room where general information is stored and shared, like a library. Lotus Notes/Domino does the same thing, as some databases like a CRM package, a HelpDesk application, or a Discussion Forum can be accessed by multiple people.

The Domino Directory is like the phone directory and/or map often found in a building's lobby. They list all the people that work in the building, their phone numbers, and where to deliver their mail.

Below is a visual description of this analogy. An office building contains rooms, which contain filing cabinets, which contain documents. A Domino domain contains servers, which contain databases, which contain documents.




To put this in context for you, below you can see an example of my Workspace. Each "square" that I click on opens a different database, and each database may be on a different server. The first two databases, my email and the Lotus Domino Directory are located on a server named WTFMAIL02. The third, my Personal Address Book, is located locally on my computer's harddrive. The fourth and fifth databases are on CAMDB04 and CAMDB18 respectively.



One final note. Just like in the physical world, Lotus Notes and Domino can provide security at many different levels to protect your information. You may need a key or security badge to get into your building, a second key to open your office door, and a third to unlock your filing cabinet. When accessing a document in Lotus Notes, you need to first have proper access to the server, then to the database, and then to the document. With Lotus Notes you can add even more levels of security, as you can control access to specific sections of a document, and even specific fields!

While you may not need to know all of these things to get your daily work done, I truly believe understanding the tools you use can really help alleviate much of the confusion and mystery.

Alan Lepofsky

Posted by how to at 4:54 PM 0 comments

Labels:

Subscribe to: Comments (Atom)