X370 Killer SLI/ AC board problems
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=6028
Printed Date: 25 Dec 2024 at 12:30pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: X370 Killer SLI/ AC board problems
Posted By: Jyaku
Subject: X370 Killer SLI/ AC board problems
Date Posted: 09 Sep 2017 at 5:08am
|
" rel="nofollow - When I bought this board, I was quite happy but over the last 2 months I keep on getting bsod's. They all have the following codes: SYSTEM_SERVICE_EXCEPTION SYSTEM_THREAD_EXCEPTION_NOT_HANDLED PAGE_FAULT_IN_NONPAGED_AREA MEMORY_MANAGEMENT I've upgraded my power supply to a 750 watt EVGA G2 since I thought it was originally the cpu was not getting enough voltage for a stable overclock. But even at stock I get BSOD's. I thought it might be memory to blame but strangely enough.. when I ran memtest when overclocked, I got a few errors. When I ran memtest at stock.. 13 rounds, no errors. My memory is F4-2400C15D-32GFXRWhich is on the QVL list. I've noticed the 3.20 bios has reduced my BSOD's but not been able to eliminate it. And I've also noticed whatever I dial into bios as an overclock.. the actual speed always shows as 25 mhz less.. for example.. 3825 will show as 3791, 3850 will show as 3816 and so and so on unless I use 3825 and 1.23125 volts with a +1.30 voltage offset. I've run out of ideas how to solve my stability problems so any and all suggestions are welcome. P.S. I know my board has LLC in some bios that I've seen but I cannot locate it my bios. How do I get to LLC settings?
|
Replies:
Posted By: datonyb
Date Posted: 09 Sep 2017 at 7:25am
i usually start with google SYSTEM_SERVICE_EXCEPTION =1] Open Command Prompt and run chkdsk /f /r on your drive to http://www.thewindowsclub.com/command-line-check-disk-windows-7" rel="nofollow - run Check Disk to identify, repair and fix bad sectors, if any, on your hard disk drive. 2] This Blue Screen can occur due to problematic drivers. Update your http://www.thewindowsclub.com/download-update-install-latest-intel-drivers-with-intel-driver-update-utility" rel="nofollow - Intel and http://www.thewindowsclub.com/update-amd-drivers" rel="nofollow - AMD drivers. Also update your Graphics or Video drivers via http://www.thewindowsclub.com/uninstall-disable-roll-back-update-drivers-windows" rel="nofollow - Device Manager . 3] Some software like McAfee, BitDefender,Virtual Clone Drive have been reported to cause this Blue Screen. Use your discretion and see if you would like to uninstall them and check if it makes the problem go away. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED = First, make sure you have enough disk space. If not, use the http://www.thewindowsclub.com/disk-cleanup-utility-windows" rel="nofollow - Disk Cleanup Tool to remove junk files and free up disk space. In my case, after the Error Code, you could see a name of a file. If a driver is identified in the bug check message, you should find out what the file is about. You could search for it on your computer and then check its Properties, or you could search on the Internet. In my case it was ??span class="gmw_">SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (nvlddmkm.sys)??/em>, where at the end you will see a file name nvlddmkm.sys displayed. A simple search showed that it is an Nvidia display driver file. This means that it was this file that caused the Blue Screen. In such cases you will have to disable the driver or check with the manufacturer for driver updates, depending n the situation. Since mine was the display driver, I decided to check if any updates were available. If it is a new Service that was added, disable it via services.msc and see if it helps. PAGE_FAULT_IN_NONPAGED_AREA = Explanation: This Stop message occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk. The system faults, but cannot find, the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error. User Action:
This Stop message usually occurs after the installation of faulty
hardware or in the event of failure of installed hardware (usually
related to defective RAM, either main memory, L2 RAM cache, or video
RAM). If hardware has been added to the system recently, remove it to
see if the error recurs. If existing hardware has failed, remove or
replace the faulty component. Run hardware diagnostics supplied by the
system manufacturer. For details on these procedures, see the owners
manual for your computer.
Another cause of this Stop message is the installation of a buggy system
service. Disable the service and determine if this resolves the error.
If so, contact the manufacturer of the system service about a possible
update. If the error occurs during system startup, restart your
computer, and press F8 at the character-mode menu that displays the
operating system choices. At the resulting Windows 2000
Advanced Options
menu, choose the
Last Known Good Configuration
option. This option is most effective when only one driver or service
is added at a time.
Antivirus software can also trigger this Stop message. Disable the
program and determine if this resolves the error. If it does, contact
the manufacturer of the program about a possible update.
A corrupted NTFS volume can also generate this Stop message. Run
Chkdsk /f /r
to detect and repair disk errors. Restart the system before the disk
scan begins on a system partition. If the hard disk is SCSI, check for
problems between the SCSI controller and the disk.
Finally, check the System Log in Event Viewer for additional error
messages that might help pinpoint the device or driver causing the
error. Disabling memory caching of the BIOS might also resolve it.
For more troubleshooting information about this Stop message, refer to
the Microsoft Knowledge Base at http://support.microsoft.com/support. MEMORY_MANAGEMENT= Memory_Management.??Those are the two unhelpful words Microsoft suggests you search for should you run into a particularly infuriating BSOD (Blue Screen of Death) error while running Windows 10. But how do you fix the memory management issue? While there are a number of causes, here are some suggestions that have worked??/span> 1. Run SFC ScannerSFC
Scanner is a Microsoft tool for detecting various problems with your
system, and running it seems to have solved some people?™s memory
management woes. Right-click the Start button, and run ?˜Command Prompt??in admin mode. A slightly intimidating black text box will pop up. Type in ?˜sfc/scannow??and press ?˜Enter?? SFC Scanner will now run through your system, seeing if it finds any errors to fix. Let it play out ??it may take some time. Even if it doesn?™t seem to find anything, some users have found their computers play nicer after it has been allowed to run in full. ------------- [url=https://valid.x86.fr/jpg250]  [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: datonyb
Date Posted: 09 Sep 2017 at 7:28am
|
sorry for the long read above ^ but it seems no short way of writing it (or copy paste in this case) so to sum up it might be hard drive failure/dodgy windows files (was this a clean + new install for ryzen? ) or dodgy video card drivers (or problematic gpu ram on the card itself) hope this helps  ------------- [url=https://valid.x86.fr/jpg250] [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: Jyaku
Date Posted: 09 Sep 2017 at 7:58am
|
yes it was a new hard drive and a new windows installation. Its a M.2 drive.
|
Posted By: parsec
Date Posted: 09 Sep 2017 at 10:16am
I have the same board with a Ryzen 1700X at 3.9GHz, VCore 1.35V + 0.00625 offset voltage, G.SKILL FlareX 16GB at 3066. I do not get any BSODs, except when testing memory over clocks at 3200. At 2933 or 3066 the PC is stable. What version of Windows are you using? What AMD chipset driver version are you using? First the slight variation in CPU clock speed is caused by small variations in the BCLK. Instead of being locked at exactly 100.0MHz, the BCLK wanders slightly, from ~99.5MHz to 100.5MHz. This slight difference in the BCLK is not unusual in board's whose UEFI/BIOS does not have a BCLK setting, and our's does not. Mine does the same thing, so I set my 3900MHz OC to 3925MHz, as you do. If the monitoring program you use in Windows showed the BCLK, you'd see the slight variation. No idea what CPU you are using, but your VCore is low for a 3825MHz OC. Is the sum of your VCore and Offset Voltage value equal to 1.30V? The CPU LLC setting is right below the Offset Voltage setting in the OC Tweaker screen. I'm still on the 3.00 UEFI, but the LLC option has always been in that location. For example:  Do you have the CPU Frequency and Voltage Change option in OC Tweaker on Manual or Auto? Are you PState over clocking, or using OC Tweaker? I assume you run your memory at 2400, and have it in the A2 and B2 slots? I suggest increasing the DRAM voltage to 1.25V when using 32GB. You may also need to increase the SOC voltage slightly to 0.950V - 1.00V. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Jyaku wrote:Posted By: Jyaku
Date Posted: 09 Sep 2017 at 12:11pm
|
" rel="nofollow - Hi there, Thank you for trying to help parsec. I am using a Ryzen 5 1600 and Windows 10 Education. Currently in my bios I have the following settings. https://ibb.co/kq0ZeF https://ibb.co/ci8bta 1.23125 base with a 1.3 v offset. I don't have anything under PState and I still can't find Load Line Calibration in the settings as you can see. Could you give me options/ guidance to have a stable 3.8 ghz overclock? I generally stuck with Gigabyte motherboards in the past and this is my first ASRock so I'm a bit confused by some of the settings.
|
Posted By: wardog
Date Posted: 09 Sep 2017 at 12:32pm
" rel="nofollow -
SAY WHAT?????????? Turn it off and reset the CMOS. 1.3v Offset? Bwhahahahaha You're lucky it's not a fireball. |
Posted By: datonyb
Date Posted: 09 Sep 2017 at 6:38pm
|
guys i also typed out the first reply regarding the volts but he states in the first post he's getting bsod on stock settings as well hence why ive suggested other options ------------- [url=https://valid.x86.fr/jpg250] [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: parsec
Date Posted: 09 Sep 2017 at 8:35pm
Your screenshot shows the Offset voltage as +130mV, which is Milli-volts, or 0.130V. That is the voltage added to, or offset from (+/-) the base VCore, in your case 1.23125V. So your actual VCore is 1.36125V. I was not sure what you meant by a 1.30V offset. If that was the true +offset (1300mV), you would be at 2.53125 volts, and have a dead CPU, if you could add that much offset. Otherwise, the way Offset voltage works is standard, a base VCore +/- the Offset voltage. Why you don't have the same VCore options that I do, I'm not sure. It may be the 3.20 UEFI version, or that you are using a Ryzen 1600. As I'm still using 3.00, I'll change to 3.20 later today and see what I get. I'm using a 1700X. Your OC to 3800 from the max Turbo clock of your CPU, 3600, would be reasonable for an Intel processor, but Ryzen CPUs don't OC much above their max Turbo clock. I'm only at ~100MHz above my processor's max Turbo of 3800MHz. So if your CPU can reach 3.8GHz remains to be seen. But you will definitely need more VCore than 1.36V. Take your OC down to 3725 with the current voltage and see what happens. Or increase the Offset to 150mV - 160mV and see what happens with the BSODs. What CPU cooler are you using? What is the CPU temperature, the Tdie if you see that shown in your monitoring program. What are you using to check VCore in Windows? What VCore do you see in Windows? ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: Jyaku
Date Posted: 10 Sep 2017 at 12:27am
|
I'm using a Deepcool Gammax 400 air cooler. My CPU temps are usually in the 40's with mild load, 55's under gaming load, but under aida64 extreme stress test it reaches a max of 72 (according to HW Mon) but max of 56 (according to the ryzen OC utility). I'm running the cpu fan at 80% fixed speed. Hmm I'll try downclocking the cpu but even at stock I was getting bsod's. (These bsod's are not like random shutdowns due to overclock). p.s. I saw your bios and am trying your settings with another offset voltage increase to SOC since I had it at stock before. It hasn't given me a bsod since... but I'll know more the longer it stays stable. I set CPU to 1.35 voltage and a 0.65v offset. Edit: Regarding the other questions.. I currently have 3825 @ 1.392v. I'm using CPU-Z and HWMon and Ryzen overclocking tool. The voltage seems to fluctuate between 1.360 and 1.392 (which is why I was looking for Load Line Control utility but still haven't been able to find it).
|
Posted By: nangu
Date Posted: 10 Sep 2017 at 1:10am
Please try to be clear with your voltage settings. 1.35 + 0.65 offset is 2 volts, I think you wrote bad numbers again becasue at that voltage your CPU will be died by now. Max recommended for Ryzen is 1.4v for 24/07 usage. Anyway, adding OC and voltage changes only will add confussion to your BSOD problem. I suggest to set frequency as manual, but leave stock value for both frequency and vcore, add only the first step on offset and test the system. Also, leave memory at default for now until you are BSOD free and can isolate the problem from the CPU.
|
Posted By: wardog
Date Posted: 10 Sep 2017 at 2:04am
|
Jyacu, please list out the hardware of your system. For me, please capture the opening Main BIOS page and post it here. Also, snap a pic of the silkscreening on the motherboard showing X370 Killer SLI/ac . |
Posted By: Jyaku
Date Posted: 11 Sep 2017 at 12:48am
|
" rel="nofollow - Ok based on advice so far, I dialed in 1.34v as cpu voltage with a 0.065v offset. It tends to fluctuate between 1.36 - 1.39v. I also upped the SOC voltage from default of 0.9 to 1.08 and although I'm running DDR4-2400mhz @ 2400mhz, I upped its voltage from 1.2v to 1.35v For 24 hours I've been stable. Is it possible that those memory issues were due to low SOC voltage? I read somewhere that 0.9V is for 2133mhz memory but I had 2400 and it would create bsod's. But now I'm running aida64 extreme and games and no crashes at all. However last week I was crashing once every 10 minutes. My hardware all together is this: Asrock x370 Killer SLI/ac Ryzen 5 1600 @ 3825 mhz (1.34 vcore with 0.065v offset) & Gammax 400 cooler G. Skill 32mb DDR4-2400 RAM F4-2400C15D-32GFXREVGA GTX 1070 Video Card EVGA 750 G2 Power Supply (upgraded from 500 watt EVGA) Western Digital Blue 256 MB M.2 Drive primary Western Digital Blue 4 GB storage drive Fractal R5 case |
Posted By: Jyaku
Date Posted: 11 Sep 2017 at 1:24am
|
" rel="nofollow - I still don't know why I cannot find Load Line Calibration in my bios no matter where I look. Any ideas?
|