On some d3d failures (when failure occurs on late initialization steps) D3DContext dtor sents notification to java about object disposals.
If the failure accurs before JMV initialization completes, it causes crash (due jvm is not exists yet)
To fix the issue:
1. set initial NULL value for jvm variable (see src/windows/native/sun/windows/awt_Toolkit.cpp, line 78)
2. before notification tests if jmv is NULL (D3DPipelineManager::NotifyAdapterEventListeners method, src/windows/native/sun/java2d/d3d/D3DPipelineManager.cpp, lines 159..176) and don't sent the notification if jmv is not set yet
Unfortunately it's hard to reproduce the issue for appropriate testing.