Event log errors on startup

[cgoldman]

I have recently taken over a Win7 machine. Through numerous AV tools at it and it is all clean and working. I do however have some errors in the log which arise on each reboot and try as I may I cannot find the cause. system.msc, autoruns, Microsoft help etc have not enabled me to eliminate these. Any advice appreciated. I have seen some similar posts here but their solutions did not work for me.

I have warnings and errors.

error 1. The following boot-start or system-start driver(s) failed to load: luafv


error 2 from Bonjour service 536: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

I think this may arise because I have network cable to router and wireless, and I have manually disabled the wireless connection.

The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&1&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_COMPACT_FLASH&REV_1.00#8&35CCDA1&0&20060413092100000&0#.

there are no stopped services and the device manager shows no issue.

 

[matts6887]

Try re-enabling the wireless and see what happens. If that does not get rid of the error; i would uninstall and then reinstall the bonjour service.

 

[cgoldman]

update

I tried that but it does not get better. In any event there are more than one error as reported.

after I re-enable wireless adaptor but still connect only with network I have the following

I just want to get rid of errors.
The 1st DHCP says
"
Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x70F1A17DA4CE. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server."

Maybe this is because the wireless connection although enabled is not connected...because I am using cable.

The 2nd Kernal syas
"
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&1&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_COMPACT_FLASH&REV_1.00#8&35CCDA1&0&20060413092100000&0#."

The 3rd is the luafv as reported before
t
he 4th is "
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications."

the 5th is "
WLAN AutoConfig service has successfully stopped."

the 6th is
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
7 user registry handles leaked from \Registry\User\S-1-5-21-2573429720-122581382-2703279237-1005:
Process 156 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2573429720-122581382-2703279237-1005\Software\Policies
Process 156 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2573429720-122581382-2703279237-1005\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Process 156 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2573429720-122581382-2703279237-1005\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Process 156 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2573429720-122581382-2703279237-1005\Software
Process 156 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2573429720-122581382-2703279237-1005\Software\Microsoft\Internet Explorer\Main
Process 156 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2573429720-122581382-2703279237-1005\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings
Process 156 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2573429720-122581382-2703279237-1005\Software\Microsoft\Internet Explorer\Main\FeatureControl"

the next is dcom "
The server {60A90A2F-858D-42AF-8929-82BE9D99E8A1} did not register with DCOM within the required timeout."