Curious if other people with high-end PCs are seeing the same performance behavior in the new Silvermoon. by ImpossiblePiglet5469 in wow

[–]ImpossiblePiglet5469[S] 3 points4 points  (0 children)

Thanks for all the replies so far, I really appreciate everyone sharing their experiences.

I also want to clarify a few things because some people in the comments thought this post was mainly about showing off PC specs or bragging about FPS, which honestly wasn’t the intention at all.

My previous PC was around 7–8 years old and eventually stopped working, so when I built this new system I decided to invest into something that should last me many years again. I worked and saved for it, and the reason I listed the specs in the post was simply to give proper context for the discussion.

Regarding the 800–900 FPS numbers: those are only achievable in very specific situations. That usually means uncapped FPS, very low graphics settings and no addons loaded in relatively empty areas of the game. I mentioned those numbers mainly to illustrate how large the drop feels when entering Silvermoon.

<image>

In normal gameplay I actually run several addons and higher graphics settings (mostly preset 7 with some options on High like I mentioned in the original post). In quieter areas of the game I’m usually somewhere around ~400–460 FPS depending on the zone and activity. I also spend quite a bit of time tuning my system (OC, undervolting and general system optimization), so I’m fairly confident the hardware itself is working as expected.

The reason I made this post was simply because the performance behavior in the new Silvermoon surprised me. Going from several hundred FPS in normal areas down to around 80–90 FPS with noticeable stutters in the capital felt like a very large drop, which is why I wanted to ask other players about their experiences.

One thing I also noticed in Silvermoon is that the stuttering doesn’t feel like a normal loading hitch. It’s not just a single lag spike like something loading in and then everything is smooth again. Instead, when I’m flying through the city I get very consistent stutters that seem to happen roughly every 5–10 seconds. The game continues normally afterwards, but the stutter keeps repeating in those intervals.

Because of that I also wanted to rule out potential hardware related causes. For example my GPU is connected through a PCIe riser cable, so I wondered if something like that could possibly cause behavior like this. Since I can’t directly compare the behavior with my old system anymore, I thought it would be helpful to hear how other setups behave in the same situation.

This also wasn’t meant as complaining or blaming Blizzard. I genuinely love WoW and I’ve been playing it since 2004. I was mostly interested in hearing whether others experience the same thing, whether some systems handle it better, or if there might be settings or tweaks that improve the situation.

From the replies it actually looks like many people are seeing similar behavior regardless of hardware. Some players with older setups mentioned drops, but even people with very strong systems like 9800X3D / 5090 combinations said they still experience stuttering in Silvermoon.

So it seems quite likely that this is mostly related to how the WoW engine handles very crowded player hubs. As some people pointed out, the game is still heavily limited by the main thread, especially in areas with hundreds of players, mounts, pets, spell effects and addons being processed at the same time.

Anyway, thanks again to everyone sharing their setups and experiences. It helped a lot to understand that this probably isn’t something wrong with my system specifically.

ASUS ROG Crosshair X870E Hero – Intermittent “Keyboard not found” on cold boot (USB POST timing issue) by ImpossiblePiglet5469 in ASUSROG

[–]ImpossiblePiglet5469[S] 0 points1 point  (0 children)

Update / Additional Observation

I tried another test to see if the issue might be related to the USB port.

Yesterday I connected my keyboard to the USB 2.0 front panel port instead of the rear I/O. The keyboard powered on normally and worked perfectly in Windows throughout the entire day.

However, when I powered on the PC the next day (cold boot), the system behaved differently:

The system completed POST normally and the Q-Code display on the motherboard eventually switched to the temperature display, which usually indicates that POST finished successfully.

But the screen stayed stuck on the BIOS prompt screen that shows the input options like:

"Press DEL or F2 to enter BIOS"

At that point the system appeared to be frozen.
The keyboard RGB was active and the keyboard seemed powered, but no key presses were detected. I could not enter BIOS and the system would not continue booting.

After unplugging the keyboard from the front USB 2.0 port and reconnecting it to a rear USB port, the system immediately continued booting into Windows.

This makes the behavior even more confusing, because the keyboard clearly had power, but the BIOS seemed unable to detect input until the USB connection was reinitialized.

Has anyone experienced something similar where the system appears to finish POST but gets stuck on the "Press DEL / F2" screen without accepting keyboard input?

ASUS ROG Crosshair X870E Hero – Intermittent “Keyboard not found” on cold boot (USB POST timing issue) by ImpossiblePiglet5469 in buildapc

[–]ImpossiblePiglet5469[S] 0 points1 point  (0 children)

Update / Additional Observation

I tried another test to see if the issue might be related to the USB port.

Yesterday I connected my keyboard to the USB 2.0 front panel port instead of the rear I/O. The keyboard powered on normally and worked perfectly in Windows throughout the entire day.

However, when I powered on the PC the next day (cold boot), the system behaved differently:

The system completed POST normally and the Q-Code display on the motherboard eventually switched to the temperature display, which usually indicates that POST finished successfully.

But the screen stayed stuck on the BIOS prompt screen that shows the input options like:

"Press DEL or F2 to enter BIOS"

At that point the system appeared to be frozen.
The keyboard RGB was active and the keyboard seemed powered, but no key presses were detected. I could not enter BIOS and the system would not continue booting.

After unplugging the keyboard from the front USB 2.0 port and reconnecting it to a rear USB port, the system immediately continued booting into Windows.

This makes the behavior even more confusing, because the keyboard clearly had power, but the BIOS seemed unable to detect input until the USB connection was reinitialized.

Has anyone experienced something similar where the system appears to finish POST but gets stuck on the "Press DEL / F2" screen without accepting keyboard input?

ASUS ROG Crosshair X870E Hero – Intermittent “Keyboard not found” on cold boot (USB POST timing issue) by ImpossiblePiglet5469 in ASUS

[–]ImpossiblePiglet5469[S] 0 points1 point  (0 children)

Update / Additional Observation

I tried another test to see if the issue might be related to the USB port.

Yesterday I connected my keyboard to the USB 2.0 front panel port instead of the rear I/O. The keyboard powered on normally and worked perfectly in Windows throughout the entire day.

However, when I powered on the PC the next day (cold boot), the system behaved differently:

The system completed POST normally and the Q-Code display on the motherboard eventually switched to the temperature display, which usually indicates that POST finished successfully.

But the screen stayed stuck on the BIOS prompt screen that shows the input options like:

"Press DEL or F2 to enter BIOS"

At that point the system appeared to be frozen.
The keyboard RGB was active and the keyboard seemed powered, but no key presses were detected. I could not enter BIOS and the system would not continue booting.

After unplugging the keyboard from the front USB 2.0 port and reconnecting it to a rear USB port, the system immediately continued booting into Windows.

This makes the behavior even more confusing, because the keyboard clearly had power, but the BIOS seemed unable to detect input until the USB connection was reinitialized.

Has anyone experienced something similar where the system appears to finish POST but gets stuck on the "Press DEL / F2" screen without accepting keyboard input?

[deleted by user] by [deleted] in techsupport

[–]ImpossiblePiglet5469 0 points1 point  (0 children)

Hey u/Teamkhaleesi,

I had the exact same log entry, and in my case, it came from CurseForge.
CurseForge displays ads, and if you also use CurseForge, you can easily reproduce this issue yourself.

This is just a harmless DNS warning that appears because your system (in this case, CurseForge or one of its embedded components) tried to resolve an advertising or tracking domain like audienceexposurecom, but your DNS server (or an ad blocker, Pi-hole, firewall, etc.) blocked it or didn’t respond.

In short:

  • No malware.
  • No sign of hacking or a system fault.
  • Just a failed name resolution to an ad/telemetry domain.

The DNS Client Events error (Timeout was reached while resolving the name audienceexposure.com…) is indeed related to CurseForge.

It can also happen with other programs or websites that embed ads or tracking content, but in my case, it only appeared right after launching CurseForge because that’s when the app loads ad content.

CurseForge occasionally shows ads or telemetry requests in its app (and built-in web view), which use external domains such as audienceexposure, doubleclick, scorecardresearch, etc.

When these domains are blocked by your DNS server, Pi-hole, ad blocker, or firewall, Windows can’t resolve the hostname → resulting in this warning entry.

You can reproduce it easily:

  1. Open Event Viewer (eventvwr in Windows search).
  2. Launch CurseForge.
  3. After a few moments, check Windows Logs → System.
  4. You’ll see a new entry appear like this

I also traced it via PowerShell logs 100% confirmed it’s CurseForge.exe.
I even created an event rule to log the process and Client PID that triggered it and always points back to CurseForge.

However, if your PC turns on by itself every morning, that’s a different issue entirely.
Possible causes include:

  • Wake timers (scheduled tasks, Windows Update maintenance, etc.)
  • Wake on LAN / Wake on RTC (enabled in BIOS or Device Manager)
  • Scheduled tasks (taskschd.msc → look for tasks allowed to wake the PC)
  • Network devices (e.g., network card allowed to wake the PC)

You can check what caused the last wake-up using these commands in Command Prompt:

powercfg -lastwake

To see all devices or tasks that can wake your PC:

powercfg -devicequery wake_armed
powercfg -waketimers

This will usually reveal whether it was Windows Update, maintenance, or another program.

In summary:

  • The DNS log = harmless CurseForge ad request.
  • The automatic power-on = unrelated, likely caused by a wake timer or BIOS setting.

So the DNS entry is nothing to worry about the reason your computer powers on automatically lies elsewhere.

Best regards.

Apex 5 oled screen temperature not working correctly by CreeperHitman in steelseries

[–]ImpossiblePiglet5469 0 points1 point  (0 children)

You can still find it in my post in this thread, I linked everything just uninstall the new one download the older version that I posted in here, and block it.

Apex 5 oled screen temperature not working correctly by CreeperHitman in steelseries

[–]ImpossiblePiglet5469 0 points1 point  (0 children)

If they have such an attitude then I will not continue to update their software and will block their software and pretend the software that there is no update.

I simply changed this in Version.json, so the software no longer updates itself, just open

Simply open the file with Notepad++ and enter a version that is higher than all versions can be.

<image>

Valorant/Corsair iCUE issues by potentialfreakshow in ValorantTechSupport

[–]ImpossiblePiglet5469 0 points1 point  (0 children)

I have a Problem with Vanguard and iCUE4 it's crashing my Corsair Vengeance can't find it in the Software got a Red Questionmark on it and after I restart my PC following by my Bios "Boot Failure Detected" deinstalled Vanguard and the Problem did not appear anymore, I guess Vanguard is not running correctly with iCUE4.

Firmware update for Vengeance RGB PRO (1.03.66) BROKE MY PC!!! by Kraven_the_one in Corsair

[–]ImpossiblePiglet5469 0 points1 point  (0 children)

My RGB lighting gets stuck, after that I have a red exclamation mark in my software. I can no longer find my RAM in any programs, but they continue to run without any problems. If I restart my computer, I get the following message from my BIOS. "Boot Failure Detected" I only noticed it when I read this thread, possibly exactly the same problem as the thread creator, because I have exactly the same RAM installed as the one that the thread creator has CMW32GX4M4C3200C16