FiX Problems with Virtual Memory

This post provide further information about computer repair services for fix computer issues. today topic focus on virtual memory problems. It may sometimes happen that the system give ‘out of memory’ messages on trying to load a program, or give a message about Virtual memory space being low. Possible causes of this are:

The setting for Maximum Size of the page file is too low, or there is not enough disk space free to expand it to that size.

The page file has become corrupt, possibly at a bad shutdown. In the Virtual Memory settings, set to “No page file,” then exit System Properties, shut down the machine, and reboot. Delete PAGEFILE.SYS (on each drive, if more than just C:), set the page file up again and reboot to bring it into use.

The page file has been put on a different drive without leaving a minimal amount on C:.

There is trouble with third party software. In particular, if the message happens at shutdown, suspect a problem with Symantec’s Norton Live update, for which there is a fix posted here. It is also reported that spurious messages can arise if NAV 2004 is installed. If the problem happens at boot and the machine has an Intel chipset, the message may be caused by an early version (before version 2.1) of Intel’s “Application Accelerator.” Uninstall this and then get an up-to-date version from Intel’s site.

Another problem involving Norton Antivirus was recently discovered by MS-MVP Ron Martell. However, it only applies to computers where the pagefile has been manually resized to larger than the default setting of 1.5 times RAM — a practice we discourage. On such machines, NAV 2004 and Norton Antivirus Corporate 9.0 can cause your computer to revert to the default settings on the next reboot, rather than retain your manually configured settings. (Though this is probably an improvement on memory management, it can be maddening if you don’t know why it is happening.) Symantec has published separate repair instructions for computers with NAV 2004 and NAV Corporate 9.0 installed. [Added by JAE 2/21/06.]

• Possibly there is trouble with the drivers for IDE hard disks; in Device Manager, remove the IDE ATA/ATAPI controllers (main controller) and reboot for Plug and Play to start over.

• With an NTFS file system, the permissions for the page file’s drive’s root directory must give “Full Control” to SYSTEM. If not, there is likely to be a message at boot that the system is “unable to create a page file.”

Upgrade with the MSDN Version of Windows XP

When you try to upgrade Microsoft Windows 2000 Professional to Windows XP Professional by using the MSDN media, you may receive the following error message after your computer restarts the first time to start Text-mode Setup:

Setup was unable to verify drive C:. Your computer may not have enough memory to examine the drive, or your Windows XP CD may contain some corrupted files. To continue, press Enter.

After you press ENTER, you may receive the following error message:

To retry, press Enter. If you are not successful after several tries, quit Setup. Then, to restart setup, copy the Windows XP installation files to your hard disk.

Setup cannot access the CD containing the Windows XP installation files. To quit Setup, press F3.

If you restart your computer and choose the Windows 2000 option on the boot menu, you may receive the following error message on a blue screen:

STOP 0x0000007B (0xED41B84C,0xC0000034,0x00000000,0x00000000) INACCESSIBLE_BOOT_DEVICE

Resolution

To resolve this problem, note that MSDN Universal, Enterprise, Professional, and Operating Systems subscribers can download the final release of Windows XP from the MSDN Web site:

1. Download the ISO CD-ROM image from the following MSDN Subscriber Downloads page:
http://msdn2.microsoft.com/en-us/subscriptions/default.aspx

2. Rename the image file that you downloaded to File name.iso.
3. Double-click the file to start the CD-ROM burning software and burn the image to CD-ROM, restart your computer, and then run Setup.


Although the MSDN DVD version of Windows XP Professional may not work correctly when you try to upgrade from a previous operating system, a clean installation works correctly.

Fix XP Memory Dump File Error

This post provide technical support for fix memory dump error in windows XP. Windows XP came out as one of the greatest revolutions in the world of computers. The major drawbacks of the windows 98 and other previous versions were removed and new features were embedded. But the problem of Blue Screen errors and memory dump still persist. The annoying factor is that these blue screens lead to a catastrophic system crash and data loss in the Windows. It is therefore necessary to fix XP memory dump as soon as you see it.This post describe how to windows Fix dump file error.

What causes the XP memory dump?

Memory dump is not different from the Blue Screen errors or memory dump issues in the previous version of windows. The stop error messages like 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED or

Beginning of Physical Memory Dump in windows comes when any of the following occurs:

* The .dll files of any of the programs of the applications are missing or corrupt. This causes critical system errors and the system fails to recover from the error. The system crashes completely and the data is lost. This critical system error occurs because, a kernel or a driver running in the Kernel mode or the mode where the programs are actually trusted not to crash crashes. This is a deadly hit to the operating system and the Blue Screen of death appears or the memory dump takes place.
* In Microsoft operating system, the memory is allocated in different places and in different amounts. If there is a deadly and incorrect misallocation of the memory, the memory dump takes place and the system faces the Blue screen of death and there are stop error messages appearing every time you reboot the computer.

How to Fix XP Memory Dump?

Memory dump can also occur because of the RAM issues or because of the communication errors. Whatever be the case, there is a solution. The Memory Dump caused by the hardware can be solved by replacing them. However, in case the Kernel is there in the picture, the registry needs to be cleaned and repaired.

There is different registry cleaner software available in the market and are capable of doing the following tasks:

* Removes unwanted and invalid entries from the registry and helps to Fix XP Memory Dump.
* Fixes registry errors.
* Optimizes the windows based computer performance.
All you need to do is to grab the best registry cleaner software and use it to keep you computer fit and Fix XP Memory Dump. For detailed info on various registry cleaners, visit us at the following site.

If you would like to know what happens to your computer, you can have a free scan by visiting the site, Fix XP Memory Dump and find out he most effective, easiest, and cheapest way to fix and maintain your computer in the same time.

How to Disable or enable the startup

This post describe how to disable or enable the startup Quick Scan in SAVCE 10.0. In SSC, right-click a server group, client group, or server. Select 'All Tasks', select 'Symantec AntiVirus', and then click 'Client Administrator Only Options'. On the 'General' tab, under 'Scan Options', clear or select the 'Run startup scan(s) when user logs in' check box, and then click 'OK'.

Here some virus removal tips for your computer security purpose. A Quick Scan quickly scans files that are loaded into memory as well as common virus and security risk locations on the computer. By default, a Quick Scan automatically runs upon startup, when virus definitions are updated, and at the beginning of any manual or scheduled scan.

To disable or enable the startup Quick Scan:
1) Start Symantec System Center.
2) Unlock the appropriate server group.
3) Right-click a server group, client group, or server.
4) Select 'All Tasks', select 'Symantec AntiVirus', and then click 'Client Administrator Only Options'.
5) In the 'Client Administrator Only Options' dialog box, on the 'General' tab, under 'Scan Options', do one of the following:
'Client Administrator Only Options' dialog box
a) To disable the startup Quick Scan, clear the 'Run startup scan(s) when user logs in' check box.
b) To enable the startup Quick Scan, select the 'Run startup scan(s) when user logs in' check box.
6) Click 'OK'.