First, thank you for your a quick answer.
In windows 10, To correct the checksum of digital signed drivers, original driver's checksum must be correct.
The test results, it was confirmed that the checksum of DemoDriver64.sys is same before and after performing the following command.
madConfigDrv DemoDriver64.sys HookProcessCreationDemoDriver HookProcessCreation32.dll HookProcessCreation64.dll -unsafeStopAllowed
Is it right?
If so, I think that madConfigDrv must change cheksum value of the driver since madConfigDrv changed the contents of the driver.
Ultimately, I wonder whether this part will be reflected in the next patch.