Okay, I'm getting a strange problem here. I am initializing D3D, rendering away all hapilly, and I'm closing down D3D when I quit (which is apparently happening smoothly). Now, after everything is closed the final thing I am doing is calling DestroyWindow on my HWND. On this call I get a big uh oh :(. As I step over the call, I get a MessageBeep sound (systemstop), and the prcoess is immedatly terminated (DestroyWindow never returns). This ONLY happens if I've used D3D during the life time of the app. I have tried enabling the D3D debug runtimes to see if it's telling me anything. But it's not telling me anything out of the ordinary. Anyone have any clues what may be happening here? These kind of bugs annoy the crap out of me >_<. The only work around I have at the moment is to not call DestroyWindow at all, but that is peh. Thanks.

Okay. After much angst, I have worked out what was happening. It, in fact, had nothing to do with D3D at all (that was just a side effect of only having the window shown when D3D was initialized).

I was calling a funtion from within WM_ACTIVATE, and in that function it was asserting. Fair enough. But why..._WHY_ didn't it come up with an assert dialog? It just hit the assert, failed the test, beeped, and then terminated without any message. That's just making assert's counter productive.

Anything I could have done to disable asserts?

[edit]
Well, I just realized that I can't have "disabled" assert dialogs, since I do remember popping up an assert earlier today. How can some assert's work properly, and some not?