Windows DNS crashes in the app log what is the best way to fix this ? should i bee worried?

Log Name:      Application
Source:        Application Error
D

ate:          1/30/1968 4:40:01 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      dc2.pizza1.local
Description:
Faulting application name: dns.exe, version: 6.1.7601.17514, time stamp: 0x4ce7a052
Faulting module name: dns.exe, version: 6.1.7601.17514, time stamp: 0x4ce7a052
Exception code: 0xc0000005
Fault offset: 0x000000000001f25e
Faulting process id: 0xc1c
Faulting application start time: 0x01cc9049a3a542c9
Faulting application path: C:\Windows\system32\dns.exe
Faulting module path: C:\Windows\system32\dns.exe
Report Id: 2d5cf502-fdb7-11e0-91e2-005056ad0101
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="2011-10-23T20:40:01.000000000Z" />
    <EventRecordID>1514</EventRecordID>
    <Channel>Application</Channel>
    <Computer>dc2.xxxxxxxd1.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>dns.exe</Data>
    <Data>6.1.7601.17514</Data>
    <Data>4ce7a052</Data>
    <Data>dns.exe</Data>
    <Data>6.1.7601.17514</Data>
    <Data>4ce7a052</Data>
    <Data>c0000005</Data>
    <Data>000000000001f25e</Data>
    <Data>c1c</Data>
    <Data>01cc9049a3a542c9</Data>
    <Data>C:\Windows\system32\dns.exe</Data>
    <Data>C:\Windows\system32\dns.exe</Data>
    <Data>2d5cf502-fdb7-11e0-91e2-005056ad0101</Data>
  </EventData>
LVL 1
NAMEWITHELD12Asked:
Who is Participating?
 
-tjsConnect With a Mentor Commented:
c0000005 is an access violation and can refer to DNS accessing a file it doesn't have access to or accessing a memory location it doesn't have access to.  The former is checked by taking a look at the DNS zones on your server, noting their location (whether in an AD partition or file), and making sure the service account running DNS has full access to those locations.  The latter can be tricky.  I'd start with an "sfc /scannow" and reboot to make sure no system files were/are damaged.  Other than that, I'd search for the latest hotfix that updates DNS and apply it (if you can - that is, if the latest update is actually newer than your DNS components) just to make sure all of the components of DNS are on the same page, so to speak.  You could also enable DNS logging and use the time noted in the event log entries to check and see what the DNS service was doing right before it crashed.
0
 
NAMEWITHELD12Author Commented:
thanks i will do that and let you know what happends
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.