afwworkplaceapplication.exe CRASH
On a Dell T3660 client (with a 32bit 800xA release 5.1), I have connected 4 monitors on two nvidia quadro600 graphics card. The process afwworkplaceapplication after some hours crash. The crash not happen if I use only two monitors. In the Client Log file this informations are collected:
Fault Reason:
-------------
afwworkplaceapplication.exe caused an in module KERNELBASE.dll at 001B:75F3C6E3, RaiseException()+0084 byte(s)
Registers:
----------
EAX=2CE8EEF8 EBX=E0434F4D ECX=00000001 EDX=00000000 ESI=2CE8EF80
EDI=21065F60 EBP=2CE8EF48 ESP=2CE8EEF8 EIP=75F3C6E3 FLG=00000212
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000
Stack:
------
001B:75F3C6E3 (0xE0434F4D 0xFFFFFFFF 0x00000001 0x00000000) KERNELBASE.dll, RaiseException()+0084 byte(s)
Fault Reason:
-------------
AfwWorkplaceApplication.exe caused an in module KERNELBASE.dll at 001B:754AC6E3, RaiseException()+0084 byte(s)
Registers:
----------
EAX=313EF6D8 EBX=E0434F4D ECX=00000001 EDX=00000000 ESI=313EF760
EDI=38CB35A0 EBP=313EF728 ESP=313EF6D8 EIP=754AC6E3 FLG=00000216
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000
Stack:
------
001B:754AC6E3 (0xE0434F4D 0xFFFFFFFF 0x00000001 0x00000000) KERNELBASE.dll, RaiseException()+0084 byte(s)
001B:715E0CFC (0x433EDA7C 0x00000000 0x00000000 0x00000000) mscorwks.dll, DllRegisterServerInternal()+81190 byte(s)
001B:7168E8A4 (0x313EF818 0x00000000 0x71ADFAD8 0x00000000) mscorwks.dll, CopyPDBs()+14832 byte(s)
001B:717F3237 (0x433E4790 0x00000000 0x433E4790 0x00000000) mscorwks.dll, CorLaunchApplication()+65790 byte(s)
001B:7098513B (0x00000000 0x00000000 0x38CB35A0 0x00000000) mscorlib.ni.dll
001B:7098844C (0x313EF8D0 0x00000000 0x1526190E 0x00000000) mscorlib.ni.dll
001B:71571B4C (0x00000000 0x00000000 0x00000000 0x00000000) mscorwks.dll
001B:71588951 (0x00000000 0x00000000 0x00000000 0x00000000) mscorwks.dll
001B:71588F43 (0x00000000 0x00000000 0x00000000 0x00000000) mscorwks.dll
001B:71588F84 (0x00000000 0x00000000 0x00000000 0x00000000) mscorwks.dll
001B:71588FF1 (0x00000000 0x00000000 0x00000000 0x00000000) mscorwks.dll
001B:715AE0F9 (0x313EFB80 0x00000000 0x71ACFF4C 0x00000000) mscorwks.dll, CoUninitializeEE()+104861 byte(s)
001B:715AC6C7 (0x313EFB20 0x00000000 0x313EFACC 0x00000000) mscorwks.dll, CoUninitializeEE()+98155 byte(s)
001B:715AC663 (0x313EFB20 0x00000000 0x9FBF7796 0xFFFFFFFF) mscorwks.dll, CoUninitializeEE()+98055 byte(s)
001B:715AC583 (0x313EFB20 0x00000000 0x00000001 0x00000000) mscorwks.dll, CoUninitializeEE()+97831 byte(s)
001B:715AC715 (0x00000001 0x00000000 0x715AE0AC 0x00000000) mscorwks.dll, CoUninitializeEE()+98233 byte(s)
001B:715ADA88 (0x00000001 0x00000000 0x715AE0AC 0x00000000) mscorwks.dll, CoUninitializeEE()+103212 byte(s)
001B:715AE079 (0x2D47AEE8 0x00000000 0x00000001 0x00000000) mscorwks.dll, CoUninitializeEE()+104733 byte(s)
001B:715AE0A8 (0x2D47AEE8 0x00000000 0x00000001 0x00000000) mscorwks.dll, CoUninitializeEE()+104780 byte(s)
001B:715AE14E (0x38EB0498 0x00000000 0x9FBF70BA 0xFFFFFFFF) mscorwks.dll, CoUninitializeEE()+104946 byte(s)
001B:715ADE10 (0x00000000 0x00000000 0x00000000 0x00000000) mscorwks.dll, CoUninitializeEE()+104116 byte(s)
001B:715AD723 (0x00000000 0x00000000 0x00000000 0x00000000) mscorwks.dll, CoUninitializeEE()+102343 byte(s)
001B:716D26DB (0x2C9D47E0 0x00000000 0x313EFD14 0x00000000) mscorwks.dll, CreateApplicationContext()+53339 byte(s)
001B:76B7ED6C (0x2C9D47E0 0x00000000 0x460CFB11 0x00000000) kernel32.dll, BaseThreadInitThunk()+0018 byte(s)
001B:7730377B (0x716D2695 0x00000000 0x2C9D47E0 0x00000000) ntdll.dll, RtlInitializeExceptionChain()+0239 byte(s)
001B:7730374E (0x716D2695 0x00000000 0x2C9D47E0 0x00000000) ntdll.dll, RtlInitializeExceptionChain()+0194 byte(s)
Any suggestion why this crash happen only with the use of 4 monitors ?
Best regards
Angelo.
Answers
Hi,
Can you check the arrangement of your Quad monitors?
For 2 Video cards, it should be
1 2
3 4
1 and 2 from Video Card1
3 and 4 from Video Card2
Not
1 3
4 2
1 and 2 from Video Card1
3 and 4 from Video Card2
Best Regards,
Deepak.
Check (true*) Virtual Bytes usage with eg Perfmon.exe or Power Shell ("PS> get-process afww*")
On 32-bit OS, 1500 MB is max recommended (true) VM usage after which you are recommended to restart the workplace at earliest possible point in time.
As usage exceed 1500 MB on the way to physical max of 2048 MB the workplace will perform slower and slower as memory allocation, especially contiguous memory blocks takes more time to perform due to memory fragmentation. Eventually allocation fails and a crash is inevitable. Crashes may occur earlier than at/near above stated levels, eg if contiguous memory is requested and the memory heap is heavily fragmented.
Memory usage increases with each monitor you add; perhaps you hit 1500 MB shortly after launch? Some displays may allocate 500+ MB or more!
With 64-bit OS the limit is at least the double.
*) The regular Task Manager tool report an incorrect VM Size and should not be used here.
If Virtual Bytes (constantly) are less than 1500 MB you may elect to enable Dump On Exception to catch a crash dump which your regional ABB support center can forward to R&D for analysis.
Add new comment