Date & Time: Ever since 6.3
Frequency: Enough to make me think it's my hardware's issue till I realized something else was off on the forums.
World Name: Tonberry , Elemental
Character Name: Denser Lorj
Party or Solo: Party, should still affect solo
In-Game Time: roughly 11:06 A.M.~ ET / 11:25 A.M.~ GMT +0
Area and Coordinates: Pharos Sirius , I had a similar issue at the start of 6.3 day 1 which prompted me to restart my PC
Steps:
1. Exist for a certain amount of playtime OR
2. Logging into the game
3. Proceed to see an unusually high amount of GPU usage

GPU performance change before and after you started having the issue:

GPU: NVIDIA GeForce RTX 2060 SUPER
Driver Version: 516.94
CPU: Processor AMD Ryzen 7 3700X 8-Core Processor, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
RAM: 16384MB RAM
Hard Drive: I don't know which detail was wanted, SSD, NTFS MP510 480 GB, assuming what drive launched the game
OS:Microsoft Windows 10 Enterprise
OS Version: 10.0.19044 Build 19044
Graphics Settings: High
FPS Limit: 60 fps
Limited when away/inactive

Nvidia's power settings had been set to "High performance" before this.
I do not intend to disable Nvidia overlay or swap off borderless windowed.
The other tool was MSI Afterburner and Nvidia's GPU activity for programs which didn't do much, mostly in the event that there was a process the task manager couldn't pick up on the GPU, I don't think it did this time.

Ignore the high memory, it's not unusual for how many tabs of google + leaving adobe vegas/photoshop in the background which I believe shouldn't have an effect.

https://gfycat.com/amusingquarrelsomebarracuda

https://cdn.discordapp.com/attachmen...5564/image.png likely not accurate but it's what I've noticed.

https://cdn.discordapp.com/attachmen...4794/image.png I didn't restart my PC this time, only the game. Launch of 6.3 had an issue where it persisted unless I restarted the PC.

There are many things that make it difficult to diagnose, I think that there are others that are affected in a way by this.
I'd probably update drivers later on in case it happens again, leaving it here in case someone else has a similarly random issue.