Solved: Inventor 2010 sim crash

anriil · ‎01-18-2012

Hello

I reinstalled IV2010Sim on the new PC and when i started doing simulations it started crashing right after the simulation finished. I looked at the dmp file, couldn't make much sense of it besides FEAManager being the culprit.

Any ideas?

System is:

Win7 Pro x64

CPU i7 2600k

GPU Nvidia GTX590

RAM 32GB DDR 1300MHz

SSD Crucial m4

Loading Dump File [C:\Users\User\Desktop\Inventor120118135110.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Wed Jan 18 13:51:10.000 2012 (UTC + 2:00)
System Uptime: not available
Process Uptime: 0 days 0:16:46.000
................................................................
................................................................
................................................................
................................................................
................................................................
................................................................
....................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(1380.438): Unknown exception - code c000000d (first/second chance not available)
ntdll!NtGetContextThread+0xa:
00000000`77661fea c3              ret
0:028> g
       ^ No runnable debuggees error in 'g'
0:028> g
       ^ No runnable debuggees error in 'g'
0:028> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for FEAManager.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for FEA_Logic.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for FWx_Master_Events_Management.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for RxAppDocView.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for rse.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fw.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for RxAssembly.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for RxUtil.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for FWx_Change_Definition.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for FWx_Business_Logic.dll - 
*** ERROR: Module load completed but symbols could not be loaded for Inventor.exe
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for adlmint.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for nvwgf2umx.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for vbc64.dll - 
Failed to load data access DLL, 0x80004005
Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
            2) the file mscordacwks.dll that matches your version of mscorwks.dll is 
                in the version directory
            3) or, if you are debugging a dump file, verify that the file 
                mscordacwks_<arch>_<arch>_<version>.dll is on your symbol path.
            4) you are debugging on the same architecture as the dump file.
                For example, an IA64 dump file must be debugged on an IA64
                machine.

You can also run the debugger command .cordll to control the debugger's
load of mscordacwks.dll.  .cordll -ve -u -l will do a verbose reload.
If that succeeds, the SOS command should work on retry.

If you are debugging a minidump, you need to make sure that your executable
path is pointing to mscorwks.dll as well.
Failed to load data access DLL, 0x80004005
Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
            2) the file mscordacwks.dll that matches your version of mscorwks.dll is 
                in the version directory
            3) or, if you are debugging a dump file, verify that the file 
                mscordacwks_<arch>_<arch>_<version>.dll is on your symbol path.
            4) you are debugging on the same architecture as the dump file.
                For example, an IA64 dump file must be debugged on an IA64
                machine.

You can also run the debugger command .cordll to control the debugger's
load of mscordacwks.dll.  .cordll -ve -u -l will do a verbose reload.
If that succeeds, the SOS command should work on retry.

If you are debugging a minidump, you need to make sure that your executable
path is pointing to mscorwks.dll as well.
GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/Inventor_exe/14_4_0_28400/4e040628/FEAManager_dll/14_4_0_28400/...

FAULTING_IP: 
FEAManager!DllUnregisterServer+a3974
00000000`33985594 498b6c2440      mov     rbp,qword ptr [r12+40h]

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000033985594 (FEAManager!DllUnregisterServer+0x00000000000a3974)
   ExceptionCode: c000000d
  ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME:  Inventor.exe

ERROR_CODE: (NTSTATUS) 0xc000000d - An invalid parameter was passed to a service or function.

EXCEPTION_CODE: (NTSTATUS) 0xc000000d - An invalid parameter was passed to a service or function.

MOD_LIST: <ANALYSIS/>

MANAGED_STACK: !dumpstack -EE
Failed to load data access DLL, 0x80004005
Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
            2) the file mscordacwks.dll that matches your version of mscorwks.dll is 
                in the version directory
            3) or, if you are debugging a dump file, verify that the file 
                mscordacwks_<arch>_<arch>_<version>.dll is on your symbol path.
            4) you are debugging on the same architecture as the dump file.
                For example, an IA64 dump file must be debugged on an IA64
                machine.

You can also run the debugger command .cordll to control the debugger's
load of mscordacwks.dll.  .cordll -ve -u -l will do a verbose reload.
If that succeeds, the SOS command should work on retry.

If you are debugging a minidump, you need to make sure that your executable
path is pointing to mscorwks.dll as well.

IP_ON_HEAP:  00000000b10000b1
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

IP_IN_VM_BLOCK: b10000b1

FRAME_ONE_INVALID: 1

LAST_CONTROL_TRANSFER:  from 0000000033985594 to 0000000072ddb1e5

FAULTING_THREAD:  0000000000000438

DEFAULT_BUCKET_ID:  STATUS_INVALID_PARAMETER

PRIMARY_PROBLEM_CLASS:  STATUS_INVALID_PARAMETER

BUGCHECK_STR:  APPLICATION_FAULT_STATUS_INVALID_PARAMETER

STACK_TEXT:  
00000000`3aefdeb0 00000000`33985594 : 00000000`339ad508 00000000`04aa3d80 00000000`04d38740 00000000`047472e8 : msvcr80!_invalid_parameter_noinfo+0x55 [f:\dd\vctools\crt_bld\self_64_amd64\crt\src\invarg.c @ 99]
00000000`3aefe470 00000000`33987f85 : 00000000`00000000 00000000`04aa3d80 00000000`04aa3d80 00000000`0474ba10 : FEAManager!DllUnregisterServer+0xa3974
00000000`3aefe860 00000000`33938b38 : 00000000`04aa3d80 00000000`04aa3d80 00000000`047484b0 00000000`04aa3d80 : FEAManager!DllUnregisterServer+0xa6365
00000000`3aefe950 00000000`33908eda : 00000000`2aa2bf08 00000000`04aa3d80 00000000`04749370 00000000`04749370 : FEAManager!DllUnregisterServer+0x56f18
00000000`3aefebf0 00000000`3391c286 : 00000000`04aa3d80 00000000`04aa3d80 00000000`0474bd40 00000000`04aa3d80 : FEAManager!DllUnregisterServer+0x272ba
00000000`3aefeca0 00000000`3391fa69 : 00000000`04aa3d80 00000000`00000004 00000000`0000ffff 00000000`04754340 : FEAManager!DllUnregisterServer+0x3a666
00000000`3aefed70 000007fe`fedf23d5 : 00000000`04a87fd8 00000000`0000ffff 00000000`00000000 00000000`00000004 : FEAManager!DllUnregisterServer+0x3de49
00000000`3aefef00 000007fe`fede69b2 : 00000000`3aeff330 00000000`2ade1630 00000000`00000030 00000000`09bff88e : rpcrt4!Invoke+0x65
00000000`3aefef60 000007fe`ff06376f : 00000000`2ade1310 00000000`00000001 000007fe`ff0771e0 000007fe`ff082fb0 : rpcrt4!NdrStubCall2+0x32a
00000000`3aeff580 000007fe`fed010c4 : 000007fe`00000001 00000000`2aa2c440 00000000`0418cbd0 000007fe`ff060883 : ole32!CStdStubBuffer_Invoke+0x9c
00000000`3aeff5b0 000007fe`ff060ccd : 00000000`00000000 00000000`00000000 ffffffff`d5299de7 00000000`00000000 : oleaut32!CUnivStubWrapper::Invoke+0xe4
00000000`3aeff600 000007fe`ff060c43 : 00000000`2ec910f0 00000000`2aa2c524 00000000`0998e560 00000000`339a2968 : ole32!SyncStubInvoke+0x5d
00000000`3aeff670 000007fe`fef1a4f0 : 00000000`2ec910f0 00000000`2adce6f0 00000000`2ec910f0 00000000`00000000 : ole32!StubInvoke+0xdb
00000000`3aeff720 000007fe`ff0614d6 : 00000000`00000000 00000000`00000010 00000000`2aa2c440 00000000`0418dd60 : ole32!CCtxComChnl::ContextInvoke+0x190
00000000`3aeff8b0 000007fe`ff06122b : 00000000`d0908070 00000000`2adce6f0 00000000`09fca3e0 00000000`29f82ca0 : ole32!AppInvoke+0xc2
00000000`3aeff920 000007fe`ff063542 : 00000000`2ec91060 00000000`00000000 00000000`00000000 00000000`00000000 : ole32!ComInvokeWithLockAndIPID+0x52b
00000000`3aeffab0 000007fe`fef2d42d : 00000000`0418dd60 106eab5d`00001269 00000000`0418c5d0 00000000`2ec91060 : ole32!ComInvoke+0xae
00000000`3aeffae0 000007fe`fef00106 : 00000000`2ab494c0 00000000`00000000 00000000`00000001 00000000`00001440 : ole32!ThreadDispatch+0x29
00000000`3aeffb10 000007fe`fef00182 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ole32!CRpcThread::WorkerLoop+0x1e
00000000`3aeffb50 00000000`773b652d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1a
00000000`3aeffb80 00000000`7763c521 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`3aeffbb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d


STACK_COMMAND:  .cxr 0000000000000000 ; kb ; ~28s; .ecxr ; kb

FOLLOWUP_IP: 
FEAManager!DllUnregisterServer+a3974
00000000`33985594 498b6c2440      mov     rbp,qword ptr [r12+40h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  feamanager!DllUnregisterServer+a3974

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: FEAManager

IMAGE_NAME:  FEAManager.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4e03f7fe

FAILURE_BUCKET_ID:  STATUS_INVALID_PARAMETER_c000000d_FEAManager.dll!DllUnregisterServer

BUCKET_ID:  X64_APPLICATION_FAULT_STATUS_INVALID_PARAMETER_feamanager!DllUnregisterServer+a3974

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/Inventor_exe/14_4_0_28400/4e040628/FEAManager_dll/14_4_0_28400/...

Followup: MachineOwner
---------

0:028> lmvm FEAManager
start             end                 module name
00000000`338a0000 00000000`33a14000   FEAManager   (export symbols)       FEAManager.dll
    Loaded symbol image file: FEAManager.dll
    Mapped memory image file: C:\Program Files\Autodesk\Inventor 2010\bin\FEAManager.dll
    Image path: C:\Program Files\Autodesk\Inventor 2010\bin\FEAManager.dll
    Image name: FEAManager.dll
    Timestamp:        Fri Jun 24 05:35:42 2011 (4E03F7FE)
    CheckSum:         0017AF63
    ImageSize:        00174000
    File version:     14.4.0.28400
    Product version:  1.0.0.1
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Autodesk, Inc.
    ProductName:      Autodesk, Inc. FEAManager
    InternalName:     FEAManager
    OriginalFilename: FEAManager.dll
    ProductVersion:   Autodesk Inventor 2010
    FileVersion:      14, 4, 0000, 28400
    PrivateBuild:     Build: 284, Release: 2010 SP4 - Date: Thu 06/23/2011       
    SpecialBuild:     Build: 284, Release: 2010 SP4 - Date: Thu 06/23/2011       
    FileDescription:  FEAManager
    LegalCopyright:   Copyright © 1996–2009 Autodesk, Inc.
    LegalTrademarks:  Copyright © 1996–2009 Autodesk, Inc.
    Comments:         Copyright © 1996–2009 Autodesk, Inc.

anriil · ‎01-20-2012

up

anriil · ‎01-23-2012

It crashes every time in static analysis, modal analysis works (excluding the mesher, see below)

Additionally, the mesher doesn't work when the average element size is below 1 (doesn't start "loading").

I did the other variant (registry), didn't change anything.

henderh · ‎01-23-2012

Thanks for providing the additional information anriil. I've sent the data on to Development for further investigation.

[Edit: Development wants to know what you see if you just do a "Mesh View" using the default mesh settings]

Hugh Henderson
QA Engineer (Fusion Simulation)

henderh · ‎01-23-2012

A few more questions and comments from Development to dig deeper into the issue:

1) Are you using comma as the decimal separator? Can you provide screenshots of the meshing dialog?

2) From the log file, you've enabled separate stress across contacts. Can you disable the option and check if solving succeeds?

3) The FEAComputeserver.log is incomplete. Please create a new part, save it as cube.ipt (something else would work, but we want a name for the model). Then do the workflow. This would enable use to get a better log file.

Thanks! -Hugh

Hugh Henderson
QA Engineer (Fusion Simulation)

anriil · ‎01-24-2012

Should be everything

henderh · ‎01-24-2012

Hi Anriil,

Thank you for posting the part and all the attachments. As you have shown, somehow the mesh settings have become zero, causing the problem.

Would it be possible to do one more test?

1) Change the O/S regional settings to not use comma as the decimal separator (e.g. English, United States)

2) Restart Inventor & open the cube part

3) Create a new simulation and use the Mesh View command

Our apologies for the inconvenience.

Best regards, -Hugh

Hugh Henderson
QA Engineer (Fusion Simulation)

anriil · ‎01-24-2012

That worked, thank you!

henderh · ‎01-25-2012

Excellent news Anriil! We appreciate the follow-up

Hugh Henderson
QA Engineer (Fusion Simulation)

Inventor 2010 sim crash

Inventor 2010 sim crash

Forums Links

Post to forums