cancel
Showing results for 
Search instead for 
Did you mean: 

Modal analysis devide by zero crash.

N/A

Hi,
I have a model that has created the following "divide by zero crash".
Is anyone at UGS interested in the files to locate the bug?
Start of the error messgae given below.
*** USER INFORMATION MESSAGE 5010 (LNCILD)
STURM SEQUENCE DATA FOR EIGENVALUE EXTRACTION.
TRIAL EIGENVALUE = 6.373017D+03, CYCLES = 1.270553D+01 NUMBER OF EIGENVALUES
BELOW THIS VALUE = 338
User information:
This message is automatic output during eigenvalue extraction. This
can be used, along with the list of eigenvalues, to identify the modes
found. See the NX NASTRAN Numerical Methods User's Guide.
MAIN: The FPU has been reset after floating point exception.
MAIN: For reference, A(MAINAL) = 4012B0, A(/SYSTEM/) = 1C930C0
MAIN: A(/XNSTRN/) = 39F0020
MAIN: "Floating point zero divide" (C000008E) exception encountered.
MAIN: Exception occurred at address 01837825.
MAIN: Context Flags 0001003F
MAIN: EAX 00000001 EBX 0012EEB8 ECX 00000001 EDX 01EF7704 ESI 00000001 EDI
60000000
MAIN: EBP 039F0030 ESP 0012ED40 EIP 01837827 EFLAGS 00010297
MAIN: The 32 bytes around exception location 01837825 are --
MAIN: 01837815 93 84 00 00 00 83 3A 02 0F 84 6B 10 00 00 DE EA
MAIN: 01837825 DE F1 DD 15 E0 E4 04 02 D9 E0 DD 9C 24 0C 01 00
MAIN: FPU Control Word 0273 StatusWord 80B7 TagWord FFF4
MAIN: FPU EIP 01837825 OpCode 06F1 DataOffset 0200FF38
MAIN: Data at 0200FF38 is 00000060 04E5B840
MAIN: FPU Reg 0 (Tag 0) 3FFF8000000000000000 1
MAIN: FPU Reg 1 (Tag 1) 00000000000000000000 ZERO
MAIN: FPU Reg 2 (Tag 3) 3FFF8000000000000000 EMPTY
MAIN: FPU Reg 3 (Tag 3) BF9792DE786000000000 EMPTY
MAIN: FPU Reg 4 (Tag 3) BFAC800003E6F3C22000 EMPTY
MAIN: FPU Reg 5 (Tag 3) 00000000000000000000 EMPTY
MAIN: FPU Reg 6 (Tag 3) BF5CEE4829BD965AB800 EMPTY
MAIN: FPU Reg 7 (Tag 3) 400BC728230000000000 EMPTY
MAIN: The 256 words on the stack, starting at 0012ED40, are --
1 REPLY

Re: Modal analysis devide by zero crash.

N/A

Carlton,
If you send me the files, I'll take a look.
Regards,
Jim

"Carlton Matthew" wrote:
>
>Hi,
>I have a model that has created the following "divide by zero crash".
>Is anyone at UGS interested in the files to locate the bug?
>Start of the error messgae given below.
>*** USER INFORMATION MESSAGE 5010 (LNCILD)
> STURM SEQUENCE DATA FOR EIGENVALUE EXTRACTION.
> TRIAL EIGENVALUE = 6.373017D+03, CYCLES = 1.270553D+01 NUMBER OF EIGENVALUES
>BELOW THIS VALUE = 338
> User information:
> This message is automatic output during eigenvalue extraction. This
> can be used, along with the list of eigenvalues, to identify the modes
> found. See the NX NASTRAN Numerical Methods User's Guide.
> MAIN: The FPU has been reset after floating point exception.
> MAIN: For reference, A(MAINAL) = 4012B0, A(/SYSTEM/) = 1C930C0
>
> MAIN: A(/XNSTRN/) = 39F0020
>
> MAIN: "Floating point zero divide" (C000008E) exception encountered.
> MAIN: Exception occurred at address 01837825.
> MAIN: Context Flags 0001003F
> MAIN: EAX 00000001 EBX 0012EEB8 ECX 00000001 EDX 01EF7704 ESI 00000001
> EDI
> 60000000
> MAIN: EBP 039F0030 ESP 0012ED40 EIP 01837827 EFLAGS 00010297
> MAIN: The 32 bytes around exception location 01837825 are --
> MAIN: 01837815 93 84 00 00 00 83 3A 02 0F 84 6B 10 00 00 DE EA
> MAIN: 01837825 DE F1 DD 15 E0 E4 04 02 D9 E0 DD 9C 24 0C 01 00
> MAIN: FPU Control Word 0273 StatusWord 80B7 TagWord FFF4
> MAIN: FPU EIP 01837825 OpCode 06F1 DataOffset 0200FF38
> MAIN: Data at 0200FF38 is 00000060 04E5B840
> MAIN: FPU Reg 0 (Tag 0) 3FFF8000000000000000 1
> MAIN: FPU Reg 1 (Tag 1) 00000000000000000000 ZERO
> MAIN: FPU Reg 2 (Tag 3) 3FFF8000000000000000 EMPTY
> MAIN: FPU Reg 3 (Tag 3) BF9792DE786000000000 EMPTY
> MAIN: FPU Reg 4 (Tag 3) BFAC800003E6F3C22000 EMPTY
> MAIN: FPU Reg 5 (Tag 3) 00000000000000000000 EMPTY
> MAIN: FPU Reg 6 (Tag 3) BF5CEE4829BD965AB800 EMPTY
> MAIN: FPU Reg 7 (Tag 3) 400BC728230000000000 EMPTY
> MAIN: The 256 words on the stack, starting at 0012ED40, are --
>