Hi all,
I'm using an Acer laptop which I bought about 3 months ago (the specs are in my sig). Recently I've noticed it's running slower and behaving slightly strangely. I generally checked my Windows environment (disk cleanup, registry cleanup, anti-virus scan, Windows updates, control panel settings, etc.) and noticed in system properties that the amount of usable RAM had decreased from the usual amount.
Basically my installed RAM is 4 gigs and my usable RAM was 3.8 gigs until I did a flash update of the BIOS (about 2 months ago) which then left me with 3.68 gigs of usable RAM. Now though it still says I have 4 gigs installed but only 2.8 gigs usable. So I scheduled a memory test on a restart and just as the test started it quit the test and started up Windows as if nothing had happened, with no error message.
I then thought to try safe mode. Before I scheduled the memory test again I checked system properties and I had my 3.68 gigs back, so it's obviously something to do with my user account. I did the test anyway and it reported there were no errors. Just to make sure I even downloaded memtest86+ (using safe mode with networking) and that also reported no errors.
When using memtest86+ though I looked at the settings for it and noticed there were 2 memory sizing modes: BIOS (standard) and "probe". I tried probe to see if it'd test the full 4 gigs rather than just the usable 3.68 gigs, but instead it tested 2.8 gigs (incredibly slowly) which is exactly what I've been getting in Windows recently. Somehow the memory sizing mode must've changed from standard to probe on a normal startup of Windows.
I'd also noticed lots of memory errors in the performance monitor of Windows since only having 2.8 gigs, so I hope it hasn't led to any data corruption on my HD.
This is a long-winded way of asking how I can change my memory sizing back to standard, why it'd changed and how to prevent it happening again. I did do a search but maybe I didn't use relevant keywords. Any help much appreciated.
Cheers,
Darren (currently in safe mode)
I'm using an Acer laptop which I bought about 3 months ago (the specs are in my sig). Recently I've noticed it's running slower and behaving slightly strangely. I generally checked my Windows environment (disk cleanup, registry cleanup, anti-virus scan, Windows updates, control panel settings, etc.) and noticed in system properties that the amount of usable RAM had decreased from the usual amount.
Basically my installed RAM is 4 gigs and my usable RAM was 3.8 gigs until I did a flash update of the BIOS (about 2 months ago) which then left me with 3.68 gigs of usable RAM. Now though it still says I have 4 gigs installed but only 2.8 gigs usable. So I scheduled a memory test on a restart and just as the test started it quit the test and started up Windows as if nothing had happened, with no error message.
I then thought to try safe mode. Before I scheduled the memory test again I checked system properties and I had my 3.68 gigs back, so it's obviously something to do with my user account. I did the test anyway and it reported there were no errors. Just to make sure I even downloaded memtest86+ (using safe mode with networking) and that also reported no errors.
When using memtest86+ though I looked at the settings for it and noticed there were 2 memory sizing modes: BIOS (standard) and "probe". I tried probe to see if it'd test the full 4 gigs rather than just the usable 3.68 gigs, but instead it tested 2.8 gigs (incredibly slowly) which is exactly what I've been getting in Windows recently. Somehow the memory sizing mode must've changed from standard to probe on a normal startup of Windows.
I'd also noticed lots of memory errors in the performance monitor of Windows since only having 2.8 gigs, so I hope it hasn't led to any data corruption on my HD.
This is a long-winded way of asking how I can change my memory sizing back to standard, why it'd changed and how to prevent it happening again. I did do a search but maybe I didn't use relevant keywords. Any help much appreciated.
Cheers,
Darren (currently in safe mode)