MySQL Bugs: #19574: MySQL Workbench has encountered a problem and needs to close

Bug #19574	MySQL Workbench has encountered a problem and needs to close
Submitted:	6 May 2006 3:26	Modified:	7 May 2006 19:07
Reporter:	Andy Sikes	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench Preview	Severity:	S3 (Non-critical)
Version:	1.01 and 1.06	OS:	Windows (XP Pro SP2 P4-512)
Assigned to:		CPU Architecture:	Any

Description:
Sounds somewhat similar to descriptions in bug 13242.  After the title screen starts up, both downloads of 1.01 and 1.06 Beta produce the same error screen stating "MySQL Workbench has encountered a problem and needs to close".  Video card is NVIDIA GeForce4 440 Go. After hitting "Don't Send" on error screen,  Application error message states "Exception EOSError in module MySQLWorkbench.exe at 000104CA.  System Error. Code: 1114.  A dynamic link library (DLL) initialization routine failed."  Next error screen states "The instruction at 0x004f22d7 referenced memory at 0x01b37c4d.  The memory could not be read."  After several repeated questions to terminate, two simple "Error" dialogs come up before program terminates.  Their messages are "Runtime error 216 at 0042571A" and "Runtime error 216 at 7C901010"

How to repeat:
Click on MySQL Workbench program link.

debug info from Visual Studio output

Attachment: debug_info.txt (text/plain), 7.27 KiB.

Word doc showing error screens.

Attachment: WorkBench App err screens.doc (application/msword, text), 57.50 KiB.

After further checking the Workbench Forum, I found Niobi in msg# 74166 had the same issue I had in the 1.06 beta.  From the solution provided by Rodger Irwin in msg# 75077, I was able to resolve the issue.  I have the GeForce4 440 Go video card, so it may be an issue with that generation of cards.  In addition, like Niobi in msg# 79107, I upgraded to the later NVidia driver (\windows\system32\DRIVERS\nv4_mini.sys) from the earlier one (\windows\system32\nv4_disp.sys) and have been able to reset the Hardware Acceleration back to "Full".
Many thanks to all of you and I will try to check the forum more closely before submitting another bug.
Andy