Processes that end with *32 are 32-bit applications running under WOW on a 64-bit OS. WOW64 allows 32-bit Windows-based applications to run on 64-bit Windows.
Microsoft created the folder named SysWOW64 for storing 32-bit .dll files. WOW64 equates to "Windows 32-bit on Windows 64-bit". This folder contains all the 32-bit .dll files required for compatibility which run on top of the 64-bit version of Windows. WOW64 is the x86 emulator that allows 32-bit Windows-based applications to run on 64-bit Windows but x86 applications are re-directed to the x86 \syswow64 when seeking the x64 \system32. The C:\Windows\System32 folder still exists in the 64-bit version of Windows but it is used as a repository for 64-bit .dll files.
Chrome.exe (Chrome.exe *32) is a legitimate process related to the Google Chrome web browser. Multiple copies of chrome.exe, referred to as process-per-tab, listed in Task Manager is intentional by design as a crash control. Chrome creates three types of processes (browser, renderers, and plug-ins). Each Chrome tab is treated as it's own individual process for the life of tab meaning it is treated as a separate process so that multiple tabs can run with less problems. This feature increases responsiveness, and prevents the browser from locking up if a particular web app or plug-in stops responding. In the event of a browser crash or hang in one tab, it prevents the entire browser from closing down. Chrome has its own built-in Task Manager which is accessed by right-clicking on the browser's title bar. You can see what which process does by going to Menu > Tools > Task Manager. The Chrome Task Manager lets you track resource usage for each individual tab and lets you kill any tabs that have stopped responding without having to restart the entire browser.
For more specific information, please refer to:
There are numerous comments about this at the Chrome Help forum. See Multiple chrome.exe in Task Manager.
Tools & Tips to Optimize & Troubleshoot Memory/CPU Usage in Firefox and Chrome: