Multiple (various) BSODs - SWTOR & ArmA III - 10-20 min playtime cycle

I just built a new PC and have started experiencing BSODs while playing SWTOR and ArmA III. The BSOD occurs about 10-20 minutes after firing up either game. This has happened consistently about 6 times. I've had a couple memory management errors, a IRQL_NOT_LESS_OR_EQUAL and most recently Faulty_Hardware_Corrupted_Page.

DM Log Collector file attached.

Thank you for your time!

-I forgot to note something. I have 355.60 driver installed at the moment. I was using the most recent driver, 358.87, but I had a BSOD then. I installed an older driver to see if it would help, but it obviously didn't.

-Another note, I was just reverting back to the 358.87 driver and I had another BSOD. This time a memory management error.

-I went into the BIOS to have a look at some of the RAM settings. I have the frequency set to AUTO and I notice it has the frequency set at 2133 when I have 2400 freq RAM. I don't know if this is a problem or not, I didn't want to touch anything yet.

Another edit..
-I looked at updates for my motherboard (ASRock Z170 Pro4). There was a BIOS update that 'improves DRAM Module Compatibility', release on 30OCT. After browsing this forum and other sites, I've seen many other people having similar issues with the same mobo. They seems to be centered around memory problems. However, I don't want to mess around with updating the BIOS without some council.

Hi McFailboat,

Welcome to the 10forums.

Please revert any overclocking back to stock while troubleshooting if there is any.

Please check Windows Update and install every update available.

Please uninstall Avira while troubleshooting
How do I uninstall my Avira Antivirus product?

Code:

*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys

I recommend testing the hard drive(s) and the memory as there are a few 0x1A(MEMORY_MANAGEMENT) and the output from a few dumps below.
Read the instructions carefully

Code:

STACK_TEXT:  
ffffd000`2484b118 fffff800`919fa37a : 00000000`0000001e ffffffff`c0000005 fffff800`a1540790 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2484b120 fffff800`919ca682 : 00000000`00000000 00000000`00000000 ffffe001`e4babdd0 ffffe001`e4a92f28 : nt! ?? ::FNODOBFM::`string'+0x2bb7a
ffffd000`2484b800 fffff800`919c8b7e : ffffc001`69d93b08 ffffc001`00000050 fffff800`a14ce1f0 00000000`000000a0 : nt!KiExceptionDispatch+0xc2
ffffd000`2484b9e0 fffff800`a1540790 : ffffe001`dd7fb180 ffffd000`00000001 ffffc001`69d93b00 ffffe001`dd7fc4f0 : nt!KiGeneralProtectionFault+0xfe
ffffd000`2484bb70 fffff800`a1540eea : ffffe001`e4b74dc8 ffffe001`dd7fc4f0 ffffc001`61240530 ffffe001`e4b74e01 : NTFS!NtfsFindPrefixHashEntry+0x730
ffffd000`2484bc80 fffff800`a1541e8a : ffffe001`e4b74dc8 ffffe001`e492b010 ffffe001`e4b74dc8 ffffd000`2484beb0 : NTFS!NtfsFindStartingNode+0x2ca
ffffd000`2484bd40 fffff800`a154192d : ffffe001`e4b74dc8 ffffe001`e492b010 ffffd000`2336f000 ffffe001`e2b99001 : NTFS!NtfsCommonCreate+0x52a
ffffd000`2484bf50 fffff800`919c2787 : ffffd000`2336efb0 000000a6`b992ef38 00000000`00000000 00000000`00000000 : NTFS!NtfsCommonCreateCallout+0x1d
ffffd000`2484bf80 fffff800`919c274d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
ffffd000`2336edf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue

Code:

SYMBOL_NAME:  ONE_BIT

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

Diagnostics Test

 HDD & SSD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Disk Check - Windows 7 Help Forums

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.