NOTICE: This forum is mostly an archive, though new posts are allowed. Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by mdexter, October 02, 2014, 08:54:18 AM
QuoteOk the one program I have on my entire PC that will BSOD my PC is Cyberlink Power Director 12 when its producing the final movie. I run Core Parking with all Cores unparked to utilize 100% of those cores, so when Powerdirector is rendering a movie it will BSOD the program, 6 Cores and 6 Threads working there butts off, see screenshot called didnt-change.jpg whereby the watchdog process did not change, once those cores etc reach around 50% usage it will bsod at some point in the rendering.
Quote from: edkiefer on October 02, 2014, 06:52:10 PMI don't know on watchdog , never tried anything close to that , wait for support .But yes, that is voltage issue, what also you could do is use XTU were you can set app profiles to OC .So you have a low OC for xx aoo , cause its not stable at your higher OC . It changes OC per app .Thats only recommendation i can make
Quote from: DeadHead on October 03, 2014, 12:29:48 PMI wonder if the order you set your rules have anything to do with this? What happens if you swap the order around?Also, what happens you choose a greater difference than only 1%, for example 35% and 25%, any difference?
Quote from: support on October 07, 2014, 02:24:55 AMI am investigating this. I will have more information soon.
Quote from: support on October 09, 2014, 12:06:57 AMYou are correct, secondary rules for the same process are being wiped out at the config level. In some cases like this, they can appear to be 'merged' even.I am going to issue a fix in v22.214.171.124 beta, which I'll upload in a few hours/day (as soon as it's done).Thank you for reporting this!
Quote from: support on October 09, 2014, 11:18:48 PMProcess Lasso v126.96.36.199 beta is building now. It will be up in about 30 minutes.This build fixes this watchdong configuration issue reported here. Thank you again for reporting it!The bug would only manifest when the secondary rule matched a prior rule in both name and action.I continue to test the watchdog to make sure everything is kosher.
Quote from: Jeremy Collake on October 13, 2014, 10:25:40 AMI believe a secondary fix is needed before those watchdog rules will function right.It's a core adjustment to the watchdog system.I am going to be working on this in this next beta series, first build coming shortly.I will get there, and it'll do what you want w/o complications -- soon.
Quote from: BenYeeHua on October 14, 2014, 01:22:20 PMYup, I will said that you should try use the Hardware H.264 encode on the Intel, AMD or Nvidia at the max bitrate, it should be the nearly same quality as uncompressed video, while greatly reducing the CPU usage and I/O load on the RAM.---But ya, the best solution is still using another computer for capture and recording only, so your will always get no affect on the gaming and recording performance.
Quote from: Jeremy Collake on October 17, 2014, 01:02:54 PMI have been testing the current beta series and can say that the new final I'm about to release, v7.0.4, will absolutely properly handle these rules. Version 7.0.2 fixed the UI issue, but I then discovered that each rule would have only been applied once. So, finally, I think you will have what you need. If you find that to NOT be the case, please do let me know - don't spare my feelings, this is business, and I certainly need to know if something doesn't work. There are so many features that it's difficult for me to test them all, something I've taken new actions to address.