sgtsixpack
New Member
- Joined
- Sep 7, 2015
double post
Last edited:
-
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
FEATURED Kingston HyperX Savage 2x4GB 2400 CL11 - HX324C11SRK2/8
- Thread starter Woomack
- Start date
sgtsixpack
New Member
- Joined
- Sep 7, 2015
My best Intel extreme tuning utility score with the improved xmp settings
A 1600 999 24 1t comparison vs 2400 10 12 13 30 313 1t
2 x 8Gb Hyper X Savage 2400 @ 10-12-13-30-313-1t
A 1600 999 24 1t comparison vs 2400 10 12 13 30 313 1t
2 x 8Gb Hyper X Savage 2400 @ 10-12-13-30-313-1t
My best Intel extreme tuning utility score with the improved xmp settings
A 1600 999 24 1t comparison vs 2400 10 12 13 30 313 1t
I tried to hit 2600Mhz again and following Sobe's settings I got beeps, I tried again with a combination of Sobe's settings ( 12-15-16-35-338-2t) and a kingston 2800 low timing profile in my bios but again got beeps. I had PCH core 1.15v and PCH IO 1.55v (the same as 2400 XMP profile) & 1.65v DDR, however I don't know what setting in the bios is related to the "memory ctrl voltage" (from Wookmack's post): http://www.overclockers.com/forums/attachment.php?attachmentid=148640&d=1408700933
Could it be system agent? I have that randomly fixed @ +0.05v it could be the problem, the only place I see it is in EasyTune and I only have that installed on a secondary OS.
Last edited:
- Thread Starter
- #23
It doesn't really matter. Memory controller is usually strong enough to run at 2600 without bumping SA or other voltage. You can try to set it higher but I doubt it will help. I was running even i3 CPUs with memory at 2933 on stock SA.
Memory OC profiles in most motherboards are usually useless. Simply most manufactuers are adding them prepared on higher memory series while not all are able to run as high or at so tight sub timings.
I think that for higher clock you are missing some correct sub timings or additional settings that are not always available on non-OC series motherboards. Anyway up to 2600/2666 should be possible on any motherboard so I'm not sure what else can be missing there. However I doubt that memory @2600+ will be faster than 2400 CL10.
Memory OC profiles in most motherboards are usually useless. Simply most manufactuers are adding them prepared on higher memory series while not all are able to run as high or at so tight sub timings.
I think that for higher clock you are missing some correct sub timings or additional settings that are not always available on non-OC series motherboards. Anyway up to 2600/2666 should be possible on any motherboard so I'm not sure what else can be missing there. However I doubt that memory @2600+ will be faster than 2400 CL10.
sgtsixpack
New Member
- Joined
- Sep 7, 2015
Its been running fine but started with hangs while p2p'ing, some CTD in BF4. Then I got a couple of BSOD while playing BF4 and used "WhoCrashed" to analyse the crash dumps:
On Fri 11/03/2016 12:11:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031116-35178-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680005DB328, 0xC6B0000371F53867, 0xFFFFFA8011F27A90)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 10/03/2016 17:55:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031016-23946-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003374070, 0xFFFFF88008F45CD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
First I thought it might be my uncore clock but after tweaking that I got the error message above about memory so I put the RAM to 2400 stock timing and so far no crashes. I've not tested that for long but now I've gone and put cas 10 back but with the other timings standard like: 10,13,14,32 (up from 10,12,13,30).
Maybe a little memory degradation? Since it was running fine for like 6 months.
On Fri 11/03/2016 12:11:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031116-35178-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680005DB328, 0xC6B0000371F53867, 0xFFFFFA8011F27A90)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 10/03/2016 17:55:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031016-23946-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003374070, 0xFFFFF88008F45CD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
First I thought it might be my uncore clock but after tweaking that I got the error message above about memory so I put the RAM to 2400 stock timing and so far no crashes. I've not tested that for long but now I've gone and put cas 10 back but with the other timings standard like: 10,13,14,32 (up from 10,12,13,30).
Maybe a little memory degradation? Since it was running fine for like 6 months.