AHCI enables hot-swap, so that's why the option to disconnect hard drive is present.
sfc /scannow can and does return 'no errors' result. Some corrupt files are no problem, but in your case it looks like you need a Windows re-install to ensure no errors are present.
The other forum did you no favours. There is nothing wrong with Windows 7/8 x64 - it is superior in almost every way in 2014. There are no major problems related to it, regardless of what you think. The problems from XP/Vista and moving to x64 are numerous, but that's history now and not actually related to the x64 architecture as a whole.
Also, you did not solve you problem, you just reverted it.
If we look back, you have been confused from the start. 32 bit Windows is fine for a machine with 4GB RAM, but it'll only use 3.25GB RAM max. We suggested to use x64 if that is an option, so that:
a) You can use full 4GB RAM.
b) Future-proofing. It's not fun to reinstall Windows, if you boost your RAM past 4GB.
__________________________________
Anyway, here is some more technical advice:
Go to:
Device manager > Disk Drives > your HDD > right-click > Properties > Policies.
Is write caching enabled?
Here's links regarding WOW emulation:
http://ask.metafilter.com/53250/How...ing-CPU-heavy-programs-in-32bit-WOW-emulation
Subjective opinion.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa384219(v=vs.85).aspx
Official MS docu saying emulation is done on-chip.
http://www.viva64.com/en/l/0002/
WoW64 on Intel 64 (AMD64 / x64) does not require instruction emulation. In this case the WoW64 subsystem emulates only the 32-bit environment through an additional layer between a 32-bit application and the 64-bit Windows API. In some places this layer is thin, in others a bit thicker. For an average program, you may expect 2% performance penalty because of this layer. For some programs, it can be larger. Two per cent is not very much but keep in mind that 32-bit applications work a bit slower under the 64-bit Windows than in the 32-bit environment.
2% hit?