It doesn’t bode well if you’re seeing an error after 3 passes. Try other testing methods to see if more errors pop up as that’d point to defective RAM (you could also take it out and inspect the traces, make sure there isn’t any debris or corrosion limiting pin contact).
For freeware certain OCCT tests are pretty good at hammering RAM, though test time will be limited to an hour with the free version. prime95 can be configured to test memory but it will absolutely hammer your system. memtest86 works but it’s a bit slow at finding errors I think. Same with HCI MemTest. Personally I use Karhu RAM Test as I find that’s fastest at finding errors, but that’s a paid license. Usually I aim for no errors after letting it run for at least 12 hours / 10,000% coverage when I’m doing final stability testing.
I used MemTest64 here. I opened up the Framework and checked the connection, there appears upon a cursory inspection, no problems there. The RAM module is what I got from Framework when I ordered DIY. Took it out of packaging and installed it right away.
For what it’s worth I’m cursed with RAM, I’ve had to RMA two kits on my desktop in the past few years.
I’d probably contact support since I’m assuming you’ll go through them if it needs replaced. You could run another test or two first to verify it’s the RAM but you shouldn’t be seeing any errors in the RAM testing ideally, especially since MemTest64 usually isn’t as efficient about finding errors as some of the others I listed (I’ve passed MemTest64 before and instantly crashed on others).
Edit: If you want to be thorough and rule out a possible mainboard issue you could also try testing in the other DIMM slot since I see you only have one stick. If it’s erroring in both almost certainly the RAM itself.
I will run it overnight. Will be traveling out of town for a while, so am taking my cheap ass Acer Spin instead. Will post results tomorrow and then figure out how to go forward. Much thanks.
OK, again thanks to everyone who helped with my BSOD issue. I took your advice and moved the RAM module to Module 0 from the default Module 1 and reran the memtest for 10 loops. Here are the test results for Module 1, where I had errors and BSOD and Module 0 where everything seems to be just fine.
Tks Nick
Module 0:
Empty
Module 1:
DDR4, 16384 MB, 64-bit, 3200 MHz
Controller1-ChannelA-DIMM0 BANK 0 Crucial Technology CT16G4SFRA32A.M16FRS
0.000: Detecting usable memory (16167 MB theoretical max)…
15.938: 14720 MB Test starting on 8 CPUs…
15.938: Allocating memory…
24.172: Memory locking failed (might be reserved by other apps/kernel)
28.235: Test finished with no errors detected
0.000: Detecting usable memory (16167 MB theoretical max)…
16.985: 14848 MB Test starting on 8 CPUs…
17.000: Allocating memory…
26.422: Starting loop 1
26.438: Stuck Address Test…
30.969: Random Data Test…
35.610: Move Data Test…
37.313: Bitpattern Test…
178.188: Starting loop 2
178.204: Stuck Address Test…
182.782: Random Data Test…
187.516: Move Data Test…
189.219: Bitpattern Test…
331.000: Starting loop 3
331.016: Stuck Address Test…
335.579: Random Data Test…
340.360: Move Data Test…
342.141: Bitpattern Test…
421.610: Error at 9016C50
482.563: Starting loop 4
482.579: Stuck Address Test…
487.157: Random Data Test…
494.688: Move Data Test…
496.563: Bitpattern Test…
574.266: Error at F9C8A2
636.688: Starting loop 5
636.688: Stuck Address Test…
641.282: Random Data Test…
646.094: Move Data Test…
647.797: Bitpattern Test…
788.813: Starting loop 6
788.829: Stuck Address Test…
793.469: Random Data Test…
798.110: Move Data Test…
799.813: Bitpattern Test…
942.625: Starting loop 7
942.641: Stuck Address Test…
947.266: Random Data Test…
952.141: Move Data Test…
953.891: Bitpattern Test…
1094.766: Starting loop 8
1094.782: Stuck Address Test…
1099.344: Random Data Test…
1106.625: Move Data Test…
1108.297: Bitpattern Test…
1249.172: Starting loop 9
1249.188: Stuck Address Test…
1253.766: Random Data Test…
1259.704: Move Data Test…
1261.391: Bitpattern Test…
1404.000: Starting loop 10
1404.016: Stuck Address Test…
1408.782: Random Data Test…
1413.704: Move Data Test…
1415.563: Bitpattern Test…
1564.047: Test finished with 2 errors
second module
Module 0:
DDR4, 16384 MB, 64-bit, 3200 MHz
Controller0-ChannelA-DIMM0 BANK 0 Crucial Technology CT16G4SFRA32A.M16FRS
Module 1:
Empty
0.000: Detecting usable memory (16167 MB theoretical max)…
16.656: 14848 MB Test starting on 8 CPUs…
16.656: Allocating memory…
26.515: Starting loop 1
26.515: Stuck Address Test…
31.250: Random Data Test…
36.078: Move Data Test…
37.734: Bitpattern Test…
182.922: Starting loop 2
82.937: Stuck Address Test…
187.562: Random Data Test…
193.890: Move Data Test…
195.609: Bitpattern Test…
338.344: Starting loop 3
338.359: Stuck Address Test…
343.015: Random Data Test…
349.703: Move Data Test…
351.500: Bitpattern Test…
496.094: Starting loop 4
496.109: Stuck Address Test…
500.687: Random Data Test…
505.531: Move Data Test…
507.219: Bitpattern Test…
650.609: Starting loop 5
650.625: Stuck Address Test…
655.172: Random Data Test…
659.969: Move Data Test…
661.703: Bitpattern Test…
806.484: Starting loop 6
806.484: Stuck Address Test…
811.281: Random Data Test…
816.187: Move Data Test…
818.172: Bitpattern Test…
960.812: Starting loop 7
960.812: Stuck Address Test…
965.437: Random Data Test…
972.109: Move Data Test…
973.828: Bitpattern Test…
1117.156: Starting loop 8
1117.172: Stuck Address Test…
1121.750: Random Data Test…
1126.547: Move Data Test…
1128.265: Bitpattern Test…
1272.156: Starting loop 9
1272.156: Stuck Address Test…
1276.765: Random Data Test…
1282.422: Move Data Test…
1284.094: Bitpattern Test…
1426.781: Starting loop 10
1426.797: Stuck Address Test…
1431.453: Random Data Test…
1438.859: Move Data Test…
1440.672: Bitpattern Test…
1586.719: Test finished with no errors detected
Support had me ship the laptop back. Did not appear to be a RAM module issue as moving RAM to Module 0 resulted in zero errors, as opposed to Module 1. Waiting for the laptop to be returned this coming Monday with a new motherboard to see if all is resolved.
Nick
Just wanted to finish off this thread. It was the motherboard, as following your and others advice, I moved the RAM module to the other slot and had zero errors. Sent the laptop off to support and got it back yesterday. Ran tests and no problems in Module 1 slot, which is where it failed before. New motherboard and all is well.
Thanks for continuing to update and follow up in this thread. It’s always nice to know if there was a resolution to an issue and what that resolution was.
Glad you got your problem fixed and you are back up and running.
Didn’t use Memtest86 before when I found the initial issue and they replaced the motherboard. Checked memory afterwards again using MemTest64 which is what I used before and that is the program that showed memory errors in one module, not the other and showed no errors in the replacement motherboard.
These dumps are from BlueScreen reading the dump issue after each BSOD in that last couple of days.
I have been scratching my head trying to figure out what it can be. I have a theory, but one from a layman’s point of view. I don’t think it is RAM at all this time around. I think it is as simple as my browser which was 32bit during these crashes. Since the last crash, I changed that browser (Seamonkey) from 32 bit to 64 bit and since that time have yet to suffer another BSOD. Will continue to use the 64 bit version and see if there are any more crashes. IF not, what does that mean? 32 bit software issues with Framework?
At a complete loss here… will post again tomorrow, but will be running this browser constantly to see how it goes. FWIW… AVG Internet Security (Paid), MalwareBytesPremium (Paid) as my malware programs. Have HotSpot Shield Premium, but don’t run it at home, just when working in insecure locations.
Tks,
NIck
Day 2 and no BSODs using Seamonkey 64 bit (instead of my old 32 bit version. (Fingers crossed!)
OK, I checked with one of the Seamonkey (aka Netscape Communicator, aka Mozilla Suite) developers. This is what he had to say about Seamonkey 32 bit:
The x86 SeaMonkey is compiled with clang 11 and the 64 bit one with VS2019 16.11 so there are differences. If you run with 4GB oder preferably 8GB or more I suggest switching to the x64. But in any case a real live BSOD is something not SeaMonkey. Usually hardware or driver related. Make sure your graphics card drivers are up to date and maybe run a memtest. The x86 might use system code in a different location from the x64.
Well, that didn’t work out well at all. Ran Memtest86 off a usb stick and it borked the MBR. Cannot boot at all and do not have a recovery disk. Any ideas much appreciated.
