No, if you’re referring to the dxdiag, the drive labled D: is my SSD. I only have two other hard drives that are just used for data - one of them is just partitioned in two (E: and F: there). As far as those impacting my machine’s performance - I have no idea why that would be the case, especially since I’m not even running anything off of them anymore.
–
As far as Pawg’s suggestions: For what it’s worth, I’ve played the game in windowed mode just fine from 2004 up until I got this bug in 10.1. Vsync keeps the game from having screen tearing. With it disabled, there’s tons of it which is why I keep it on. That being said, this bug still occurs when playing the game with both vsync on and off, as well as both fullscreen and windowed mode.
I did also try running it fresh when I reinstalled to my SSD - that means a brand new install, brand new UI, all default options (including cvar resets). I’ve created another vid showcasing all of this, this time in Dornogal.
This is a fresh install, full screen, default UI, default cvars. You can see the game plays normally for about two minutes until I go through the training dummy area a second time. It only impacts that one specific area - even going back by the auction house is fine. Returning to the dummy area triggers the bug again, and brings it back down until I use my gxrestart macro to fix it.
I want to stress once more that WoW is the only game that has given me any type of issues ever since this bug started in 10.1. All other Blizzard games run fine. Other MMOs still run perfectly fine. No issues in lag-heavy areas in any other games. It’s just WoW.
Edit: Also I don’t know if it’s relevant but I also have that bug where the TWW video plays every time I log on to one of my 70s.
I know the error section in your DXDIAG report was blank last time, since you said you recently upgraded Windows, but now would be a good time to run it to and upload it to pastebin again. It’s been plenty long enough to have entries in the error section again, since even perfectly healthy Windows installations will still produce soft-errors for various OS related things from time to time. Ironically, I just checked my log and it’s empty as well, even though I updated to 24H2 weeks ago? Maybe they finally fixed some of the MS related errors that would randomly bloat the logs.
It’s possible you have some kind of memory leak issue(wouldn’t likely be coming from WoW, but rather, from OS related things like security softwares and other external programs)
Another possibility is that something is triggering your CPU into a lower performance state like power plan settings or maybe some transient spike in temperatures (talking on the 1-100ms scale that won’t report in apps that read the temperature) is triggering it to thermally throttle.
All I know is that what you’re experiencing doesn’t seem to actually be the result of WoW itself and is a behaviour I haven’t seen in the WoW client yet. I’ve been doing this for quite some time, have a boatload of experience developing/debugging/QA with other game engines and it’s leaving me scratching my head.
The only last suggestion I can give would be for you to try installing an older version of the Nvidia drivers? Maybe go back a couple branches to around the 565, 560 or 555 branches? It’s possible some of the recent changes to fix issues with Win11 24h2 aren’t meshing well with the archaic Windows 10 builds.
Yeah, I’ve tried quite a few different ones. Most recently I tried the 528.49 which was a recommendation from another thread having issues. I actually thought that may have fixed the problem because I could not reproduce the bug at the Valdrakken spot. That actually led me to resub just to check Dornogal - where I instantly fell victim to both the bug and extreme disappointment.
At this point I’m left with no other options than to assume there is some faulty hardware somewhere… but that still doesn’t explain why it hasn’t affected any other games yet.
Yeah it’s showing a bunch of LiveKernelEvents, RADAR_PRE_LEAK_64 for Overwatch and AppHangTransient for Hearthstone. The LiveKernelEvent errors are usually driver related, but can be hard to pinpoint down because they can come from something as simple as a bad USB device or device driver, but can also come from GPU driver related issues as well.
Check your motherboard manufacturer’s support page for all the most recent drivers for everything. Even something like an unused Realtek soundcard driver can cause issues with a system if the driver is out of date.
I don’t know if it’s related at all but I’ve been having a weird issue with my USB devices for a long time now. Every once in a while when I am browsing the net or watching media all of my USB devices will stop working for about 5 seconds and then come back on.
I’ve searched a lot to try to find a fix for this issue but I was never successful. I just learned to live with it because it’s never ever happened when I am playing a game - it only happens when I am browsing the net or doing other simple tasks like chatting on Discord. It still happens on a freshly installed OS with a formatted drive - so I just assumed it was a benign issue with my case/ports.
But yeah, like I said it’s never happened when I am playing a game - which in itself is very strange.
Is your usb device/s set to turn off after a set period. I had a problem where usb devices were turning off after 5 minutes because of a power saving feature for laptops. My system is not a laptop.
That’s it. That fixed the problem, and boosted my framerate where I didn’t notice it was lacking in other games.
I don’t know how or why this worked, but it did. I spent so long flying around Dornogal tonight trying to reproduce the bug - because I couldn’t believe THAT would be the fix. And it never bugged out. A two-year long problem solved by something so simple. I thought I was gonna lose my mind trying to find the fix.
Anyway, thanks everyone here for all the suggestions and resources during this trip.
Hell yeah, glad to hear you fixed the issue! I had a feeling it was usb device/driver related, which is why I brought it up in my last post.
It probably just reinstalled the drivers for it since it saw it as a “new device” and maybe unscrewed some settings that were bugging out with the other port.
Also, a lot of times, PCs will have multiple USB hubs to them. Like you might have a hub for 3.2, 2.0 and so on. So if one hub is bugging out, moving it from say a 3.2 to a 2.0 port might fix things since it’s running on a different set of hardware and drivers. Front panel hubs can also be culprits if the case company skimps on components and grounding.
If you’re on the tech savy side, you can go into your device manager->view->hidden devices and go around removing any old copies of the devices. Let’s say your PC has 6 usb slots and you plug your mouse into one, then another, then another and so on, and then leave it in the 6th port. Within the device manager, you’ll likely see 5 hidden copies of the mouse and 1 active copy of it. You can safely remove the hidden duplicates, but as soon as you plug the mouse back into another port, it will make another copy.