Has anyone got Windows 2000 Professionalwith 2GB RAM??

[letdown427]

Erm, just ran CCleaner, and noticed it's now saying 2.0GB of RAM. Whereas before, it wasn't. Can't say I've done anything, although I tried changing a setting in the BIOS yesterday, which caused the PC to not boot at all, so the motherboard automatically reset itself to default settings. That appears to have solved the problem. I have to be up for work in 7 hours, so I can't test what setting it is that screwed Windows up, but I'll post the answers tomorrow sometime. Thanks to everyone for trying, this site has to be the best computing resource there is.

Many thanks,

James

 

[mrSHEiK124]

Originally posted by: mike3uz
Does your system have onboard graphics.

That use 1 GB of RAM for framebuffer? letdown427 better be packin two 7800GTXs on that motherboard

Glad to hear its working fine now

 

[Steve]

Amazing! I'd also suggest popping in your (slipstreamed) CD and doing Start->Run: sfc /scannow in case any system files are corrupted.

 

[Smilin]

I'm going to lean towards nothing being up with Windows. It simply uses bios calls to get that information and can only work with what's reported to it. It's also a value that's not really preserved anywhere on the system. It's new each boot.

 

[M16Grenadier]

I have the same amount of RAM, same OS, and same motherboard with no problems. All 2 GB is recognized, but I do not notice a difference in performance (probably due to reduction of timings 2.5-3-3-8 1T to 2.5-4-4-8 2T).

 

[icash55]

I have the same problem on Windows XP Pro SP2, only 1GB is recognized with Task Manager or System properties->General. Although msinfo32 says Total Physical Memory=2048MB, Available Physical Memory is currently ~605MB, the same as in Task Manager - free memory is not recognized.

MB: ASRock 939Dual (v1.50 bios)
CPU: X2 4400+
RAM: 2GB OCZ EL DDR PC3200 Platinum Series Dual Channel kit (OCZ4002048ELDCPE-K)

BUT Windows XP Pro x64 recognizes 2GB correctly, no problem! I think I even know what is causing this: strange memory addressing. When I run MemTest-86 it says: Testing 108k-1024M ... Testing 4096M-5120M
And since 32bit Windows can address only the first 4GB it doesn't sees the memory above 4096MB, right?

Others who have this problem please test this on MemTest-86, I'd like to know if I'm not alone.

Hopefully a bios update will be able to fix this.

 

[icash55]

Problem solved. Try this:

1) in the bios if 'AGP Aperture Size' is set to 256MB change it to 128MB or less
2) Save Changes and Exit
3) At this point Windows XP still recognized only 1GB. Restart PC (Windows)
4) 2GB is now recognized? [Smile]

Also I was getting errors/PC restarts in MemTest-86 test 8 if the memory was set to specification settings (CAS: 2, TRCD: 3, TRP: 2, TRAS: 5, MA: 1T), I changed CAS=2.5, TRAS=6 and set 'DRAM voltage' to 'High'.

Edit: Still getting lockups in MemTest-86. Seems to be fixed by changing MA to 2T.

Hope this helps.

 

[imported_Seer]

Same mobo, same processor, different memory, same problem! I even had the same, odd, memory addressing stuff in memtest.

I will try the suggestions here. Thank you so much!

BTW: what proc do you have, letdown427? If its an x2 4400+, I think we found the problem.

 

[VirtualLarry]

Originally posted by: icash55
BUT Windows XP Pro x64 recognizes 2GB correctly, no problem! I think I even know what is causing this: strange memory addressing. When I run MemTest-86 it says: Testing 108k-1024M ... Testing 4096M-5120M
And since 32bit Windows can address only the first 4GB it doesn't sees the memory above 4096MB, right?

Others who have this problem please test this on MemTest-86, I'd like to know if I'm not alone.

Hopefully a bios update will be able to fix this.

I think that you have found your problem. For some reason, that hardware (which I am not particularly familiar with), seems to be mapping the 2nd GB of RAM to physical hardware addresses above the 4GB mark - from 4GB to 5GB. Not sure why, but that could easily explain why BIOS reports 2GB found but Windows (32-bit) only sees 1GB. Very curious.