BSOD on export - Memory issue?

[Scitz0]

Hi,

I built a new system to be able to work with and handle video editing smoothly. I also reused some parts to save some money.

Hardware spec is as follows:

Intel 6800k

NZXT Kraken X61

ASUS X99-E

32GB Corsair LPX 3200 (8x4)

EVGA Supernova G2 750W

Nvidia GTX 670

500GB Samsung 850 EVO

256GB Samsung 950 PRO m.2

10Gbit NIC to storage server.

This is running on Windows 10 with latest CC 2017.

Video clips is stored on storage server and all project files and scratch files are stored on the 950 Pro SSD. OS on 850 SSD.

I wanted to do some edits on an older CC 2015 project so I converted it to 2017 and did the edits.

The sequence is 30 min long and consist of video clips with different frame rates and resolutions as well as dynamically linked after effects compositions.

When exporting this sequence to a H264 media file I get a BSOD after a couple of hours. Usually with a NO_PAGES_AVAILABLE Bug Check String.

I have tried encoding both directly with Premiere Pro and through Media Encoder with the same result. I have also tried to pre encode the after effects compositions and add these media files to the sequence with the same result.

I checked the system for stability issues by running Prime95 for about 8h with small FFT and another 16h or so in blend mode, no errors.

I then booted memtest86 7.1 and ran a memory check for about 8h, no errors. Windows own memory check didn't show any problems either.

Ran a couple of 3DMark tests with the free version to test GPU, no issue. I'm at a loss to what more to test for system stability. CPU stays cool.

I'm not sure but I think its a memory issue with Adobe during encoding. I have set in the settings that it should leave 10GB of memory to other applications, ie 22GB available to Premiere Pro. Checking in Media Encoder gives the same value. It is also set to memory mode instead of performance.

Looking at the Activity Monitor during encoding it looks like Adobe is using way more than its allowed 22GB. Correct me if I'm wrong but I read it as Windows has 64GB of virtual memory, 32GB physical and 32GB system page file. When I took these screenshots before going to bed it seems to me that almost all of the virtual 64GB memory is used, 54.1 of 63.9? And when I got up this morning the computer had crashed and restarted. Checking created mini dump showed the NO_PAGES_AVAILABLE bug check string.

What can I do to sort this out?

[John T Smith]

BSOD shutdowns http://forums.adobe.com/thread/1427408?tstart=0 (may be due to hardware problems???)

-http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-after-effect...

-http://www.howtogeek.com/222730/how-to-find-out-why-your-windows-pc-crashed-or-froze/

-http://www.howtogeek.com/school/using-windows-admin-tools-like-a-pro/lesson3/

[Scitz0]

Before posting the issue here on the Adobe forum I read and searched all I could for different reasons BSOD could appear. I also searched this forum to the best of my ability to see if there were other with similar issues.

This is why I have tried to rule out hardware by running different kinds of stress test and memory checks.

Do you have any comment on the huge memory allocation even though it is limited in settings?

[excited_Genie16B8]

What can I do to sort this out?

First thing I recommend, lose the network.  Take the machine off it entirely.  Delete any special networking software you have installed.

Yes, that does mean moving all assets over to a local drive for the test.

[Scitz0]

A followup after doing some more tests.

The four 8gb memory sticks designed to run at 3200mhz was running at 2133mhz, ie XMP was disabled in bios. So I enabled XMP profile and memory sticks changed to 3200 like specification say.

I then started Memtest86 and after about 2,5h it froze(pass 2 test 7 I think), no errors. Hard reboot of computer and restarted the test and yet again it froze after less than two hours at the end of pass 1. I then removed two of the memory sticks(in C1 and D1) keeping the other two in A1 and B1 slots. Restarted the Memtest86 check, still at 3200mhz, completed all four passes without any errors or lockups. Removed the two good memory sticks and placed the other two in A1 & B1. These also passed Memtest86 check without errors or lockups. Seems like there is some issue with the quad channel mode on the ASUS mb? Or could CPU be the issue.

Never the less, lets skip this part for now. I started the computer with only two sticks installed for a total of 16GB and set adobe to leave 6gb for other apps. Started a new encoding of the project and about 25% in adobe crashed(no BSOD) with a message that memory was depleted and that it had to kill adobe process. It didn't kill windows though like before. Restarted the encoding but this time I changed from running with CUDA support to sw only. After about the same amount of time, or just a bit longer I checked on the status for the encoding. No crashes or messages about force closing adobe or so but checking activity monitor in Windows it showed 0% cpu usage and memory was static for all adobe applications. So even though I didnt have any error messages it seems like the encoding was stuck yet again. Klicking stop on the encoding made the Media Encoder freeze and not respond. Had to force close the application.

So I'm still not able to encode my project even though I'm currently free from BSOD issue.

Suggestions?

[John T Smith]

You MAY have a bad motherboard

[Scitz0]

Ok, that may be, test suggest this or maybe the two dual-channel kits doesn't play nice in quad channel mode.

But if we skip this and focus on the last part of my previous post. I'm now running only with two sticks(16gb) and system is stable.

Adobe still wont encode though, either app is crashing because of no memory or as in the case with sw only it just stalled and did nothing, clock ticking and the expected time until complete steadily climbing.

I can't see this as a hw issue but rather a sw issue with adobe?

[Scitz0 · Accepted solution]

Problem with BSOD was solved by returning the two dual-channel kits and getting a matched 64gb(4x16) quad kit. Ran memtest for about 22h and it was at the end of pass 4 at that time when I canceled it, no errors or lockups.

Adobe encoding still crashed after this though, but only the adobe application for running out of memory.

So I opened the project and removed all color grading with Magic Bullet Looks plugin and redid the color grading for the entire project using the built in lumetri color panel(really good now). With Looks gone from project the encoding went fine. So it seems the issue was the Looks effect eating up all memory. But as the color grading inside Premiere Pro is so good now I can live without external color grading tools/effects, ie problem solved.