Bug Report Stopping Recording Stuck

[Sigma 27]

I've read threads about this before and I can't seem to solve the issue.

I press the stop recording button, it says 'stopping recording' and won't change, I terminate the program to stop it and thus I lose part of my recording. Today I lost 90% of what I recorded. This seems to happen randomly, I can recreate the bug, but it's random.

I've attached a log.

Any assistance on this matter is appreciated, this issue is driving me nuts.

 

[koala]

21:12:28.151: [NVENC encoder: 'recording_h264'] nvenc_encode: Error encoding: Unknown error occurred 21:12:28.267: Error encoding with encoder 'recording_h264'
I saw this kind of error before, and as far as I remember, this may be a hardware error on the GPU in the nvenc circuit. In case you overclocked you GPU: revert the overclock. This includes "OC" editions. And check the GPU fans and the GPU temperature to avoid overheating.

 

[Sigma 27]

21:12:28.151: [NVENC encoder: 'recording_h264'] nvenc_encode: Error encoding: Unknown error occurred 21:12:28.267: Error encoding with encoder 'recording_h264'
I saw this kind of error before, and as far as I remember, this may be a hardware error on the GPU in the nvenc circuit. In case you overclocked you GPU: revert the overclock. This includes "OC" editions. And check the GPU fans and the GPU temperature to avoid overheating.

I've read a similar thing while searching other threads. I've never changed anything that would enable overclocking on my GPU and my hardware knowledge is limited. Fans may need a bit of a clean but otherwise I think the temp is fine. I have no idea what you mean by "OC editions" as I've never heard of the term myself. To be honest I have no idea where I'd go to check the overclocking options.

I appreciate the reply but due to my lack of understand I'm still at square one.

 

[Harold]

Why are you using CBR instead of CQP for recording?

 

[koala]

Many GPU card manufacturer sell "OC editions" of their cards. They come factory-overclocked. You identify them by spotting a "OC" in the name of the graphics card. It's a questionable practice, because not every card is running as stable as any non-overclocked one. If you got none of these, you have some different issue. The only certain thing about your issue is that the nvenc circuit on your GPU failed one minute into the recording, thus leaving a broken video file. That failure is unusual and extremely rare.

 

[Sigma 27]

Why are you using CBR instead of CQP for recording?

I wasn't able to get CQP working for audio quality properly. After a few hours across 2 days of fiddling with all the settings I finally got it working with CBR and had no interest in confusing my self more and giving my self a headache.

I have little knowledge with the differences between CBR & CQP, in the end I got one to work for me and there wasn't a problem I noticed. I'm unsure if my problem is related to CBR or not.

 

[Sigma 27]

Many GPU card manufacturer sell "OC editions" of their cards. They come factory-overclocked. You identify them by spotting a "OC" in the name of the graphics card. It's a questionable practice, because not every card is running as stable as any non-overclocked one. If you got none of these, you have some different issue. The only certain thing about your issue is that the nvenc circuit on your GPU failed one minute into the recording, thus leaving a broken video file. That failure is unusual and extremely rare.

I see. I'm not sure if mine is that or not. Yeah I noticed the video file only had 55 seconds out of 30 minutes. It has happened a few times.

My computer has a few unusual and rare problems and several I can't fix, but that's a different case entirely and regarding windows 10.

 

[Harold]

The nvenc settings have no control over audio quality, as nvenc is purely a video encoder. Using CQP or CBR in your nvenc settings has no bearing on audio quality.
A lot of problems that come up with recording come from using nvenc in CBR mode.

Use CQP as your rate control with a CQP value of about 16.

 

[Sigma 27]

The nvenc settings have no control over audio quality, as nvenc is purely a video encoder. Using CQP or CBR in your nvenc settings has no bearing on audio quality.
A lot of problems that come up with recording come from using nvenc in CBR mode.

Use CQP as your rate control with a CQP value of about 16.

Thank you for this information, it's things more clear to me. I'll change it to CQP and see if I can get it working properly tomorrow. I'll report my results tomorrow, but I can't report whether or not the issue will be fixed for me as it happened randomly to begin with. Once I've made the changes, only time will tell if this thread ends after this message or carries on with the issue persisting.

Again, thank you for the help. With luck this will be one problem i've run into that I can actually consider fixed.

 

[Sigma 27]

I've made the changes suggested and so far after a few recordings (just test recordings) everything is hunky-dory. Time will tell whether or not my problem has been fixed so I'll reply to this thread again in about a week to report whether or not the issue persists.

 

[Sigma 27]

I still have this issue as it has just happened again today.

 

[Sigma 27]

Just had a thought, would changing the encoder for record help to resolve my issue or provide me with a temporary solution until this gets resolved?

Any assistance is appreciated!

 

[koala]

Changing the encoder will probably make the problem go away for you, because the failing nvenc circuit isn't used any more.

Regarding "until this gets resolved": The sudden nvenc failure is a local problem on your machine, and the only one who is able to provide a resolution is yourself. It's a hardware problem on your GPU, either by overclocking, or by overheating, or by an incompatibility between mainboard and GPU, or a defective GPU.This isn't something OBS can fix.

 

[Sigma 27]

Changing the encoder will probably make the problem go away for you, because the failing nvenc circuit isn't used any more.

Regarding "until this gets resolved": The sudden nvenc failure is a local problem on your machine, and the only one who is able to provide a resolution is yourself. It's a hardware problem on your GPU, either by overclocking, or by overheating, or by an incompatibility between mainboard and GPU, or a defective GPU.This isn't something OBS can fix.

That might be what I'll have to do then. I was afraid that might be the case. As such I don't know where to begin fixing the issue or if it's possible. I've not forced it to overclock or done anything to do with that. Overheating might be something but I haven't run into any other issues that can result from overheating. The incompatibility might be something, this computer does have a few issues from the Win 10 not updating to 1806 to BSOD saying something different every time. Check disk says nothings wrong. DISM and SFC Scannow has NEVER worked for me, even after reinstalling win10 3 times. As I said, could be anything and I can't fix any of these issues.

Cheers anyway though, I'll probably just change the encoder. If the issue persists there then I'll just cry :P.

 

[koala]

The description of your PC issues isn't too good. A properly designed and built PC doesn't bluescreen/BSOD with Windows 10. Windows 7 had the occasional bluescreen once in 3 months, but Windows 10 is running 100% stable on proper hardware. No BSOD at all. If your Windows 10 PC is less stable than that, it needs fixing or a replacement. With fixing I mean fixing the hardware, not reinstall of OS or software.
If you bought too cheap, you may have to buy again. This is sometimes the result of buying too cheap, so buying too cheap isn't cheap at all.

 

[Sigma 27]

The description of your PC issues isn't too good. A properly designed and built PC doesn't bluescreen/BSOD with Windows 10. Windows 7 had the occasional bluescreen once in 3 months, but Windows 10 is running 100% stable on proper hardware. No BSOD at all. If your Windows 10 PC is less stable than that, it needs fixing or a replacement. With fixing I mean fixing the hardware, not reinstall of OS or software.
If you bought too cheap, you may have to buy again. This is sometimes the result of buying too cheap, so buying too cheap isn't cheap at all.

Buying cheap wasn't the problem. I don't know if win10 runs 100% stable on proper hardware as I've heard many different tales about win10 running both well and badly across many different hardware. Fixing or replacement may be the idea but after all the time I've already spent setting it up it is not financially viable to replace it or get it repaired and at this moment in time I've not willing to spend even more time to fix the issue. I contacted PC Specialist who I bought it from and they were not sure of the issues or how to fix. I spoke to friends who are very knowledgeable on hardware and fixing computers and they were also not sure.

Besides the BSOD only happens when firefox is open. I often have Vegas pro 14.0 and firefox open the BSOD only happen in accordance with firefox. I get different messages from video scheduler errors to memory management errors. I've done several memory scans and they come up just fine.