Event ID 57665: Insufficient system resources exist to complete the requested service

Final error: 0xe00084c8 – The backup storage device has failed - Resolution with screenshots

Event ID 33808: An error occurred while processing a B2D command. Drive: ReadMTFData() ReadFile failed. Error=1450 - Resolution with screenshots

Event ID 57665: Insufficient system resources exist to complete the requested service - Resolution with screenshots

Event ID 34113: The job failed with the following error: The backup storage device has failed - Resolution with screenshots

Situation: The client is running Backup Exec to back up their data to a 4 TB external USB drive. The backup is failed with these errors: Final error: 0xe00084c8 – The backup storage device has failed. Final error category: Backup Device Errors

In the application event log there are these events:

Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 33808
Description: An error occurred while processing a B2D command. Drive: ReadMTFData() ReadFile failed. Error=1450

Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 57665
Description: Storage device “Friday N:” reported an error on a request to read data from media.

Error reported:
Insufficient system resources exist to complete the requested service.

Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 34113
Description: Backup Exec Alert: Job Failed
(Job: “Friday – Backup to N:”) Friday – Backup to N: — The job failed with the following error: The backup storage device has failed.

Possible cause:

Possible resolutions:

A. Set the USB drive to “Optimize for performance”. Go to Device Manager. Navigate to Disk drives>USB drive name. Right click it and select Properties. Click Policies tab. Check Optimize for performance.

B. Registry setting 1

1. Click Start, click Run, type regedit in the Open box, and then click OK.

2. Locate and then click the following registry subkey:

3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

4. On the Edit menu, point to New, and then click DWORD Value.

5. Type PoolUsageMaximum as the entry name, and then press ENTER.

6. Right-click PoolUsageMaximum, and then click Modify.

7. Click Decimal.

8. In the Value data box, type 60, and then click OK.

10. Important

11. Use 60 as your initial value. If your backup does not succeed, use 40 as your value. If that does not work, you must change the behavior of your backup program to reduce the demand of paged pool. If the value works, you may want to increase the value by approximately 25 percent until the backup does not work. If the backup is unsuccessful, use the second registry setting that is described in this article.

12. Make sure that the value for this registry setting is not more than 60.

13. If you are using the /3GB switch, use 40 as your initial setting. Note that this value is a percentage value.

14. Quit Registry Editor.

15. Restart your computer.

C. Registry setting 2

1. Click Start, click Run, type regedit in the Open box, and then click OK

2. Locate and then click the following registry subkey:

3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

4. On the Edit menu, point to New, and then click DWORD Value.

5. Type PagedPoolSize as the entry name, and then press ENTER.

6. Right-click PagedPoolSize, and then click Modify.

7. Click Hexadecimal.

8. In the Value data box, type a value of FFFFFFFF, and then click OK.

10. Important

11. Setting PagedPoolSize to 0xFFFFFFFF (-1) allocates the maximum paged pool instead of other resources to the computer. This is typically required on a domain controller or a terminal server. By default, most Windows 2000 systems seem to be limited to a paged pool maximum size of 160 MB. You can verify this by downloading the kernel debuggers from the public Web site and opening a kernel dump in the debugger that you want to use. The command to use is !vm. This shows a paged pool maximum of 163840 KB, for example. Adding this value reduces the Page Table Entries (PTEs) that are available on a system and extends the paged pool maximum to 343 MB in Windows 2000. The paged pool maximum size can be extended to a larger value in Windows Server 2003.

12.

13. Note The default and maximum paged pool values for Windows Server 2003 are much larger than in Windows 2000. Typically, the Windows Server 2003 values are at least 50 percent higher than the values found in Windows 2000. These larger values makes it more unlikely that you will experience the issue where paged pool values contribute to the problem that is described in this article. However, it is still possible that this issue may occur.

14. This value restricts the system PTEs that are available. PTEs are another unrelated system resource that your system uses. This setting may cause your operating system to stop unexpectedly and to display a stop 0x3F error on a blue screen when it starts. You can recover from this by using the Last Known Good restart option on the system restart menu or recovery console. Use Performance Monitor to view the Free System Page Table Entries counter. You can add the PagePoolSize setting if the observed free values are over 40,000.

15. If you are running /3GB and /PAE together, do not set this setting without extensive testing and before you establish exactly how many system PTES you must have in your environment. You will probably see values in the range of 10,000-20,000 free. Use the articles to configure paged pool memory but never drop below 10,000 free system PTEs. Do not set this to any other value if you are using the /3GB switch. The only supported values are 0, 0A000000, and FFFFFFFF.

16. Quit Registry Editor.

17. Restart your computer.

D. We have the similar case. We fix the problem by replacing 4 TB USB 3 Drive with 2 TB USB 2 Drive.

Contact a consultant