Labview 2013 crashing when restarting VI

My VI runs and I have no problems.
If I stop then Vi and re-run it, pretty much every second time it crashes. It does not point to anything and the only message I get is:
Problem signature:
Problem Event Name: APPCRASH
Application Name: LabVIEW.exe
Application Version: 13.0.0.4051
Application Timestamp: 525595c6
Fault Module Name: NiViPxi.dll
Fault Module Version: 5.4.0.49152
Fault Module Timestamp: 51c243ad
Exception Code: c0000005
Exception Offset: 0000bbe0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 6153
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
This only clue in the above I can find is NiViPxi.dll
I am using a PXI rack so maybe it is to do with one of the devices?
I would be nice to have more clues, does anyone know why labVIEW keeps crashing?
Rgds,
Sean
Solved!
Go to Solution.

Hi jinfone.t
I managed to root cause it to a netway 72 PXI dll and have fixed the issue, (took a lot of effort!)
- Does the crash only occur when you re run this particular VI that you are talking about?
Yes
- Is there any crash logs generated?
None that I know of apart from the output I pasted on the screen. It's possible there is something in the event monitor
- What does your VI do?
It function tests our product, (IOT)
- Would it be possible to show the code?
I'm afraid not as it is proprietary. However, the issue appears to be due to the dll. Netway may release the VIs but I believe you are required to buy hardware/ software.
The issue I have is that LabVIEW is not handling this crash well at all. It does not point to the problem dll nor does it drop a fail log that I know of.
Thanks for the feedback.
Ciao,
Sean

Similar Messages

Outlook 2013 crashes when PDFMaker add-in is enabled

Outlook 2013 crashes when the Acrobat v.11.0.3 PDFMaker add-in is enabled. Outlook 2013 will automatically disable the add-in.
The Outlook 2013 version is 15.0.4517.1509, 32 bit. Windows 7 Pro 64 bit is the OS.
Below is the screenshot of the Outlook Account Info page.
Any comments or suggestions would be appreciated.

I was having to start Outlook 2013 two times every time I turned on my computer (running Windows 8.1 64-bit). The first time, Adobe Acrobad crashed Outlook, disabled PDF Maker, and closed. The second time Outlook started, told me it disabled PDF Maker, and gave me the option to re-enable. I then click to re-enable PDF Maker.
However, I tried LoriAUC's suggestion #1, to launch Outlook 2013 as Administrator. When I did that, Outlook just started up without disabling PDF Maker and without crashing. And PDF Maker remained availble to use within Outlook. That's the way it should always work.
So, I remember that Outlook ran fine with PDF Maker until this month of February 2014. I wonder what changed, Outlook or Acrobat Standard Edition so that Outlook crashes (unless running Outlook as Administrator).
In the meantime, I wonder how to make Outlook start as Administrator automatically without my having to do any extra steps. Or is there a better fix.

Labview 8 crashes when saving a vi with a 'Bundle By Name' function

We have a working vi (Get_AN_Fast.vi), created with Labview 7.1.
Trying to open this vi with Labview 8 crashes Labview.
Problem seems to be related to a 'Bundle by Name' function, but it is not that simple as using this function by itself wirks fine.
Any ideas would be a help.
Attachments:
Labview_Upgrade_Crash.zip ‏117 KB

Sorry for the delay, I have been testing on other machines.
We can reproduce the error on other machines, with completly fresh installs of Labview 8.
The ActiveX Object we are connecting to is our own COM server, for interfacing to USB based data acquisition devices.
I have found that when our COM server is not installed on a computer, then the VI will open, but with errors related the the missing COM Server.
When the COM Server is installed, Labview 8 crashes when opening the vi.
I realise that our COM server might have bugs, but it worked fine with Labview 6 and 7, and it is Labview 8 that gives the error, not our COM Server (which is a stand-alone executable).
I have attached a zip file with our COM server, it just needs to be unzipped to a temporary file, and then run the 'register.bat' file to register the server.
It will not install any other files on your computer and, can just be deleted when you are finished.
Thanks
Charlie.
Attachments:
COM_Server.zip ‏659 KB
Labview_Upgrade_Crash.zip ‏117 KB

Sharpoint designer 2013 crashes when Workflow People/Group Selection after adding AAM

I have same issue as mention in this post. Sharpoint
designer 2013 Stopping when Workflow People/Group Selection. SharePoint designer crashing after selecting peopicker in workflow. This is happening after adding AAM url.
And also as answer mentioned My website has same thing. like http://<systemname> as
Default and http:\\mycompany.com as
intranet.
And aslo I opened in website in designer is http://<systemname> .
It used to work before I adding AAM url. Now it is not working.
ItsMeSri SP 2013 Foundation

Hi,
Please check ULS log for more information about error to help narrow down the issue.
If you find error message as "the service '/_vti_bin/spclaimproviderwebservice.svc' cannot be activated due to an exception during compilation, The exception message is: This collection already contains an address with scheme http, There can be
at most one address per scheme in this collection.
http://xblogs.kompas-xnet.si/post/SharePoint-Designer-2013-Crashing-when-using-select-peoplegroups-from-SharePoint-site.aspx
Then the issue might be caused by more than one IIS Site Binding in single web application.
Please firstly remove AAM settings following the steps below:
In IIS manager, remove the added url binding from IIS site for SharePoint web application.
In CA, remove url under AAM settings and execute IISReset. Now you can check if the issue is resolved.
If you need to configure AAM for your web application, please extend web application and set AAM on the extended web application.
Regards,
Rebecca Tu
TechNet Community Support

Outlook 2013 crashes when opening Calendar search result

I have a user who uses her Outlook 2013 calendar extensively, mainly to note for herself when she has spoken to a customer, and creating appointments for when she needs to speak to them again. (This is outside of our policy to note the contact in
MS CRM.) She can have scores of such Calendar items each day.
When seraching for these appointments in her Calendar, she gets the list of results, but Oulook crashes when she tries to open any of them. Sometimes Outlook restarts on its own, sometimes she must relaunch it herself.
Related threads reference a wwlib.dll error, but she is not getting that. It is Outlook.exe itself that is crashing. There are other threads that reference other open windows, or items containing webpages or tables, but these do not apply to her, either.
Event Data (two related entries) contain the following:
OUTLOOK.EXE
15.0.4551.1004
5253ad6f
c0000005
00025b09
19cc
01cef2a610938033
C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
77f5e493-5e9b-11e3-9ef4-00219b4a7172
And:
3915849571
1
APPCRASH
Not available
0
OUTLOOK.EXE
15.0.4511.1004
5253ad6f
OUTLOOK.EXE
15.0.4551.1004
5253ad6f
c0000005
00025b09
C:\Users\[username]\AppData\Local\Temp\163947659.cvr C:\User\[username]\AppData\Local\Temp\CVR780F.tmp.cvr
C:\Users\[username]\AppData\Local\Temp\WERA546.tmp.WERInternalMetadata.xml
C:\Users\[username]\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_OUTLOOK.EXE_2e80497b46642ed3f64262bb26bbba2f6ecc_02d1bdd5
0
77f5e493-5e9b-11e3-9ef4-00219b4a7172
0
On answers.microsoft.com, Girish M (Support Engineer who eventally directed me here), asked me to run Scanpst.exe. I would paste the results here, but this window does not seem to allow pasting. A summary description of what it found on her .ost file (no
.pst in use) is basically this:
**Beginning NDB recovery
**Attempting to open database
**Attempting to validate header
**Attempting to validate AMap
**Attempting to validate BBT
**Attempting to validate NBT
**Attempting to validate BBT refcounts
    ??Couldint find BBT entry in the RBT (E025CC)
**Attempting to validate header NID high-water marks
**Beginning PST/OST recovery
**Attempting to recover all top-level objects
    **Store created by biuld: 15.4517
**Attempting to walk all folders
      Failed to add row to the FLT, RowID = 719
      Failed to add row to the FLT, RowID = 6CD
      Failed to add row to the FLT, RowID = 6DE
      Failed to add row to the FLT, RowID = 6D8
and so on, and so on, with a few hundred more FLT RowID errors, finally ending with:
**Attempting to locate any orphaned folders/messages
**Performing Final HMP validation
**Attempting to check top-level objects for consistency
**Updating folder hierarchy
  **Verifying message moves
My understanding of the Scanpst.exe process is that it also disables any addons which might cause crashing, but the issue is still being experienced. Running Scanpst.exe a second time (appending the previous log, although it seemed to actually prepend the
file) only returned a few lines from the top of the result above ending with "Attempting to validate BBT."
Fixes not attempted yet that I have found performing searches include running the Office Repair tool, or checking for KB2817631 (a Word update that is apparently having adverse affects on Outlook, not attempted yet because it seems to be related to the wwlib.dll
error, which is not happening here).
Any thoughts out there? Thanks!

Mavis,
Thanks for the reply. Running Outlook using /cleansharing and
/cleanroamedprefs did not have any effect when used individually or in combination with each other.
Running the Search Index Rebuild option also did not seem to do anything, as the pop-up message indicated that it may take a long time to finish, and yet seemed to finish instantaneously, not giving any indication that the indexing took place. The option
window immediately said "Indexing complete" for 23,755 items.
As to the Outlook Forum, they are the ones who directed me to this forum (you can see the thread on the Answers support page under Office - Office 2013 - Microsoft Office Outlook - Office on Windows 7, under the title "Outlook 2013 restarts when
opening Calendar Search result item" first posted on Dec 11, 2013), as Girish M felt that it might be due to Exchange, and not Outlook. (I have no reports of any of our other users on the same Exchange server having the problem with their Outlook, but
they also do not use it the way this user has been.)
I can repost the issue there, or continue the same thread, if you think the issue lies with them. Was the "Answers" site the improper place to post, perhaps? Should it go in a different thread on Technet instead?
Thanks for your assistance!
Edited to add:
Here are the KBs installed just before or on the date the problem started (12/6/2013):
12/5/2016 (Office updates, all 32-Bit):
Security Update Office 2013 KB2768005
Office 2013 KB2768016
Office 2013 KB2817640
Office 2013 KB2827228
Security Office 2013 KB2837618
Word 2013 KB2817631
InfoPath 2013 KB2752078
Office 2013 KB2817493
Office 2013 KB2760539
Office 2013 KB2827235
Office 2013 KB2827225
Security Excel 2013 KB2827238
Office 2013 KB2760242
Office 2013 KB2817626
Office 2013 KB2817314
Office 2013 KB2760610
Access 2013 KB2768008
Office 2013 KB2738038
SkyDrive Pro KB2825633
Security Office 2013 KB2817623
Office 2013 KB2760267
Visio Viewer 2013 KB2768338
Office 2013 KB2827230
OneNote 2013 KB2810016
Office 2013 KB2827228
Office 2013 KB2767845
Definition Office 2013 KB2760587
Office 2013 KB2726996
Security Office 2013 KB2810009
Office 2013 KB2817316
Word 2013 KB2817631
Lync 2013 KB2817621
Office 2013 KB2760224
Office 2013 KB2726954
Office 2013 KB2817640
Publisher 2013 KB2752097
PowerPoint 2013 KB2817625
Office 2013 KB2760257
Office 2013 KB2817309
Security Outlook 2013 KB2837618
Visio 2013 KB2752018
Office 2013 KB2817490
Word 2013 KB2827218
Office 2013 KB2760553
12/6/2013 (for Windows, all Security):
KB2900986
KB2888505
KB2876331
KB2868725
KB2868626
KB2862152
I listed all updates because there have been reported instances of a Word update causing Outlook to crash, but she is not getting the wwlib.dll error related to that KB. If you are aware of any issues with these updates, and which ones might be worth uninstalling
in an attempt to fix, please let me know.
Thanks again!

Access 2013 crashed when I export a table from the access

Hi!
Access 2013 always crashed when I export a table from the access to the Database Symfoware.
1、The conditions of the Access 2013 crashed are the follows.
1)Create a table in the Access 2013.
2)Using the ODBC driver of the Database Symfoware to export the table from the access to the Database Symfoware.
2、The Environments are the follows.
1)Access 2013 X64(Version:15.0.4420.1017)
2)Win2008R2 X64
3)Symfoware V11.1 X64
3、The Application log from the Win2008R2 are follows.
ログの名前: Application
ソース: Application Error
日付: 2014/04/18 16:21:06
イベント ID: 1000
タスクのカテゴリ: (100)
レベル: エラー
キーワード: クラシック
ユーザー: N/A
コンピューター: WIN-29UTU2AIK6J
説明:
障害が発生しているアプリケーション名: MSACCESS.EXE、バージョン: 15.0.4420.1017、タイムスタンプ: 0x50674523
障害が発生しているモジュール名: ACECORE.DLL、バージョン: 15.0.4420.1017、タイムスタンプ: 0x506742b7
例外コード: 0xc0000005
障害オフセット: 0x0000000000171f36
障害が発生しているプロセス ID: 0xb6c
障害が発生しているアプリケーションの開始時刻: 0x01cf5ad638668c5b
障害が発生しているアプリケーションパス: C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE
障害が発生しているモジュールパス: C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL
レポート ID: 00e87957-c6ca-11e3-ad2c-0050568d2ced
イベント XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-18T07:21:06.000000000Z" />
<EventRecordID>3442</EventRecordID>
<Channel>Application</Channel>
<Computer>WIN-29UTU2AIK6J</Computer>
<Security />
</System>
<EventData>
<Data>MSACCESS.EXE</Data>
<Data>15.0.4420.1017</Data>
<Data>50674523</Data>
<Data>ACECORE.DLL</Data>
<Data>15.0.4420.1017</Data>
<Data>506742b7</Data>
<Data>c0000005</Data>
<Data>0000000000171f36</Data>
<Data>b6c</Data>
<Data>01cf5ad638668c5b</Data>
<Data>C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE</Data>
<Data>C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL</Data>
<Data>00e87957-c6ca-11e3-ad2c-0050568d2ced</Data>
</EventData>
</Event>
4、When the access crashed,I got the dump file .Then I use the Windbg got some information from the dump files.
The detailes are follows.
FAULTING_IP:
+58872faf03d6dd84
00000000`00000000 ?? ???
EXCEPTION_RECORD: 00000000001723c0 -- (.exr 0x1723c0)
ExceptionAddress: 000007fee3951f36 (ACECORE+0x0000000000171f36)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
FAULTING_THREAD: 00000000000010b8
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
PROCESS_NAME: MSACCESS.EXE
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ACECORE
FAULTING_MODULE: 0000000076eb0000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 506742b7
ERROR_CODE: (NTSTATUS) 0x80000003 - {
EXCEPTION_CODE: (NTSTATUS) 0x80000003 (2147483651) - {
MOD_LIST: <ANALYSIS/>
CONTEXT: 0000000000171ed0 -- (.cxr 0x171ed0)
rax=0000000001be3598 rbx=0000000000000000 rcx=01cf5d1b0f402a5c
rdx=0000000009cfad30 rsi=0000000006688ef0 rdi=0000000001be35d0
rip=000007fee3951f36 rsp=0000000000172490 rbp=00000000001727a0
r8=0000000009b409d0 r9=0000000006688ef0 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000001be19f0
r14=0000000009cfad30 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
ACECORE+0x171f36:
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12 ds:00000000`00000000=????????????????
Resetting default scope
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 000007fee395c095 to 000007fee3951f36
STACK_TEXT:
00000000`00172490 000007fe`e395c095 : ffffffff`ffffffff 00000000`00000000 00000000`01bddaa2 ffffffff`ffffffff : ACECORE+0x171f36
00000000`001727b0 000007fe`e388f8eb : 000007fe`e399dc10 000007fe`e399dc30 000007fe`e399dc50 00000000`000000f9 : ACECORE+0x17c095
00000000`00172b50 000007fe`e388f590 : 00000000`06688ef0 00000000`00000004 00000000`000000f9 00000000`00000000 : ACECORE+0xaf8eb
00000000`00172ba0 000007fe`e388f406 : 00000000`00000004 00000000`000000f9 00000000`11cb1130 00000000`000000f9 : ACECORE+0xaf590
00000000`00172c30 000007fe`e391aee7 : 00000000`00000000 00000000`00173198 00000000`06688ef0 00000000`11cb0998 : ACECORE+0xaf406
00000000`00172c70 000007fe`e3933a72 : 00000000`00400100 00000000`00000002 00000000`00000001 00000000`06688ef0 : ACECORE+0x13aee7
00000000`00172e50 000007fe`e384e5b1 : 00000000`00000000 00000000`11cb0020 00000000`06688ef0 00000000`00000001 : ACECORE+0x153a72
00000000`00172e90 000007fe`e38358d1 : 00000000`000007ff 00000000`06688ef0 00000000`01bd99f0 00000000`00000000 : ACECORE+0x6e5b1
00000000`00173280 000007fe`e38718eb : 00000000`000007ff 00000000`06688ef0 00000000`11cb0000 00000000`00000000 : ACECORE+0x558d1
00000000`00173340 00000001`3f3b0cd2 : 00000000`0a0945c0 00000000`000000fe 00000000`000007ff 00000000`00000000 : ACECORE+0x918eb
00000000`00173430 00000001`3f3b0b9b : 00000000`00173730 00000000`001741e0 00000000`065e5b00 00000000`00000100 : MSACCESS!CreateIExprSrvObj+0x16af32
00000000`00173630 00000001`3f3afcea : 00000000`00173730 00000000`00000000 00000000`00000000 00000000`065e5b00 : MSACCESS!CreateIExprSrvObj+0x16adfb
00000000`001736a0 00000001`3f983140 : 00000000`00174401 00000000`0a3235e0 00000000`0a319aa0 00000000`00179fc8 : MSACCESS!CreateIExprSrvObj+0x169f4a
00000000`00174290 00000001`3f3aabeb : 00000000`00000000 00000000`00000000 00000000`00179f38 00000000`00000000 : MSACCESS!FUniqueIndexTableFieldEx+0x26ab4
00000000`00174530 00000001`3f3a9670 : 00000000`001778e0 00000000`00179f38 00000000`00000031 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x164e4b
00000000`00177870 00000001`3f3a8c1b : 00000000`00000010 00000000`108c5990 003d0044`00570050 00000000`74ac3f69 : MSACCESS!CreateIExprSrvObj+0x1638d0
00000000`001779d0 00000001`3f5450df : 00000000`0a0945c0 00000000`0000009c 00000000`0a0945c0 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x162e7b
00000000`00179e30 00000001`3f64e915 : 00000000`43ed8000 00000000`00000000 00000000`3f800000 00000000`00000000 : MSACCESS!FillADT+0x5830b
00000000`0017c450 00000001`3f33b172 : 00000000`00000000 00000000`0006075e 00000000`0017e370 00000000`00000000 : MSACCESS!IdsComboFillOfActidIarg+0xaddf1
00000000`0017d730 00000001`3f33a9ef : 00000000`0017e0a0 00000000`00000b86 00000000`00000000 00000000`0fea0000 : MSACCESS!CreateIExprSrvObj+0xf53d2
00000000`0017d790 00000001`3f33a20c : 00000000`06620400 00000000`00000000 00000000`00000001 00000000`0017e420 : MSACCESS!CreateIExprSrvObj+0xf4c4f
00000000`0017e400 00000001`3f6019cd : 0071023b`007a000a 00000000`00374a30 00000000`00000005 00000000`0000000c : MSACCESS!CreateIExprSrvObj+0xf446c
00000000`0017e850 00000000`06706fd5 : e2504700`aa00ee81 00005d1b`0f2363ea 00000000`0017e9e0 00000001`3f200000 : MSACCESS!IdsComboFillOfActidIarg+0x60ea9
00000000`0017e8f0 00000000`0a30c378 : 00000000`00000000 00000000`00000008 00000000`067069ac 00000000`00000000 : 0x6706fd5
00000000`0017e960 00000000`00000000 : 00000000`00000008 00000000`067069ac 00000000`00000000 00000000`00000008 : 0xa30c378
FOLLOWUP_IP:
ACECORE+171f36
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ACECORE+171f36
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ACECORE.DLL
STACK_COMMAND: .cxr 0x171ed0 ; kb
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_80000003_ACECORE.DLL!Unknown
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/MSACCESS_EXE/15_0_4420_1017/50674523/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1
Followup: MachineOwner
5、Where the access crashed I used the ODBC trace to get the trace log of the ODBC API.
The ODBC API called by Access before it crashed are the follows.
I also ansysised the log,and I did not find any Abnormal.
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
6
SWORD
-8 <SQL_C_WCHAR>
PTR 0x00000000002C1F20 [
12] "LENGTH"
SQLLEN 62
SQLLEN * 0x00000000002C1E38 (12)
Test 1174-10f0
ENTER SQLGetData
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38 (-1)
Test 1174-10f0
ENTER SQLFetch
HSTMT 0x0000000009F7C490
Test 1174-10f0
EXIT SQLFetch with return code 100 (SQL_NO_DATA_FOUND)
HSTMT 0x0000000009F7C490
Test 1174-10f0
ENTER SQLFreeStmt
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
Test 1174-10f0
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
6、I also did the test with the Access 2010,and with the Sql Srever/Oracle.
The results are the follows.
1) With the Access 2010(X86 or X64) and Access 2013 X86,it successes when I export the table to the DB Symfoware.But only with the Access 2013 X64,the Access crashed.
2)With the Access 2010(X86 or X64) and Access 2013(X86 or X64),using the Sql Srever/Oracle,it always successes .
According to all the descrived above, I wonder if it a bug of the Access2013 .
Could anyone can help me ?
Thanks for any help.

George Zhao
Thank you for your help.
I have already install
the latest patches of the Office 2013.But it doesn't work.It is down also too. And ODBC
drive of Database Symfoware is the newest driver of the Database Symfoware. Now I wonder that
if it si a bug of the ODBC
drive of Database Symfoware,I should fix the bug,but I have analysised the odbc trace log and I do not find any wrongs ,so I think maybe it is a bug of the Access .
I have see many situations about the Access down on the internet .

LabVIEW is crashing when i am trying to build the exe

I am trying to build an executable from a program in which i am communicating with several instruments, whenever i am trying to build an exe labview is crashing and i am getting the error Exception: access violation(0xc0000005)at eip=0x10054DD1.
after reading some posts on forum i tried builduing an exe on other system also, but still i am getting the same error.
below i am attaching the program and the image of the error i am getting.
Attachments:
labview crash.png ‏53 KB
automation.zip ‏4455 KB

Ritu wrote:
waiting for the reply....
Realize this community is by a large majority volunteer based. If you need urgent support contact NI directly
http://sine.ni.com/apps/utf8/nicc.call_me?loc=en-US
That being said I would try to disable the large amount of code. Say you have a Main that launches a bunch of stuff, put a disabled diagram code around the launching part and then try to rebuild. It is a very slow process (especially when the build takes a while to fail) but by doing this you can more isolate the parts of the code that can cause the crash. The only time I've seen a crash on build like you described, I simply rebooted and it was fine. Usually because of my own fault by stopping code in a bad way previously leaving things in memory.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Excel 2013 crashes when creating VFP OLE DB Data connection

Hi all,
I don't know how often the DBF format is used in Office but it seems some demand still exists because Microsoft created 64 bit version of dBase ODBC and OLE DB driver (in Access data engine). Then I don't understand why Microsoft ignores its own FoxPro
DBF data format because FoxPro ODBC driver is not supported already and no 64 bit version of VFP OLE DB driver is planned...
I am testing DBF file import to Excel 2013 (32 bit) but it crashes instantly. I have VFP OLE DB driver (the last version), some small DBF file, and I am trying to read it as external data in Excel.
Steps to reproduce (menu prompts are translated, so some differences may occur):
Open empty worksheet
Click "Other data sources" on Data ribbon
Select Data Connection Wizard and from the list of available drivers select "Other" and click "Next"
A list of OLE DB providers installed appears, select Microsoft OLE DB Provider for Visual FoxPro and click "Next >>"
Excel 2013 crashes...
This process works in Excel 2010 and 2007 so the problem must be in Excel 2013...
The question is how to read DBF data in FoxPro format when there is no older Office version available?

To connect to a Visual FoxPro database or table in Excel
Open an Excel worksheet.
From the Data menu, point to Import External Data, and click
Import Data.
In the Select Data Source dialog box, click New Source Data Connection.
In the Data Connection Wizard, select Other/Advanced.
In the Provider tab, select Microsoft OLE DB Provider for Visual FoxPro.
The Connection tab in the Data Link Properties dialog box appears.
To connect to a Visual FoxPro database or table in Word
Open a Word document.
From the View menu, point to Toolbars, and click
Database.
On the Database toolbar, click the Insert Database icon.
In the Database dialog box, click Get Data.
In the Select Data Source dialog box, click New Source Data Connection.
In the Data Connection Wizard, select Other/Advanced.
In the Provider tab, select Microsoft OLE DB Provider for Visual FoxPro.
The Connection tab in the Data Link Properties dialog box appears.
To add a Visual FoxPro database or table folder
On the Connection tab and in the Select or enter a database name box, type path and name of the database or table folder you want.
-or-
To browse for a Visual FoxPro database or table folder, click the ellipsis (...) button to the right of the
Select or enter a database name box to open the Configure Connection dialog box.
Specify a different collating sequence if desired.
To test the connection, click Test Connection. If connection is successful, click
OK.

T440P [20AN] - Lync 2013 Crashing When Sharing Desktop - Intel Driver

Hello,
After updating to the latest video drivers from the ThinkVantage Update Retriever, our Lync clients crash when sharing desktop on our T440P series and X240 series. I noticed when I uninstall the video driver I am able to screen share without incident. Also, if I update the driver from Windows Update I am able to share successfully. We use the update retriever and thininstaller to install our drivers in our environment. I have tried uninstalling the Lync updates all the way down to the base version and experience the same issue at every level. It crashes 100% of the time when sharing desktop. I have tested it on T440p machines in our environment that do not have the latest display driver, and no crashes occurred. Here are the specifics:
Thinkpad X240 [20AL]
Thinkpad T440p [20AN]
ThinkVantage Update Retriever 5.00.0007
Thinkvantage Thin Installer 1.2.0010
Intel HD Graphics Driver - gid634ww (10.18.10.3412)
Microsoft Lync 2013 SP1 32 Bit (15.0.4569.1503)
Error Message from Application Log:
Faulting application name: lync.exe, version: 15.0.4569.1503, time stamp: 0x52b0af33
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x00000879
Fault offset: 0x0000c42d
Faulting process id: 0x220c
Faulting application start time: 0x01cf707ca316ae96
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: C:\WINDOWS\syswow64\KERNELBASE.dll
Report Id: 9bb7c6e4-dc70-11e3-b695-5c514fb23d46
Any help or insight is greatly appreciated.
Thank you,
John
Solved!
Go to Solution.

Just as an updated to this:
I'm still waiting on updated drivers to fix the issue, however, there is a workaround. If you disable Desktop Composition screen sharing will work.
Control Panel -> Performance and Information Tools -> Adjust Visual Effects -> Uncheck “Enable desktop composition
John

Labview 7 crashes when opening an earlier Labview version VI

Hello guys. I am using Labview 7 professional edition. The labview crashes when opening an earlier labview version VI. The error message I'm getting is just "Labview has encounted a problem and eneds to close. We are sorry for the inconvenience." The VI contains a few Tag SubVIs, and It is written with an earlier version of Labview(BridgeView is what it was called).
Do anyone have any ideas that how I can fix this bug? It's going to be a great help. Thank you very much.

Hello,
LabVIEW should not be crashing in this situation. Now, does this happen for other similar VIs too? It could be possible that a particular VI is corrupt. Also could you post your VI here so that I can try and reproduce the problem at my end.
Regards,
Chetan K
Application Engineering
National Instruments

Outlook 2013 crashes when clicking calendar icon to get to the calendar

When clicking the calendar icon, Oulook 2013 crashes and leaves this event:
Faulting application name: OUTLOOK.EXE, version: 15.0.4551.1004, time stamp: 0x5253ab76
Faulting module name: OUTLOOK.EXE, version: 15.0.4551.1004, time stamp: 0x5253ab76
Exception code: 0xc0000005
Fault offset: 0x00025b09
Faulting process id: 0x2668
Faulting application start time: 0x01cef1ede0ad9dd8
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
Faulting module path: C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
Report Id: 25f2f8e0-5de1-11e3-aa96-b8ca3a76ef90
Faulting module is OUTLOOK.exe so I don't know what to look for. I have done the following:
Ran outlook in safe mode
Ran outlook without addons
Created a new mail profile
Repaired Office 2013, also uninstalled and reinstalled Office 2013
Cleared temp files
I am not sure why this is crashing and I don't see any hints in the event viewer logs or in the error report that was created. It just says that Oulook crashed but has no indication. What can I look for in these logs to find a culprit?
Version=1
EventType=APPCRASH
EventTime=130307499751212652
ReportType=2
Consent=1
UploadTime=130307499751836680
ReportIdentifier=47e54e86-5dee-11e3-8617-b8ca3a76ef90
IntegratorReportIdentifier=47e54e85-5dee-11e3-8617-b8ca3a76ef90
WOW64=1
Response.BucketId=3941454205
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=OUTLOOK.EXE
Sig[1].Name=Application Version
Sig[1].Value=15.0.4551.1004
Sig[2].Name=Application Timestamp
Sig[2].Value=5253ab76
Sig[3].Name=Fault Module Name
Sig[3].Value=OUTLOOK.EXE
Sig[4].Name=Fault Module Version
Sig[4].Value=15.0.4551.1004
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5253ab76
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00025b09
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
UI[3]=Microsoft Outlook has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Program Files\Microsoft Office 15\root\office15\AppVIsvSubsystems32.dll
LoadedModule[5]=C:\Program Files\Microsoft Office 15\root\office15\AppVIsvStream32.dll
LoadedModule[6]=C:\Program Files\Microsoft Office 15\root\office15\c2r32.dll
LoadedModule[7]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[10]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[11]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[12]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[13]=C:\Windows\syswow64\ole32.dll
LoadedModule[14]=C:\Windows\syswow64\GDI32.dll
LoadedModule[15]=C:\Windows\syswow64\USER32.dll
LoadedModule[16]=C:\Windows\syswow64\LPK.dll
LoadedModule[17]=C:\Windows\syswow64\USP10.dll
LoadedModule[18]=C:\Windows\system32\USERENV.dll
LoadedModule[19]=C:\Windows\system32\profapi.dll
LoadedModule[20]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[21]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[22]=C:\Program Files\Microsoft Office 15\root\office15\MSVCR100.dll
LoadedModule[23]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[24]=C:\Program Files\Microsoft Office 15\root\office15\MSVCP100.dll
LoadedModule[25]=C:\Windows\system32\IMM32.DLL
LoadedModule[26]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[27]=C:\Windows\syswow64\oleaut32.dll
LoadedModule[28]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
LoadedModule[29]=C:\Windows\system32\MSIMG32.dll
LoadedModule[30]=C:\Windows\system32\uxtheme.dll
LoadedModule[31]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\Comctl32.dll
LoadedModule[32]=C:\Windows\system32\dwmapi.dll
LoadedModule[33]=C:\Windows\system32\d2d1.dll
LoadedModule[34]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[35]=C:\Windows\system32\WINSTA.dll
LoadedModule[36]=C:\Windows\system32\dxgi.dll
LoadedModule[37]=C:\Windows\system32\VERSION.dll
LoadedModule[38]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[39]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[40]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[41]=C:\Program Files\Microsoft Office 15\Root\Office15\olmapi32.dll
LoadedModule[42]=C:\Windows\system32\msi.dll
LoadedModule[43]=C:\Program Files\Microsoft Office 15\root\office15\1033\OUTLLIBR.DLL
LoadedModule[44]=C:\Windows\system32\mscoree.dll
LoadedModule[45]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[46]=C:\Windows\system32\DavClnt.DLL
LoadedModule[47]=C:\Windows\system32\DAVHLPR.dll
LoadedModule[48]=C:\Program Files (x86)\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\osppc.dll
LoadedModule[49]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\riched20.dll
LoadedModule[50]=C:\Program Files\Microsoft Office 15\Root\Office15\1033\mapir.dll
LoadedModule[51]=C:\Windows\system32\ntmarta.dll
LoadedModule[52]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[53]=C:\Windows\syswow64\urlmon.dll
LoadedModule[54]=C:\Windows\syswow64\iertutil.dll
LoadedModule[55]=C:\Windows\syswow64\WININET.dll
LoadedModule[56]=C:\Windows\syswow64\Normaliz.dll
LoadedModule[57]=C:\Windows\system32\DWrite.dll
LoadedModule[58]=C:\Windows\system32\d3d10_1.dll
LoadedModule[59]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[60]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[61]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[62]=C:\Windows\system32\d3d11.dll
LoadedModule[63]=C:\Windows\system32\igd10umd32.dll
LoadedModule[64]=C:\Program Files\Microsoft Office 15\root\office15\wwlib.dll
LoadedModule[65]=C:\Program Files\Microsoft Office 15\root\office15\oart.dll
LoadedModule[66]=C:\Program Files\Microsoft Office 15\Root\Office15\contab32.dll
LoadedModule[67]=C:\Program Files\Microsoft Office 15\Root\Office15\EMSMDB32.DLL
LoadedModule[68]=C:\Windows\system32\WSOCK32.dll
LoadedModule[69]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[70]=C:\Windows\syswow64\NSI.dll
LoadedModule[71]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[72]=C:\Windows\System32\netprofm.dll
LoadedModule[73]=C:\Windows\System32\nlaapi.dll
LoadedModule[74]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[75]=C:\Windows\system32\rsaenh.dll
LoadedModule[76]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[77]=C:\Windows\System32\npmproxy.dll
LoadedModule[78]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[79]=C:\Windows\system32\WINNSI.DLL
LoadedModule[80]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[81]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[82]=C:\Windows\SysWOW64\SFC.DLL
LoadedModule[83]=C:\Windows\system32\sfc_os.DLL
LoadedModule[84]=C:\Program Files\Microsoft Office 15\Root\Office15\MSPST32.DLL
LoadedModule[85]=C:\Windows\system32\mssprxy.dll
LoadedModule[86]=C:\Windows\system32\mswsock.dll
LoadedModule[87]=C:\Windows\System32\wshtcpip.dll
LoadedModule[88]=C:\Windows\System32\wship6.dll
LoadedModule[89]=C:\Windows\system32\DNSAPI.dll
LoadedModule[90]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[91]=C:\Windows\system32\rasadhlp.dll
LoadedModule[92]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[93]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[94]=C:\Windows\system32\secur32.dll
LoadedModule[95]=C:\Windows\system32\credssp.dll
LoadedModule[96]=C:\Windows\SysWOW64\Kerberos.DLL
LoadedModule[97]=C:\Windows\system32\cryptdll.dll
LoadedModule[98]=C:\Windows\system32\bcrypt.dll
LoadedModule[99]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[100]=C:\Windows\system32\mlang.dll
LoadedModule[101]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\MSPTLS.DLL
LoadedModule[102]=C:\Windows\system32\explorerframe.dll
LoadedModule[103]=C:\Windows\system32\DUser.dll
LoadedModule[104]=C:\Windows\system32\DUI70.dll
LoadedModule[105]=C:\Windows\SysWOW64\actxprxy.dll
LoadedModule[106]=C:\Program Files\Microsoft Office 15\Root\Office15\ADDINS\ColleagueImport.dll
LoadedModule[107]=C:\Windows\system32\NETAPI32.dll
LoadedModule[108]=C:\Windows\system32\netutils.dll
LoadedModule[109]=C:\Windows\system32\srvcli.dll
LoadedModule[110]=C:\Windows\system32\wkscli.dll
LoadedModule[111]=C:\Program Files\Microsoft Office 15\Root\Office15\ONBttnOL.dll
LoadedModule[112]=C:\Program Files\Microsoft Office 15\Root\Office15\SOCIALCONNECTOR.DLL
LoadedModule[113]=C:\Program Files\Microsoft Office 15\Root\Office15\mfc100u.dll
LoadedModule[114]=C:\Program Files\Microsoft Office 15\Root\Office15\ADDINS\UmOutlookAddin.dll
LoadedModule[115]=C:\Windows\system32\MAPI32.dll
LoadedModule[116]=C:\Windows\system32\OLEACC.dll
LoadedModule[117]=C:\Program Files\Microsoft Office 15\root\office15\1033\UmOutlookStrings.dll
LoadedModule[118]=C:\Program Files\Microsoft Office 15\Root\Office15\FACEBOOKPROVIDER.DLL
LoadedModule[119]=C:\Program Files\Microsoft Office 15\Root\Office15\LINKEDINPROVIDER.DLL
LoadedModule[120]=C:\Windows\System32\msxml6.dll
LoadedModule[121]=C:\Windows\system32\UIAutomationCore.DLL
LoadedModule[122]=C:\Program Files\Microsoft Office 15\Root\Office15\SHAREPOINTPROVIDER.DLL
LoadedModule[123]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[124]=C:\Windows\system32\RASAPI32.dll
LoadedModule[125]=C:\Windows\system32\rasman.dll
LoadedModule[126]=C:\Windows\system32\rtutils.dll
LoadedModule[127]=C:\Windows\system32\sensapi.dll
LoadedModule[128]=C:\Windows\system32\SXS.DLL
LoadedModule[129]=C:\Windows\SysWOW64\schannel.dll
LoadedModule[130]=C:\Windows\system32\ncrypt.dll
LoadedModule[131]=C:\Windows\system32\GPAPI.dll
LoadedModule[132]=C:\Windows\system32\cryptnet.dll
LoadedModule[133]=C:\Program Files\Microsoft Office 15\Root\Office15\outlph.dll
LoadedModule[134]=C:\Windows\system32\tquery.dll
LoadedModule[135]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[136]=C:\Windows\system32\WINMM.dll
LoadedModule[137]=C:\Windows\system32\MMDevAPI.DLL
LoadedModule[138]=C:\Windows\system32\PROPSYS.dll
LoadedModule[139]=C:\Windows\system32\wdmaud.drv
LoadedModule[140]=C:\Windows\system32\ksuser.dll
LoadedModule[141]=C:\Windows\system32\AVRT.dll
LoadedModule[142]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[143]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[144]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[145]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[146]=C:\Windows\system32\msacm32.drv
LoadedModule[147]=C:\Windows\system32\MSACM32.dll
LoadedModule[148]=C:\Windows\system32\midimap.dll
LoadedModule[149]=C:\Windows\system32\msadp32.acm
LoadedModule[150]=C:\Windows\system32\apphelp.dll
Sec[0].Key=LCID
Sec[0].Value=1033
Sec[1].Key=skulcid
Sec[1].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Outlook
AppPath=C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE

Hello,
Did you try to create a new mail profile without exchange account?
Besides, I recommend you use CalCheck to check Outlook Calendars for problems.
And then you can delete corrupt calendar item or use Calendar Repair Assistant to repair the corrupt calendar item.
Here is the blog for your reference.
http://blogs.msdn.com/b/webdav_101/archive/2012/02/28/how-to-check-for-calendar-corruption.aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Imac late 2013 crashes and restarts.

hello
I received my new imac there 2 days and it is completely unstable.
it crashes and restarts.
I tried with 16GB and 8GB with original but nothing changes.
have this kind of problems?
thanks
configuration:
IMac 27 "late 2013
Processor: 3.5 Ghz
crucial memory 32 GB
Fri Nov 8 12:46:00 2013
panic(cpu 0 caller 0xffffff8003edc19e): Kernel trap at 0xffffff83946ebcc0, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff83946ebcc0, CR3: 0x0000000006ad6000, CR4: 0x00000000001606e0
RAX: 0x0000000000000000, RBX: 0xffffff80441f49a8, RCX: 0x0000000000042933, RDX: 0xffffff80441d1370
RSP: 0xffffff83946ebca8, RBP: 0xffffff80442021a8, RSI: 0xffffff80441d1008, RDI: 0xffffff804415a008
R8: 0x00000000000057e8, R9: 0xffffff83946ebc3c, R10: 0xffffff83946ebe20, R11: 0xffffff7f84bda516
R12: 0xffffff83946ebd1c, R13: 0xffffff80441f49a8, R14: 0xffffff83946ebd14, R15: 0xffffff80441d1008
RFL: 0x0000000000010292, RIP: 0xffffff83946ebcc0, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff83946ebcc0, Error code: 0x0000000000000011, Fault CPU: 0x0 Kernel NX fault
Backtrace (CPU 0), Frame : Return Address
0xffffff83946eb930 : 0xffffff8003e22f69
0xffffff83946eb9b0 : 0xffffff8003edc19e
0xffffff83946ebb80 : 0xffffff8003ef3606
0xffffff83946ebba0 : 0xffffff83946ebcc0
0xffffff80442021a8 : 0x8000000
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0x100000000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
13A603
Kernel version:
Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
Kernel slide:     0x0000000003c00000
Kernel text base: 0xffffff8003e00000
System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)
System uptime in nanoseconds: 25623295729719
last loaded kext at 19452793773068: com.apple.filesystems.afpfs          11.0 (addr 0xffffff7f8644e000, size 348160)
last unloaded kext at 14467405141563: com.apple.driver.AppleUSBCDC          4.2.1b2 (addr 0xffffff7f86430000, size 16384)
loaded kexts:
at.obdev.nke.LittleSnitch          4052
com.apple.filesystems.afpfs          11.0
com.apple.nke.asp-tcp          8.0.0
com.apple.driver.AppleBluetoothMultitouch          80.14
com.apple.driver.AudioAUUC          1.60
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.filesystems.autofs          3.0
com.apple.iokit.IOBluetoothSerialManager          4.2.0f6
com.apple.driver.AppleMikeyHIDDriver          124
com.apple.driver.AGPM          100.14.11
com.apple.driver.ApplePlatformEnabler          2.0.9d1
com.apple.driver.X86PlatformShim          1.0.0
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.driver.AppleHDA          2.5.2fc2
com.apple.driver.AppleUSBDisplays          360.8.14
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.2.0f6
com.apple.driver.AppleMikeyDriver          2.5.2fc2
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AppleLPC          1.7.0
com.apple.driver.AppleSMCLMU          2.0.4d1
com.apple.driver.AppleHWAccess          1
com.apple.driver.AppleThunderboltIP          1.0.10
com.apple.GeForce          8.1.8
com.apple.driver.AppleUpstreamUserClient          3.5.13
com.apple.driver.AppleIntelHD5000Graphics          8.1.8
com.apple.driver.AppleIntelFramebufferAzul          8.1.8
com.apple.driver.AppleBacklight          170.3.5
com.apple.driver.AppleMCCSControl          1.1.12
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          35
com.apple.driver.AppleUSBHub          650.4.4
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.4.0
com.apple.driver.AppleSDXC          1.4.0
com.apple.iokit.AppleBCM5701Ethernet          3.6.9b9
com.apple.driver.AirPort.Brcm4360          800.21.45
com.apple.driver.AppleAHCIPort          2.9.5
com.apple.driver.AppleUSBXHCI          650.4.3
com.apple.driver.AppleRTC          2.0
com.apple.driver.AppleACPIButtons          2.0
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          2.0
com.apple.driver.AppleACPIEC          2.0
com.apple.driver.AppleAPIC          1.7
com.apple.nke.applicationfirewall          153
com.apple.security.quarantine          3
com.apple.security.SecureRemotePassword          1.0
com.apple.driver.IOBluetoothHIDDriver          4.2.0f6
com.apple.driver.AppleMultitouchDriver          245.13
com.apple.kext.triggers          1.0
com.apple.iokit.IOSerialFamily          10.0.7
com.apple.driver.DspFuncLib          2.5.2fc2
com.apple.vecLib.kext          1.0.0
com.apple.iokit.IOBluetoothFamily          4.2.0f6
com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.0f6
com.apple.driver.AppleUSBAudio          2.9.3f17
com.apple.iokit.IOAudioFamily          1.9.4fc11
com.apple.kext.OSvKernDSPLib          1.14
com.apple.driver.X86PlatformPlugin          1.0.0
com.apple.driver.IOPlatformPluginFamily          5.5.1d27
com.apple.driver.AppleHDAController          2.5.2fc2
com.apple.iokit.IOHDAFamily          2.5.2fc2
com.apple.driver.AppleSMC          3.1.6d1
com.apple.driver.AppleThunderboltEDMSink          1.2.1
com.apple.iokit.IOAcceleratorFamily          98.7.1
com.apple.driver.AppleSMBusPCI          1.0.12d1
com.apple.nvidia.driver.NVDAGK100Hal          8.1.8
com.apple.nvidia.driver.NVDAResman          8.1.8
com.apple.iokit.IOSurface          91
com.apple.iokit.IOAcceleratorFamily2          98.7.1
com.apple.AppleGraphicsDeviceControl          3.4.12
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.iokit.IONDRVSupport          2.3.6
com.apple.driver.AppleSMBusController          1.0.11d1
com.apple.iokit.IOGraphicsFamily          2.3.6
com.apple.driver.AppleUSBHIDKeyboard          170.15
com.apple.driver.AppleHIDKeyboard          170.15
com.apple.iokit.IOUSBHIDDriver          650.4.4
com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.0
com.apple.driver.AppleThunderboltDPOutAdapter          2.5.0
com.apple.driver.AppleThunderboltDPInAdapter          2.5.0
com.apple.driver.AppleThunderboltDPAdapterFamily          2.5.0
com.apple.driver.AppleThunderboltPCIDownAdapter          1.4.0
com.apple.driver.AppleUSBMergeNub          650.4.0
com.apple.driver.AppleUSBComposite          650.4.0
com.apple.driver.CoreStorage          380
com.apple.iokit.IOUSBUserClient          650.4.4
com.apple.driver.AppleThunderboltNHI          1.9.2
com.apple.iokit.IOThunderboltFamily          2.8.5
com.apple.iokit.IOEthernetAVBController          1.0.3b3
com.apple.iokit.IO80211Family          600.34
com.apple.driver.mDNSOffloadUserClient          1.0.1b4
com.apple.iokit.IONetworkingFamily          3.2
com.apple.iokit.IOAHCIFamily          2.6.0
com.apple.iokit.IOUSBFamily          650.4.4
com.apple.driver.AppleEFINVRAM          2.0
com.apple.driver.AppleEFIRuntime          2.0
com.apple.iokit.IOHIDFamily          2.0.0
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          278.10
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.AppleKeyStore          2
com.apple.driver.DiskImages          371.1
com.apple.iokit.IOStorageFamily          1.9
com.apple.iokit.IOReportFamily          21
com.apple.driver.AppleFDEKeyStore          28.30
com.apple.driver.AppleACPIPlatform          2.0
com.apple.iokit.IOPCIFamily          2.8
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0
com.apple.kec.pthread          1

Looks like this is a hardware issue.
No word yet if it's Apple or Crucial's fault.
http://forum.crucial.com/t5/Apple-Mac-Memory/Late-2013-iMac-randomly-restarts-it self-once-a-day/td-p/136875/highlight/false/page/4

Word 2013 crashes when doing a save as pdf

Word 2013 will crash when doing a 'save as' pdf

It sounds like an item in HD/Library/Contextual Menu Items. Drag the contents of that folder to the desktop and test again. If that sorts it put the items back one at a time to find the culprit..
If that's not it, go to ~(yourHome)/Library/Contextual Menu Items and do the same.
Open "Console" in your Utilities folder. From the Sidebar choose: Log
Files >> CrashReporter >> "~/ Library Logs" >> Preview and paste the contents here for the latest Preview crash and maybe we can figure what's going on.
-mj
[email protected]

Scehudling assistant causes Outlook 2013 crash when creating meeting with external attendee

Good morning
I have a very annoying problem with Outlook 2013 that occurs when a user attempts to create a meeting, inviting and external attendee and uses the Scheduling Assistant to help them organise timings. We are running Exchange 2013 CU3 with no other versions
of Exchange in our environment.
Everything works fine until the user attempts to use the Scheduling assistant, as soon as they do, Outlook promptly crashes. Using OWA, things seem to work as expected.
This is the error logged in event viewer:
Event ID: 1000
Faulting application name: OUTLOOK.EXE, version: 15.0.4569.1503, time stamp: 0x52b0b282
Faulting module name: mso.dll, version: 15.0.4605.1000, time stamp: 0x531f9fba
Exception code: 0xc0000409
Fault offset: 0x00009408
Faulting process id: 0x1320
Faulting application start time: 0x01cf6453441df03b
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
Report Id: 62895ac5-d04a-11e3-8285-7071bc433f94
Faulting package full name:
Faulting package-relative application ID:
Has anyone experienced this before and if so can you help me fix it please? Is this a bug with Outlook or Exchange? I am going to test the same scenario on a machine running Outlook 2010 to see if the same issue still persists.

Open Outlook with /safe command (Or hold Ctrl key when open Outlook) starts Outlook without the Reading Pane or toolbar customizations. Both native and managed Component Object Model (COM) add-ins are turned off. To narrow down the cause,
you can also try /safe:1 and /safe:3 commands.
/safe:1 Starts Outlook with the Reading Pane off.
/safe:3 Both native and managed Component Object Model (COM) add-ins are turned off.
To do this, press Windows key + R to open the Run command, type outlook.exe /safe:1
and press Enter.
In addition, you can refer to the steps in this article to troubleshoot issue that Outlook does not crash when you start it in safe mode. See the "Step 6: Start Outlook in safe mode" section:
http://support.microsoft.com/kb/2934538/en-us
Please let me know the result.
Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Outlook 2013 Crashes when sending mail

The system is a Windows 8.1 Pro x64, the Office installation is Office Home & Business 2013 32.
repeatedly the Outlook will crash after entering a contact email address when entering content into the subject line. Often it will crash when any attempt is made to enter content into the body.
All add-ins have been disabled.
If started in Safe mode, Outlook is able to send mail.
The error message in the event log is;
Faulting application name: OUTLOOK.EXE, version: 15.0.4551.1511, time stamp: 0x52947f7f
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f0c22
Exception code: 0xc0000005
Fault offset: 0x0003c558
Faulting process id: 0xeec
Faulting application start time: 0x01cf23061492ec78
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
Faulting module path: C:\Program Files\Microsoft Office 15\root\office15\MSVCR100.dll
Report Id: 693a0ed9-8ef9-11e3-be9f-b4b67633f44a
Faulting package full name:
Faulting package-relative application ID:
A capture of the add-ins dialog when Outlook is started in normal mode is shown below.
I have run scanpst on the local pst files and performed repairs.
I also disabled the use of auto-complete.
Nothing has worked.
Please provide some new suggestions.
Thx - Eli

Hi,
Since this issue doesn't occur when using Outlook in Safe Mode and it's not add-ins related, I suspect the NormalEmail.dotm is corrupted in your case.
NormalEmail.dotm is the default template that opens when creating a new mail message. When you start Outlook in Safe Mode, it is not loaded.
Please go to the following location:
C:\Users\<username>\AppData\Roaming\Microsoft\Templates
Find the NormalEmail.dotm file, rename it to ".old". Outlook then will create a new one, check if this issue persist with the new NormalEmail.dotm file.
Regards,
Melon Chen
TechNet Community Support

Labview 2013 crashing when restarting VI

Similar Messages

Maybe you are looking for