@EP_X0FF & Fyyre:
I wrote something identical to this months back for the same purpose which is the collection of malware drivers so I decided to leave you some constructive criticism. This DrvMon tool's "concept" is great but the actual tool itself needs to address some major issues... ;)
[1] DrvMon's disabling of drivers can easily be completely bypassed by setting any driver's AddressOfEntryPoint to 0 for example, and then placing a jump to the real OEP address directly below the MZ signature inside the driver file. DrvMon cannot prevent the driver load anymore (DrvMon can only log it) because DrvMon (like my own tool) relies on this optional header member to be a "valid" relative address
[2] "Monitor->Deny drivers loading" is very unstable by design since you're denying all drivers from loading and in essence important OS drivers such as vga.dll (in XP) for example cannot load resulting in a one way ticket to a frozen OS environment if you're lucky, otherwise it's an instant BSOD! Perhaps you should allow "sfc protected" system files or something like this to automatically be permitted to load, this is basically what I did to solve the problem in my tools
[3] Abnormally terminating the DrvMon executable and rerunning it, the driver doesn't correctly handle this scenario and will BSOD the machine
Accept nothing less than STATUS_SUCCESS
