The OC scan in ASUS GPU Tweak was used to retrieve the driver "profile" for the card when running the ASUS v472.12 driver downloaded from the ASUS website. The short answer is the v511.09 SD (studio driver) appear to yield stability on my system. I've had about 5+ hours in both FH and WZ without crashing. If you really fancy going for it, try and grab some "clean" logs (no crashes) and if / when BSODs.įirstly, many thanks to all those involved - and sorry for the delay in posting an update. This will keep the log files tidy.ĪIDA will generate a summary and a detail log, It would be cool if you can send both. Launch AIDA just before you launch FH5, close it when done. Try and log all the "interesting" stuff, like clock speeds, utilization etc. You select a location to save the logs to and what you want logging. This will activate the panel on the right hand side. My preference is NVI (nVidia Inspector) because it does not need installing.Īnd then select the "Logging" option, should be 5th one from the bottom. I think all the overclocking tools work the same way. What do you mean by logging the results? Nvidia inspector on the other hand is a program i am not familiar with, but i can use afterburner to adjust the clockspeed. GraphicsDrivers PlatformSupportMiracast : 1 Hive: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l PS C:\Windows\system32> Get-Item -Path "HKLM:\System\CurrentControlSet\Control\GraphicsDri vers" Hive: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\GraphicsDriversīasicDisplay BasicDisplayUserNotified : 1 PS C:\Windows\system32> Get-ChildItem -Path "HKLM:\System\CurrentControlSet\Control\GraphicsDri vers" Get-Item -Path "HKLM:\System\CurrentControlSet\Control\GraphicsDri vers" Get-ChildItem -Path "HKLM:\System\CurrentControlSet\Control\GraphicsDri vers" Sadly a BSOD eventually occurred, no stutter - it was an immediate thing. WZ even stuttered and felt like it was about to BSOD, then recovered. I thought I was onto something with TDR values and had around 4 hours of WZ without issue. I have been logging "everything" with AIDA64 and so far nothing out of the ordinary is occurring, no spiking values etc.
OBS STUDIO WINDOWS 10 BSOD SOFTWARE
I "think" this is a software issue, somewhere! I am keeping away from making any physical changes to the system because it was stable in W10. It's a fresh W11 install, all updates applied etc.
Once again, thanks for taking the time to think and post. These days I'm finding the gains minimal.
Change / measure / document rinse and repeat. In the past, If i wanted to overclock and test I would use benchmark tools (3d mark etc.). I used to really enjoy squeezing every little bit out of every piece of hardware. I need as few things as possible stealing / locking resources and trying to overlay things. This is one of the reasons why I do not use tools with an OSD etc. WZ is just something I started using to test / prove stability - and started to enjoy it. If i'm stable with OC off i will find it difficult to justify the time and effort to get an additional 30Mhz. You can get that kind of variance between benchmark runs. Realistically, the physical OC yields about 30Mhz. If I am stable I may try and achieve the same OC in software. If it comes back, I'll probably start logging data instead of using OSD. Monitoring "in game": For now, I'm going to leave "as is" and see if I get a BSOD. It wasn't!Īnother game: The only thing installed with a benchmark mode is FH5, PNG below.
At one point I thought it was my RAID card interfering with it. Performance: Yes, WZ performance is more than acceptable (when it works)!.Įrror message: Yep, it's certainly an odd one and it's something that would normally be observed with an extreme OC.
0 kommentar(er)
