Problem

Systems booted to ggRock frequently hang while updating games, running games, or performing other network-intensive or system resource-intensive operations.

Errors may be displayed in the server log similar to the following:

tcp_sendpage() failure: 2752

tcp_sendpage() failure: -512

error 8 user aborted the transfer received from "client pc IP address"

Solution 1

  1. Increase system RAM installed in one of the systems affected to determine if the issue is memory-related (e.g. we need to reduce the amount of disk swapping that is occurring).

  2. Boot the test system and perform actions that would normally result in a system hang or freeze otherwise.

Solution 2

  1. Research game settings that might reduce the amount of system resources consumed by a given game, which will reduce the network load by requiring less paging.

  2. Modify in-game settings per the above research.

  3. Boot the test system and perform actions that would normally result in a system hang or freeze otherwise.

Solution 3

In the case of this particular situation, it is advised to install the latest version of the network driver for your network interface card.

Follow the steps outlined in this support article:

Adding a New PC Type to a ggRock Image

General Outline of Procedure

1. Using the ggRock IC Tool, write your image from a PXE booted system to a standard internal hard drive/ssd.

2. Install the drive into one of your systems.

3. Boot the system from the internal drive (not PXE).

4. Download and install the latest Realtek driver.

5. Generate the VHD image using the ggRock IC Tool.

6. Copy the new system image VHD file to an external USB drive.

7. Plug the USB drive into your ggRock server.

8. Import the new system image to your ggRock server.

9. Set at least one system to boot from the new system image.

10. Boot that system up to determine if the issue is resolved.

Additional Information

The ggRock system mounts images (system and game images) over iSCSI which means any interruption in network connectivity will result in an immediate blue screen similar to unplugging a SATA cable from a standard drive a system is booted from.

This particular revision of driver is unstable under high network loads, and therefore results in "Critical Process Died" blue screens.

Did this answer your question?