[gmx-users] Re: mdrun dies with STATUS_ACCESS_VIOLATION
Justin A. Lemkul
jalemkul at vt.edu
Thu Mar 12 02:35:19 CET 2009
Jack Shultz wrote:
> Also the dump file contains this information
>
> Exception: STATUS_ACCESS_VIOLATION at eip=0044C09B
> eax=000533A4 ebx=00000045 ecx=000528B4 edx=7F956C88 esi=FD6A65C0 edi=7F5D6C88
> ebp=7FB40020 esp=0022AE30 program=C:\Documents and Settings\All
> Users\Application Data\BOINC\slots\0\gromacs\bin\mdrun.exe, pid 2396,
> thread main
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> Stack trace:
> Frame Function Args
> 7FB40020 0044C09B (00000000, 00000000, 00000000, 00000000)
> End of stack trace
>
> On Wed, Mar 11, 2009 at 9:25 PM, Jack Shultz <jshultz at hydrogenathome.org> wrote:
>> Has anyone come across this error on a windows platform? Any
>> suggestions? I ran it through a BOINC workunit then tried it
>> stand-alone for troubleshooting. It produces the same result.
>>
>> 23 [main] mdrun 4084 _cygtls::handle_exceptions: Exception:
>> STATUS_ACCESS_VIOLATION
>> 316870 [main] mdrun 4084 open_stackdumpfile: Dumping stack trace to
>> mdrun.exe.stackdump
>>
I think this might be the Windows equivalent of a segmentation fault. Could be
wrong on that one, it's been a while since I've been on a Windows box.
From the output you posted, it's clear that your system did not minimize
properly (Fmax is still very large), and your PR dynamics are exploding, so
mdrun is crashing. To eliminate any problems with mdrun, I'd suggest building a
system that will energy-minimize properly and try again.
-Justin
>> Here are the details
>> http://hydrogenathome.org/result.php?resultid=1290554
>>
>>
>> --
>> Jack
>>
>> http://www.facebook.com/home.php#/profile.php?id=832713248
>> http://hydrogenathome.org
>>
>
>
>
--
========================================
Justin A. Lemkul
Graduate Research Assistant
ICTAS Doctoral Scholar
Department of Biochemistry
Virginia Tech
Blacksburg, VA
jalemkul[at]vt.edu | (540) 231-9080
http://www.bevanlab.biochem.vt.edu/Pages/Personal/justin
========================================
More information about the gromacs.org_gmx-users
mailing list