Ask Me Solution

As web hosting is the one of the key factor for your company’s existence in the internet , you should pay attention to which web host service are you going to use for your business. This doesn’t mean that you should opt for the expensive web host in the market. Just find a web host which provides the feature your website uses or is planning to use in the near future. And believe me it’s not hard to find one which cost less than $10 per month.

Some of the characteristic you should be looking in a web hosting service is the features it provides for the price that you pay. You may want to avoid free ones, as those hosts will have very limited services like storage, FTP upload volume, Email accounts and security. If you are running an ecommerce website, then would need features like SSl, MySQL, PHP, Perl, FTP, telnet etc. Before you sign up for a web host, check if they offers these services or not. Also, check how much bandwidth and space your website will get in the plan. Make sure your web host can serve you if you need to upgrade in future.

Other important factors are:-

1.Customer Support:
If your website ever need help in some critical situation, then your hosting service must be good enough to respond to you quickly. Trying testing the customer support by calling them at odd hours and see if they can respond to you in real-time.

2.Uptime:
If you want attract audience then your site must have uptime of 99.9%. You can find some hosts offering you a 100% guarantee system uptime. It is quite impracticable to offer this but such host will give you some recompense in case of any downtime.

3.Company Stability:
You cant afford to have unreliable web hosting services for your business. It is always wise to read the web hosting reviews and choose your host carefully.

Stop Code: STOP 0×0000007B
INACCESSIBLE_BOOT_DEVICE
Code Meaning:
Caused when Windows loses access to the system partition during the Startup process. This can be caused by: an incorrect driver for a SCSI, RAID, or UDMA IDE controller; incorrect ARC path in the Boot.ini; or a failed boot device.
Recommended Resolution:
Verify that the disk storage device is installed correctly and working. Reinstall or update the device driver. Verify that the BIOS setting for the device is correct. Verify the integrity of the hard disk.

Stop Code: STOP 0×0000007F
UNEXPECTED_KERNEL_MODE_TRAP
Code Meaning:
Caused when the CPU generates an error that the kernel does not catch. Usually hardware related—especially RAM. Can also be caused by CPU overclocking, or defective components on the motherboard. Recommended Resolution:
1. Run the memory diagnostic to test RAM.
2. Restore overclocked settings to previous values.
3. Repair/replace the motherboard.
4. Disable sync negotiation in SCSI BIOS; check SCSI termination.

Stop Code: STOP 0×000000D1
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Code Meaning:
Occurs when the system attempts to access pageable memory at a process IRQL that is too high Recommended Resolution:
Very similar to STOP 0xA. Remove, disable or stop the offending drivers, backup utilities or anti-virus programs. Get updated software from the manufacturer.

Stop Code: STOP 0xC000021A

STATUS_SYSTEM_PROCESS_TERMINATED
Code Meaning:
Caused when the user-mode subsystem (Winlogon or CSRSS) is fatally compromised and security cannot be guaranteed. The most common causes are third-party applications or mismatched system files.
Recommended Resolution:
1. Remove, disable, or roll back any newly-installed device driver.
2. Uninstall any newly-installed software.
3. Use Windows-compatible backup/restore programs.
4. Restore full control permissions to the local SECURITY account on the systemroot folder by doing a fresh parallel installation of Windows on a separate partition.

Stop Code: STOP 0×0000000A
IRQL_NOT_LESS_EQUAL

Code Meaning :
Faulty device drivers, or services from backup utilities or virus scanners
Recommended Resolution:
Remove, disable or stop the offending drivers, backup utilities or anti-virus programs. Get updated software from the manufacturer.

Stop Code: STOP 0×0000001E
KMODE_EXCEPTION_NOT_HANDLED

Code Meaning:
Some driver files may be causing a problem.
Recommended Resolution:
Remove, disable or update the driverfile listed in the error message. Verify if new hardware installation
is correct.

Stop Code: STOP 0×00000024
NTFS_FILE_SYSTEM

Code Meaning:
Usually caused by disk corruption in the NTFS file system or third-party disk defragmenters.

Recommended Resolution:
Use hard disk diagnostic software to verify that the hard disk is working. Remember to always Use
Microsoft-certified disk defragmenters.

Stop Code: STOP 0×0000002E
DATA_BUS_ERROR

Code Meaning:
Caused by a parity error in the system memory. Almost always caused by hardware problems—a configuration issue, defective hardware, or incompatible hardware.

Recommended Resolution:
If physical RAM was recently added to the system, remove it and see if the error still occurs. If the error persists, try disabling memory caching in the BIOS. Else remove, repair or reinstall the defective hardware.

Stop Code: STOP 0×00000050
PAGE_FAULT_IN_NONPAGED_AREA

Code Meaning :
Caused when requested data is not found in memory; the system checks the page file, but the missing data is identified as unable to be written to the page file

Recommended Resolution:
Remove any newly-added hardware or run diagnostic software supplied by the manufacturer to check if
the component has failed. Install updated device drivers or roll back to a previous driver.

When a BSOD occurs, the first step is to note down the Stop number, the ‘friendly name’ of the error and also the name of the file that is reported as the cause of the problem. The Stop number will be in hexadecimal format—something like this:
STOP : 0×0000000A (0xDB000000, 0×00000001, 0×00000002,0xB04FB0DB)
The friendly name will be something like this:
IRQL_NOT_LESS_OR_EQUAL

• If the error comes up very briefly, before you can note it down, and the system restarts, you will need to change a setting to tell Windows not to automatically reboot. Right-click My Computer, select the Advanced tab, and click “Startup and Recovery”, in Windows 2000, clear the “Automatically Reboot” checkbox. In Windows XP, click Settings and clear the “Automatic Restart” checkbox. This, of course, assumes that Windows has rebooted normally and you are able to change the setting.

• If you are not able to boot normally, restart Windows and press [F8] repeatedly during the POST cycle. This will take you to the Advanced Options menu. Choose Safe Mode. Windows will attempt to load with a minimum set of drivers. If Windows is able to boot into Safe Mode, this most likely means that the problem is with a particular software, and is not hardware-related. If Windows is not able to boot into Safe Mode, restart the computer, bring up the Advanced Options screen (by pressing [F8] during POST) and select “Last Known Good Configuration”. Windows will then attempt to load the last settings where everything worked normally. If that doesn’t work, then it most likely means you have a serious hardware or critical startup system file error. If this error has occurred after any recent hardware additions, remove the hardware and try to boot again.

• If you are able to boot into Safe Mode, first perform a virus and spyware scan using a tool such as Norton AntiVirus and Spybot S&D. Uninstall any recently added software, and remove or roll back any
  updated device drivers. (To roll back device drivers, go to the Properties page of the device in Device Manager, select the Driver tab, and click Roll Back Driver). In XP, you can perform one additional step—running System Restore, as explained above for Windows ME.

• Restart the computer normally and check if the problem recurs. If it is an intermittent problem, and occurs at random, you can note down the error number the next time it occurs, since you disabled
  Automatic Restart after a crash. Boot into Safe Mode and see if you get the same random error. If you do, then the problem is likely hardware-related. Resolve the issue by following the hardware troubleshooting steps explained below. If the error only occurs in normal mode, then it is likely a software problem. Follow the steps for software and device driver troubleshooting described below.

• Look in Device Manager and troubleshoot any hardware device conflicts as explained in the troubleshooting Hardware Device Conflicts in Windows section. You can remove or disable the device, or roll back its driver to a previous version.

• If the BSOD is caused by a faulty program that crashes Windows at system startup, you can disable the software from starting up by using msconfig.exe. Type Start > Run, type in “msconfig” and press
  [Enter]. Select the Startup tab and disable any or all software you think may be the ones causing the problem. Better still, you could disable all the software in the list, enable them one at a time, and
  reboot the computer to identify the offending software.

• If the BSOD is caused by faulty hardware, remove any recently added hardware—after switching off the PC, of course! If the BSOD still occurs, or there are no newly added hardware, test the RAM for errors by using a memory diagnostic program such as Windows Memory Diagnostic (http://oca.microsoft.com/en/windiag.asp). If the diagnostic reports errors, then you’ve found the culprit. Replace the defective RAM.

• If the BSOD is due to corrupt system startup files, you can repair Windows by performing a Repair nstall. Boot the PC from the Windows installation CD, press [Enter] to set up Windows XP, press
  [F8] to accept the license agreement, and then press [R] to start the Repair Installation. Windows will reinstall all the system files and redetect all the hardware.
  Note: You will have to visit the Windows Update site to reinstall any patches and Service Packs, since the repair installation will remove them.

• If you are still getting BSODs, switch off the PC, open the cabinet and remove all but the essential hardware: the mouse, keyboard, hard disk, CD-ROM, display card and RAM, along with the PSU and processor of course! Now, first attempt booting into Safe Mode, and if that works, reboot normally. If you are successful, the problem is with one of the peripheral devices. Add all the peripherals back one by one till you get a BSOD again—the last added peripheral is the culprit.

• If you are getting BSODs during installation, then the problem could be with the RAM, hard disk, processor, or one of the peripherals. Test the RAM using a memory diagnostic tool as described above, check the hard disk for errors (most hard disk manufacturers provide software utilities that can diagnose
  errors), verify that the CPU is not overheating by following the instructions in the Motherboard section of this guide, and remove all peripherals and run the installation with the minimum configuration as described above. If the installation is successful, you can troubleshoot the rest of the hardware devices
  from within Windows.

One of the most dreaded error messages for a Windows user is the blue screen, or the Blue Screen of Death (BSOD) as it is popularly known, which suddenly pops up informing you that something is seriously wrong with Windows. What this screen essentially means is that Windows has crashed and needs to reboot to recover. Usually, you will be able to recover and continue without any problems, but it can sometimes be a hair-raising experience—like when you’re pressed for time and have to get that owerPoint presentation ready for your boss!

Problems causing the BSOD
The BSOD is the main way for virtual device drivers to report a problem. The error description will state that Windows faced a problem (exception) at a particular memory address (a portion of the RAM) in a certain file, usually with the prefix VxD (virtual device driver), or the file name may have the DLL xtension. At the minimum, it indicates that there was a problem with that particular file. Typically, this ay have been caused by some action of the user that Windows does not allow—like accessing a ocument from a floppy and then removing the floppy before closing document. In other cases it may ndicate that there is a problem with a particular software or hardware. If the BSOD repeats with the same message, then there is potentially something seriously wrong, and you should investigate further.

Problem:Shutdown is very slow.

.

Cause:

Windows is waiting for all running programs and services to stop before shutting down.

Solution:
In XP, many programs (including Windows itself) install services that run in the background, waiting for some action from the user. Some of these may take a long time to shut themselves down after receiving the Shutdown command from Windows. Identifying the service or services causing this problem will mostly be a trial and error process. If you have installed some software recently it might have a service that is slow in exiting and is delaying the shutdown process. To find out the list of services that are running on your system, click Start > Run, type in “services.msc” and click OK. This launches the Services Manager. Look through the list and identify any
services related to software you have recently installed.

Stop the services one at a time and shut down the system till you identify the offending service. Restart all the other services and shutdown again just to make doubly sure you’ve stopped the right service. Note: Ensure that you don’t stop any Windows systems services and other essential services. Stopping critical and essential services will cause more problems. Also, you should be aware that if you stop a service related to any software you have installed, that particular software may not function correctly or not function at all. Check the vendor’s Web site for more details on the issue and any updates to correct it.

Problem: A BSOD during shutdown.

Cause:

This is most likely a problem with the hardware; it may also be caused by rogue software or problems with system services.

Solution:

Note down the stop message error code and the friendly name. Refer to the Troubleshooting BSODs section for general principles on how to troubleshoot the problem. Troubleshoot problems with Windows system services .

Problem: The system hangs at the “Saving your settings” screen.

Cause:

This is a known issue in older XP releases, and can be patched by upgrading to Service Pack 1. Also, some software drivers “lock” during the shutdown process, preventing Windows XP from shutting down completely.

Solution:

Upgrade your system to at least Service Pack 1. Update the device drivers. If the problem persists, uninstall problematic devices through Device Manager and all their associated software, and restart the computer. Windows XP will auto-detect the hardware and ask you to provide the location for the software drivers. Specify the location of the new drivers and let Windows complete the installation. Some devices may require a firmware update. See the Updating the BIOS section of this guide to understand the general principles on how it is done. Refer to the manufacturer’s Web site for details on the exact steps to be followed.

Problem: When you click on “Shut down”, XP reboots!

Cause:

Windows XP, by default, is configured to restart in case of an error. This behavior may occur if an error is generated during the shutdown process. It could be either hardware or a software problem.

Solution:

Disable Automatic Restart. Right-click My Computer. Select Properties > Advanced > Settings > Startup and Recovery. Clear the “Automatically Restart” checkbox. Shut down the computer and see if you get an error message or a BSOD. Follow the troubleshooting steps explained earlier in the BSOD section of this guide. If there is no error message or BSOD, check your hardware.

Some of the most common culprits are CD-Writing software suites (Roxio, Nero, etc.), some specialty keyboards such as Internet keyboards, USB devices, and power management settings. Check the drivers for all the hardware devices and update them if possible. Unplug the hardware devices one by one and go through the shutdown process to isolate the device. Check the power management settings and switch to the “Always On” option. Troubleshoot problems with Windows system services as explained earlier in this chapter.

Tip
Disabling the wrong service will cause further problems so be sure of the service you wish to disable. If you wish to reenable a service from Recovery Console type “enable <servicename_ type>”. Here, servicename_ type should be the same type that was showed on your screen when you shut down the service.

Problem: You receive an error message when Windows XP starts.
Cause: A recently installed file or service or software program is incompatible with Windows XP and is preventing it from starting. Look carefully at the error message. If a file or service name is referred to in the error message, then you can troubleshoot by either clean booting or by stopping the service.
Solution 1a: To perform a clean boot in Windows XP, use the following steps:

1. Start the system configuration tool by going to Start > Run, typing in “msconfig”, and pressing [Enter]
2. Click Selective Startup and clear the following checkboxes: “Process System.ini File”, “Process Win.ini File”, and “LoadStartup Items”.
3. Select the Services tab and click the “Hide All Microsoft Services” checkbox, and then select “Disable All”.
4. Click OK and then “Restart” to restart your system.
5. When Windows restarts, if the error doesn’t occur, re-open “msconfig” and check the “Process System.ini File” checkbox,click OK and restart your computer. If the error returns, you know that the problem is with one of the System.ini entries. If the error doesn’t occur, progressively enable the remaining checkboxes (“Process Win.ini File”, “Load Startup Items”, and “Load System Services”). Restart the computer after you enable each checkbox till the error occurs again.
6. Once you have identified the area in which the error occurs, disable the entry or stop/disable the service as the case may be.

Solution 1b:If you are unable to perform a clean boot to troubleshootthe problem and you know the name of the service,then start the Recovery Console as explained earlier. From thecommand prompt, change to the System32 folder. Type in “listsvc” at the command prompt in the System32 folder. A list of all services on your computer will be displayed. Locate the service name that is causing the error. Type “disable ” and press [Enter].
The computer will print a message listing the “start type” that is being shut down. Note it down in case you need to re-enable the service. Type “exit” and allow the computer to restart normally.

Solution 1c: If you recently installed a program that is causing this error, remove the program. If the program is not listed in the Add/Remove list, you’ll have to visit the developer’s Web site for instructions on how to remove the program.
Problem: After an upgrade, programs that loaded during startup do not start.
Cause: This symptom is noticed when you log in for the first time after upgrading from Windows 98 or ME. Windows XP will remove all programs from the startup list, which it ‘feels’ are not compatible.
Solution: Click Start > Run, type in “msconfig” and press [Enter]. Click the Startup tab. Select the “Restore Startup Programs” option and click OK. Restart the computer. (This option won’t be available if Windows XP Setup did not disable any startup programs.)