Categories
Knowledge Support Support exacqVision Client Categories Products

Bad Memory Causes exacqVision Client Crash and System Reboot

On certain exacqVision A Series and Z Series systems, faulty memory causes the system to restart and causes the Windows exacqVision Client to crash (if VGA Acceleration Mode enabled).

The following procedure can determine whether the affected memory is installed on a system:

<br>

WINDOWS

  1. Log in to Windows as an administrator.
  2. Select the Start menu and type power.
  3. Find Windows PowerShell (x86). Right-click it and select Run As Administrator.
  4. In the Windows PowerShell command window, type gwmi -class win32_PhysicalMemory.
  5. Scan the results for PartNumber. There should be an entry for each memory module.
  6. Look at the letter following the period. “C” indicates bad memory. Any other letter is acceptable.


<br>

LINUX

  1. Log in to Linux as an administrator.
  2. On the Start menu, select Accessories and then Terminal.
  3. Type sudo lshw -class memory.
  4. For each bank, look at the Product tag.
  5. Look at the letter following the period. “C” indicates bad memory. Any other letter is acceptable (such as “M” in the following image).


IDENTIFYING PHYSICAL MODULES

It is possible that some systems could contain both “C” memory modules and modules with other letters. If you need to replace the memory in such a system, use the following photos to identify the “C” modules.

Front and Back of “C” Memory (Bad)