The following error message may be displayed on your Windows Server:

Stop 0x00000077

Or

KERNEL_STACK_INPAGE_ERROR

Cause of the Error

This error, also known as the Stop 0×77 error, is displayed when either:

• The master boot record (MBR) of your system is infected with a boot sector virus, or
• Paging file is unable to read a requested kernel data into memory.

To find the cause of the error it is essential to further interpret the error message. If, in the error code, both first and third parameters are zero, then the four parameters are defined in the following way:

1 – Zero (0)
2 – Page Table Entry (PTE) value at time of error
3 – Zero (0)
4 – Address of kernel stack signature

In case either, the first or third parameter is not zero then the following will apply:

1 – Status code
2 – Status code of I/O
3 – Number of Page File
4 – Offset into Page File

In this case, the cause of the problem is determined by the second parameter that depicts the I/O status code. The following information listed in the value of the second parameter helps you determine the general cause of the error message:

0xC000000E (STATUS_NO_SUCH_DEVICE): The required drive is unavailable, indicating either one or all of the following are bad:

• Hard drive
• Disk controller
• Disk array

0xC000009A (STATUS_INSUFFICIENT_RESOURCES): Non-paged resources are not available.

0xC000009C (STATUS_DEVICE_DATA_ERROR): There are bad blocks on the hard disk.

0xC000009D (STATUS_DEVICE_NOT_CONNECTED): Cable is bad or is not terminated, or the controller is unable to gain access to the hard disk.

0xC000016A (STATUS_DISK_OPERATION_FAILED): There are bad blocks on the hard disk.

0xC0000185 (STATUS_IO_DEVICE_ERROR): SCSI-based devices are not terminated properly or the cable is defective. Or, two devices are trying to gain access to the same IRQ.

Resolution Methods

You can use the following methods to resolve these errors.

Method 1: Scan and Remove Boot Sector Virus

To scan the MBR of your system, use a reliable Antivirus tool  and scan the boot sector of your system. If there is an infection in the boot sector, your antivirus tool should clean it and resolve the problem.

Method 2:

If the error is not caused due to a boot sector virus, perform the following tasks.

First, open the Event Viewer on your Windows computer and then in the System log look for additional error messages that may help you determine the device that is causing the error.

If the first and second parameters are zero (0), it indicates that the stack signature could not be located in the kernel stack. This problem occurs due defective hardware.

Now, if the I/O status is C0000185 and the paging file exists on a SCSI hard disk, you must ensure that there is no problem with SCSI termination and cabling.

In case the I/O status code is 0xC000009C or 0xC000016A, it usually indicates that there are bad blocks on the disk due to which data could not be read. In this case, when you reboot your Windows PC, the Autochk must run automatically on the system to determine and mark the bad sector. In case the tool does not run automatically, you must manually run it to determine the bad sector(s) on the disk. In case you have NTFS partition on your hard disk, run the Chkdsk /f /r on the system partition. Also, you must reboot the system before the scanning process starts. If you are unable to start the PC, use the Command Prompt of your Windows computer to run the Chkdsk /r command.

Some of the other tasks that you can perform to repair the error are:

• Ensure that RAM or memory of your computer is not defective.
• Ensure that all adaptors are properly seated in their slots.
• Ensure that the connectors of all adaptors connected to your system are clean.
• Disable system caching from BIOS to see if doing this resolves the issue.
• Check your motherboard for faults.

Getting userenv 1030 and 1058 in event viewer

Windows  provides the ability to resize volumes directly from the command line using the Diskpart utility. The Windows Diskpart utility is a command line program for managing the disk partitions, or volumes, on your computer. Some of the tasks you can do with this utility include repartitioning drives, deleting partitions, creating partitions, changing drive letters, and now shrinking and expanding volumes.

To access the diskpart utility follow these steps:

1. Click on the Start Menu button.
2. In the Run/Search field type Diskpart and press the enter key on your board.
3. Windows Vista may ask if you want to allow this program to run and you should press the Continue button.
4. A command prompt will now open and you will be within the Diskpart console. For a list of commands that you can use within the Diskpart console you can type help. For the help instructions for a particular command you can type the name of the command followed by help, such as select help .

Before you can expand or shrink a volume using Diskpart you must first select the volume you would like to work with. To do this you need to use the list volume command to find the IDs associated with each volume. When you type list volume and then press enter, diskpart will display a list of Windows volumes on your computer. Next to each volume will also be a numbers that can be used to identify that specific volume. An example of what the list volume command looks like can be found below.

After determining the ID of the volume that you would like to work with, you need to select that volume using the select volume command. To use this command you would type select volume ID, where ID is the ID associated with the volume you found using the list volume command. Now that the volume has been selected, diskpart knows that any further commands will be associated with this particular volume until you enter another select volume command.

To shrink a selected volume you would use the shrink command. The shrink command has two arguments that you can use to define how you want diskpart to shrink the volume. The first argument is desired= which will shrink the volume by the desired amount in MB if possible. The second argument is minimum= which tells diskpart that it should only shrink the volume if it can shrink it by the specified amount in MB. If you do not use either of these arguments, diskpart will shrink the partition by the maximum amount possible. If you would like to determine the maximum amount of space that you can shrink a volume, you can type the shrink querymax command.

Shrink examples are:

Shrinking a volume from the command line

To extend a selected volume you would use the extend command. For the extend command the most common arguments are size and disk. The size= argument will extend the selected volume by the desired amount of MB. The disk= argument allows you to specify the disk which has the free space you wish to extend a volume with. If no argument, or no disk= argument, is provided when using the extend command, diskpart will use all the available space on the current disk to extend the volume. As said previously, we strongly suggest that you do not use the disk= argument to extend a volume onto another disk as this increases your chance of losing data if one of the two drives has a hardware failure.

Extend examples are:

Steps for Transferring the FSMO Roles
To transfer the PDC,RID and then Infrastructure Master roles
Open dsa.msc and right click on the domain name and click on Operations Master and click on change to change the DC
To transfer the Domain Naming Master Role
Open domain.msc and right click on the domain name and click on operations master and click on change
To transfer the Schema Master
Start-Run-regsvr32 schmmgmt.dll
Open the schema snap in and transfer the role

RESOLUTION : “Assume User Called SRC and Server is called SRV”
============
– We created a new group policy with the following settings enabled (Under Computer Configuration=> Administrative Templates=> System=> User Profiles)
1. Add the Administrators security group to roaming user profiles
2. Delete cached copies of roaming profiles
- We opened Active Directory users and computers
- We moved the user SRC to a new OU UserSRCProfile
- We went to the properties of the user SRC and clicked on the profile tab
- We pointed the roaming profile for user SRC to the following share \\srv\userprofiles\%username%
- We logged in with the user SRC and made changes to the profile and logged off
- We Went to the location of the roaming profile for user SRC (\\srv\userprofiles\src) and renamed the ntuser.dat to ntuser.man (to make the profile mandatory)
- We logged back in and verified that the settings are taking affect
- We tried to log in to a different computer (ex. computer7) and we noticed that the settings did not take affect
- We logged in to computer7 as the administrator and went to control panel=> regional and language options=> languages tab and install files for East Asian languages
- We deleted the locally cached profile of user SRC (under c:\documents and settings\SRC) and rebooted computer7
- Customer created a new group policy with the following settings enabled (under User Configuration=> Administrative Templates)
1. Start Menu and Taskbar=> Remove Run menu from Start Menu
2. Control Panel=> Prohibit access to the Control Panel
3. Desktop=> Hide and disable all items on the desktop
- We logged in with user SRC and verified that the settings are taking affect