Vista - Did not load driver AFD.SYS- PC not booting up properly

Hello

When I boot up my PC it freezes after the Microsoft loading screen
What I have to do then is boot up in safe mode and then restart my pc.
I have reinstalled both my graphic's cards drivers and my Realtek NIC's drivers.
I have done a boot log and the main problem is :

Did not load driver AFD.SYS

Does anybody know about this system file and what can I do to fix it? Is it a driver?

Urgently need help

Please post back asap

Thanks

Poker

AFD = Ancillary Function Driver

It's part of Winsock. It provides access to the rest of the network stack for apps and many components of the OS. Without it, browsers and mail clients wont work, just as an example.

Does the PC boot without errors into safe mode?

Does it boot into "safe mode + net"?

Do you have a Vista DVD or is this an OEM preinstall?

Thanks for your reply.

Yes the PC boots without errors into safe mode.

Yes the PC boots into "safe mode + networking".

Yes I have a Vista DVD..

So what now?

Interesting.May any non -system aplication service cause this? Disable all non-system services (look here how to do that for test:How to perform a clean boot procedure to determine whether background programs are interfering with a game or a program that you currently use ) and run system in normal mode and we'll see results...

Im afraid this did not work.

Once I am in normal mode (boot up through safe mode and then restart in normal mode), I can restart back into normal mode. It is only when I shut down that I cannot boot directly back into normal mode.

Any ideas?

I'm pretty sure it isn't a non-system application service that is causing this...

Can you post more of that boot log here? I'm not entirely sure that failure to initialise afd.sys is by itself causing your cant-boot-from-cold symptom. That might be more of a side effect.

Also, are there any warnings or errors in the system event log during one of these problem boots? (Run eventvwr afterwards to check based on timestamps.)

Here are more from my boot log:

Multiple instances of:

Did not load driver @nettun.inf,%isatap.displayname%;Microsoft ISATAP Adapter
Did not load driver @nettun.inf,%isatap.displayname%;Microsoft ISATAP Adapter
Did not load driver @nettun.inf,%tunmp.displayname%;Microsoft Tun Miniport Adapter
Did not load driver @hal.inf,%acpiapic.devicedesc%;ACPI x86-based PC
Did not load driver @netrasa.inf,%mp-l2tp-dispname%;WAN Miniport (L2TP)
Did not load driver @netrasa.inf,%mp-bh-dispname%;WAN Miniport (Network Monitor)
Did not load driver @netrasa.inf,%mp-ip-dispname%;WAN Miniport (IP)
Did not load driver @netrasa.inf,%mp-ipv6-dispname%;WAN Miniport (IPv6)
Did not load driver @netrasa.inf,%mp-pppoe-dispname%;WAN Miniport (PPPOE)
Did not load driver @netrasa.inf,%mp-pptp-dispname%;WAN Miniport (PPTP)
Did not load driver @netsstpa.inf,%mp-sstp-dispname%;WAN Miniport (SSTP)

Multiple instances of :
Did not load driver ASUS EAH4870 series
Did not load driver ATITool Driver

Multiple instances of :

Did not load driver @oem32.inf,%rtl8168c.devicedesc%;Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NIC (NDIS 6.0)

Multiple instances of:

Did not load driver @cpu.inf,%intelppm.devicedesc%;Intel Processor
Did not load driver @cpu.inf,%intelppm.devicedesc%;Intel Processor


Once into Event Viewer, the timestamps of the warnings coincide with my unsuccessful
attempts and direct booting.
This message is repeated multiple times.
Level : Warning
Source: Winlogon
Event ID: 6000
Task Category:None

When I went to event properties this is what it said:

- System

- Provider

[ Name] Microsoft-Windows-Winlogon
[ Guid] {DBE9B383-7CF3-4331-91CC-A3CB16A3B538}
[ EventSourceName] Wlclntfy

- EventID 6000

[ Qualifiers] 32768

Version 0

Level 3

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2009-03-14T06:36:32.000Z

EventRecordID 15653

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel Application

Computer PokerKing

Security


- EventData

GPClient
D9060000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 000006D9


In Bytes

0000: D9 06 00 00 Ù...

Last things first. The 6D9 data in the Winlogon event is almost certainly a Win32 status code. 6D9 hex is 1753 decimal, and hence:

V:\>net helpmsg 1753
There are no more endpoints available from the endpoint mapper.

The endpoint mapper failure would be a side-effect of other stuff on your machine not working by that point, so I think you should ignore the Winlogon event for now on the basis that it's expected given half the OS has failed to initialise

I also suspect AFD is another victim. There are more fundamental drivers in that list which appear to be having issues... and yet the list does seem rather network-y, at least the portions which you've pasted here.

Since the problem only occurs during a cold boot, I'd suggest you first flash your BIOS to the latest version. If that still does nothing for you, try pulling out the NIC temporarily and testing cold boot into normal mode without it. If the NIC is embedded, try disabling it completely in the BIOS (most BIOSes offer that functionality).

My gut feeling is that your issue is more BIOS/hardware than software. I could easily be wrong though.

how would I go about flashing my bios?

My motherboard is a Gigabyte G31M-S2L

Are there any dangers with relation to my hardware + software with flashing my bios?

Thanks for your help so far