F5F Stay Refreshed Hardware Desktop Performed Ran MemTest64, system restarted. Possible RAM issue or another cause?

Performed Ran MemTest64, system restarted. Possible RAM issue or another cause?

Performed Ran MemTest64, system restarted. Possible RAM issue or another cause?

L
Leumas_R
Member
155
09-29-2018, 03:28 PM
#1
I purchased 96 GB (two 48 GB units) DDR5 memory from G.Skill at 4800 MHz. After running MemTest64.exe overnight, the system restarted itself. When I opened the event viewer in the morning, it had rebooted just one hour after starting the test. At shutdown time, the Software Protection service ended abruptly—this has occurred once before. The next steps will restart the service; it has already terminated twice. A reboot was scheduled in 120,000 milliseconds. The error message read: %%2296144000. The last system shutdown on January 14th at 12:58 AM was unexpected and came from a bugcheck (0x0000003b). A dump was saved to C:\Windows\MEMORY.DMP. The reboot happened without a clean shutdown. This might point to memory issues or a critical Windows process exhausting resources. I’m unsure if this means the memory is faulty or if it’s just a rare occurrence. I’ve run MemTest64 earlier today and it completed fine with no errors. So far, everything seems normal. I’m considering returning the memory, but it appears to be functioning correctly. This could be related to unstable kits like G.Skill RipJaws 96 GB.
L
Leumas_R
09-29-2018, 03:28 PM #1

I purchased 96 GB (two 48 GB units) DDR5 memory from G.Skill at 4800 MHz. After running MemTest64.exe overnight, the system restarted itself. When I opened the event viewer in the morning, it had rebooted just one hour after starting the test. At shutdown time, the Software Protection service ended abruptly—this has occurred once before. The next steps will restart the service; it has already terminated twice. A reboot was scheduled in 120,000 milliseconds. The error message read: %%2296144000. The last system shutdown on January 14th at 12:58 AM was unexpected and came from a bugcheck (0x0000003b). A dump was saved to C:\Windows\MEMORY.DMP. The reboot happened without a clean shutdown. This might point to memory issues or a critical Windows process exhausting resources. I’m unsure if this means the memory is faulty or if it’s just a rare occurrence. I’ve run MemTest64 earlier today and it completed fine with no errors. So far, everything seems normal. I’m considering returning the memory, but it appears to be functioning correctly. This could be related to unstable kits like G.Skill RipJaws 96 GB.

J
julian_PVP
Senior Member
465
09-29-2018, 03:28 PM
#2
No, I didn't try it.
J
julian_PVP
09-29-2018, 03:28 PM #2

No, I didn't try it.

I
iTzDrVansPT
Member
165
09-29-2018, 03:28 PM
#3
I didn't know, but I just tested it and it worked without any issues.
I
iTzDrVansPT
09-29-2018, 03:28 PM #3

I didn't know, but I just tested it and it worked without any issues.

A
ali_303
Member
50
09-29-2018, 03:28 PM
#4
Check if underclocking the RAM to 4400MHz helps, as this might indicate a RAM issue. Ensure your BIOS is up to date. Install 48GB sticks, but verify CPU and BIOS compatibility. Test with one stick at a time in different slots. Update your chipset and relevant drivers.
A
ali_303
09-29-2018, 03:28 PM #4

Check if underclocking the RAM to 4400MHz helps, as this might indicate a RAM issue. Ensure your BIOS is up to date. Install 48GB sticks, but verify CPU and BIOS compatibility. Test with one stick at a time in different slots. Update your chipset and relevant drivers.