Ja mata, TosaInu. You will forever be remembered.
Proud![]()
![]()
![]()
![]()
Been to:![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Swords Made of Letters - 1938. The war is looming in France - and Alexandre Reythier does not have much time left to protect his country. A novel set before the war.
A Painted Shield of Honour - 1313. Templar Knights in France are in grave danger. Can they be saved?
You do know that the 4GB limit goes for the total of all memory mapped devices (most important of which would be the graphics card) ?
@Husar: the point is/was not that memtest86+ is always right. In particular how it classifies hardware may very well be completely off. However that doesn't matter too much for the problem at hand: first of all no program does direct memory access, there is always a hardware controller of sorts between <code> and <RAM>: that is the device responsible for ensuring that the RAM/CPU combination works properly provided both individual components work properly. Second of all the real problem is that OP wants to know whether or not the problem with RAM detection lies with (a) dud sticks; (b) missing sticks; or (c) dud software.
Last edited by Tellos Athenaios; 08-09-2009 at 22:59.
- Tellos Athenaios
CUF tool - XIDX - PACK tool - SD tool - EVT tool - EB Install Guide - How to track down loading CTD's - EB 1.1 Maps thread
“ὁ δ᾽ ἠλίθιος ὣσπερ πρόβατον βῆ βῆ λέγων βαδίζει” – Kratinos in Dionysalexandros.
Bookmarks