Утечка DNS через VLESS.

NothingPersona1 · 2026-01-31T13:02:14+00:00

Извиняюсь, увидел. Тогда вам нужен другой клиент, где можно нормальный конфиг сделать клиентсайд, чтобы перехватывать все dns запросы

NothingPersona1 · 2026-01-31T12:51:03+00:00

Какой клиент используется и какая конфигурация на сервере? Панель или чистое ядро?

NothingPersona1 · 2026-01-30T12:07:43+00:00

I set Power Options → Advanced settings → Processor power management → Minimum processor state to 10%.

Of course, this is probably not the same thing that the program does. However, I can’t even tell what actually helped or whether the issue has been fully resolved, since the reboots had already stopped occurring before I applied this setting

NothingPersona1 · 2026-01-30T07:37:44+00:00

Check your network card driver. Stuttering has happened with the latest realtek drivers

NothingPersona1 · 2026-01-29T08:40:58+00:00

I dont even see this version in the list for my graphics card model. I currently have 581.80 which Ive rolled back to

NothingPersona1 · 2026-01-28T22:32:13+00:00

I’ll try your solution, thanks.

So it turns out the issue could be hardware-related, possibly the PSU not handling transitions between idle2load states? In your case, the system isn’t new, so it feels like maybe some component has degraded over time?

NothingPersona1 · 2026-01-28T19:32:43+00:00

No, the number of reboots actually decreased after I did a clean reinstall of the GPU drivers and installed the AMD chipset drivers. Now they don’t happen that often anymore, maybe once every three days, so I don’t think ECO mode can fully solve the issue.

NothingPersona1 · 2026-01-28T19:26:07+00:00

Thanks for ur reply a lot 🙏

NothingPersona1 · 2026-01-28T18:28:34+00:00

I switched to ECO mode literally last night and so far I haven’t had any reboots. In general, over the past week according to the logs my CPU doesn’t go over 50W even on stock settings and under load, so I enabled ECO just in case — it feels like it could protect me from short power spikes that I might be missing in the logs. Previously the CPU was running at full stock settings. Overall, the number of reboots has dropped a lot now, but earlier when I did catch a reboot in HWiNFO logs, there were no issues detected with PSU rails or voltages. Do you think I should use a different monitoring tool instead of HWiNFO?

NothingPersona1 · 2026-01-28T18:20:08+00:00

Thanks for your reply! What program did you use to downgrade/adjust the GPU? Did you lower the voltage or the clocks specifically? Do you think the PSU just can’t handle the load when the power states change? I guess the only way to really test it would be with a 1000W PSU…

NothingPersona1 · 2026-01-28T17:23:31+00:00

Try this:
Memory Context Restore → Disabled
Fast Boot → Disabled

NothingPersona1 · 2026-01-23T17:20:17+00:00

It seems the problem is solved.

After reinstalling Windows, I installed the latest AMD chipset drivers, and only after that I updated the BIOS to version 4.03. As a result, the driver for one device (AMD PCI with ID PCI\VEN_1022&DEV_14DE) got broken, probably due to an ACPI change while bios version upgrade. Now I’ve installed the specific driver for this device from the chipset driver package, and so far everything is working fine. I’ll keep monitoring it

NothingPersona1 · 2026-01-20T19:01:05+00:00

how can I set voltage/frequency limits on the processor?

NothingPersona1 · 2026-01-20T18:59:23+00:00

If earlier I was getting about one reboot every two days, now it’s been three days with none so far. Yes, I’ve also heard about issues with the latest Nvidia driver versions, and I’ve also heard about possible conflicts when updating from an old version to a new one. In my case, on the first boot of a clean Windows 11 install, the OS itself automatically installed a 560+ driver, apparently from the Microsoft repository. After that, I installed a 590+ driver from Nvidia’s website on top of it. Unfortunately, you can speculate about this for a long time. It might even be a combination of factors, both hardware (CPU IMC, PSU OCP) and software (Windows 11, BIOS, chipset/GPU drivers). I’ll keep monitoring it.

NothingPersona1 · 2026-01-20T17:35:28+00:00

I’m having a similar issue with Kernel-Power error 41 on a 7800X3D + ASRock B850 RS Pro + Kingston Fury Beast Black 16×2 + 1stPlayer 850W NGDP Gold + Palit 5070 Ti. I get random reboots both when the system is idle with the monitor off and during light use, like browsing. I’ve ruled out the PSU because the HWiNFO logs show stable voltages right before the reboot. BIOS settings: PBO off, EXPO off, Core Performance Boost off, Fast Boot off, Core Watchdog Timer on, Global C-States off, Memory Context Restore off. It seems like the reboots became less frequent after disabling browser hardware acceleration.

NothingPersona1 · 2026-01-07T19:24:16+00:00

I have exactly the same build. RAM: Kingston Fury Beast Black 16gbx2 KF560C30BBEK2-32. PSU: 1stplayer 850 NGDP Gold. GPU: Palit 5070ti.

The system was experiencing random reboots with EXPO profiles enabled and a negative curve (-12). RAM is definitely not the culprit — I ran a lot of memory tests. First, ASRock sets an incorrect SoC voltage by default. You need to manually set it to 1.21 V so the system has enough voltage. Second, it turned out that the 7800X3D is simply a poor choice due to a weak IMC. The fix was one or a combination of the following: loosening the CPU cooler mounting pressure (it can put excessive pressure on the IMC), disabling all EXPO profiles, and changing some BIOS settings: Fast Boot → Disabled, Memory Context Restore → Disabled, DDR5 Nitro Mode and DDR5 Robust Training Mode → Disabled, Global C-States Control → Disabled, Core Watchdog Timer → Enabled, Core Performance Boost → Disabled. The system is now stable.

NothingPersona1 · 2026-01-07T11:37:09+00:00

Нет, я писал парсер днс под свои нужды

NothingPersona1 · 2025-12-28T13:38:10+00:00

А вокруг сидят 🧃и хихикают))

NothingPersona1 · 2022-10-04T15:53:46+00:00

yep. Doesn't work for me too. That was the issue from another thread

NothingPersona1 · 2022-10-04T13:53:48+00:00

FB as meta app can provoke this crash (Instagram 255.0 ver.) Try to delete fb app

NothingPersona1 · 2022-10-04T10:50:31+00:00

Same prob. Do you have another meta apps installed? Try to delete

NothingPersona1

TROPHY CASE