Forums
Bruker Media
Community Media
Bruker AFM Probes
SPM Digest
Application Notes
NanoTheater
Website
中文
Brochures & Datasheets
Publications
Probes Catalog
Events
Manuals & Documentation
Presentations
Guide to AFM Modes
News
Journal Club
Webinars & Video
Nanovations
Other
Hello,
I'm working with both a di3100 and multimode V afms. Recently, i've been getting the following "internal error" message from both systems:
(via multimode afm)
FATAL ERROR: SEtranslator FaultD:\V613r1\Z.exe 02/09/2005 14:08:40NanoScope (R) IV 6.13R1Quadrexed MultiMode (7039ev.scn), D:\CAPTURE\Alperen.wksRun 12/12/2010 15:03:20, Running 01:37:16 01730130 running fore noabort0857F820 ?DebugTransaction@SysManager@@KAXAAUDebRecord@@PAD@Z+AE0857F858 00BB423CDump terminated: exception0857FE14 ?do_poll@poll@@QAEXXZ 01730054 runnable fore noabort0651FE1C ?CallFunction@@YAXPAX0000K0K@Z+470651FE44 ?init_boot@fiber@@KAXAAUFiberBootArgs@@@Z+5B0651FE14 ?UpdateClock@nanoclock@@QAEXXZ 0173016C runnable fore noabort08EDFD6C ?FastMonitorProcess@FastScan232@@AAEXXZ+2508EDFE44 ?init_boot@fiber@@KAXAAUFiberBootArgs@@@Z+5B08EDFE14 ?FastMonitorProcess@FastScan232@@AAEXXZ 01730090 runnable fore noabort0192FE18 ?SysFiberMain@ProcessManager@@CAXXZ+50192FE44 ?init_boot@fiber@@KAXAAUFiberBootArgs@@@Z+5B0192FE14 ?SysFiberMain@ProcessManager@@CAXXZ 017300F4 runnable fore noabort01B2F698 ?release@ProcessManager@@SAXN@Z+31Dump terminated: exception01B2FE14 _WinMainCRTStartup 017300CC back noabort01A2FE00 ?SysThreadSleep@ProcessManager@@CAXXZ+4601A2FE18 ?SysThreadMain@ProcessManager@@CAXXZ+501A2FE44 ?init_boot@thread@@KAXAAUThreadBootArgs@@@Z+7301A2FE14 ?SysThreadMain@ProcessManager@@CAXXZ@DumpSize: 00000544Dump continues below (2):FATAL ERROR: internal errorD:\V613r1\Z.exe 02/09/2005 14:08:40NanoScope (R) IV 6.13R1Quadrexed MultiMode (7039ev.scn), D:\CAPTURE\Alperen.wksRun 12/12/2010 15:03:20, Running 01:37:16 01730130 running fore noabort0857F1F8 ?DebugTransaction@SysManager@@KAXAAUDebRecord@@PAD@Z+AE0857F230 00BB3AB8Dump terminated: exception0857FE14 ?do_poll@poll@@QAEXXZ 01730054 runnable fore noabort0651FE1C ?CallFunction@@YAXPAX0000K0K@Z+470651FE44 ?init_boot@fiber@@KAXAAUFiberBootArgs@@@Z+5B0651FE14 ?UpdateClock@nanoclock@@QAEXXZ 0173016C runnable fore noabort08EDFD6C ?FastMonitorProcess@FastScan232@@AAEXXZ+2508EDFE44 ?init_boot@fiber@@KAXAAUFiberBootArgs@@@Z+5B08EDFE14 ?FastMonitorProcess@FastScan232@@AAEXXZ 01730090 runnable fore noabort0192FE18 ?SysFiberMain@ProcessManager@@CAXXZ+50192FE44 ?init_boot@fiber@@KAXAAUFiberBootArgs@@@Z+5B0192FE14 ?SysFiberMain@ProcessManager@@CAXXZ 017300F4 runnable fore noabort01B2F698 ?release@ProcessManager@@SAXN@Z+31Dump terminated: exception01B2FE14 _WinMainCRTStartup 017300CC back noabort01A2FE00 ?SysThreadSleep@ProcessManager@@CAXXZ+4601A2FE18 ?SysThreadMain@ProcessManager@@CAXXZ+501A2FE44 ?init_boot@thread@@KAXAAUThreadBootArgs@@@Z+7301A2FE14 ?SysThreadMain@ProcessManager@@CAXXZ@DumpSize: 00000AB4Dump continues below (3):FATAL ERROR: ERROR: in fiber::init_boot. Default exception caught.D:\V613r1\Z.exe 02/09/2005 14:08:40NanoScope (R) IV 6.13R1Quadrexed MultiMode (7039ev.scn), D:\CAPTURE\Alperen.wksRun 12/12/2010 15:03:20, Running 01:38:12 01730130 running fore noabort0857F1F4 ?DebugTransaction@SysManager@@KAXAAUDebRecord@@PAD@Z+AE0857F22C 00BB4638Dump terminated: exception0857FE14 ?do_poll@poll@@QAEXXZ 0173016C runnable fore noabort08EDFD6C ?FastMonitorProcess@FastScan232@@AAEXXZ+2508EDFE44 ?init_boot@fiber@@KAXAAUFiberBootArgs@@@Z+5B08EDFE14 ?FastMonitorProcess@FastScan232@@AAEXXZ 01730090 runnable fore noabort0192FE18 ?SysFiberMain@ProcessManager@@CAXXZ+50192FE44 ?init_boot@fiber@@KAXAAUFiberBootArgs@@@Z+5B0192FE14 ?SysFiberMain@ProcessManager@@CAXXZ 017300F4 runnable fore noabort01B2FAE0 ?OnTimer@CMainFrame@@IAEXI@Z+1201B2FB64 73DD1B9B01B2FB84 73DD1B0501B2FBE4 73DD1A5801B2FC04 73E6847D01B2FC30 77D4873401B2FC5C 77D4881601B2FCC4 77D489CD01B2FD24 77D496C701B2FD34 73DD125A00C2F5B8 0000011300020400 0000000001B2FE14 _WinMainCRTStartup 017300CC back noabort01A2FE00 ?SysThreadSleep@ProcessManager@@CAXXZ+4601A2FE18 ?SysThreadMain@ProcessManager@@CAXXZ+501A2FE44 ?init_boot@thread@@KAXAAUThreadBootArgs@@@Z+7301A2FE14 ?SysThreadMain@ProcessManager@@CAXXZ
Has anyone experienced the same issue? What happens is that while switching from imaging to Force mode or just randomly at times, the system outputs this error and requires me to reopen the software, deleting any unsaved work or acquired data. Seeking solutions to this problem.Thanks!
Hi,
We regularly have the same problems with a MultimodeV when switching from imaging to force spectroscopy.
Guillaume
Alperen,
It's likely one of your PAR files is corrupted. It could be system.par, or other PAR files. Please refer to the following tech support bulletin, to locate the backup PAR files on your hard drive, and replace the current PAR files:
ftp://anonymous@sboftp.veeco.com/outgoing/GPTech/Manuals/NBSB0022_An_Internal_Error_Occured_on_Startup_of_v5_and_v6.pdf
Let me know if that works.
Regards,
Ruizi
AFM Tech Support: 800-873-9750AFMsupport@bruker-nano.com
it's aslo valuable for the v7 ?