BSOD Error in Windows XP  

Scenario

Unmountable Boot Volume

STOP: 0x000000ED (0x8578be30, 0xc000000……..)

STOP: 0x0000007B

The computer is restarting with the above error. You will not notice this error unless you choose the option “ Disable automatic restart on system failure”. To get this Advanced option at Restart Windows and  startup press F8 and you will get this option along with other options like “ Safe Mode and Safe Mode with Networking”.

Now the moment the windows crashes at startup it won’t restart and instead throw the above mentioned error in BLUE SCREEN a.k.a BSOD error.

Solution:

The Stop: 0x7b error is related to HDD error. “unmountable boot volume” error arises for many reasons like corrupt partition table, MBR or boot sector. To fix it follow the below steps:

 Boot with Windows XP CD  and  choose ‘R’ for  repair windows  using Recovery Console.

Type:

chkdsk c: /r

C: is the drive letter of the Operating System, replace it with whatever letter you have assigned to your OS drive.

The above command checks for bad sectors and fixes them.  It will run for about 20-30 mins depending upon the severity of the corruption. After completion, Type “exit” and press Enter.

The computer will restart, take the CD out.

In 90% cases it solves the problem.

You can use Hiren boot’s Mini XP option and ERD Commander to solve this issue also.

After booting into Mini XP open cmd and type the command  “chkdsk c: /r”.

This will also resolve the issue.

Remote Desktop Connection License Issue

Error : The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer. Please contact the server administrator.

The solution is to delete the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing

After deleting the key from the registry start Remote desktop connection as administrator by right clicking on the"mstsc.exe" icon in c:\windows\system32\mstsc.exe.

How to Clone or Copy a Bootable Pen Drive

1. Download ImageUSB application from here. It is available in ZIP format so you can use any good Compression tool to extract ZIP files like WinZip or WinRAR.

2. Now insert your working bootable pen drive which is fully functional and the one you want to clone onto the other slot available and start ImageUSB application from extracted ZIP file folder.

3. ImageUSB will detect automatically both your pen drives. If for any reason your pen drive shows as not available then click on refresh button to detect the pen drive.

4. Now select your pen drive from the list and then click on Create from UFD option (You can see it asStep 2 on application). First we want to make a complete image of your pen drive and save them on the system. So we have to select Create from UFD option.

5. Now browse location where you want to save image of you bootable pen drive and it will save it as .bin file on the system. Finally click on Create image button and application will start image creation process and save it on the computer. It will take a few minutes depending on the system speed and pen drive size.

6. Now we have the full image of your multi bootable pen drive and now need to burn it to another pen drive to make it multi bootable identical to your cloned pen drive.

7. Insert your new pen drive and click on Refresh Drives to detect your inserted pen drive (please remove your old one). Now you can see your pen drive in the list, select your pen drive from list and then select option Write to UFD (on application you can see it as Step 2).

Note: Please backup your pen drive data because image burning process will remove all data from the pen drive and write image file. So be careful before starting this process.

8. Finally browse image (bin file) which you had created using step 5 on this post and click on Write to UFD button to start image file burn process into new pen drive. Again it will take few minutes and then your new pen drive will become a clone of you old working multi-boot pen drive.

Now you have full image backup of your bootable USB pen drive and using this image you can make many bootable clone pen drives. Once you create image from Bootable pen drive you will never use any other application to create a bootable pen drive.

Note: On application you can see one more option Post Image Verification, you can use this application without selecting it. Just use it only for verification and sometimes for application shows verification failed but pen drive works well. So I think there is nothing to worry if application shows verification failed, you pen drive will 100% work in such cases as well.

Windows 7 Temp login Issue

Sometimes when you log in you find that your desktop files. the wallpaper and everything changed but don't panic, your DATA is secure. It is just that your user profile has been logged into a temp profile.
When there something goes wrong with your user profile Windows 7 logs you in with a Temporary profile so at-least you can work, it's actually a feature unlike previous versions of windows where you  are denied access from logging in from your own PC and that's truly frustrating.

Now let's how you can take back your profile.

1)      Log in with temp profile.
2)      Start registry editor by typing regedit in find box in Windows 7.
3)      Navigate the following location in Windows 7.

4)      You can see similar keys under profile list with .bak difference, as shown below.

5)      You correct profile key is marked as bak. Currently your Windows 7 computer logged in with fresh profile with same key. So, rename the new profile key ( which is not having.bak) and remove .bak from correct profile key. See below.

6)      That’s it. Log off and log in with your user name and password. You must get your icons and profile settings back in Windows 7. This is very simple and easy method to fix temp profile in Windows 7  issue.

Changing RDP Port no (XP/2003/2008)

explore the following registry key & change the value from 3389 to "xxxx" (different from registered port nos)

key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]

String : PortNumber

String Value: 3389 (decimal mode)

chenge the string value to your desired port no "xxxx"

Changing UID of virtual Hardisk of Virtual Box

The situation of changing the UID of virtual Hardisk of Virtualbox arises when you want to use the existing hard disk to create a new virtual machine(VM) without going through the whole process of installing the OS. The virtualbox simply don't accept the existing hard disks. To get around that you need to change the virtual hard disks UID(Unique Identifier). The virtualbox provides you with this facility inside it's package. Follow these steps:

a) Open command prompt: Start->run->cmd

b) Go to the path where your virtualbox is installed which is normally is in your

c:\program files.

Type "cd D:\Virtual-Box"

c) Once inside the directory type in:

"VBoxManage internalcommands setvdiuuid d:\Vm-HDD\Win-2003-Server-adc.vdi"

Note: VBoxManage is the application which changes the UID of the hard disk.

"d:\Vm-HDD" is the location where you store your virtual hard disks.

"Win-2003-Server-adc.vdi " is the name of your harddisk. So change it according to your virtual hard disks name.

Hardware Interrupts taking high CPU

First of all Check with the utility from "sysinternal" called "Process Explorer", google it and download it. If it is showing that Hardware Interrupts is taking the CPU, then you to follow the below steps.

If your problem is having the following similar characterstics i.e:

a) Copying a large file within a drive for eg. C: drive giving only 2-5 mb speed.

b) Your Hard Disk is working in PIO transfer mode instead of Ultra DMA mode.

# To check right click on "My Computer"

# Click on Manage ->Device Manager

# On the right pane, expand IDE ATA/ATAPI controller

# Right Click on primary or secondary IDE controller on which your HDD is connected to.

# Click on" Advanced Setting" Tab

# If your HDD is connected to "Device 0" or "Device 1" check it's "Transer Mode" is set to " DMA if available" and "Current Transerfer mode" is Ultra DMA mode.

Note: PIO mode is the slowest of all and windows OS set it to PIO when 6 times CRC error happens.

Solution: Copy the following visual basic script and paste it to a text file and save it with the extension ".vbs" Eg. "resetDMA.vbs". Click on the file and click ok and the manually reboot. And then to check it follow the above steps to see if the HDD current transfer mode has come back to "Ultra DMA Mode".

To double check copy a large file and you will notice the speed by yourself.

VB Script

===================================================================

' Visual Basic Script program to reset the DMA status of all ATA drives

' Copyright © 2006 Hans-Georg Michna

' Version 2007-04-04

' Works in Windows XP, probably also in Windows 2000 and NT.

' Does no harm if Windows version is incompatible.

If MsgBox("This program will now reset the DMA status of all ATA drives with Windows drivers." _

& vbNewline & "Windows will redetect the status after the next reboot, therefore this procedure" _

& vbNewline & "should be harmless.", _

vbOkCancel, "Program start message") _

= vbOk Then

RegPath = "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\"

ValueName1Master = "MasterIdDataChecksum"

ValueName1Slave = "SlaveIdDataChecksum"

ValueName2Master = "UserMasterDeviceTimingModeAllowed"

ValueName2Slave = "UserSlaveDeviceTimingModeAllowed"

ValueName3 = "ResetErrorCountersOnSuccess"

MessageText = "The following ATA channels have been reset:"

MessageTextLen0 = Len(MessageText)

ConsecutiveMisses = 0

Set WshShell = WScript.CreateObject("WScript.Shell")

For i = 0 to 999

RegSubPath = Right("000" & i, 4) & "\"

' Master

Err.Clear

On Error Resume Next

WshShell.RegRead RegPath & RegSubPath & ValueName1Master

errMaster = Err.Number

On Error Goto 0

If errMaster = 0 Then

On Error Resume Next

WshShell.RegDelete RegPath & RegSubPath & ValueName1Master

WshShell.RegDelete RegPath & RegSubPath & ValueName2Master

On Error Goto 0

MessageText = MessageText & vbNewLine & "Master"

End If

' Slave

Err.Clear

On Error Resume Next

WshShell.RegRead RegPath & RegSubPath & ValueName1Slave

errSlave = Err.Number

On Error Goto 0

If errSlave = 0 Then

On Error Resume Next

WshShell.RegDelete RegPath & RegSubPath & ValueName1Slave

WshShell.RegDelete RegPath & RegSubPath & ValueName2Slave

On Error Goto 0

If errMaster = 0 Then

MessageText = MessageText & " and "

Else

MessageText = MessageText & vbNewLine

End If

MessageText = MessageText & "Slave"

End If

If errMaster = 0 Or errSlave = 0 Then

On Error Resume Next

WshShell.RegWrite RegPath & RegSubPath & ValueName3, 1, "REG_DWORD"

On Error Goto 0

ChannelName = "unnamed channel " & Left(RegSubPath, 4)

On Error Resume Next

ChannelName = WshShell.RegRead(RegPath & RegSubPath & "DriverDesc")

On Error Goto 0

MessageText = MessageText & " of " & ChannelName & ";"

ConsecutiveMisses = 0

Else

ConsecutiveMisses = ConsecutiveMisses + 1

If ConsecutiveMisses >= 32 Then Exit For ' Don't search unnecessarily long.

End If

Next ' i

If Len(MessageText) <= MessageTextLen0 Then

MessageText = "No resettable ATA channels with Windows drivers found. Nothing changed."

Else

MessageText = MessageText & vbNewline _

& "Please reboot now to reset and redetect the DMA status."

End If

MsgBox MessageText, vbOkOnly, "Program finished normally"

End If ' MsgBox(...) = vbOk

' End of Visual Basic Script program

===================================================================