Solved Hardware is using up most of my RAM HP Probook 4530s

[gregrocker]

In addition HP has the worst load of factory bloatware in the industry, which throttles Win7 from its native state. That's why most tech enthusiasts Clean Reinstall - Factory OEM Windows 7.

At the least I'd Clean Reinstall - Factory OEM Windows 7 starting by establishing a Clean boot to get the freeloaders off of Win7's back.

 

[AddRAM]

But I don`t even think a clean install is gonna change anything as far as hardware reserved. Windows takes what it takes. We need to find someone who knows if it can somehow be altered, and how to do it.

Now take a look at my XFX board , 1 MB, I repeat 1 MB is hardware reserved, yeeehaaaa !!! Like I`ve always been say`n it`s all about the motherboard. 19% used physical memory, now that`s what you wanna see

 

[gregrocker]

In that case I'd shrink C and do a test install to see if Hardware Reserved replicates itself. I doubt it. The factory preinstall corrupts most everything including likely this.

If it corrects the problem build it out with all Important and Optional Updates, Chrome, and other programs to see if it resolves the issue, then move the files over and we'll help you remove the old corrupt install and recover its space.

 

[AddRAM]

It will replicate itself, because it`s HARDWARE reserved and has nothing to do with software. I`ve done it and it`s always the same. It`s all about the MOTHERBOARD and the graphics card. I`m gonna do an experiment right now, well maybe not right now. But I`ll take out my BFG 9600 GT with 512 on the board and pop in my XFX 9600 GSO with 768 on the board and see if there is any change to the amount of hardware reserved.

 

[gregrocker]

But its the OS that's reading it.

What is apportioned in BIOS?

 

[AddRAM]

I`m taking my toys and going home, I`ll swap the cards and see if there`s a change. I`ll print out all pre and after snips.

What does bios have to do with os, the bios just makes sure everything is cool and then hands it over to windows

 

[m0stlyharmless]

It turns out that I had to start up the system from a different partition. Apparently I have to start the computer by booting into the partition titled SYSTEM versus the one titled Windows. This probably has something to do with having to load additional drivers into the system before Windows boots. Regardless, that was apparently the issue and I have now solved it.