Windows 7: BSOD fun

Hey Guys,



My debugger decided to stop working but that is another issue. Can anyone help me with the problem on this dump log?

Define "not working"? Not loading? Symbol issues? Extension problems?

Anyways, the issue is that there was a NT Exception fault that occurred during SMB activity. There's no doubt we're dealing with accessing a network file here, as mup.sys is involved, as well as SMB present in faulting callstack. The stack fits all the characteristics of using an existing named pipe to access a networked resource.

Since this occurred during the SearchProtocol process (which is part of the Indexing Service), make sure you haven't incidentally set Windows to index networked resources like remote drives and whatnot, that may cause an issue. I also did notice that a Trend Micro filter driver exists in the raw stack for the thread. It's woefully dated from Nov 2011 so you'll want to see what you can do about updating it if at all possible.

Other then that, I can't really debug further from here, as this is just a measly ole minidump. I could probably get the name of the named pipe and other misc. info with a kernel dump.

If you wish, you can turn on Driver Verifier and have it crash a few more times. For checks to select, select all of them except Force Pending I/O Requests, Low Resource Sim and IRP Logging. Restart after everything's finished. If you experience boot loop, go into Safe Mode and turn off DV from there. Send us all resulting crashdumps.

EDIT: Oops, forgot to tell you the NT Exception. It's a common c0000005, bad memory address. Looks like a dereferenced null pointer.

DOUBLE EDIT: I noticed just now you are using a company PC. Probably not wise to progress further on this through public means, especially if you decide to provide us a kernel dump, as that'd be quite compromising to internal security. You'll want to contact your corporate IT department for assistance on this problem. Provide them the crashdump and my recommendations, as well as my explanation for what it is so far. Btw, to add, this may be caused by an issue with mapped network drives. Try recreating them. Other than that, I can - and shouldn't - offer any more assistance on this, as I'm sure it's against company policy.