There seems to be two major variations in the debug mode "blank screen."
In the first variation, the "blank screen" window has a task bar. The program loops at the second access violation message. Cpu use ranges from 1 to 20%. The debug log is like the one attached at
In the second variation, the "blank screen" window has no task bar. However, there is a window with a task bar underneath the colored area (you can see it all around the margins of the visible "blank screen"). Cpu use is in a steady 45 to 55% range. The debug log is like the right side thumbnails in the prior post.
Here's a "Problem signature" from the first variation:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: jv16PT.exe
Application Version: 1.8.0.455
Application Timestamp: 2a425e19
Hang Signature: 5434
Hang Type: 0
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1033
Additional Hang Signature 1: bafe58ff6a41709b19cd908bbcd2997b
Additional Hang Signature 2: 3c12
Additional Hang Signature 3: 530572e07b6c8274dc64aac4b58e27c1
Additional Hang Signature 4: 5434
Additional Hang Signature 5: bafe58ff6a41709b19cd908bbcd2997b
Additional Hang Signature 6: 3c12
Additional Hang Signature 7: 530572e07b6c8274dc64aac4b58e27c1
