This post is more than 5 years old
3 Posts
0
3859
August 26th, 2017 14:00
Teredo Network Issue XPS 8900
Hello. My XPS 8900 is running Windows 10 Pro 64 bit Creator's Edition and is up-to date.
Over the last 3 weeks, "every" 3 minutes without fail , Windows Error Reporting sends the following error report to Microsoft (evidenced via the Event Viewer):
START OF REPORT:
Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0
Problem signature:
P1: x64
P2: *TEREDO
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_999351ce61e948adcd69eb2ce10f92a449fa48_00000000_05aeb529
Analysis symbol:
Rechecking for solution: 0
Report Id: fbd8b8b7-8b09-4896-ab7a-c0ab8f940131
Report Status: 4100
Hashed bucket:
END OF REPORT
It seems Windows is looking for and cannot find a Teredo Tunneling Adapter driver. A Teredo device doesn't show up at all in my network devices and if I try to search for legacy drivers by Microsoft, the Teredo driver is not offered as an option to add it. It doesn't show up if I show hidden devices. There are no devices in Device Manager showing errors, yet the device manager listing will refresh just prior to the Teredo error report being sent to Microsoft.
- I have tried re-installing the current Dell networking drivers.
- I have tried uninstalling the network drivers, rebooting, and letting windows reinstall the drivers.
- If I disable the network devices, the error reporting ceases and the device manager stops refreshing.
- If I re-enable the network devices (w-fi and/or Ethernet) the 3 minute Teredo error reporting and Device Manager refreshing resumes (Bluetooth is disabled since I don't use it).
- When the error report sends, the blue circle appears beside my mouse pointer for a couple of seconds and hard drive activity increases (very irritating).
Should my XPS 8900 have a Teredo Tunneling Adapter driver? If so, how do I add it? If not, how do I stop Windows 10 from trying to install it and sending an error report every 3 minutes?
LogicalSpock
3 Posts
0
October 2nd, 2017 12:00
A month later and the problem has not returned.
The fix was to manually stop the "Plug and Play" service once as I posted above. The Plug and Play service has since restarted, of course, but the Teredo Event ID 122 issue never returned thereafter.
Brad L (retired)
9 Legend
•
2.7K Posts
0
August 28th, 2017 14:00
Have you seen this link This is not exactly your error but following the steps might allow it to reset fully and reinstall. If it doesn't work, can you let me know what wifi card you have? And do you connect via wifi or ethernet?
Best regards,
Brad
LogicalSpock
3 Posts
0
September 3rd, 2017 10:00
Thanks for responding Brad.
I cannot perform the Command Promt fix in the link because the Teredo Tunneling Pseudo-Interface device never appears in the device manager - and never has since the error appeared.
I have performed more research and tasks on my Teredo issue since I posted:
The error report to Microsoft regarding this Teredo device issue is an Event ID 122. I have been able to disable "Metadata Refresh" in the registry and confirmed it is disabled, yet the 3 minute Event ID 122 error continued to be sent.
Going back through the event log, the Teredo error began the same day I installed an Oculus Rift (I have a GTX 1060 card and 24 gigs of RAM in my XPS 8900). Based on that, I completely disconnected and uninstalled all drivers for the Rift. A few reboots later, the errors still continued.
I completely uninstalled NVidia's Geforce Experience and video drivers. Then reinstalled the drivers manually (not using Geforce Experience). The Teredo errors still continued.
Maybe fixed.....
In my last computing session (a few days ago), I went into "Services" and painstakingly reviewed all running services. "Plug and Play" was running (set on Manual), so I stopped it (not disabled it of course). The 3 minute Teredo error cycle immediately stopped. Today, I cold booted and I've been running for about an hour and "Plug and Play" service has not started and I have not had the 3 minute Teredo event occur.
I'll report back after a few cold boot sessions or if the Teredo error resumes, but hopefully stopping "Plug and Play" a few days ago is the permanent fix.