Memtest86 Test 6 and 13 Failure (Require Assistance)

[JoeShmo]

Hi all,
Recently I have been getting these irreparable BSODs and I figured to do a MemTest to look for erros. I tried everything from disk wipes to driver updates (although I will admit I do have old CPU drivers but those usually do not cause issues). My PC worked from approx. 2 months until it got a BSOD that I have been trying to repair since August 28th. I have taken it to a shop which thought it was a minor error and improperly repaired it and thus I will take it back if I must. However the results of my Memtest have me wondering whether this is driver/bios related or hardware damage. There was no hardware change/damage between the night before and after I had this BSOD but I want to check all scenarios, especially since this has been such a troublesome issue. I am running a rig with a 2080, aorus Z390 pro wifi motherboard, as well as a 9900k and 16 gigabytes of DDR4 (in 2 8gig sticks respectively). It is a custom built rig however it worked just fine for the initial few months so I do not believe it was an issue with the build itself, however I am open to critique. I copied the most prominent errors, please let me know if you would like a full copy of the memtest (stopped on pass 3 because I decided I needed to go to bed). Thanks in advanced!




2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41A21E678, Expected: FF7DFFFF, Actual: FFFDFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41A41E678, Expected: FF7EFFFF, Actual: FFFEFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41A53E678, Expected: FF7FFFFD, Actual: FFFFFFFD
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41A73E628, Expected: FF7FFFFF, Actual: FFFFFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41A73E678, Expected: FF7FFFFE, Actual: FFFFFFFE
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41AA56728, Expected: FF7FFFF7, Actual: FFFFFFF7
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 41713E628, Expected: F77FFFFF, Actual: F7FFFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41AAC6678, Expected: FF7FFF7F, Actual: FFFFFF7F
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41AB3E678, Expected: 7F7FFFFF, Actual: 7FFFFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 4172C6628, Expected: FF7FFFFB, Actual: FFFFFFFB
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 4172C6678, Expected: FF7FFFF7, Actual: FFFFFFF7
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41AC8E728, Expected: FF3FFFFF, Actual: FFBFFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 417376778, Expected: FF7BFFFF, Actual: FFFBFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41AD3E678, Expected: BF7FFFFF, Actual: BFFFFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 41741E678, Expected: FF7FFEFF, Actual: FFFFFEFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41AE1E628, Expected: FF7FFBFF, Actual: FFFFFBFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 4175E6678, Expected: FF6FFFFF, Actual: FFEFFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41AFE6628, Expected: FF3FFFFF, Actual: FFBFFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41B08E728, Expected: FF6FFFFF, Actual: FFEFFFFF
2019-09-08 21:16:13 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 41773E678, Expected: FD7FFFFF, Actual: FDFFFFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41B13E678, Expected: EF7FFFFF, Actual: EFFFFFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41B1E6678, Expected: FF3FFFFF, Actual: FFBFFFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41B33E678, Expected: F77FFFFF, Actual: F7FFFFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 417C1E628, Expected: FF7FFFF7, Actual: FFFFFFF7
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41B456728, Expected: 7F7FFFFF, Actual: 7FFFFFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41B48E728, Expected: FF7BFFFF, Actual: FFFBFFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 417E56728, Expected: FB7FFFFF, Actual: FBFFFFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41B576728, Expected: FF7EFFFF, Actual: FFFEFFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 417E8E728, Expected: FF7FDFFF, Actual: FFFFDFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 417F3E628, Expected: FF6FFFFF, Actual: FFEFFFFF
2019-09-08 21:16:14 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41B9AE778, Expected: FF7FFFFB, Actual: FFFFFFFB
2019-09-08 21:16:15 - [MEM ERROR - Data] Test: 6, CPU: 12, Address: 417FAE728, Expected: 7F7FFFFF, Actual: 7FFFFFFF
2019-09-08 21:16:15 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41BEC6678, Expected: BF7FFFFF, Actual: BFFFFFFF
2019-09-08 21:16:15 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41BF3E678, Expected: FF5FFFFF, Actual: FFDFFFFF
2019-09-08 21:16:15 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41BF76778, Expected: FF7FEFFF, Actual: FFFFEFFF
2019-09-08 21:16:15 - [MEM ERROR - Data] Test: 6, CPU: 14, Address: 41BFAE728, Expected: 7F7FFFFF, Actual: 7FFFFFFF
2019-09-08 21:16:15 - [MEM ERROR - Data] Test: 6, CPU: 0, Address: 41E0C6678, Expected: FF7FEFFF, Actual: FFFFEFFF
2019-09-08 21:16:15 - [MEM ERROR - Data] Test: 6, CPU: 0, Address: 41E28E778, Expected: EF7FFFFF, Actual: EFFFFFFF
2019-09-08 21:16:15 - [MEM ERROR - Data] Test: 6, CPU: 0, Address: 41E576728, Expected: FE7FFFFF, Actual: FEFFFFFF
2019-09-08 21:16:15 - [MEM ERROR - Data] Test: 6, CPU: 0, Address: 41EA56728, Expected: FF7FFFF7, Actual: FFFFFFF7
2019-09-08 21:16:16 - [MEM ERROR - Data] Test: 6, CPU: 0, Address: 41F976778, Expected: FF7F7FFF, Actual: FFFF7FFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 42201E628, Expected: FF7DFFFF, Actual: FFFDFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 42201E678, Expected: FF7BFFFF, Actual: FFFBFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 6, Address: 42AA8E728, Expected: FFFFFFFF, Actual: FF7FFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 4220C6628, Expected: FF7FF7FF, Actual: FFFFF7FF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 8, Address: 42E776728, Expected: FFFFFFFF, Actual: FF7FFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 4223AE728, Expected: FF7FEFFF, Actual: FFFFEFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 4223E6628, Expected: EF7FFFFF, Actual: EFFFFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 422456778, Expected: FF7FFF7F, Actual: FFFFFF7F
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 422656728, Expected: FF7FFFDF, Actual: FFFFFFDF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 42288E728, Expected: FE7FFFFF, Actual: FEFFFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 4228C6628, Expected: FF7FFF7F, Actual: FFFFFF7F
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 422976728, Expected: FF3FFFFF, Actual: FFBFFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 422B3E678, Expected: 7F7FFFFF, Actual: 7FFFFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 422BE6628, Expected: FE7FFFFF, Actual: FEFFFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 4, Address: 427B3E678, Expected: FFFFFFFF, Actual: FF7FFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 422CC6628, Expected: FF7FFFDF, Actual: FFFFFFDF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 8, Address: 42F93E628, Expected: FFFFFFFF, Actual: FF7FFFFF
2019-09-08 21:16:17 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 422E1E678, Expected: FF7FF7FF, Actual: FFFFF7FF
2019-09-08 21:16:18 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 422EC6678, Expected: FF7FFFDF, Actual: FFFFFFDF
2019-09-08 21:16:18 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 42308E778, Expected: FF5FFFFF, Actual: FFDFFFFF
2019-09-08 21:16:18 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 423176728, Expected: FF7BFFFF, Actual: FFFBFFFF
2019-09-08 21:16:18 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 4231AE778, Expected: FF7FFFBF, Actual: FFFFFFBF
2019-09-08 21:16:18 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 42333E678, Expected: F77FFFFF, Actual: F7FFFFFF
2019-09-08 21:16:18 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 42353E678, Expected: FB7FFFFF, Actual: FBFFFFFF
2019-09-08 21:16:18 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 423576778, Expected: FF7DFFFF, Actual: FFFDFFFF
2019-09-08 21:16:18 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 423776728, Expected: FF7F7FFF, Actual: FFFF7FFF
2019-09-08 21:16:18 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 423976728, Expected: FF7FBFFF, Actual: FFFFBFFF
2019-09-08 21:16:19 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 423B3E628, Expected: FF3FFFFF, Actual: FFBFFFFF
2019-09-08 21:16:19 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 423BE6678, Expected: FF7DFFFF, Actual: FFFDFFFF
2019-09-08 21:16:19 - [MEM ERROR - Data] Test: 6, CPU: 2, Address: 423F3E678, Expected: FF5FFFFF, Actual: FFDFFFFF
2019-09-08 21:16:24 - Cleanup - Releasing all memory ranges...

2019-09-08 21:34:24 - RunHammerTest - Running hammer test on 3 CPUs (158MB each) [0x100000 - 0x1DDD5000]
2019-09-08 21:34:25 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:34:33 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:34:40 - RunHammerTest - Running hammer test on 2 CPUs (176MB each) [0x1DE15000 - 0x33E55000]
2019-09-08 21:34:41 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:34:49 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:34:56 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:35:04 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:35:12 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x100000000 - 0x120000000]
2019-09-08 21:35:12 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:35:20 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:35:28 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x120000000 - 0x140000000]
2019-09-08 21:35:28 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:35:36 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:35:43 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x140000000 - 0x160000000]
2019-09-08 21:35:44 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:35:52 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:35:59 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x160000000 - 0x180000000]
2019-09-08 21:36:00 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:36:08 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:36:15 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x180000000 - 0x1A0000000]
2019-09-08 21:36:16 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:36:24 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:36:31 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x1A0000000 - 0x1C0000000]
2019-09-08 21:36:31 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:36:40 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:36:47 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x1C0000000 - 0x1E0000000]
2019-09-08 21:36:47 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:36:56 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:37:03 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x1E0000000 - 0x200000000]
2019-09-08 21:37:03 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:37:11 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:37:19 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x200000000 - 0x220000000]
2019-09-08 21:37:19 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:37:27 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:37:35 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x220000000 - 0x240000000]
2019-09-08 21:37:35 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:37:43 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:37:51 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x240000000 - 0x260000000]
2019-09-08 21:37:51 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:37:59 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:38:06 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x260000000 - 0x280000000]
2019-09-08 21:38:07 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:38:15 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:38:22 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x280000000 - 0x2A0000000]
2019-09-08 21:38:23 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:38:31 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:38:38 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x2A0000000 - 0x2C0000000]
2019-09-08 21:38:39 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:38:47 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:38:54 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x2C0000000 - 0x2E0000000]
2019-09-08 21:38:55 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:39:03 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:39:10 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x2E0000000 - 0x300000000]
2019-09-08 21:39:10 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:39:19 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:39:26 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x300000000 - 0x320000000]
2019-09-08 21:39:26 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:39:34 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:39:42 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x320000000 - 0x340000000]
2019-09-08 21:39:42 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:39:50 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:39:58 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x340000000 - 0x360000000]
2019-09-08 21:39:58 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:40:06 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:40:14 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x360000000 - 0x380000000]
2019-09-08 21:40:14 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:40:22 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:40:30 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x380000000 - 0x3A0000000]
2019-09-08 21:40:30 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:40:38 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:40:45 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x3A0000000 - 0x3C0000000]
2019-09-08 21:40:46 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:40:54 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:41:01 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x3C0000000 - 0x3E0000000]
2019-09-08 21:41:02 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:41:10 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:41:17 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x3E0000000 - 0x400000000]
2019-09-08 21:41:18 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:41:26 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:41:33 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x400000000 - 0x420000000]
2019-09-08 21:41:33 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:41:42 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:41:49 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x420000000 - 0x440000000]
2019-09-08 21:41:49 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:41:57 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:42:05 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x440000000 - 0x460000000]
2019-09-08 21:42:05 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:42:13 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:42:21 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x460000000 - 0x480000000]
2019-09-08 21:42:21 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:42:29 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:42:37 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x480000000 - 0x4A0000000]
2019-09-08 21:42:37 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:42:45 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:42:53 - RunHammerTest - Running hammer test on 3 CPUs (159MB each) [0x4A0000000 - 0x4BDF00000]
2019-09-08 21:42:53 - Memory range 0x8000 - 0x5E000 was not locked. Ignoring...
2019-09-08 21:43:01 - Cleanup - Unlocking all memory ranges...

[Richard (PassMark)]

RAM errors typically indicates the RAM is bad.

Did you or the shop replace the RAM? If it was replaced and you still get MemTest86 errors, then possibly something else besides the RAM is bad.

See the following page for troubleshooting, https://www.memtest86.com/troubleshooting.htm

[JoeShmo]

Neither I nor the shop have replaced the RAM. I will try updating my BIOS and testing MemTest with one stick, as well as checking my RAMs compatibility with the motherboard. If none of this works I will take it back to the shop and explain what happened and ask to see if they can try using different RAM. Thanks for the quick response, please leave the post open until I am confirm my issue is solved!

[JoeShmo]

I am having trouble finding a 64 bit of the F10 BIOS for the Z390 AORUS PRO WIFI Motherboard. Any chance I can get help on that? Also my .F10 files are opening with notepad, do I need to fix that or will it work nonetheless? I've read that they're ok but I thought I'd ask anyways

[JoeShmo]

Oh I believe I need to use UEFI to do so ^... Is this correct? Also should I update my Standard SATA AHCI Controller to the Intel(R) 300 Series Chipset SATA AHCI Controller? My SSD runs on M.2 so im predicting it wont make a difference.

[JoeShmo]

After some research I am wondering whether or not to convert to a GPT drive. I only currently run one disk, so would this be possible to do from bootup (it doesn't allow me to do it on a disk with a pagefile volume, which im assuming is just the main disk with windows installed)? As far as BIOS goes that is the main thing I would like to see if anybody could help me with because I believe I am doing something improperly. Is there a 64 bit BIOS for my system? Will running a 16 bit be just fine (not really effect performance)? How would I install my BIOS (I assumed it'd be similar to running MemTest but with UEFI, but booting from UEFI just takes me back to the startup menu). Sorry I feel like I am spamming but based on the fact the website gives me a timezone from Europe or Asia I am figuring to get all my questions down now so that hopefully if you get the chance you could respond. Thanks again for the help, it is greatly appreciated (especially because my frustration with this issue is endless and I feel testing BIOS and RAM can allow me to find the source of the issue and a solution). Just to add this as well, what are the chances this is due to a PATH file error? I was noticing some similarities but I dont think it wouldve caused my previous bluescreens. Just to build on that, they used to be every time I logged into windows but with some PC wipes, driver updates, and more, I have reduced the bluescreens dramatically to about 1 per day. That's still not good enough, though, and I get an error where my chrome randomly shows the "aw man" error for 3 minutes or so, as well as corrupt downloads/initiation (I can test to see if this is still happening by trying to run a game). I do not care about wiping my data if necessary but this has been an extremely frustrating and time consuming process so any advice is extremely greatly appreciated.

[David (PassMark)]

Contact Gigabyte if you need help updating your motherboard firmware. They should have instructions on their web site. There is no such thing as 64bit/32bit/16bit options for modern firmware.

MemTest86 log is pretty conclusive in my opinion. RAM is bad. So that is the problem that needs addressing. Not SATA device drivers. If new RAM doesn't fix it, then go looking for other causes.

[JoeShmo]

Ok thank you for the help it is greatly appreciated. If it doesnt turn out to be the RAM I will take it to the local repair shop to get checked out.