Getting "Not enough memory available to complete this operation" error message using Sound Recorder

You install disk is corrupt (probably from a scratch on the disk), you can download a new copy to burn, making sure it passes the MD5 checksum after download is complete (and use your key during installation).

When you start your computer, you may receive one of the following error messages:

• STOP: 0x0000007B (parameter1, parameter2, parameter3, parameter4)
  INACCESSIBLE_BOOT_DEVICE
• Setup has encountered a fatal error that prevents it from continuing.
  
  Contact your product support representative for assistance. The following status will assist them in diagnosing the problem.
  
  (0x4, 0x1, 0, 0)
  
  Setup cannot continue. Power down or reboot your computer now.

You may also receive a "Stop 0x0000007B" error message during Windows XP Setup when the Setup program restarts during the installation process. When you receive a Stop error while the Setup program is running, you receive the second error message. To troubleshoot this issue, read the following four sections to determine if any one of the issues applies to you. If none of the issues apply to you, use the following general troubleshooting steps at the end of the article. Back to the top Boot-Sector Viruses You may receive a "Stop 0x0000007B" error message if your computer is infected with a boot-sector virus. If the problem is intermittent and you can start Windows, check your computer for viruses. If you find a virus, also check any floppy disks for viruses before you use them again.

For a list of antivirus software manufacturers, click the following article number to see the article in the Microsoft Knowledge Base: 49500 List of Antivirus Software Vendors Note You may have to use more than one brand of virus-detection software to detect and remove various viruses.

Important If your computer has been infected, it may be open to additional forms of attack. We recommend that you rebuild infected Internet-facing servers by following the guidelines that are published on the CERT Web site. Internet-facing servers are servers that function without a firewall or other protection. It is also a good idea to rebuild any other computers that are at risk because of their proximity to infected computers before you put them back in service.

If a virus has infected your Windows XP-based computer and a virus-detection program cannot remove the virus and repair the system, you must repartition and format your hard disk and reinstall Windows XP. For additional information about partitioning and formatting a hard disk with Windows XP, click the following article number to view the article in the Microsoft Knowledge Base: 313348 How to partition and format a hard disk in Windows XP For more information about how to help protect the boot sector from viruses in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base: 122221 How to protect boot sector from viruses in Windows Back to the top Device Driver IssuesYou may receive a "Stop 0x0000007B" error message in the following scenarios:

• A device driver that the computer boot controller needs is not configured to start during the startup process.
• A device driver that the computer boot controller needs is corrupted.
• Information in the Windows XP registry (information related to how the device drivers load during startup) is corrupted.

Windows XP requires a miniport driver to communicate with the hard disk controller that is used to start your computer. If Windows XP does not supply a device driver for your controller or if Windows XP is using a corrupted or incompatible driver, you must replace the driver with a valid copy that is compatible with your controller and Windows XP.

During the first phase of the Windows XP installation, Setup displays the following message at the bottom of the screen: Press F6 if you have to install a third-party SCSI or RAID driver. Press F6 and then follow the instructions to install a mass-storage device driver from your Original Equipment Manufacturer (OEM). For additional information about using F6 to load an OEM device driver to support, click the following article number to view the article in the Microsoft Knowledge Base: General Troubleshooting If none of the issues that have been described in this article apply to you, use the following general troubleshooting steps:

1. If you receive one of these error messages while you are installing Windows XP, update the computer BIOS or obtain Windows XP drivers for your hard disk controller (from the manufacturer of your computer, system board, or hard disk controller), or do both. For information about how to update your computer's BIOS or obtain Windows XP drivers, contact your computer manufacturer. For additional information about the availability of drivers, see the Device Driver Issues section in this article.
   
   Note: If Windows NT 4.0 or Windows 2000 was installed previously on a mirrored boot partition, see the Other Issues section in this article.
2. Use the Last Known Good Configuration feature. This may resolve the problem if you recently installed an incompatible device driver for your boot controller. For additional information about using the Last Known Good Configuration feature, click the following article number to view the article in the Microsoft Knowledge Base: 307852 How To start your computer by using the Last Known Good Configuration feature in Windows XP
3. Use the Repair option with Windows XP Setup. For additional information about repairing Windows XP by using the Setup program, click the following article number to view the article in the Microsoft Knowledge Base: 315341 How to perform an in-place upgrade (reinstallation) of Windows XP
4. Restore a registry backup. For additional information about restoring a registry backup, click the following article number to view the article in the Microsoft Knowledge Base: 307545 How to recover from a corrupted registry that prevents Windows XP from starting

When you try to connect a drive that was previously connected to a Distributed File System (DFS) resource, you may receive the following error message: System error 85 has occurred. The local device name is already in use.This error message persists for the particular drive letter in that particular Terminal Services session. The same drive letter for other Terminal Services sessions may work as expected. A different drive letter that is not typically used also works as expected. The only way to correct the issue is to restart the Terminal Services-based system.
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 260910 How to obtain the latest Windows 2000 service pack (if you are using windows 2000)

Use a floppy disk or USB memory key to create a password reset disk using the following Microsoft instructions: How to Create a Password Reset Disk



The easiest way to recover from a lost password situation is to use a password reset disk. If you have a reset disk, follow these steps:

1. At the Windows logon screen, click Reset password.



2. Insert the recovery diskette or USB key.



3. Follow the instructions on-screen to create a new password.



4. Log onto the account using your new password.

Note: Password reset disks are valid for the account they were created on. If you use a password reset disk to recover your password, you do not need to create a new reset disk afterwards.
Issue 3: Resolve Error: The User Profile Service Failed the Logon

The following Microsoft Knowledge Base Article provides instructions on how to resolve The User Profile Service Failed the Logon. User profile cannot be loaded error.
"Error message when you log on to a Windows Vista-based computer by using a temporary profile: "The User Profile Service failed the logon. User profile cannot be loaded" Article ID: 947215.
Issue 4: If You do not have a Password Reset Disk

If you have lost or forgotten your password, and a password reset disk is not available, reinstalling the operating system is the only recourse. For information on reinstalling Windows, refer to Dell Knowledge Base Article, How To Restore or Reinstall Microsoft® Windows® on a Dell™ Computer

CAUSE:
The Windows 32-bit protected-mode cache driver (Vcache) determines the maximum cache size based on the amount of RAM that is present when Windows starts. Vcache then reserves enough memory addresses to permit it to access a cache of the maximum size so that it can increase the cache to that size if needed. These addresses are allocated in a range of virtual addresses from 0xC0000000 through 0xFFFFFFFF (3 to 4 gigabytes) known as the system arena.

On computers with large amounts of RAM, the maximum cache size can be large enough that Vcache consumes all of the addresses in the system arena, leaving no virtual memory addresses available for other functions such as opening an MS-DOS prompt (creating a new virtual machine).

WHAT CAN U DO?
To work around this problem, use one of the following methods:

• Use the MaxFileCache setting in the System.ini file to reduce the maximum amount of memory that Vcache uses to 512 megabytes (524,288 KB) or less. For additional information about how to use the MaxFileCache setting, click the article number below to view the article in the Microsoft Knowledge Base: 108079 (http://support.microsoft.com/kb/108079/EN-US/ ) 32-Bit File Access Maximum Cache Size
• Use the System Configuration utility to limit the amount of memory that Windows uses to 512 megabytes (MB) or less.For additional information about how to use the System Configuration utility, click the article number below to view the article in the Microsoft Knowledge Base: 181966 (http://support.microsoft.com/kb/181966/EN-US/ ) System Configuration Utility Advanced Troubleshooting Settings
• Reduce the amount of memory that is installed in your computer to 512 MB or less.

This indicates you don't have enough onboard RAM memory in your computer. There are some informative articles at this site:http://www.pc-music.com/category/content-tags/articles

his Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.
User Action:
If the I/O status is C0000185 and the paging file is on a SCSI disk, the disk cabling and SCSI termination should be checked for problems. Check your computer for viruses, using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. An I/O status code of 0xC000009C or 0xC000016A normally indicates the data cannot be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map out the bad sector. If Autochk does not scan the hard disk for errors, manually launch the disk scanner. Run Chkdsk /f /r on the system partition. Restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r . Caution: If your system partition is formatted with the FAT file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOSbased hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks. Another common cause of this Stop message is failing RAM. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. Check that all network adapters in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure network adapter contacts are clean. Check the System Log in Event Viewer for additional error messages that might help pinpoint the device causing the error. Disabling memory caching of the BIOS might also resolve it. Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.

Hi,

there are a couple things you can try,

First update your windows, xp is limited but can handle more than three GB of RAM. You will need to update to service pack 3 which is available through windows update.

If that doesn't work, go to dell.com and click on support, then enter your service tag or express service code(on a white sticker on the bottom of the laptop) then go to downloads for your unit and look for firmware updates that relate to memory and any updates relating to your chipset.

Follow the instructions on the firmware carefully as messing this one up can damage the laptop.

Once you have finished try once again. If it still doesn't work you can try increasing your virtual memory to allow for some overflow, but if the first two suggestions don't work it's unlikely more virtual memory will help, still, worth a try.

Hope this helps FixYa

Chris

SYMPTOMS loadTOCNode(1, 'symptoms'); You receive the following error message in multiple languages: System Error. Contact Xbox Customer Support. CAUSE loadTOCNode(1, 'cause'); Typically, this error message is caused by a hardware failure. THINGS TO TRY loadTOCNode(1, 'whattotry'); Note If you receive an error message and see one flashing red light on the front of the console, see the following article in the Microsoft Knowledge Base: 907536 (http://support.microsoft.com/kb/907536/) Xbox 360: One red light flashes on the Ring of Light and you receive an error message 1. Turn off the console, disconnect and then reconnect all cables. Turn the console on again. 2. If an Xbox Hard Disk Drive is attached to the console, turn off the console, and then remove the Hard Disk.

For more information about how to remove the Hard Drive, click the following article number to view the article in the Microsoft Knowledge Base: 906204 (http://support.microsoft.com/kb/906204/) Xbox 360: How to attach or remove the Xbox 360 Hard Drive Turn on the console, and then test for the error message. If you do not receive the error message, turn off the console, and then reattach the Hard Disk. Alternate testing with the hard drive connected and removed to see whether the error message occurs only when the hard drive is attached. If the on-screen alpha-numeric error is E67 in the error message, see the following article in the Microsoft Knowledge Base: 917874 (http://support.microsoft.com/kb/917874/) Xbox 360: One red light flashes on the Ring of Light, and you receive error E67, E68, or E69 3. If an Xbox Memory Unit (MU) is plugged in to the console, turn off the console, and then remove the Memory Unit. Turn on the console again and test for the error message. If the error message does not reoccur, turn off the console, and then reinsert the MU. Alternate testing with the MU inserted and removed to see if the error message occurs only when the MU is inserted. 4. If you continue to experience this behavior, contact Xbox Customer Service.

This issue may occur if any of the following conditions exist: • A damaged file exists in the folder in which Windows is installed, and this file is not overwritten during Setup. For example, if you receive the error message that references the User32.dll file, the User32.dll file may be damaged. • One or more of the random access memory (RAM) modules that are installed in your computer is faulty, or the RAM configuration is incompatible

RESOLUTION loadTOCNode(1, 'resolution'); To resolve this behavior, use one of the following methods. Method 1: Extract a New Copy of the User32.dll File from the Windows XP CD loadTOCNode(2, 'resolution'); Extract a new copy of the User32.dll file from the Windows XP CD to the drive:\Windows\System32 folder on your hard disk, where drive is the drive on which Windows is installed: 1. Insert a Microsoft Windows Millennium Edition (Me) or Microsoft Windows 98 Startup disk into your computer, and then restart the computer.

NOTE: For additional information about what to do if you do not have a Windows Millennium Edition or Windows 98 Startup disk, click the following article numbers to view the articles in the Microsoft Knowledge Base: 186300 (http://support.microsoft.com/kb/186300/EN-US/) How to Create a Windows 98 Startup Disk from MS-DOS 267287 (http://support.microsoft.com/kb/267287/EN-US/) How to Create a Startup Disk in Windows Me 2. When the Windows Startup menu appears, use the ARROW keys to select Start Computer with CD-ROM Support, and then press ENTER. 3. Make a note of the drive letter of your CD-ROM drive. 4. Rename the User32.dll file to User32.old. To do so, type the following lines at the command prompt, pressing ENTER after each line, where Drive is the drive on which Windows is installed: Drive:
cd windows\system32
ren user32.dll user32.old 5. Insert the Windows XP CD into your CD-ROM or DVD-ROM drive. 6. Extract a new copy of the User32.dll file from the Windows XP CD to the Windows\System32 folder on your hard disk. To do so, type the following lines at a command prompt, pressing ENTER after each line, where CDROMDrive is the drive letter of the CD-ROM or DVD-ROM drive that contains the Windows XP CD-ROM, and Drive is the drive on which Windows is installed: a:
extract CDROMDrive:\i386\user32.dl_ Drive:\windows\system32\user32.dllFor example, if your CD-ROM is drive E and Windows is installed on drive C, type extract e:\i386\user32.dl_ c:\windows\system32\user32.dll, and then press ENTER. 7. Remove the Windows 98 or Windows Millennium Edition startup disk from your computer, and then restart the computer.
Method 2: Remove or Replace the Faulty RAM loadTOCNode(2, 'resolution'); Remove the memory modules that are installed in your computer, leaving enough RAM for the computer to start and run Windows. Restart the computer, and then run Setup again.

For additional information about Windows XP RAM requirements, click the following article number to view the article in the Microsoft Knowledge Base: 314865 (http://support.microsoft.com/kb/314865/EN-US/) System Requirements for Windows XP Operating Systems If the issue is not resolved, remove a different memory module. To identify the specific memory module that is not working correctly, you may have to restart your computer more than one time.

For information about how to add and remove RAM to the computer, contact the manufacturer of the computer, or view the documentation that is included with your computer.
Method 3: Install Windows to a Different Folder loadTOCNode(2, 'resolution'); NOTE: Before you install Windows to a different folder, first try the troubleshooting procedures in the following article in the Microsoft Knowledge Base: 310064 (http://support.microsoft.com/kb/310064/EN-US/) HOW TO: Troubleshoot Windows XP Setup Problems During Installation When You Upgrade from Windows 98 or Windows Me If the issue is not resolved by using the troubleshooting procedures in 310064, install Windows to a different folder. For more information about how to do this, see the "Installing to a New Folder" section of the following article in the Microsoft Knowledge Base: 316941 (http://support.microsoft.com/kb/316941/EN-US/) HOW TO: Install Windows XP MORE INFORMATION loadTOCNode(1, 'moreinformation'); For additional information about how to troubleshoot "STOP: C0000221 error messages", click the article number below to view the article in the Microsoft Knowledge Base: 314474 (http://support.microsoft.com/kb/314474/EN-US/) "STOP: C0000221 Unknown Hard Error" or "STOP: C0000221 STATUS_IMAGE_ CHECKSUM_MISMATCH" Error Message Occurs For additional information about upgrading to Windows XP, click the article number below to view the article in the Microsoft Knowledge Base: 316639 (http://support.microsoft.com/kb/316639/EN-US/) HOW TO: Prepare to Upgrade Windows 98 or Windows Millennium Edition to Windows XP For additional information about how to troubleshoot startup problems in Windows XP, click the article number below to view the article in the Microsoft Knowledge Base: 308041 (http://support.microsoft.com/kb/308041/EN-US/) Resources for Troubleshooting Startup Problems in Windows XP For additional information about Windows XP Setup, click the article numbers below to view the articles in the Microsoft Knowledge Base: 306824 (http://support.microsoft.com/kb/306824/EN-US/) Release Notes for Windows XP Setup Contained in the Home.txt File 286463 (http://support.microsoft.com/kb/286463/EN-US/) Release Notes for Windows XP Setup Contained in the Pro.txt File 286647 (http://support.microsoft.com/kb/286647/EN-US/) Windows XP Read1st.txt File Contents For information about how to contact your hardware manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base: 65416 (http://support.microsoft.com/kb/65416/EN-US/) Hardware and Software Third-Party Vendor Contact List, A-K

60781 (http://support.microsoft.com/kb/60781/EN-US/) Hardware and Software Third-Party Vendor Contact List, L-P

60782 (http://support.microsoft.com/kb/60782/EN-US/) Hardware and Software Third-Party Vendor Contact List, Q-ZMicrosoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. Let me know if u got help and rate me as fixya please!!!