Member Avatar for zillah

Hi
I have got domain environment (AD win2003 server) under Event Viewer (Application and DNS Server) I have got couple of Event IDs.

I know that Google is our friend but I got confused which Event IDs should I examine

The error message that I have been experiencing is the snapshot below

http://www.wallpaperama.com/forums/at-least-one-service-or-driver-failed-during-system-startup-t6274.html

At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

I have got lengthy Event Viewer (Specially for Applications but not DNS Server) therefore I did not post them

Thanks

  • 1 Contributor
  • 1 Reply
  • 357 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by zillah

Dani AI

Generated

As already pointed out, the popup itself is just a generic symptom — the real diagnostic details are in the Event Viewer entries created at boot. Focus first on the System log and the Service Control Manager events around the time the machine last started; those entries normally name the failing service/driver and give an error code you can act on.

  1. Open Event Viewer (eventvwr.msc) -> System. Filter by Source = Service Control Manager and review events around the boot time. Prioritize Event IDs in the 7000–7043 range (7000, 7001, 7009, 7011, 7023, 7031/7034 are the common ones).
  2. Read the full event text: note the service or driver name, the service display name, and the binary path. If the event reports "file not found" the driver/exe is missing or quarantined; if it shows "access denied" check file permissions.
  3. Isolate the offender: boot to Safe Mode — if the message disappears suspect a third‑party service/driver. Use msconfig or Sysinternals Autoruns to disable non‑Microsoft services/startups and reboot incrementally to identify the item.
  4. For drivers, check Device Manager, reinstall/roll back the driver, or run Driver Verifier (use with caution — it can cause BSODs so enable only for short tests and with a recovery plan).
  5. Run integrity checks: sfc /scannow and chkdsk /f. Consider Last Known Good configuration if the problem started after a recent change.
  6. On domain controllers pay special attention to Netlogon, DNS and the NIC driver — a failed NIC or delayed start can block many dependent services.

Keep backups and document the exact Event ID, service/driver name, timestamp and error message — that combination is what lets you move from general troubleshooting to a precise fix.

Member Avatar for zillah

under Event Viewer (Application and DNS Server)

Sorry I should have added System as well

(Specially for Applications but not DNS Server)

And System

Edited by zillah because: n/a
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.