4 Replies Latest reply on Jul 8, 2017 12:51 AM by AN_Other

    NUC7i5BNH - memory errors when both slots populated

    AN_Other

      Hi, all.

       

      After experiencing multiple BSODs (MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA) with my new NUC7i5BNH, I've found through trial and error that the cause appears to be memory errors - but the errors only occur when both slots are populated.

       

      My NUC's hardware consists of:

      2 x Crucial CT16G4SFD8213 16GB 2133MHz SODIMMs

      1 x Crucial CT1050MX300SSD4 1TB M.2 SSD

       

      The NUC has been updated to the latest 0047 BIOS, and the BIOS is using default settings. (I had previously turned Hyper-Threading off with the 0046 BIOS in case that was the problem, but it didn't help; after updating to 0047 I reloaded the default settings but that made no difference either.)

       

      I've tested each SODIMM individually in both the lower and upper memory slots, and the system works perfectly with either one as long as the other slot is empty; the NUC runs stably and repeated tests show no memory errors. Populating both slots and booting into Memtest86, however, results in memory test failures. Memtest86 also sometimes crashes midway through the test, showing "CPU Error: Could not start CPU 0".

       

      At first the memory errors were extremely intermittent and I had difficulty reproducing them reliably, but now they occur nearly all the time when both slots are filled and a Memtest86 test is run. Are there any further steps I should try before considering an RMA?

        • 1. Re: NUC7i5BNH - memory errors when both slots populated
          N.Scott.Pearson

          Usually, if a pair of SODIMMs seem to work perfectly fine when tested individually (including in both sockets), but failures are seen when these SODIMMs are used together, the issue is that the SODIMMs are actually different. I have seen cases where two SODIMMs, despite being marked identically and coming as a "matched pair", actually require (slightly) different timings. I would start by verifying whether or not the parts are indeed different. This can include inspection of the individual ICs used to see that they are identical, comparison of the SPD data, etc.

           

          Hope this helps,

          ...S

          • 2. Re: NUC7i5BNH - memory errors when both slots populated
            AN_Other

            Thanks for the suggestion - I've visually inspected both SODIMMs and both have eight Micron chips per side, all marked "6QA47 D9SRJ".

             

            SPD autodetection for both SODIMMs (tested individually) shows identical timings, 15-15-36-14-6-23-8316-374-11-8-16-1n.

            • 3. Re: NUC7i5BNH - memory errors when both slots populated
              AN_Other

              Well, a new development just came up - for the first time ever, I had a BSOD (CRITICAL_PROCESS_DIED) with only one SODIMM in the NUC. I rebooted into Memtest86 and it detected memory errors.

               

              I've now swapped the other SODIMM into the same slot and it seems stable so far. I'll run the NUC over the weekend, and if nothing goes wrong by Monday I'll RMA the suspect memory module.

               

              Thanks again for the helpful suggestions.

              • 4. Re: NUC7i5BNH - memory errors when both slots populated
                AN_Other

                ...and I just got an application crash with the other SODIMM in the same slot (the lower one). Rebooted to Memtest86 and the test detected several hundred memory errors.

                 

                I've shifted the SODIMM to the upper slot, and Memtest86 hasn't found any errors so far.