All right, I have bittersweet news...
Nvidia has released a new nforce driver for the 680i Series. It didnt help... (this isn't the news I'm talking about.)
Using the
/set removememory switch in
BCDedit, I removed 512 mb of my full 4GB ram, and since then the system is running Awesome, on 3.5GB ram. I also tried removing very little amounts of ram like 32 MB/64 MB/128 MB but removing 512 MB gave me the best results yet. I am yet to try the same with removing 256 MB.
Okay so even if it's not using the full 4GB, It's somewhere near it now, and it's stable
Here's what I did in detail:
1. Open command prompt as an
administrator. Otherwise Bcdedit won't work.
2. Use the following command:
bcdedit /set removememory [amount]
In place of amount, you can add the number of MB you want to remove from your physically installed RAM (
without the brackets). So, to remove 512 MB of RAM, the command should look like this:
bcdedit /set removememory 512
There is no need to specify a boot entry if you are using a single OS. If you are dual booting, you might need to specify which boot entry you want to apply the RAM limit to. Normally, without any specified boot entry, BCDedit applies the switch to the OS currently running.
The same friend of mine from MS who confirmed this bug suggested this after I told him that I was using the older /MAXMEM switch through MSConfig which gave me a stable system.
The system as been completely stable for 24 hours after removing 512 MB. I will try removing only 256 MB after another 24 hours. Needless to say, I will post the results here.
Of course, this is by no means a solution... Just a workaround. But who's complaining? :D