| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Richard Lucking wrote: |
| 5 |
> Anything I may have overlooked? I've emailed Gigabyte on the off chance |
| 6 |
> that throws up something, as I know this isn't a gentoo problem as I |
| 7 |
> first thought. |
| 8 |
> |
| 9 |
|
| 10 |
When you tested modules on their own, did you try them in the same slots |
| 11 |
you use with everything installed? Or, did you put one module in slot |
| 12 |
0, and then after that worked put the other module in slot 0? It could |
| 13 |
be a physical problem with one of your slots. Granted, your motherboard |
| 14 |
might not let you run one with memory only in slot 1, but if it does see |
| 15 |
if that makes a difference. Seems odd, but computers are hardware, and |
| 16 |
if there is some kind of defect in the traces you might get some noise |
| 17 |
on only one of the slots. |
| 18 |
|
| 19 |
Just grasping at straws, but I figured ideas won't hurt you at this point. |
| 20 |
|
| 21 |
Did you try running memtest86 for a long period of time, or some tool |
| 22 |
designed to burn-in RAM? If the modules are fine on their own it could |
| 23 |
be a bad motherboard. If it is warranted you might consider returning |
| 24 |
it. Might not hurt to try swapping RAM with a friend if you can manage |
| 25 |
first. |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v1.4.2.2 (GNU/Linux) |
| 28 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 29 |
|
| 30 |
iD8DBQFEkKB0G4/rWKZmVWkRAkT7AJ9GzSa8wrlnnbcslyouOEUQLVA4WwCfYLaC |
| 31 |
gAhWHiw1gBxe4cSOz1VjbT0= |
| 32 |
=MyCL |
| 33 |
-----END PGP SIGNATURE----- |
Archives