Bug Report Crash report submission

[NomadicCanuck]

Hi guys,
The crash log says I should report this here... so I will.

Before I do, here's some background:
System: Asus Sabertooth 990 R2.0; AMD FX-9590; 16GB w/ SSD
Video: XFX R9 280 (3GB)
I've been using OBS to record MechWarrior Online matches recently. It has been working well.
A short while ago, I started having BSOD's when trying to record. At some point between 30 seconds to 4 minutes after recording, my entire system would crash. The behaviour changed slightly so I wouldn't even get a BSOD and the computer would instantly soft reboot without warning.

I updated the BIOS and have now killed ASUS's AI Suite II software & tools and that seems to get me back working. Now, OBS crashes but does not take out the system. Here is the log file and minidump.dmp file (Sorry, had to be zipped to get under the 1MB limit).

This crash appears to have occured in the 'c:\program files\obs\libx264-142.dll' module.

**** UNHANDLED EXCEPTION: c0000005
Fault address: 00000000678AB7A3 (c:\program files\obs\libx264-142.dll)
OBS version: Open Broadcaster Software v0.638b
Windows version: 6.1 (Build 7601) Service Pack 1
CPU: AMD FX(tm)-9590 Eight-Core Processor

Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
000000000C94DBC0 00000000678AB7A3 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-142.dll!0x678ab7a3
000000000C94DCF0 00000000678CB661 0000000000000000 00000000678DB865 000000000A8C2AC0 00000000678DB72A libx264-142.dll!0x678cb661
000000000C94FB50 00000000678CDA44 0000000000000000 00000000FFFFFFFE 0000000000000000 000007FEFFC01302 libx264-142.dll!0x678cda44
000000000C94FBA0 00000000678DB0CE 00000000089522E0 00000000089522E0 0000000000000000 0000000000000000 libx264-142.dll!0x678db0ce
000000000C94FBF0 00000000678DB5B3 00000000089522E0 0000000000000000 0000000000000000 0000000000000000 libx264-142.dll!0x678db5b3
000000000C94FC20 000007FEFFC0415F 000007FEFFC91EA0 00000000089522E0 0000000000000000 0000000000000000 msvcrt.dll!0x7feffc0415f
000000000C94FC50 000007FEFFC06EBD 0000000000000000 0000000000000000 0000000000000000 0000000000000000 msvcrt.dll!0x7feffc06ebd
000000000C94FC80 00000000779F59ED 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x779f59ed
000000000C94FCB0 0000000077B2C541 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x77b2c541

A minidump was saved to C:\Users\<UserName>\AppData\Roaming\OBS\crashDumps\OBSCrashDump2014-12-08_1.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address Module

 

[R1CH]

Your hardware is faulty, check your RAM with a tool like memtest86+ or Prime95 and remove any overclocks.

 

[NomadicCanuck]

I had previously run memtest (no errors) and will be running a memtest86+ overnight and tomorrow.
I didn't have a good way of testing vid card memory but am, as I type this, trying "Video Memory stress test v1.7.116"... will see how that goes. Any other recommendations on this front?

Furmark tests seem to run just fine, but not as smoothly as in the past and nothing shows up on the benchmarks.

I would love to prove it's my hardware to RMA this video card... there is no love lost between me and it. Suggestions?

I have not overclocked this system. Running stock and cooled appropriately.

 

[NomadicCanuck]

Hi All. Any other suggestions?

I have run through numerous MEM checks with no errors.
I have reported the problem the XFX and tried working with their support but they tell me it is not a hardware issue.

How are you sure it is a hardware issue? What is it that indicates that it is hardware?

I continue to get this error on crash:

**** UNHANDLED EXCEPTION: c0000005
Fault address: 000000006631B79B (c:\program files\obs\libx264-142.dll)
OBS version: Open Broadcaster Software v0.638b
Windows version: 6.1 (Build 7601) Service Pack 1
CPU: AMD FX(tm)-9590 Eight-Core Processor

Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
000000000CDBD7C0 000000006631B79B 0000000000000000 0000000000000000 0000000000000000 0000000000000000 libx264-142.dll!0x6631b79b
000000000CDBD8F0 000000006633B661 0000000000000000 000000006634B865 0000000000497F00 000000006634B72A libx264-142.dll!0x6633b661
000000000CDBF750 000000006633DA44 0000000000000000 00000000FFFFFFFE 0000000000000000 000007FEFEFD1302 libx264-142.dll!0x6633da44
000000000CDBF7A0 000000006634B0CE 00000000004AC110 00000000004AC110 0000000000000000 0000000000000000 libx264-142.dll!0x6634b0ce
000000000CDBF7F0 000000006634B5B3 00000000004AC110 0000000000000000 0000000000000000 0000000000000000 libx264-142.dll!0x6634b5b3
000000000CDBF820 000007FEFEFD415F 000007FEFF061EA0 00000000004AC110 0000000000000000 0000000000000000 msvcrt.dll!0x7fefefd415f
000000000CDBF850 000007FEFEFD6EBD 0000000000000000 0000000000000000 0000000000000000 0000000000000000 msvcrt.dll!0x7fefefd6ebd
000000000CDBF880 00000000774859ED 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x774859ed
000000000CDBF8B0 00000000776BC541 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x776bc541

 

[R1CH]

x264 crashing indicates hardware issues 99.9% of the time. x264 is widely used by millions of people and companies and is unlikely to have any software bugs that cause random crashes. The code is also hand optimized assembly which stresses your system far more than "normal" code as it makes use of advanced CPU features like AVX.

Crashing in x264 generally indicates that your system isn't stable and failed while it was under the heavy stress of the x264 code. You may not be able to reproduce such crashes without stress testing with tools like Prime95, OCCT or LinX. It's also very unlikely to be GPU related, most likely it is memory or CPU.

 

[NomadicCanuck]

Thanks R1CH. I'm going to go back and run through OCCT... and I haven't heard of LinX before, but I'll give it a shot.