-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Wireless and Networking
- High ping [ realtek rtl8822be 802.11ac pcie adapter driver]

Create an account on the HP Community to personalize your profile and ask a question
10-02-2019 03:07 PM - edited 10-02-2019 03:35 PM
Hello members,
1 month ago I bought the HP Gaming laptop but found out that my wireless adapter is either not working good or bugged.
Everytime I run a game I have high latency/ping. I have tried many solutions since this was a common problem with the wireless adapter. I have updated the driver multiple times and I am now at Driver Version: 2024.0.10.106 and Driver Date: 07/08/2019.
EDIT: I have now update the driver to Driver Date: 27/08/2019 and Driver Version: 2024.0.8.110
And I still have the same problem,
I also have run a BIOS update.
So again my problem is high latency/ping, my phone and pc are working fine on the wifi except for my laptop.
I hope someone can help me even when this is a common problem with the realtek rtl8822be 802.11ac pcie adapter driver
Kind regards,
10-02-2019 03:47 PM
Hi
ComputerName : internetbeacon.msedge.net RemoteAddress : 13.107.4.52 InterfaceAlias : WiFi
SourceAddress : 192.168.0.11
PingSucceeded : True
PingReplyDetails (RTT) : 18 ms
Since you don't quote any values, it is difficult to know what is considered fast/long/slow/short etc.
Copy, Paste and Save in Notepad, as LBB.bat (not a .TXT) and double click to run.
Preferably run as an Administrator.
OR copy and use the individual command lines as needed.
Post anything non-personal, but relevant please.
@Echo OFF
getmac
netsh lan show interfaces
netsh wlan show interfaces
netsh wlan show drivers
PAUSE
systeminfo
PowerShell -Command "Get-NetAdapter"
PowerShell -Command "Get-NetAdapter -Name * | Format-Table -View Driver"
PowerShell -Command "GIP -Detailed"
PowerShell -Command "Test-NetConnection"
PAUSE
10-02-2019 03:51 PM
Physical Address Transport Name
=================== ==========================================================
80-E8-2C-90-48-1B Media disconnected
EC-5C-68-A1-D8-A7 \Device\Tcpip_{E105CCA9-D558-4A1E-9658-6EDC2F223E3A}
The Wired AutoConfig Service (dot3svc) is not running.
There is 1 interface on the system:
Name : WiFi
Description : Realtek RTL8822BE 802.11ac PCIe Adapter
GUID : e105cca9-d558-4a1e-9658-6edc2f223e3a
Physical address : ec:5c:68:a1:d8:a7
State : connected
SSID : H3xxxxxxx
BSSID : 50:78:b3:85:ae:38
Network type : Infrastructure
Radio type : 802.11n
Authentication : WPA2-Personal
Cipher : CCMP
Connection mode : Auto Connect
Channel : 8
Receive rate (Mbps) : 144.4
Transmit rate (Mbps) : 144.4
Signal : 91%
Profile : H3xxxxxxx
Hosted network status : Not available
Interface name: WiFi
Driver : Realtek RTL8822BE 802.11ac PCIe Adapter
Vendor : Realtek Semiconductor Corp.
Provider : Realtek Semiconductor Corp.
Date : 27/08/2019
Version : 2024.0.8.110
INF file : oem110.inf
Type : Native Wi-Fi Driver
Radio types supported : 802.11n 802.11g 802.11b 802.11ac 802.11n 802.11a
FIPS 140-2 mode supported : Yes
802.11w Management Frame Protection supported : Yes
Hosted network supported : No
Authentication and cipher supported in infrastructure mode:
Open None
WPA2-Personal CCMP
Open WEP-40bit
Open WEP-104bit
Open WEP
WPA-Enterprise TKIP
WPA-Personal TKIP
WPA2-Enterprise TKIP
WPA2-Personal TKIP
WPA-Enterprise CCMP
WPA-Personal CCMP
WPA2-Enterprise CCMP
Vendor defined TKIP
Vendor defined CCMP
Vendor defined Vendor defined
Vendor defined Vendor defined
WPA2-Enterprise Vendor defined
WPA2-Enterprise Vendor defined
Vendor defined Vendor defined
Vendor defined Vendor defined
IHV service present : Yes
IHV adapter OUI : [00 e0 4c], type: [00]
IHV extensibility DLL path: C:\windows\system32\Rtlihvs.dll
IHV UI extensibility ClSID: {6c2a8cca-b2a2-4d81-a3b2-4e15f445c312}
IHV diagnostics CLSID : {00000000-0000-0000-0000-000000000000}
Wireless Display Supported: Yes (Graphics Driver: Yes, Wi-Fi Driver: Yes)
10-02-2019 03:59 PM
Hi
Channel : 8
Receive rate (Mbps) : 144.4
Transmit rate (Mbps) : 144.4
A different channel gives what value?
C:\>ping bbc.co.uk
Pinging bbc.co.uk [151.101.192.81] with 32 bytes of data:
Reply from 151.101.192.81: bytes=32 time=27ms TTL=56
Reply from 151.101.192.81: bytes=32 time=20ms TTL=56
Reply from 151.101.192.81: bytes=32 time=16ms TTL=56
Reply from 151.101.192.81: bytes=32 time=17ms TTL=56
Ping statistics for 151.101.192.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 27ms, Average = 20ms
C:\>ping google.com
Pinging google.com [172.217.169.78] with 32 bytes of data:
Reply from 172.217.169.78: bytes=32 time=24ms TTL=54
Reply from 172.217.169.78: bytes=32 time=21ms TTL=54
Reply from 172.217.169.78: bytes=32 time=18ms TTL=54
Reply from 172.217.169.78: bytes=32 time=17ms TTL=54
Ping statistics for 172.217.169.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 24ms, Average = 20ms
So why can you not give comparable figures?
10-02-2019 04:10 PM
AND I get
Average Latency: 108.08ms
Average Jitter: 4.11ms
So I guess this packet loss people are pinging the moon or somewhere.
108 ms, laughable.
Heart of England to OZ and back.
10-02-2019 04:10 PM
C:\Users\xxxxx> ping www.google.com -n 25
Pinging www.google.com [172.217.168.196] with 32 bytes of data:
Reply from 172.217.168.196: bytes=32 time=9ms TTL=57
Reply from 172.217.168.196: bytes=32 time=3321ms TTL=57
Reply from 172.217.168.196: bytes=32 time=9ms TTL=57
Reply from 172.217.168.196: bytes=32 time=12ms TTL=57
Reply from 172.217.168.196: bytes=32 time=9ms TTL=57
Reply from 172.217.168.196: bytes=32 time=13ms TTL=57
Reply from 172.217.168.196: bytes=32 time=12ms TTL=57
Reply from 172.217.168.196: bytes=32 time=16ms TTL=57
Reply from 172.217.168.196: bytes=32 time=17ms TTL=57
Reply from 172.217.168.196: bytes=32 time=2771ms TTL=57
Reply from 172.217.168.196: bytes=32 time=10ms TTL=57
Reply from 172.217.168.196: bytes=32 time=13ms TTL=57
Reply from 172.217.168.196: bytes=32 time=13ms TTL=57
Reply from 172.217.168.196: bytes=32 time=12ms TTL=57
Reply from 172.217.168.196: bytes=32 time=13ms TTL=57
Reply from 172.217.168.196: bytes=32 time=13ms TTL=57
Reply from 172.217.168.196: bytes=32 time=92ms TTL=57
Reply from 172.217.168.196: bytes=32 time=2900ms TTL=57
Reply from 172.217.168.196: bytes=32 time=158ms TTL=57
Reply from 172.217.168.196: bytes=32 time=13ms TTL=57
Reply from 172.217.168.196: bytes=32 time=13ms TTL=57
Reply from 172.217.168.196: bytes=32 time=13ms TTL=57
Reply from 172.217.168.196: bytes=32 time=15ms TTL=57
Reply from 172.217.168.196: bytes=32 time=14ms TTL=57
Reply from 172.217.168.196: bytes=32 time=13ms TTL=57
Ping statistics for 172.217.168.196:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 3321ms, Average = 379ms
10-02-2019 04:18 PM - edited 10-02-2019 04:20 PM
Hi
Well a radio signal round trip to the moon is 2.57 seconds ish; (2572 milliseconds).
You have pings to Google in the US of A, I suspect, I don't know from where (do you live on the moon?) of Maximum = 3321ms.
So do you use a proxy?
Do you have a fixed frequency or channel?
You do have a problem, that I accept.
10-02-2019 04:28 PM
C:\Users\xxxxx>ping bbc.co.uk -n 20
Pinging bbc.co.uk [151.101.128.81] with 32 bytes of data:
Reply from 151.101.128.81: bytes=32 time=38ms TTL=60
Reply from 151.101.128.81: bytes=32 time=44ms TTL=60
Reply from 151.101.128.81: bytes=32 time=15ms TTL=60
Reply from 151.101.128.81: bytes=32 time=2992ms TTL=60
Reply from 151.101.128.81: bytes=32 time=11ms TTL=60
Reply from 151.101.128.81: bytes=32 time=10ms TTL=60
Reply from 151.101.128.81: bytes=32 time=10ms TTL=60
Reply from 151.101.128.81: bytes=32 time=10ms TTL=60
Reply from 151.101.128.81: bytes=32 time=11ms TTL=60
Reply from 151.101.128.81: bytes=32 time=12ms TTL=60
Reply from 151.101.128.81: bytes=32 time=11ms TTL=60
Reply from 151.101.128.81: bytes=32 time=2863ms TTL=60
Reply from 151.101.128.81: bytes=32 time=10ms TTL=60
Reply from 151.101.128.81: bytes=32 time=10ms TTL=60
Reply from 151.101.128.81: bytes=32 time=10ms TTL=60
Reply from 151.101.128.81: bytes=32 time=11ms TTL=60
Reply from 151.101.128.81: bytes=32 time=13ms TTL=60
Reply from 151.101.128.81: bytes=32 time=11ms TTL=60
Reply from 151.101.128.81: bytes=32 time=10ms TTL=60
Reply from 151.101.128.81: bytes=32 time=2824ms TTL=60
Ping statistics for 151.101.128.81:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 2992ms, Average = 446ms
Unfortunaly I'm not on the moon right now neither do I use a proxy or have swapped out channels or used other frequency's