d3anio97

Personally I think this dude is bullshi^^ing us! I did the math and for the battery to drain as fast as they're claiming it would HAVE to be able to deliver 15.6A of current for it to drain that fast! that's NOT gonna happen from a battery that small!! The MOST current I've had from a 2600mAH battery from a phone is 4.8A under a dead short from a full charge. The only cells that could even push that current are the 18650 Li-Ion cells. The same ones used in a laptop battery pack...

Both legacy and Studio have been known to cause issues, but it's a huge oddball because I can record with higher settings than I stream at and it goes completely flawlessly. I did everything that's in the link you sent and it had no effect whatsoever. Even dropping the stream settings to 1024 x 600, 1000KBPS at 30FPS did nothing to resolve it, besides make the stream look like crap!! It has me completely stumped atm!

And this is the log... [Attached to make posting easier] What I did notice is that every time OBS craps out there's an encoder overflow. I can't seem to find the exact origin though as it doesn't happen while recording. debug.log

Alright... so I used the new settings AND bound to ethernet with no improvement. I'm gonna add the log to my next post.

Ok, so I managed to fathom that somehow it's while streaming only that the issue happens. I altered the settings and did a test recording with a round of Rocket League. OBS had no issues with recording the full match without dropping a single frame. HOWEVER... when I moved onto testing with a livestream with the altered settings (Again, they worked perfect while recording) and within 20 seconds, OBS had frozen and started lagging. So I'm gonna bind OBS to the primary network adaptor, attempt to stream again and pull the important data from OBS' log if it fails again.

I'll give dropping the framerate and bitrate a shot as well as altering the quality balance on the encoder and see if that works... I'll get back to ya with the results

Just so I can debunk this first, the issue absolutely is NOT related to Twitch itself or my bandwidth. So it appears that I have another issue related to livestreaming... To be more specific, whenever there's the slightest amount of load on the encoder while recording or streaming, it causes OBS to freeze and in turn also creates a HUGE lag spike in the game with framerates dipping as low as 80% or causing said game to crash. I'm gonna check to see what the log has to offer but so far these are my settings; INTERNET: Upload: 10.2MBPS Download: N/A for this post Base resolution; 2560 x 1440 Scaled resolution; 1280 x 720 with Lanczos filtering Framerate: 50 FPS Bitrate: 3500KBPS Encoder: AMD AMF (aka VCE) Encoding device: GPU 0 (AMD Radeon HD 7950) CFR is enabled Keyframe interval is set to 2 the x264 preset is set to "veryfast" Encoding profile is set to "Main" I've used these same settings for a good 2 years and they've never caused issues. Even when I had a weaker system and less upload bandwidth, so I know for a fact my system is capable of handling the encoding without a problem. The link is a clip from today's VOD, where I attempted to get Rocket League working. Sadly, whenever there was even the slightest bit of motion, it began to lag and freeze with no legit explanation why. I've tried a bunch of other settings to no avail besides making the image quality go through the floor!! https://www.twitch.tv/d3anio97/v/84096495 I also have the raw footage stored on my computer, so I'll upload that to MediaFire so you can take a look if needs be... but it's literally just as bad as the VOD!

Yeah, it was defo board related. I have the GPUs and power supply in a different machine and they're humming away without a problem... Only downside is I'm stuck with a Core2 Duo E6850 and 4GB DDR2 for 6 weeks!! At least I can still play my less CPU intensive titles in 1440p though!! That would bug me to hell and back if I was stuck without Goat Simulator XDD

Yeah... the brightside is that my hard disks, SSD, fan controller and both my GPUs live to livestream again XDD It's not too hard to find a cheap 990FX board nowadays though, so it shouldn't be more than a few weeks or so before I have BLU3_5N0W (That's my system's codename btw) back in fighting form

OKAY... I CAN NOW 100% WITHOUT A SHADOW OF A DOUBT CONFIRM THAT THE PROBLEM IS MOTHERBOARD RELATED. This means 2 things: 1: I'm totally screwed for 6 whole Weeks!! 2: I get a motherboard upgrade But the fact I'm getting a board upgrade on the same CPU is depressing T^T I at least wanted to wait for AMD's "Zen" chips to arrive before I jumped the gun and get a new board! As for confirmation of the issue?: I took 2 power supplies. The one in my rig and a spare I had lying around that I knew works 100%. I had my main supply powering the GPUs, hard disks and the secondary specifically powering the motherboard... Whichever power supply cut out first would either show a different issue or confirm my belief... The result was that after 30 seconds of AIDA64... the power supply controlling the motherboard lost power!! This reinforced my thought that the motherboard had issues... However, the issue appears to manifest itself as a PCI-e VRM issue and not a PS_ON latch issue like I initially thought!! This means I'm now gonna have to get a new board so I can use the system again. Wish me luck on not gong stir-crazy without my fix of 1440p Goat Simulator!!

I highly doubt it's power supply related, and the reason I can verify that has just happened... 1: The system has a 750W power supply. the system draws 85-680W from the wall (that's idle to load) and the power supply can handle a power input of about 780W with an output of 750 continuous. 2: the system has just cut out again, but this time, I was browsing Facebook when it happened. This has lead me to the suspicion that it's related to the latching circuit that sends +5VSB to ground, which should trigger PS_ON and send a PS_OK signal to the motherboard... which it does, but there's a high chance there's an issue with that section of the board since the entire thing loses all power for a split second before the USB ports get their +5V back (The USB ports are powered via +5VSB when in standby mode. Now, that doesn't mean I'm not gonna look at this more in-depth. I have a spare power supply that's got EPS and 20+4 power, so I'm gonna use that to power the board, then all my drives and the GPUs will be powered off the main power supply. If I lose power to the disks and GPUs then I know there is a fault with my power supply. I'll probably look into having it RMA'd if that turns out to be the issue. If not, and the known working PSU has the same issue, then I know it's an issue with the PS_on latching circuit and I need a new board... let's see how things go!!... #990FXHYPE XDD

ok, UPDATE: 40 minutes in and it just died again... I might try reinstalling Windows or refreshing it and see if anything changes

ok, so I have the system "idling" (i.e no games running, just streaming a single screen to Twitch), Attempt 1 caused the system to power off literally 5 seconds into streaming, and the seconds attempt (after having to run a repair because the shutdown lead to a crash at boot) seems to be doing okay... I'm 36 minutes in as of posting this and I've not (fingers crossed) had the system power off yet!! I'll report back if everything turns to $h*t

Totally up for winning something this badass!! And the fact it doesn't need to (but can be) attached to a wall or ceiling makes it an extremely compelling option for someone doing presentations or gaming comps on the go with very little space to do them!! Also... Spec sheet says a 100W LED... That things' not gonna blow any time soon unlike the Xenon lamp of a DLP!! Also a "Bit less explosive" if the lamp ever wears out!!

The troubleshooting steps mostly don't apply here because I have AMD GPUs, and the featuresets are slightly different. the MA scaling is a little better with OBS and the AMF capture compared to NVENC with SLI. HOWEVER... after resetting and tinkering with the render settings, I got one version of OBS to work for 20 minutes and no shutdown... I'm gonna test more extensively with both OBS and OBS studio before I mark this as solved... but it's looking promising so far!