/vt/ - Virtual Youtubers

>>43604498
well, it'll be easier for you now too! clearly hard at work with important business
>>43604507
it's a bit more complicated than that. was running the latest drivers. I don't know that the VRAM was at 100C for certain, I do know that Tj was 100C, and that the fuckin fan wasn't spinning at all. Meaning the VRAM was likely significantly hotter than that. I thought the GPU had died.
>AMD
>overclocking utility thing in their driver is called "wattman" for reference
>didn't overclock my card at all - au contraire - undervolted and underclocked, also used it to make the fan curve more aggressive, because it's a "zero fan" piece of shit where the fan doesn't kick in at all until like 70C
>AMD drivers are shit
>ANY kind of driver fault, ANY, including, "oh, Chrome had a booboo and your screen went black for a second? driver fault" results in "WATTMAN HAS RESTORED DEFAULT SETTINGS DUE TO A CRASH"
>meaning the driver itself actively works against you by restoring the default fan curve and "overclocking" your card in this case
>be me
>in VR, extremely low GPU utilization, but the video decoder is active (kek)
>VRAM balls to the wall
>video player exit
>render VR world
>browser has a booboo outside of VR
>suddenly GPU usage
>fan curve reset to something it actually shouldn't have
>measured junction temp was 100C, don't actually know what the VRAM temp was
>VRServer.exe has crashed
>take headset off
>both monitors look like picrel
>BSOD 2 seconds later
So yeah, I don't take it to chance anymore. Afterburner has my fan curve set to "plaid" all the fucking time. Wattman can bitch and moan all it wants, because Afterburner will never change the fan curve unless I ask it to.
>>43589137
chuba of your choice controlnet'd into "that" picture of Linus