BCreen Win7 BSOD on TCPIP.sys randomly error 0x000000d1

[BCreen]

This started in October. Dell small form factor, NIC built into M.B. Since it mentioned TCPIP.sys I ass-u-me'd it was the NIC and disable the onborad when I added a standalone ePCI NIC (with 3 USBs). The StarTech.com card seemed to work for a few days then BSODs resumed -- same error.
Have since run all Windows updates, removed the StarTech card and reverted to the onboard NIC. Still getting BSOD -- sometimes immediately upon bootup, occasionally will run for hours before happening again.
Will try attaching the file-information zip I made.

Haven't called Dell yet -- it is still in warranty.

Appreciate any insight into this frustrating problem.

Regards,
Bill

 

[axe0]

If DriverUpdate has been used to update drivers, revert those drivers and remove driverupdate.
Then proceed to driver verifier.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[Acova]

I've gone through your Event Viewer Logs, found a 'popular' error:

Peer Name Resolution Protocol

I've found several sources for you to read:
1) Cant start Peer Name Resolution Protocol
2) %%-2140993535 and 0x80630801 in event viewer after crash
3) Error Code:%%-2140993535 - Windows 7
4) why does my computer keep randomly restarting - Microsoft Community
5) Event ID 102 — PNRP Protocol

Sorted them in priority for reading sequence.
Or in few words:
1) C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming
2) idstore.sst
3) they suggest removing it, and it will get rebuilt on its own, resolving this error (before doing anything, do read to ensure you're not harming the system any further).

I would see after that if it's helped to stop these crashes afterwards.

However... event viewer logs shows many other errors as well and ...

[SIZE="1"]Event[57813]:
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2017-12-25T20:09:30.000
  Event ID: 1001
  Level: Error
...
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x000000000000001c, 0x0000000000000002, 0x0000000000000001, 0xfffff88002062726). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 122517-8673-01.[/SIZE]

[SIZE="1"]Event[57625]:
  Source: Service Control Manager
  Date: 2017-12-25T19:47:49.071
  Event ID: 7000
  Level: Error
...
  Description: 
The lxdoCATSCustConnectService service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.[/SIZE]

[SIZE="1"]Event[57619]:
  Source: Service Control Manager
  Date: 2017-12-25T19:47:48.871
  Event ID: 7000
  Level: Error
...
  Description: 
The Service Installer TrueKey service failed to start due to the following error: 
The system cannot find the file specified.[/SIZE]

[SIZE="1"]Event[56575]:
  Source: Service Control Manager
  Date: 2017-12-25T18:46:25.192
  Event ID: 7001
  Level: Error
...
  Description: 
The PnP-X IP Bus Enumerator service depends on the Function Discovery Provider Host service which failed to start because of the following error: 
The dependency service or group failed to start.
 Reason Code: 0x0
 Shutdown Type: restart
 Comment: 
No title for this reason could be found
 Reason Code: 0x500ff
 Shutdown Type: restart
 Comment: [/SIZE]

[SIZE="1"]Event[56553]:
  Source: Service Control Manager
  Date: 2017-12-25T18:44:25.197
  Event ID: 7026
  Level: Error
...
  Description: 
The following boot-start or system-start driver(s) failed to load: 
AFD
avipbb
avkmgr
CSC
DfsC
discache
NetBIOS
NetBT
nsiproxy
Psched
rdbss
snapman
spldr
tdx
vwififlt
Wanarpv6[/SIZE]

....


Are you up to date with drivers for your components? Though, if you say you are up-to-date with Windows Updates, that suggests the same for drivers as far as I can assume, though I suspected that a driver was causing BSODs besides the previous "idstore.sst" thing.

When there are way too many problems to face with, I would rather back up data, and reinstall OS ensuring it gets the right drivers..

Can be also useful for reading (despite OS version over there): Tcpip.sys BSOD - Microsoft Community

(one more resource for reading: The computer has rebooted from a bugcheck. 0x000000d1 - Windows 7 Help Forums)