As far as I know, System Profiler won't display information for any .kext's that are being loaded and are located somewhere else besides the /System/Library/Extensions/ folder.
To get comprehensive information about the kernel extensions which are currently loaded and in use on your Mac, you can use the kextstat command line tool.
Open up the Terminal application (in the /Applications/Utilities/ folder), type the following at the prompt, and then hit return:
kextstat
You will get a large list of all the loaded kernel extensions. You'll primarily want to focus on the bundle identifiers of the loaded .kexts. (That's the backwards domain name string such as "com.apple...."). You should be able to eliminate the ones that include "com.apple", as those will be Apple's and should have a K64 version. Once you've gotten rid of those, you'll then need to go over the remaining ones to make sure they are built as universal K32+K64 versions, or whether you may need to make sure you have the latest updates.
For example, after eliminating all the Apple kexts on the output I get, I have the following kexts listed. Since I switched to K64 a year or so ago, all of these are in order so everything is fine.
MacPro:~ mdouma46$ kextstat
Index Refs Address Size Wired Name (Version) <Linked Against>
73 0 0xffffff7f8111a000 0x8000 0x8000 com.AmbrosiaSW.AudioSupport (3.2) <72 5 4 3 1>
81 0 0xffffff7f811bf000 0x9000 0x9000 jp.plentycom.driver.SteerMouse (4.0.2) <55 29 24 5 4 3>
105 0 0xffffff7f81499000 0x5000 0x5000 com.Cycling74.driver.Soundflower (1.5.2) <72 5 4 3>
115 0 0xffffff7f814bf000 0xd1000 0xd1000 com.vmware.kext.vmx86 (3.1.2) <7 5 4 3 1>
116 0 0xffffff7f81590000 0xc000 0xc000 com.vmware.kext.vmci (3.1.2) <5 4 3 1>
117 0 0xffffff7f8159c000 0x7000 0x7000 com.vmware.kext.vmioplug (3.1.2) <29 24 5 4 3 1>
118 0 0xffffff7f815a3000 0xa000 0xa000 com.vmware.kext.vmnet (3.1.2) <5 4 3 1>
119 0 0xffffff7f815ad000 0x2000 0x2000 com.nvidia.CUDA (1.1.0) <4 1>
Best Answer
KEXT files can reside in 3 locations:
/Library/Application Support/Library/ExtensionsGenerally where the app developer chooses to place the kext files depends on the app itself and what makes sense for it (eg. how it stores local data, how frequently a kext might need to be updated, etc).
Kext files related to system functions, like network adapter or mouse drivers, will almost always be inside
/Library/Extensionsas those are loaded on startup. While app specific kext files like what VirtualBox has, can be located elsewhere as they only need to be loaded when the app is in use.Here's a source: https://developer.apple.com/library/archive/technotes/tn2459/_index.html