Curious BSOD

[seekermeister]

While watching a flick on Hulu, just a bit ago, the computer BSODed, and said that the cause was SandBox64, which is part of my firewall. When I rebooted, I ran the Crash Analyzer and it said the same thing, but the speaker icon in the Notification Tray was red Xed, and there was no audio available. This coupled with the fact that the speakers emitted a loud buzzing sound at the crash, led me to check in the DM for the sound card. The Properties said that there was no driver installed for it. I let Windows reinstall it and after rebooting the audio became normal.

Therefore, I'm not seeking a solution to fix the sound, but am
trying to comprehend how a firewall that has been installed for a while, and a sound driver that has also been installed for a while, with no apparent problems, could suddenly cross swords with each other? I doubt that there is a clear cut answer for this, but I would like to hear any ideas, regardless of how unclear they may be.

 

[YakSipper]

Hey there. If you post the actual crash dump, we may be able to figure something out differently or determine the exact cause.

 

[seekermeister]

I would have done that sooner, but for some reason I was having a problem saving it. However, here it is now:

EDIT: Oops! You said that crash dump, not the analysis. Do you really need the dump?

 

[seekermeister]

I just realize that I was wrong about what I said before. The BSOD named filtmgr, not SandBox64.

EDIT: I just tried to upload the minidump, but it wouldn't accept it, saying that it was an invalid file. I suppose that is because it has a .dmp extension, which isn't listed among the acceptable types, but I know others have uploaded them, so I'm stumped.

 

[Tews]

You need to zip the .dmp file, then attach it ...