Fresh install build 1903 - 2 BSOD Win32kBase & Win32kFull

Well, things didn't stay good. I've had to swap my new PC out for my older one. The BSODs came back with a vengeance. I wiped it and installed Ubuntu just to see if the hardware worked okay with their drivers. Nope it locked up solid a few times, I was going to swap out the M.2 for a mechanical and install Ubuntu but instead decided to run MemTest86 again, MANY errors this time. Running it back to back (free version only allows for 4 passes at a time) to break the tie of 0 errors during the first check and a bunch today. Regardless, I've contacted Newegg to see about RMA options as it has been about 2 months.

Computers are fun ��

Interesting that it (MemTest) didn't find the errors the first time that you ran it.
Let's see how it works w/the new (RMA'd) RAM and move on from there.
Good luck!

I know it is odd for sure, my attempt to run it a 2nd and 3rd time today restarted and then just shutdown my PC

I ran it on 6-16 - when windows started misbehaving (about a month after the build)

Code:

2019-06-16 08:35:38 - =============================================
2019-06-16 08:35:38 - MemTest86 V8.1 Free Build: 1000 (64-bit)
2019-06-16 08:35:38 - =============================================
2019-06-16 08:35:38 - SMBIOS BIOS INFO Vendor: "American Megatrends Inc.", Version: "P2.30", Release Date: "05/08/2019"2019-06-16 08:35:38 - SMBIOS SYSTEM INFO Manufacturer: "To Be Filled By O.E.M.", Product: "To Be Filled By O.E.M.", Version: "To Be Filled By O.E.M.", S/N: "To Be Filled By O.E.M.", SKU: "", Family: ""
2019-06-16 08:35:39 - SMBIOS: Found SMBIOS BaseboardInformation (pbLinAddr=0xE6DAB, FormattedLen=15, iTotalLen=123)
2019-06-16 08:35:39 - SMBIOS BASEBOARD INFO Manufacturer: "ASRock", Product: "B450M-HDV R4.0", Version: "                      ", S/N: "M80-C3010601144", AssetTag: "                      ", LocationInChassis: "                      "
2019-06-16 08:35:39 - EFI Specifications: 2.70
....
2019-06-16 12:07:17 - Cleanup - Unlocking all memory ranges...
2019-06-16 12:07:17 - MtSupportRunAllTests - Test execution time: 1084.149 (Test 13 cumulative error count: 0)
2019-06-16 12:07:17 - Finished pass #4 (of 4) (Cumulative error count: 0)

Then today:

Code:

2019-07-12 12:18:30 - SMBIOS BIOS INFO Vendor: "American Megatrends Inc.", Version: "P2.30", Release Date: "05/08/2019"
2019-07-12 12:18:30 - SMBIOS SYSTEM INFO Manufacturer: "To Be Filled By O.E.M.", Product: "To Be Filled By O.E.M.", Version: "To Be Filled By O.E.M.", S/N: "To Be Filled By O.E.M.", SKU: "", Family: ""
2019-07-12 12:18:30 - SMBIOS: Found SMBIOS BaseboardInformation (pbLinAddr=0xE6DAB, FormattedLen=15, iTotalLen=123)
2019-07-12 12:18:30 - SMBIOS BASEBOARD INFO Manufacturer: "ASRock", Product: "B450M-HDV R4.0", Version: "                      ", S/N: "M80-C3010601144", AssetTag: "                      ", LocationInChassis: "                      "
2019-07-12 12:18:30 - EFI Specifications: 2.70
.....
2019-07-12 14:58:27 - Cleanup - Unlocking all memory ranges...
2019-07-12 14:58:27 - MtSupportRunAllTests - Test execution time: 1161.476 (Test 13 cumulative error count: 173)
2019-07-12 14:58:27 - Finished pass #3 (of 4) (Cumulative error count: 173)
2019-07-12 14:58:27 - Starting pass #4 (of 4)

The last 2 tests there are no summaries:
2nd attempt:

Code:

2019-07-12 17:08:53 - SMBIOS BIOS INFO Vendor: "American Megatrends Inc.", Version: "P2.30", Release Date: "05/08/2019"
2019-07-12 17:08:53 - SMBIOS SYSTEM INFO Manufacturer: "To Be Filled By O.E.M.", Product: "To Be Filled By O.E.M.", Version: "To Be Filled By O.E.M.", S/N: "To Be Filled By O.E.M.", SKU: "", Family: ""
2019-07-12 17:08:53 - SMBIOS: Found SMBIOS BaseboardInformation (pbLinAddr=0xE6DAB, FormattedLen=15, iTotalLen=123)
2019-07-12 17:08:53 - SMBIOS BASEBOARD INFO Manufacturer: "ASRock", Product: "B450M-HDV R4.0", Version: "                      ", S/N: "M80-C3010601144", AssetTag: "                      ", LocationInChassis: "                      "
2019-07-12 17:08:53 - EFI Specifications: 2.70
.....
2019-07-12 17:37:52 - RunHammerTest - Running hammer test on 4 CPUs (128MB each) [0x100000000 - 0x120000000]
2019-07-12 17:37:53 - Memory range 0x8000 - 0x3F000 was not locked. Ignoring...
2019-07-12 17:37:55 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 87FCF400, Expected: D4C17A37, Actual: D4C1FA37
2019-07-12 17:37:55 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 87FCF408, Expected: CFBF3269, Actual: CFBFE269
2019-07-12 17:37:55 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 87FCF410, Expected: 08B6FC2B, Actual: 08B65C2B
2019-07-12 17:37:55 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 87FCF418, Expected: 605BE3FD, Actual: 605B53FD
2019-07-12 17:37:55 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 87FCF420, Expected: 480D5A5F, Actual: 480D6A5F
2019-07-12 17:37:55 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 87FCF428, Expected: BFDA53D1, Actual: BFDA73D1
2019-07-12 17:37:55 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 87FCF430, Expected: 099D68D3, Actual: 099D98D3
2019-07-12 17:37:55 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 87FCF438, Expected: E1F9F5E5, Actual: E1F985E5
2019-07-12 17:37:57 - Memory range 0xD3A8C000 - 0xD3AB9000 was not locked. Ignoring...
2019-07-12 17:37:57 - Memory range 0xD4DF7000 - 0xD4E29000 was not locked. Ignoring...
2019-07-12 17:37:57 - Memory range 0xD63D1000 - 0xD6428000 was not locked. Ignoring...
2019-07-12 17:37:57 - Memory range 0xD6434000 - 0xD643F000 was not locked. Ignoring...
2019-07-12 17:37:59 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 18608F400, Expected: 7F7DBA74, Actual: 7F7D5A74
2019-07-12 17:37:59 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 18608F408, Expected: CB823C8E, Actual: CB82AC8E
2019-07-12 17:37:59 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 18608F410, Expected: 881D5F78, Actual: 881DDF78
2019-07-12 17:37:59 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 18608F418, Expected: 0818A9B2, Actual: 081879B2
2019-07-12 17:37:59 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 18608F420, Expected: F92DD5BC, Actual: F92D85BC
2019-07-12 17:37:59 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 18608F428, Expected: 00A87216, Actual: 00A8B216
2019-07-12 17:37:59 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 18608F430, Expected: 66148140, Actual: 6614B140
2019-07-12 17:37:59 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 18608F438, Expected: 846219BA, Actual: 846239BA
2019-07-12 17:38:06 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 3AF30A400, Expected: AC1E3D08, Actual: AC1EFD08
2019-07-12 17:38:06 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 3AF30A408, Expected: CFE2F3C2, Actual: CFE2E3C2
2019-07-12 17:38:06 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 3AF30A410, Expected: A520F04C, Actual: A520E04C
2019-07-12 17:38:06 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 3AF30A418, Expected: 04BEE126, Actual: 04BE3126
2019-07-12 17:38:07 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 3AF30A420, Expected: 8BBCE8D0, Actual: 8BBCC8D0
2019-07-12 17:38:07 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 3AF30A428, Expected: 43203DCA, Actual: 4320BDCA
2019-07-12 17:38:07 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 3AF30A430, Expected: C03BCA94, Actual: C03BFA94
2019-07-12 17:38:07 - [MEM ERROR - Data] Test: 13, CPU: 0, Address: 3AF30A438, Expected: 483DCDAE, Actual: 483D9DAE
2019-07-12 17:38:08 - Memory range 0x8000 - 0x3F000 was not locked. Ignoring...
2019-07-12 17:38:11 - Memory range 0xD3A8C000 - 0xD3AB9000 was not locked. Ignoring...
2019-07-12 17:38:11 - Memory range 0xD4DF7000 - 0xD4E29000 was not locked. Ignoring...
2019-07-12 17:38:11 - Memory range 0xD63D1000 - 0xD6428000 was not locked. Ignoring...
2019-07-12 17:38:11 - Memory range 0xD6434000 - 0xD643F000 was not locked. Ignoring...

that was the end of the log, even though I restarted it to begin a test again ..

the 3rd attempt didn't log anything and the PC was running but with no activity. I had to press and hold the power button to turn it off.

so yeah, I hope they allow me to RMA the kit else I'll have to order more.

I'm also concerned that the test passed in the beginning.
What if the memory went bad due to some other hardware issue?
The concern here is that you could RMA the RAM, then it could go bad again.
Unfortunately, the only way to tell is to give it a try.
Good luck!

true enough, thank you

Update - I had to run the RMA through G.Skill, it has been sent off and it'll be a few days to a week until I get them back. So during prime day I bought Ballistix Sport LT 16GB Kit (8GBx2) DDR4 2400 MT/s (PC4-19200) CL16 SR x8 DIMM 288-Pin - BLS2K8G4D240FSBK (Gray), when I got the box and opened it, the memory was the only thing in the box no packing material. The ram was out of its packaging and had been bouncing around the box for who knows how long. That can't be good for it - uhg so I asked for replacement because it might be just damaged enough to work now and then die later. I did put it in just for testing sake and MemTest86 ran a couple time just fine.

I'm running some tests in Ubuntu by running YouTube videos for an hour or so. This would lockup with the ram I have RMA'd, if this runs okay for a few days then I'll reinstall Windows 10 1903 and let that ruminate for a while as well.

So zero issues, I was unable to watch any video or open more than a few tabs in Chrome w/o BSOD issues. Last 3 days have been perfect. I may even tempt fate and flip on my Insider build switch on this machine again

I suggest setting a System Restore point now.
And, if you're really concerned, create a system image to backup the entire drive. That way you can go back to this exact point if you want.

jdc1 said:

I suggest setting a System Restore point now.
And, if you're really concerned, create a system image to backup the entire drive. That way you can go back to this exact point if you want.

Always I use Marcium Reflect to create an image of the boot drive before any changes are made and of course I have a usb rescue stick that allows me to restore them.

So after testing with 3 OSes (Linux, Windows 1903, and Windows Insider build 18941 and thus different drivers) and not experiencing any issues for just under a week. I can safely say the RAM was indeed the issue and this is solved. Thank you jdc1 for your assistance and your time.