I have a SCSI HBA serving as the boot controller in a dual processor
hyper-threaded system running WinXP x64 edition. Upon generating a crash via
Crash-On-Ctrl-Scroll or the HCT crashdumptest, I have seen proof via WinDbg
that the runtime (miniport) driver is still running when the crashdump
driver is being loaded. Specifically, I have seen an interrupt generated
during crashdump initialization get serviced by the runtime driver. I have
also seen the one second timer I have continue to run on the runtime driver.
No need to explain what a driver collision like this can do to the hardware.
If I disable hyper-threading and one of the processors, the problem goes
away. Why isn't crashdump processing disabling the other processors?
Thanks
Scott