Application hung, eip = 0

using r42356, l33t.exe from http://ryanross.net/leet/ and windows mfc42.dll
I launched l33t.exe type in some text to convert to leet and hit the translate button, the application is now hung. tested in vbox 3.0.0 r49315

I preceded to break into kdbg to analyze the issue.
You might notice that kdbg thread list command shows an eip for the thread, but the backtrace command does not.

PuTTYEntered debugger on embedded INT3 at 0x0008:0x808c06f6.
kdb:> proc list
PID State Filename
*0x00000004 In Memory System
0x00000050 In Memory smss.exe
0x00000088 In Memory csrss.exe
0x000000ac In Memory winlogon.exe
0x000000c8 In Memory services.exe
0x000000d0 In Memory lsass.exe
0x000000ec In Memory VBoxService.exe
0x00000104 In Memory eventlog.exe
0x0000011c In Memory umpnpmgr.exe
0x00000138 In Memory spoolsv.exe
0x00000150 In Memory rpcss.exe
0x00000170 In Memory dhcp.exe
0x000001c8 In Memory explorer.exe
0x000001f0 In Memory VBoxTray.exe
0x00000274 In Memory cmd.exe
0x000002ac In Memory l33t.exe
kdb:> proc attach 0x2ac
Attached to process 0x000002ac, thread 0x000002b0.
kdb:> thread list
TID State Prior. Affinity EBP EIP
*0x000002b0 Ready 8 0x00000001 0x14244c8d 0x2282e804
kdb:> bt
Eip:
<00000000>
Frames:
<msvcrt.dll:1362c> lib/sdk/crt/mbstring/mbslwr.c:40 (_mbslwr)
<MFC42.DLL:24882>
<00000001>
<l33t.exe:1390>
<25ff0040>
Couldn't access memory at 0x40B02603!
kdb:>

It has happened consistently every time i tried this application...