New
#11
MemTest86 is different from MemTest86+, we recommend the + version :)
got it, starting the test right now. :)
well, ran MemTest86+ version 5.01 for over 8 passes with no single error.
so I stopped it during the 9th pass as I need the pc for my work.
glad to see there is no RAM issue, but still suspicious there might be an issue I can't reproduce.
haven't had a single BSOD since I started troubleshooting though. :)
after working great the last few days I got a total system freeze today.
the only solution to recover was a system reset.
rebooting worked fine and now system is running as if nothing happened.
I was doing nothing special while it happened, just 2 browser were running.
I attached the log files, hope it helps.
note: I realize that no dump file was written although it's switched on.
A dump is only created with a bluescreen as that is actually a system crash that can be caught. The other crashes can't be caught by the system, with a freeze the system can't response and with a shutdown/restart the system doesn't get the opportunity to generate a dump because the data in the memory will be gone already as it is volatile memory (memory that is present as long as there is power).
got a BSOD right now, 5 min. after the reboot.
as if something made the system unstable, while doing actually nothing I suddenly got the "IRQL_NOT_LESS_OR_EQUAL" BSOD caused by ntoskrnl.exe.
Are you OC'ing?
What are the memory timings according to the BIOS?Code:CPUID: "Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz" MaxSpeed: 3500 CurrentSpeed: 3504
They should be
Code:15-15-15-36
no, I'm not - everything on stock and auto in the bios.
for the ram I use the XMP-2400 profile (last attached picture).
my ram is 1,5 months old, exact specs:
Corsair Vengeance LPX 16GB (4 x 4GB) DDR4 DRAM 2400MHz C14 memory kit for DDR4 Systems (CMK16GX4M4A2400C14) at Amazon.com
Last edited by sahafiec; 18 Feb 2016 at 13:17.
after the BSOD I rebooted and run a "sfc /scannow" which found and corrected some errors.
those were not there prior the BSOD but still I don't know if they are a cause or a result of the BSOD.
but strangely mostly after a BSOD there are some errors, luckily all repairable by "sfc /scannow".
Please remove all OC'ing on your system, OC'ing may make the system stability worse when there are problems present.
Even if the OC'ing is not the cause just remove it with the reason that it may cause more instability.