VMD-L Mailing List

From: MyLinkka (mylinkka_at_gmail.com)
Date: Wed May 20 2009 - 06:28:10 CDT

update:
 I changed back to an ancient driver (176.06 for HP, released ~06.2008 )
for the Quadro
FX2700M on my laptop. The problem was the same as described before.

Doesn't this problem is related to the hardware capability? Is anyone
using VMD with
the same card?

ting

John Stone wrote:
> Hi,
> Which NVIDIA driver version are you running? This sounds like an
> OpenGL driver bug to me, since I don't get a crash on either my
> NVIDIA-equipped test boxes at the lab, or an an old laptop with
> an outdated ATI chipset.
>
> I've had two other people tell me that they have encountered a
> crash with the beta, having the exact driver information
> for affected machines will be very helpful so I can report bugs
> the GPU vendors.
>
> Cheers,
> John Stone
> vmd_at_ks.uiuc.edu
>
> On Tue, May 19, 2009 at 12:14:34PM +0200, MyLinkka wrote:
>
>> Hi,
>>
>> I'm eager to try out the new Beta version. 2 days ago, I installed 1.8.7
>> beta 2 on both my laptop and
>> desktop PC. Beta 2 crashes on the laptop but worked on the PC. Both
>> computers have Nvidia graphics
>> card (FX2700M and Geforce 8600 GT). Today I installed the latest beta
>> 3 on both. Sadly beta 3
>> crashed on both computers! Before install beta2, I didn't install any
>> software or update drivers.
>> That's why I turn to this mailing list, cause I think it is almost for
>> sure an issue from vmd.
>>
>> The symptom is the same. After starting vmd, first the console window
>> showed, it seems fine and
>> it listed information and capability of my graphics card. Then the 3D
>> window popped up, I could
>> see the 3D texts and the axes at the corner. (my feeling it the OpenGl
>> context and scene had been
>> created without problem.) Finally it's the turn of the main control
>> windows, I can see the window
>> frame, but before the contents (menus,buttons) could be seen the program
>> crashed.
>>
>> on my laptop, the system report a "the memory could not be 'read'"
>> error. On the PC,
>> an error happend at offset 0x00028c0d in ntdll.dll.
>>
>> BTW, vmd 1.8.6 work perfect on both computers.
>>
>> Could anyone point me what to do? Is there a way to generate a startup
>> log file to address the error
>> source?
>>
>> thanks!
>>
>> ting
>>
>
>