Blur Busters Forums

Just by playing the game on my PNY drive doesn't change anything. Maybe I have to move my windows drive to the PNY one if that is indeed the problem area. Also forgot to mention this since I wasn't sure about it. I don't do this, but I have in the past and thought it was weird. You know when you hold down the power button on a pc and it force shutdown? Well, when I have done it in the past, my computer will not turn back on until I cycle the power by turning off the psu. Not sure if this is normal behavior, I just thought I would mention it

Saphyen wrote: ↑

26 Apr 2025, 16:52

Just by playing the game on my PNY drive doesn't change anything. Maybe I have to move my windows drive to the PNY one if that is indeed the problem area. Also forgot to mention this since I wasn't sure about it. I don't do this, but I have in the past and thought it was weird. You know when you hold down the power button on a pc and it force shutdown? Well, when I have done it in the past, my computer will not turn back on until I cycle the power by turning off the psu. Not sure if this is normal behavior, I just thought I would mention it

Tried with windows on pny sdd and it's just the same

Saphyen wrote: ↑

26 Apr 2025, 16:52

Just by playing the game on my PNY drive doesn't change anything. Maybe I have to move my windows drive to the PNY one if that is indeed the problem area. Also forgot to mention this since I wasn't sure about it. I don't do this, but I have in the past and thought it was weird. You know when you hold down the power button on a pc and it force shutdown? Well, when I have done it in the past, my computer will not turn back on until I cycle the power by turning off the psu. Not sure if this is normal behavior, I just thought I would mention it

You still didnt show the other Tabs in LatencyMon.
And forcefully shutdown, shouldnt cause this. Sounds more like a Firmware Issue, does the same happen with BIOS Default Settings?

Sounds like it could be either a corrupt BIOS image or Intel ME. At least, I've only seen these symptoms when something is wrong with the BIOS. ( Faulty Settings, Faulty Image or ... )

Does the same thing happen with a different BIOS version?
What does the BIOS say for Intel ME version?
- If it shows 0.0.0.0 as Version, Intel ME is not initialized.

Saphyen wrote: ↑

26 Apr 2025, 23:42

The main game I play is Apex Legends so I ran the thing in it while moving my mouse around. I have also decided to redo the test as I did it in the firing range before and now I show it in an actual live match. It feels like my input constantly just cuts out and cuts back in over and over sometimes.

Saphyen wrote: ↑

26 Apr 2025, 23:42

Before this gpu I had a 3080 and it was a while back, but I don't remember being affected by latency issues with the old 3080 and PNY ssd combo. I haven't tried to use the pny for gaming really after I swapped it to be a backup drive. I came into this 3080ti for free through circumstances in late 2023. Other than my current one, I don't have access to any other gpus.

As boring as this may sound, it might be your GPU...
There could also be some BIOS sheningans going on, as St1cky mentioned

St1cky wrote: ↑

27 Apr 2025, 04:45

Saphyen wrote: ↑

26 Apr 2025, 16:52

Just by playing the game on my PNY drive doesn't change anything. Maybe I have to move my windows drive to the PNY one if that is indeed the problem area. Also forgot to mention this since I wasn't sure about it. I don't do this, but I have in the past and thought it was weird. You know when you hold down the power button on a pc and it force shutdown? Well, when I have done it in the past, my computer will not turn back on until I cycle the power by turning off the psu. Not sure if this is normal behavior, I just thought I would mention it

You still didnt show the other Tabs in LatencyMon.
And forcefully shutdown, shouldnt cause this. Sounds more like a Firmware Issue, does the same happen with BIOS Default Settings?

Sounds like it could be either a corrupt BIOS image or Intel ME. At least, I've only seen these symptoms when something is wrong with the BIOS. ( Faulty Settings, Faulty Image or ... )

Does the same thing happen with a different BIOS version?
What does the BIOS say for Intel ME version?
- If it shows 0.0.0.0 as Version, Intel ME is not initialized.

I reset the bios and yes it still happens. I have updated from 13~ to 16.02 through each update and it has been the same. It was like this when I had my old mobo as well. I looked in my bios and my intel ME version shows 16.1.30.2264. Is this the tab that you want shown?

Kind of finished tweaking Windows 11 for about a month now. I want to see how these results fare.

Hyote wrote: ↑

21 May 2025, 02:45

Kind of finished tweaking Windows 11 for about a month now. I want to see how these results fare.

It would be nice if you could mention the test environment you've had when running this xtw report.
It seems that you've had some game running (dxgkrnl.sys is graphics-related driver).

As for what each metric in xtw means, here's a explanation from the creator (valleyofd00m):

Total Elapsed Time (usecs / microseconds) — the sum of elapsed time for each driver
there is also Count which just tells you how many times a ISR/DPC was scheduled for that driver but it can be kinda useless because you don't know how long each ISR/DPC will take to execute

interval (ms) — how often the ISR/DPC is scheduled in milliseconds
e.g. 1ms is 1000 times a second, 0.125ms is 8000 times a second, it's the same as mouse tester (or just polling rate in general)
you don't want unimportant drivers to be scheduled often, so a higher value is a good indicator.

Elapsed Time (usecs / microseconds) — how long it took for the ISR/DPC to execute
e.g. end timestamp minus start timestamp

kyube wrote: ↑

21 May 2025, 14:18

Hyote wrote: ↑

21 May 2025, 02:45

Kind of finished tweaking Windows 11 for about a month now. I want to see how these results fare.

It would be nice if you could mention the test environment you've had when running this xtw report.
It seems that you've had some game running (dxgkrnl.sys is graphics-related driver).

As for what each metric in xtw means, here's a explanation from the creator (valleyofd00m):

Total Elapsed Time (usecs / microseconds) — the sum of elapsed time for each driver
there is also Count which just tells you how many times a ISR/DPC was scheduled for that driver but it can be kinda useless because you don't know how long each ISR/DPC will take to execute

interval (ms) — how often the ISR/DPC is scheduled in milliseconds
e.g. 1ms is 1000 times a second, 0.125ms is 8000 times a second, it's the same as mouse tester (or just polling rate in general)
you don't want unimportant drivers to be scheduled often, so a higher value is a good indicator.

Elapsed Time (usecs / microseconds) — how long it took for the ISR/DPC to execute
e.g. end timestamp minus start timestamp

Thanks for checking it, I actually had nothing open while running the script, dxgkrnl is my doing.

Saphyen wrote: ↑

27 Apr 2025, 20:55

St1cky wrote: ↑

27 Apr 2025, 04:45

Saphyen wrote: ↑

26 Apr 2025, 16:52

Just by playing the game on my PNY drive doesn't change anything. Maybe I have to move my windows drive to the PNY one if that is indeed the problem area. Also forgot to mention this since I wasn't sure about it. I don't do this, but I have in the past and thought it was weird. You know when you hold down the power button on a pc and it force shutdown? Well, when I have done it in the past, my computer will not turn back on until I cycle the power by turning off the psu. Not sure if this is normal behavior, I just thought I would mention it

You still didnt show the other Tabs in LatencyMon.
And forcefully shutdown, shouldnt cause this. Sounds more like a Firmware Issue, does the same happen with BIOS Default Settings?

Sounds like it could be either a corrupt BIOS image or Intel ME. At least, I've only seen these symptoms when something is wrong with the BIOS. ( Faulty Settings, Faulty Image or ... )

Does the same thing happen with a different BIOS version?
What does the BIOS say for Intel ME version?
- If it shows 0.0.0.0 as Version, Intel ME is not initialized.

I reset the bios and yes it still happens. I have updated from 13~ to 16.02 through each update and it has been the same. It was like this when I had my old mobo as well. I looked in my bios and my intel ME version shows 16.1.30.2264. Is this the tab that you want shown?
Screenshot 2025-04-27 202447.png

How long did you run it and please show everything, i want to see cpu tab too -DONT use very old Latencymon Versions!

Wdf01000.sys insane high, depends on how long you measured.

What you can also see is that all values ​​are relatively high. Even HDAudBus and nvme, which should normally be low. Is there something running in the background?

- Reset BIOS ( Disable only C-States, Disable any Auto OC, use Intel Stock Power Settings ( old asus boards in example had issues with very high power settings, causing massive issues. Maybe Update BIOS latest, Disable TPM and SecureBoot, i saw issues with TPM and Latencymon )
- Unplug Devices ( Do Measurment without HW connected, without !GPU!, Disabled NIC, Disconnected Devices )
( And do again measurment, best do it in safemod boot, per xperf or similiar, since latencymon doesnt work there )

You dont need to downgrade BIOS, since like 90% it will not downgrade your intel me firmware! Only BIOS.

How did you update Intel ME? - Never Update Intel ME or BIOS if PC is running fine.
( BIOS Flash + ME updates can have very negative effects and it is almost impossible to get the original condition back. )
"have updated from 13~ to 16.02"

The most important thing is to first find out what is causing the problem, whether it is a device or software.