BSoD at starting system when I enable "Code integrity checks" option in Driver Verifier on selected drivers - no crash dump files

[MrPepka]

I have such a problem. I have a pair of drivers in my system that are incompatible with the "Code integrity checks" feature of Driver Verifier. The effect is simple: Attempting to enable the "Code integrity checks" option from Driver Verifier on these incompatible drivers causes a blue screen on boot. I reported the problem to the developers of these drivers, but one of them (the developer of Daemon Tools software) wants memory dumps from these blue screens from me. The problem is that when I get a blue screen while booting the system, no memory dumps are created (then there is a message that the computer has encountered a problem and needs to be restarted and that the computer can be restarted, there is no information that any memory dumps are created). Let me mention that when I call the blue screen while the system is running, the memory dumps are created so this function works fine. Any of you know what to do to create memory dumps when the blue screen appears on boot?

 

[axe0]

Do these drivers load when system drivers are loaded?

My first guess is that a crash happens too early for Windows to create a dump.

 

[MrPepka]

Yes, these drivers load at system startup. I also think that the blue screen shows up too quickly and the crash dump driver just doesn't start in time before the blue screen shows up, but what can I do about it?

 

[xrobwx71]

Can you create a delayed service startup in services.msc?

 

[MrPepka]

Are you talking about the memory dump service? If so, unfortunately it is not in services.msc, the creation of memory dumps is controlled by a special driver called crashdmp.sys which sometimes loads too late (the blue screen on boot may appear before the above-mentioned driver loads)

 

[axe0]

I believe he may be talking about the drivers you're selecting in driver verifier.

Rob, boot and system drivers are loaded just before the crash dump generation process starts so any such driver causing a problem and there's never a dump. Unless these drivers are connected to a service it's not really possible to delay them, whether that's smart to do is something else.