| 1 |
On 08/21/2011 06:33 PM, Mark Knecht wrote: |
| 2 |
> On Sun, Aug 21, 2011 at 8:12 AM, Nikos Chantziaras<realnc@×××××.de> wrote: |
| 3 |
>> On 08/21/2011 02:19 PM, Francesco Talamona wrote: |
| 4 |
>>> |
| 5 |
>>> I wish yours it's not a RAM |
| 6 |
>>> issue, it could be tricky to spot, because memtest is not putting any |
| 7 |
>>> load to the machine, so it's very useful when it reports error, but when |
| 8 |
>>> it doesn't you can't be sure if RAM modules are in good health. |
| 9 |
>> |
| 10 |
>> CPU load doesn't affect RAM errors. CPU load affects CPU errors. If you |
| 11 |
>> only get RAM errors during heavy load, the RAM is just fine, but your CPU |
| 12 |
>> has a fault. |
| 13 |
> |
| 14 |
> Unless the CPU loading causes excessive heat and the RAM has problems |
| 15 |
> only when it gets hot. |
| 16 |
|
| 17 |
The RAM gets hot when there's RAM load (meaning being used heavily), not |
| 18 |
when there's CPU load :*) |
Archives