HP Xw460c Administrator's Guide for Microsoft Windows on HP ProLiant Blade Wor - Page 96

Troubleshooting Windows problems, RAM discrepancies, Unable to wake from hibernation or standby

Get HP Xw460c - ProLiant - Blade Workstation PDF manuals and user guides View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 96 highlights

13-4 Troubleshooting Windows problems Table 13-4 Troubleshooting Windows problems Problem Cause Suggestions RAM discrepancies Blade workstation configurations using 4 GB of RAM report only 3,456 MB during the system BIOS POST (when the system first boots). When using 2 GB of RAM, the blade reports 2048 MB. A portion of the total RAM will be utilized by various system devices, most notably the graphics card. Accounting for this fact, the BIOS does not report the total RAM installed during the POST. None Unable to wake from hibernation or standby The blade workstation will not wake after it has gone into Windows hibernation or standby mode. If the Windows option of hibernation is enabled (with the Power Options Properties in the Windows Control Panel) and the blade workstation is allowed to hibernate, you will not be able to wake the blade workstation from the remote client system because the RGS application has been terminated by the workstation and the client has no remote access to turn the workstation back on. Ensure that hibernation and standby are disabled. DLL initialization error While using the Windows Restore CD (that shipped with your blade workstation) to restore the blade workstation to the factory shipped Windows operating system, multiple "DLL Initialization Failed" errors can appear after the first boot into Windows. Print warning in event logs After the initial boot into Windows, Reboot the blade. Such DLL errors a reboot is necessary for certain should not occur on any subsequent operating system settings to take reboots into Windows. effect. Such DLL errors are a byproduct of this required system reboot. "Print" warnings can appear in the Networked client printers are blade workstation Windows System automatically installed to the blade Event Log when using the Windows workstation when a Windows Remote Desktop Connection Remote Desktop Connection application to access the between a Windows client PC to a workstation. blade workstation has been made. As the connection to the workstation is terminated, such "Print" warnings can appear as these printers are deleted. Accessing the blade using RGS does not generate such warnings. (These warnings do not affect the functionality of the blade or client.) Troubleshooting the blade workstation solution 96

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
Troubleshooting the blade workstation solution
96
13-4 Troubleshooting Windows problems
Table 13-4
Troubleshooting Windows problems
Problem
Cause
Suggestions
RAM discrepancies
Blade workstation configurations
using 4 GB of RAM report only
3,456 MB during the system BIOS
POST (when the system first boots).
When using 2 GB of RAM, the
blade reports 2048 MB.
A portion of the total RAM will be
utilized by various system devices,
most notably the graphics card.
Accounting for this fact, the BIOS
does not report the total RAM
installed during the POST.
None
Unable to wake from hibernation or standby
The blade workstation will not
wake after it has gone into
Windows hibernation or standby
mode.
If the Windows option of
hibernation is enabled (with the
Power Options Properties in the
Windows Control Panel) and the
blade workstation is allowed to
hibernate, you will not be able to
wake the blade workstation from
the remote client system because
the RGS application has been
terminated by the workstation and
the client has no remote access to
turn the workstation back on.
Ensure that hibernation and
standby are disabled.
DLL initialization error
While using the Windows Restore
CD (that shipped with your blade
workstation) to restore the blade
workstation to the factory shipped
Windows operating system,
multiple “DLL Initialization Failed”
errors can appear after the first
boot into Windows.
After the initial boot into Windows,
a reboot is necessary for certain
operating system settings to take
effect. Such DLL errors are a
byproduct of this required system
reboot.
Reboot the blade. Such DLL errors
should not occur on any subsequent
reboots into Windows.
Print warning in event logs
“Print” warnings can appear in the
blade workstation Windows System
Event Log when using the Windows
Remote Desktop Connection
application to access the
workstation.
Networked client printers are
automatically installed to the blade
workstation when a Windows
Remote Desktop Connection
between a Windows client PC to a
blade workstation has been made.
As the connection to the
workstation is terminated, such
“Print” warnings can appear as
these printers are deleted.
Accessing the blade using RGS
does not generate such warnings.
(These warnings do not affect the
functionality of the blade or client.)