Solved Network Connections Constantly Crashing, Need Help!

[LiteralEdit]

So recently I've been having network issues. It started when I realized that my Network Adapters were not showing in the Network Connections folder, despite being in the device manager and working correctly. I tried every solution on the net to fix this, and nothing seems to work. However, I think I've located the core of the problem and I was wondering if you could help.

This screen shot is from the Action Center Recent Problems page or whatever its called:
Screenshot by Lightshot

Checking for solution provides no help.

However, this shows that the network connections is literally failing every minute. Which I think is the root cause of my main issue. If anyone has any idea how to solve this, Id love some help.

Another screenshot here shows the details of the crashes:
Screenshot by Lightshot

I believe all are the same.

 

[GokAy]

Start with running cmd as admin:

sfc /scannow

If corruption is found, run this in cmd too and attach the sfcdetails.txt (check desktop) here:

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\desktop\sfcdetails.txt"

Please attach the screenshots and files to SevenForums as described by http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[LiteralEdit]

Hi, GokAy

I performed the sfc scan and it says corruption was found. However Im having trouble carrying out the second operation. I assume im supposed to replace the "[SR]" and %userprofile% and maybe remove the quotations, but im not entirely sure. could you clarify please

 

[GokAy]

open command prompt and copy paste it without any modifications

 

[LiteralEdit]

Here are the screenshots from the sfc scan.

 

[GokAy]

I am not sure if your issue is related to that one corruption. But searching for dot3api.dll show it is related to 802.3 and

IEEE 802.3 is a working group and a collection of IEEE standards produced by the working group defining the physical layer and data link layer's media access control (MAC) of wired Ethernet. This is generally a local area network technology with some wide area network applications.

So likely it is, I will PM our expert on this issue once CBS.zip is uploaded. But also need you to attach CBS.log as described in http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html #4 (log collection).

Attach the files as described in http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[LiteralEdit]

That does sound like a problem, considering im using ethernet to connect to a TP-Link adapter which then connects to my router via the mains, I think. So this could definitely be the problem. I appreciate the help and your patience so far, GokAy.

The zip file created is 33.9MB, which I think is too large to upload, as the max seems to be 8MB. What should I do?

 

[GokAy]

You can upload to a cloud sharing site; OneDrive or Dropbox works. I guess there is a way to reduce the size but I couldn't be sure:

simply delete the oldest CBSPersist files

If it doesn't help, just upload to cloud as I said.

 

[LiteralEdit]

Ok, I deleted some CBSPersist files from a few days ago, and kept one from earlier today and the log of course. Here is the file:
View attachment 367819

 

[GokAy]

PM sent to NoelDP, expect him to respond (hopefully soon, may not be today as he is usually very busy). I will be watching the thread. Take care for now.

 

[LiteralEdit]

Alright, thanks for your help!

 

[NoelDP]

Here's the critical bits from the SFC scan...

	Line 9203: 2015-08-01 19:46:37, Info                  CSI    00000349 [SR] Repairing 1 components
	Line 9204: 2015-08-01 19:46:37, Info                  CSI    0000034a [SR] Beginning Verify and Repair transaction
	Line 9207: 2015-08-01 19:46:37, Info                  CSI    0000034c [SR] Cannot repair member file [l:22{11}]"dot3api.dll" of Microsoft-Windows-Dot3svc, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 9210: 2015-08-01 19:46:38, Info                  CSI    0000034e [SR] Cannot repair member file [l:22{11}]"dot3api.dll" of Microsoft-Windows-Dot3svc, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol a little later.

 

[NoelDP]

I've uploaded a file - letaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\letaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\letaa
or
DIR E:\letaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\letaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[LiteralEdit]

I carried out the operations and everything works perfectly now! My network connections are in the folder, everything that was wrong is fixed!

Heres the screenshots of the sfc scan:






Im pretty sure my problem is solved. Thank you so much Noel for your help, you are a GOD!
And thanks to GokAy as well for the initial help.

What do you think caused the problem in the first place, if you have time to answer?

 

[GokAy]

I would have no idea why it got corrupted But glad to know it got fixed.

Good job, and of course thanks to Noel too. He worked his magic as usual

 

[NoelDP]

I must admit I didn't expect that to actually cure your problems! - glad it did!

Good luck.