| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 22/05/14 09:20, wraeth wrote: |
| 5 |
> Just a quick suggestion to help rule it out: try booting a LiveCD or other |
| 6 |
> "one-size-fits-most" medium and seeing if your full memory is registering |
| 7 |
> there. If it is, then it's not a hardware malfunction; if it doesn't, then |
| 8 |
> either you've got bad hardware or a configuration issue in your BIOS. |
| 9 |
|
| 10 |
Just had another thought, too: you could check what the BIOS reports either by |
| 11 |
entering the BIOS configuration and going to the system information area, or |
| 12 |
by inspecting your machines POST output (the diagnostic information that is |
| 13 |
displayed during boot, sometimes hidden by a splash screen with "Press |
| 14 |
[something] to show details". |
| 15 |
|
| 16 |
cheers |
| 17 |
wraeth |
| 18 |
-----BEGIN PGP SIGNATURE----- |
| 19 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 20 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 21 |
|
| 22 |
iF4EAREIAAYFAlN9ZGAACgkQXcRKerLZ91mfFgD/RljFu05+0ymLJrOs8BRUvTji |
| 23 |
bk1s4RhOGroibx8GaMkA/2xZjYptJrj7PM+7ebw+2FN0juGKFZQyQ5VrL81yYn0z |
| 24 |
=eRY0 |
| 25 |
-----END PGP SIGNATURE----- |
Archives