 RLGL wrote:What is the EXACT error message you are seeing? |
| badbri wrote: Samsung-SSD-970-EVO-Plus-1TB Average user bench = 263% so you are not far off the average for that SSD. |
| badbri wrote: the website DOES NOT state if a RAID array was in use for the tests from what I could see. |
| badbri wrote: That could be the reason. What does the BIOS say when you load the SPD ? At 2666 (not overclocked for any 300 series motherboard) good ram will be at 15-15-15-35 1.2v @ 2666Mhz. I suggest G.SKILL ram, F4-3000C15D-16GTZ would be a good choice if you want 3000Mhz or if you do not want to overclock above 2666 then RipJaws F4-2666C15D-16GVR. Both are designed for low CAS at rated speed and are on the QVL list. |
| Xaltar wrote: The debug code that is displayed last and remains on the display is the one that indicates where the problem lies. If the codes all clear and the system then boots then there is not problem, if a code sticks and the system halts, that is when you have a problem and the code will give you an idea as to where. Make sure your RAM is installed in slots A2 and B2 and that it is properly seated. Code 55 typically means the RAM was not detected. Before you go to all the trouble of getting different RAM, make sure it isn't something simple like the RAM not being fully inserted. |
| Event4101 wrote: I noticed you used the word "lately" which seems to hint that everything had been working fine until just recently, when the BSOD started to appear. Just about all BSODs will provide a stop code along with a set of four, eight character, hexadecimal codes that can provide additional insight into what went wrong. You might want to take notice of those codes and then refer to this web page for how to interpret that information for additional clues to what went wrong. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management Searching the Windows "System" or "Application" event logs for the time just before the BSOD appeared might also provide you with some clues to the problem. You can also use a utility program like BlueScreenView to help analyze the Windows crash dump file that is often written to the hard drive when a BSOD occurs. http://www.nirsoft.net/utils/blue_screen_view.html You didn't mention what version of Windows you are using, but be aware that Windows 10 has a habit of installing new hardware drivers as part of the automatic patch/update process. New hardware drivers can be buggy, or encounter unforeseen compatibility issues, which often result in memory corruption or memory violation errors, that then lead to the surprise BSOD. You may want to review the Windows Update installation log to see if any updated drivers were recently installed without your direct knowledge. Running a memory test like memtest86, or the built-in Windows memory diagnostic tool, is also a decent way to tell if there is a memory related hardware problems, versus a potential driver problem. It does seem like you ran a memory test that returned no errors, once again making me suspicious that your problem may not be related to a failing component. It appears you are using a Corsair 8GBx2 dual channel memory kit. Something you might want to try would be to run on a single stick of memory to see if the problem disappears. Try one memory stick and then the other, and maybe try different memory slots. See if the problem follows a specific memory stick or is related to a specific memory slot. It is also possible for hardware to develop problems as components heat-up. So notice if things tend to crash after the computer has been powered-on for a while, or maybe during some hard use, such a gaming. Another troubleshooting technique would be to remove all add-on components and run the computer in the most basic, stripped-down, bios defaults, configuration. That could help to isolate the problem to an external USB device, a third-party graphics card, an add-on SATA controller, a changed bios setting, etc, etc, etc. Anyway, that is my two cents in 500 words or less. :) |
