Download Patch
http://support.microsoft.com/kb/894391
Thursday, September 23, 2010
Troubleshooting info from Windows XP BSOD error messages
Microsoft Windows XP systems are notorious for crashing for any number of reasons and in a number of ways. Some of these crashes are mild and can easily be overcome simply by closing a non-responding application or by rebooting the system. However, others are more serious and can bring the entire system to its knees. Microsoft calls these types of crashes “Stop errors” because the operating system stops responding. When a Stop error occurs, the GUI is replaced by a DOS-like blue screen with a cryptic error message followed by a code number. This screen is affectionately referred to as the Blue Screen Of Death, or BSOD for short.
Common BSODs in Windows XP
Now that you have a good idea of how to dissect a BSOD and pull out the relevant pieces of information from all the gibberish on the screen, let’s look at some of the more common BSODs in Windows XP. I’ll only cover just a few of the BSOD conditions, but there are lots of possible Stop errors. For each BSOD I discuss, I’ll provide a link to an article on the Microsoft Knowledge Base that covers that particular Stop error. (Since more than one article might address a Stop error, you may want to search the Knowledge Base if you discover that you need more information.)
STOP:0×0000000A
IRQL_NOT_LESS_OR_EQUAL
This Stop error, which can be caused by either software or hardware, indicates that a kernel-mode process or driver attempted to access a memory location it did not have permission to access or a memory location that exists at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access other only processes that have an IRQL that’s equal to or lower than its own.
Troubleshooting a Stop 0×0000000A error in Windows XP
STOP: 0×0000001E
KMODE_EXCEPTION_NOT_HANDLED
This Stop error indicates that indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause this Stop error can be either software or hardware related and result from invalid memory and access violations, which are intercepted by Windows’ default error handler if error-handling routines are not present in the code itself.
Possible Resolutions to STOP 0×0A, 0×01E, and 0×50 Errors
STOP: 0×00000050
PAGE_FAULT_IN_NONPAGED_AREA
This Stop error 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 this Stop error.
Possible Resolutions to STOP 0×0A, 0×01E, and 0×50 Errors
STOP: 0×0000007B
INACCESSIBLE_BOOT_DEVICE
This Stop error 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 this Stop error. This error could also indicate a possible virus infection.
Troubleshooting Stop 0×0000007B or “0×4,0,0,0″ Error
STOP: 0×0000007F
UNEXPECTED_KERNEL_MODE_TRAP
This Stop error indicates a hardware problem resulting from mismatched memory, defective memory, a malfunctioning CPU, or a fan failure that’s causing overheating.
General causes of “STOP 0×0000007F” errors
STOP: 0×0000009F
DRIVER_POWER_STATE_FAILURE
This Stop error indicates that a driver is in an inconsistent or invalid power state. This Stop error typically occurs during events that involve power state transitions, such as shutting down, or moving in or out of standby or hibernate mode.
Troubleshooting a Stop 0×9F Error in Windows XP
STOP: 0×000000D1
DRIVER_IRQL_NOT_LESS_OR_EQUAL
This Stop error indicates that 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). It can also be caused by faulty or mismatched RAM or a damaged pagefile.
Error Message with RAM Problems or Damaged Virtual Memory Manager
STOP: 0×000000EA
THREAD_STUCK_IN_DEVICE_DRIVER\
This Stop error indicates that 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.
Error message: STOP 0×000000EA THREAD_STUCK_IN_DEVICE_DRIVER
STOP: 0×00000024
NTFS_FILE_SYSTEM
This Stop error indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to drives formatted with the NTFS file system. (A similar Stop message, 0×00000023, exists for the file allocation table [FAT16 or FAT32)] file systems.)
Troubleshooting Stop 0×24 or NTFS_FILE_SYSTEM Error Messages
STOP: 0xC0000218
UNKNOWN_HARD_ERROR
This Stop error indicates that a necessary registry hive file could not be loaded. The file may be corrupt or missing. The registry file may have been corrupted due to 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.
How to Troubleshoot a Stop 0xC0000218 Error Message
STOP: 0xC0000221
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.
“STOP: C0000221 unknown hard error” or “STOP: C0000221 STATUS_IMAGE_CHECKSUM_MISMATCH” error message occurs
Common BSODs in Windows XP
Now that you have a good idea of how to dissect a BSOD and pull out the relevant pieces of information from all the gibberish on the screen, let’s look at some of the more common BSODs in Windows XP. I’ll only cover just a few of the BSOD conditions, but there are lots of possible Stop errors. For each BSOD I discuss, I’ll provide a link to an article on the Microsoft Knowledge Base that covers that particular Stop error. (Since more than one article might address a Stop error, you may want to search the Knowledge Base if you discover that you need more information.)
STOP:0×0000000A
IRQL_NOT_LESS_OR_EQUAL
This Stop error, which can be caused by either software or hardware, indicates that a kernel-mode process or driver attempted to access a memory location it did not have permission to access or a memory location that exists at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access other only processes that have an IRQL that’s equal to or lower than its own.
Troubleshooting a Stop 0×0000000A error in Windows XP
STOP: 0×0000001E
KMODE_EXCEPTION_NOT_HANDLED
This Stop error indicates that indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause this Stop error can be either software or hardware related and result from invalid memory and access violations, which are intercepted by Windows’ default error handler if error-handling routines are not present in the code itself.
Possible Resolutions to STOP 0×0A, 0×01E, and 0×50 Errors
STOP: 0×00000050
PAGE_FAULT_IN_NONPAGED_AREA
This Stop error 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 this Stop error.
Possible Resolutions to STOP 0×0A, 0×01E, and 0×50 Errors
STOP: 0×0000007B
INACCESSIBLE_BOOT_DEVICE
This Stop error 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 this Stop error. This error could also indicate a possible virus infection.
Troubleshooting Stop 0×0000007B or “0×4,0,0,0″ Error
STOP: 0×0000007F
UNEXPECTED_KERNEL_MODE_TRAP
This Stop error indicates a hardware problem resulting from mismatched memory, defective memory, a malfunctioning CPU, or a fan failure that’s causing overheating.
General causes of “STOP 0×0000007F” errors
STOP: 0×0000009F
DRIVER_POWER_STATE_FAILURE
This Stop error indicates that a driver is in an inconsistent or invalid power state. This Stop error typically occurs during events that involve power state transitions, such as shutting down, or moving in or out of standby or hibernate mode.
Troubleshooting a Stop 0×9F Error in Windows XP
STOP: 0×000000D1
DRIVER_IRQL_NOT_LESS_OR_EQUAL
This Stop error indicates that 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). It can also be caused by faulty or mismatched RAM or a damaged pagefile.
Error Message with RAM Problems or Damaged Virtual Memory Manager
STOP: 0×000000EA
THREAD_STUCK_IN_DEVICE_DRIVER\
This Stop error indicates that 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.
Error message: STOP 0×000000EA THREAD_STUCK_IN_DEVICE_DRIVER
STOP: 0×00000024
NTFS_FILE_SYSTEM
This Stop error indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to drives formatted with the NTFS file system. (A similar Stop message, 0×00000023, exists for the file allocation table [FAT16 or FAT32)] file systems.)
Troubleshooting Stop 0×24 or NTFS_FILE_SYSTEM Error Messages
STOP: 0xC0000218
UNKNOWN_HARD_ERROR
This Stop error indicates that a necessary registry hive file could not be loaded. The file may be corrupt or missing. The registry file may have been corrupted due to 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.
How to Troubleshoot a Stop 0xC0000218 Error Message
STOP: 0xC0000221
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.
“STOP: C0000221 unknown hard error” or “STOP: C0000221 STATUS_IMAGE_CHECKSUM_MISMATCH” error message occurs
Reaset Print Spooler Services In XP
If you were looking for a way to reset the print spooler on a Mac but ran across this article, check out this previous post. Otherwise, here was the situation. I had a user who was having issues printing on a Windows XP computer. The print spooler would crash, and even if the spooler was running the Printers folder would lock up if you tried to look at it. I did some digging and found an article that solved my problem, and also pointed to Microsoft KB 324757. I tweaked the steps a little to fit my situation, and didn't use safe mode, but it still worked. Here's what to do:
1. Stop the print spooler service if it's running, but leave the window open because you'll need to start it again at the end. If you don't know how to stop or restart the spooler, check out my previous post
2. Navigate to C:\Windows\system32\spool\printers\ and delete all the files you find there
3. Now go into C:\Windows\system32\spool\drivers\w32x86\ and delete all the files you find there
4. Open the registry editor. To do that, go to Start->Run, then type regedit and click Ok
At this point make sure you follow the directions exactly. Any changes to the registry are immediate, and have the potential to corrupt your Windows install if not done correctly.
5. In the registry editor, navigate to HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Control->Print->Environments->Windows NT x86
6. Expand the Windows NT x86 key. You should only see "Drivers" and "Print Processors". If there is anything else there delete it
7. Expand "Drivers", then expand the Version-x folder. I'm guessing it will be Version-3 for most of you, but the number may differ. Delete all the folders within the Version-x folder. These correspond to drivers installed on your system
8. Now go to HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Control->Print->Monitors
9. There should be 5 keys here: "BJ Language Monitor", "Local Port", "PJL Language Monitor", "Standard TCP/IP Port", and "USB Monitor". If you have any others, delete them.
10. Close the Registry Editor
11. Start the print spooler service
12. Restart the computer and reinstall your printer(s)
1. Stop the print spooler service if it's running, but leave the window open because you'll need to start it again at the end. If you don't know how to stop or restart the spooler, check out my previous post
2. Navigate to C:\Windows\system32\spool\printers\ and delete all the files you find there
3. Now go into C:\Windows\system32\spool\drivers\w32x86\ and delete all the files you find there
4. Open the registry editor. To do that, go to Start->Run, then type regedit and click Ok
At this point make sure you follow the directions exactly. Any changes to the registry are immediate, and have the potential to corrupt your Windows install if not done correctly.
5. In the registry editor, navigate to HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Control->Print->Environments->Windows NT x86
6. Expand the Windows NT x86 key. You should only see "Drivers" and "Print Processors". If there is anything else there delete it
7. Expand "Drivers", then expand the Version-x folder. I'm guessing it will be Version-3 for most of you, but the number may differ. Delete all the folders within the Version-x folder. These correspond to drivers installed on your system
8. Now go to HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Control->Print->Monitors
9. There should be 5 keys here: "BJ Language Monitor", "Local Port", "PJL Language Monitor", "Standard TCP/IP Port", and "USB Monitor". If you have any others, delete them.
10. Close the Registry Editor
11. Start the print spooler service
12. Restart the computer and reinstall your printer(s)
Tuesday, September 21, 2010
Double click on a drive opens in new window
Problem:
When i double-click on a drive, it opens in new window. What is the problem, Is it because of a virus. Please help me.
Solution:
Open any explorer window, Click on Tools >> Folder options >> View.
Click on restore defaults.
If this does not solve your problem the it may be because of a virus attack.
You can perform the following steps to get rid of this.
Solution 1
Open start menu and click Run.
Type regsvr32 /i shell32.dll
Click Ok and if this message shows “DllRegisterServer and DllInstall in shell32.dll succeeded” that means the problem is solved.
Solution 2
In Run type regedit.exe to open the registry editor.
Traverse to HKEY_CLASSES_ROOT/Directory/Shell
Double click on the default value on right and set it as “none”.
Repeat the procedure for the key HKEY_CLASSES_ROOT/Drive/Shell.
Solution 3
Alternatively, you can download a registry file and merge it with your registry by double clocking it. Reboot your system after merging the file.
One of the methods listed above will definitely solve your problem.
When i double-click on a drive, it opens in new window. What is the problem, Is it because of a virus. Please help me.
Solution:
Open any explorer window, Click on Tools >> Folder options >> View.
Click on restore defaults.
If this does not solve your problem the it may be because of a virus attack.
You can perform the following steps to get rid of this.
Solution 1
Open start menu and click Run.
Type regsvr32 /i shell32.dll
Click Ok and if this message shows “DllRegisterServer and DllInstall in shell32.dll succeeded” that means the problem is solved.
Solution 2
In Run type regedit.exe to open the registry editor.
Traverse to HKEY_CLASSES_ROOT/Directory/Shell
Double click on the default value on right and set it as “none”.
Repeat the procedure for the key HKEY_CLASSES_ROOT/Drive/Shell.
Solution 3
Alternatively, you can download a registry file and merge it with your registry by double clocking it. Reboot your system after merging the file.
One of the methods listed above will definitely solve your problem.
NTDS.DIT
KCC: (Knowledge Consistency Checker):
It is a service of A.D., which is responsible for intimating, or updating the changes made either in DC or ADC.
Active Directory is saved in a file called NTDS.DIT
C:\windows\ntds\ntds.dit
NTDS.DIT - New Technology Directory Services. Directory Information Tree
It is a file logically divided into four partitions.
1. Schema partition
2. Configuration partition
3. Domain partition
4. Application partition
It is a set of rules schema defines AD, it is of 2 parts classes & attributes.
Ad is constructed with the help of classes and attributes.
1. Schema:
Logical partition in AD database “template” for AD database.
· Forms the database structures in which data is stored.
· Extensible
· Dynamic
· Protect by ACL (Access Control Lists) DACLs and SACLs (Directory&System ACLs)
· One schema for AD forest.
Collection of objects is called class.
Piece of information about the object is called attribute.
2. Configuration Partition:
Logical partition in AD database.
1 “map” of AD implementation
2 Contains information used for replication logon searches.
3 Domains
4 Trust relationships
5 Sites& site links
6 Subnets
7 Domain controller locations.
3. Domain Partition:
1 Logical partition in AD database.
2 Collections of users, computers, groups etc.
3 Units of replication.
4 Domain controllers in a domain replicate with each other and contain a full copy of the domain partition for their domain.
5 DCs do not replicate domain partition information for other domains
4. Application Partition:
1 It is a newly added partition in win2003. It can be added or removed
2 It can be replicated only to the specified DCs.
3 Useful when we are using AD integrated services like DNS, TAPI services etc..
It is a service of A.D., which is responsible for intimating, or updating the changes made either in DC or ADC.
Active Directory is saved in a file called NTDS.DIT
C:\windows\ntds\ntds.dit
NTDS.DIT - New Technology Directory Services. Directory Information Tree
It is a file logically divided into four partitions.
1. Schema partition
2. Configuration partition
3. Domain partition
4. Application partition
It is a set of rules schema defines AD, it is of 2 parts classes & attributes.
Ad is constructed with the help of classes and attributes.
1. Schema:
Logical partition in AD database “template” for AD database.
· Forms the database structures in which data is stored.
· Extensible
· Dynamic
· Protect by ACL (Access Control Lists) DACLs and SACLs (Directory&System ACLs)
· One schema for AD forest.
Collection of objects is called class.
Piece of information about the object is called attribute.
2. Configuration Partition:
Logical partition in AD database.
1 “map” of AD implementation
2 Contains information used for replication logon searches.
3 Domains
4 Trust relationships
5 Sites& site links
6 Subnets
7 Domain controller locations.
3. Domain Partition:
1 Logical partition in AD database.
2 Collections of users, computers, groups etc.
3 Units of replication.
4 Domain controllers in a domain replicate with each other and contain a full copy of the domain partition for their domain.
5 DCs do not replicate domain partition information for other domains
4. Application Partition:
1 It is a newly added partition in win2003. It can be added or removed
2 It can be replicated only to the specified DCs.
3 Useful when we are using AD integrated services like DNS, TAPI services etc..
Transfer of FSMO Roles
We can transfer the roles for some temporary maintenance issues on to ADC and again we can transfer back the roles onto DC.
We can transfer the roles in two ways
1. Command mode
2. Graphical mode
Transfer of roles through command:
On DC
Go to command prompt and type ntdsutil
Type: roles
Connections
Connect to server (name of ADC ex.sys2)
Q
Transfer schema master
Transfer RID master
Transfer infrastructure master
Transfer PDCQ
Q
Exit
Transferring roles using GUI:
On DC
Register the schema
For registering schema
Start > run > regsvr32 schmmgmt.dll
Transferring schema master
On Dc
Start>Run>mmc>click on file> select add/remove snap in
Select A.D.Schema>add>close>ok
From console root
Expand console root
Right click AD Schema
Change domain controller
Specify name
Ok
Right click AD schema
Select operations master
Click on change
Yes> ok> file> exit (need not to save)
Transferring Domain naming master:
On DC
Start>p>admin tools> ADDT>right click on ADDT
Connect to domain controller
Select ADC
Ok
Right click on ADDT
Operations master
Click on change>yes>ok> close
Transferring Domain wide master operations:
Start >p>admin tools> ADUC
Right click on ADUC
Connect to DC
Select ADC > ok
Right click on Domain name
Select operations master
Change>yes
Select PDC> change>yes>select infrastructure>change>close>close.
Subscribe to:
Posts (Atom)