Инсталирайте Steam
вход
|
език
Опростен китайски (简体中文)
Традиционен китайски (繁體中文)
Японски (日本語)
Корейски (한국어)
Тайландски (ไทย)
Чешки (Čeština)
Датски (Dansk)
Немски (Deutsch)
Английски (English)
Испански — Испания (Español — España)
Испански — Латинска Америка (Español — Latinoamérica)
Гръцки (Ελληνικά)
Френски (Français)
Италиански (Italiano)
Индонезийски (Bahasa Indonesia)
Унгарски (Magyar)
Холандски (Nederlands)
Норвежки (Norsk)
Полски (Polski)
Португалски (Português)
Бразилски португалски (Português — Brasil)
Румънски (Română)
Руски (Русский)
Финландски (Suomi)
Шведски (Svenska)
Турски (Türkçe)
Виетнамски (Tiếng Việt)
Украински (Українська)
Докладване на проблем с превода
i am probably a victim of confirmation bias here lol i see this and this; ah this is my issue lol. thanks for clearing it up
A look into the Windows event viewer can give more information if the problem is caused inside of the Computer or at the network side (if no logs point to a driver restart or System fault).
Powerline Adapters Interfer with DSL signals and they also often get broken over time.
getting a completely new router and a mesh network soon anyway.
'Powerline Adapters Interfer with DSL signals and they also often get broken over time.' - after some thought. I think it's this. It's not just elden ring so i need to accept it's this. It's uncommon so not a huge deal. I'll probs go wireless soon anyway.
Would nice to see the logs.
Device PCI\VEN_8086&DEV_51F0&SUBSYS_00748086&REV_01\3&11583659&0&A3 was configured.
Driver Name: oem70.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Driver Date: 01/21/2024
Driver Version: 23.30.0.6
Driver Provider: Intel
Driver Section: Install_GEN_SLR_HrP2_201_AX_2x2_WinT_non_6e
Driver Rank: 0xFF0001
Matching Device Id: PCI\VEN_8086&DEV_51F0&SUBSYS_00748086
Outranked Drivers: oem13.inf:PCI\VEN_8086&DEV_51F0&SUBSYS_00748086:00FF0001
Device Updated: true
Parent Device: ACPI\PNP0A08\0
Error:
Device PCI\VEN_8086&DEV_51F0&SUBSYS_00748086&REV_01\3&11583659&0&A3 had a problem starting.
Driver Name: oem70.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Service: Netwtw14
Lower Filters:
Upper Filters: vwifibus
Problem: 0x0
Problem Status: 0xC00000E5
Hmm, so for this Wifi device is no firnware update and driver update available at Intel.
Than you have a real problem with this Adapter at Hardware side or at Windows core the driver itself tells that a internal error occured
After some investigation there are a lot of ppl with similar problems at this device trying to connect to 5 GHz and 6 GHz networks.
It looks like the driver is wrong and not the driver that supports this device, if this Wifi card is a Motherboard or Laptop integrated device you have to install the driver from the manufacturer Support page, the Intel driver is not compatible with them and Windows could have installed the Intel OEM driver for this Wifi chipset.
Some solved the problem by install the windows 10 drivers instead the windows 11 drivers from the manufacturer Website.
At the Intels own chipset exists a Firmware update that make the actual windows OEM Intel driver compatible.
You could also consider getting a tp link so you can directly plug an ethernet cable in.From experience they are more reliable than direct wifi.
So far it looks like the driver of the wireless adapter has a wrong ident Tag or the driver has a exception coding fault this cause that EAC recognize it as a input device and send a call to it, this cause that the device get a internal exception fault and restarts.
This happend at a lot of devices a few months ago but got fixed normally by biosupdate, Firmware update and driver updates.
In some cases if a manufacturer used a oem chipset from Intel the manufacturer did not offered a firmware update and the device became useless (happend with Intel chipset wireless adapters from gigabyte, intel offered a firmware fix, gigabyte not).
Possible similar things happen to your device.
A part of the EAC routine is running in the eldenring.exe.
It is also possible the device is faulty at a other Level.