UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Msaccess.exe Faulting Event Id 1000, Access 2010    
 
   
havesometea
post Sep 6 2012, 11:07 AM
Post#1



Posts: 2
Joined: 6-September 12



Combed the Internet trying to find a solution to this and coming up with nothing. Any ideas?
og Name: Application
Source: Application Error
Date: 9/6/2012 11:33:17 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: redacted Description:
Faulting application name: MSACCESS.EXE, version: 14.0.6024.1000, time stamp: 0x4d83e4fc
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x1d30
Faulting application start time: 0x01cd8c44d5fc1f26
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 2dc72368-f838-11e1-9100-f0def162deb1
Event 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="2012-09-06T15:33:17.000000000Z" />
<EventRecordID>35283</EventRecordID>
<Channel>Application</Channel>
<Computer>redacted</Computer>
<Security />
</System>
<EventData>
<Data>MSACCESS.EXE</Data>
<Data>14.0.6024.1000</Data>
<Data>4d83e4fc</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec49b8f</Data>
<Data>c0000374</Data>
<Data>000ce6c3</Data>
<Data>1d30</Data>
<Data>01cd8c44d5fc1f26</Data>
<Data>C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE</Data>
<Data>C:\Windows\SysWOW64\ntdll.dll</Data>
<Data>2dc72368-f838-11e1-9100-f0def162deb1</Data
Go to the top of the page
 
bulsatar
post Sep 6 2012, 11:23 AM
Post#2



Posts: 1,208
Joined: 16-June 10
From: Indiana, USA


did a quick search on the module that was faulting (ntdll.dll) and came up with this:
ntdll.dll errors
Go to the top of the page
 
havesometea
post Sep 6 2012, 11:39 AM
Post#3



Posts: 2
Joined: 6-September 12



I doubt that is the issue because this is happens on every computer that tries to access this current field.
Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    3rd September 2015 - 05:48 AM