Windows 7 iSCSI driver charged with manslauter

My desktop here at work is a rather nice Windows 7 machine - quad core, 8GB, SSD drive (thanks Red Gate!). It's only a few months old, so I was rather shocked to arrive at work this morning to the old friend: a Blue Screen of Death!

A quick reboot, and it seemed fine, but soon after, another crash, then a third after that. Not best pleased at this point, I wandered over to our IS guys to see if they had any ideas. Windows Updates were called into question, but turned up nothing. Then Helen suggested I tried running WinDbg against the crash dump...

1. Grab "Debugging Tools for Windows" from Microsoft.com - either 32-bit or 64-bit depending on the flavour of your OS.
2. Run WinDbg. If you've got UAC turned on, you'll need to run it elevated.
   
3. Go to File -> Symbol Search Path, and enter http://msdl.microsoft.com/download/symbols - the Microsoft public symbol server.
4. File -> Open Crash Dump..., and locate the BSOD crash dump - in my case it was in C:\Windows\MEMORY.DMP.
5. Wait a while...

After that, you should get an analysis, hopefully with the line "Probably caused by: {some driver or another}" in there. In my case, it was msiscsi.sys, the Windows iSCSI initiator.

So, why had this just started happening, and how to fix it?

A little while back, I'd spun up an OpenSolaris virtual machine running a ZFS iSCSI target (thanks Isaac!), and connected to it from my desktop. All good. The VM had since been shut down, but the iSCSI target remained. My theory - and this has very little evidence - is that the DHCP lease had finally expired last night, and it'd just been re-allocated to some other machine on the network, at which point the IP became reachable again, but without an iSCSI target at the end.

Suffice it to say, I removed the target, and everything's been fine since...