Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

[parsec]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Still beating on this thread, the forum is slow lately...

My Haswell Xeon without Hyper-Threading:



Not in safe mode. I suppose the hard core over clocking crowd is aware of this, just noobs like me aren't.

So would you rather have four threads at 184GFLOPs or eight threads at 163GFLOPs?

Or is all that matters is a high OC speed?

EDIT: Not sure what happened to that pic, but fixed now.

[Ken429]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

I think we should change the title of this thread - the LinX Contest?!

Are you trying to keep your attachment a secret? Attachment 7711 won't display for me.

I am getting more confused every time I run an new iteration of LinX. Looks like disabling Hyper Threading and running memory set to 2048 and then 4096 gives a different GFlop result. Is that normal? I had hoped that disabling Hyper Threading might reduce the Vcore required and also the core temps so I could increase the multiplier and get past 46 but that was not to be. In fact the maximum core temp reached 86C during the 4096 run.

Now I understand, the site must be broke since I can not add an attachment either.

[parsec]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Yes, seems to be a little something not right with the post editor. Just fixed the picture, hopefully it will stay.

You don't seem to be reading Prof Jim's post about LinX.

Increasing the amount of memory used during the tests changes the GFLOP results, they should be higher. The time each iteration takes is longer too. Since each iteration runs longer at ~100% core usage, your core temperatures will increase.

You may not notice this with your CPU cooler's fans and fan speed configuration, but LinX does not run the CPU cores at 100% usage throughout the entire test, or each iteration. You have seen the change in core usage in HWiNFO when LinX runs, right? The minimal memory tests don't stay at high core usage for very long, but use more memory and they last longer. My CPU cooler's fan speed is going up and down all the time in a "short" test, meaning the core temperatures are going up and down constantly.

Disabling Hyper-Threading increased my GFLOP results on my Xeon, I don't see why your CPU would be different.

I know disabling Hyper-Threading is a common trick in over clocking, it may only help stability rather than temperatures. A CPU core can only do so much work, and apparently the amount of additional components in a CPU to allow for hyper threading is small. You should research that question or test it more thoroughly before deciding if it is worth disabling.

[Ken429]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Thought I'd add the screen dump that should of gone with a previous post. The forum software would not let me add it for a day or two. Like I said above, I was hoping I could "cheat" and get to 250 GFlops by disabling Hyper Threading and increasing the multiplier but the max core temps were already beyond what I would consider reasonable and "safe".

[parsec]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Darn close to 250GFLOPs, that's just a nice round number, your results are great.

I'd like to see what a comparable Haswell-E processor would do in LinX. Getting one to 4.6GHz would be difficult, the highest stock clock is the 5930K, 3.7GHz max Turbo. Quite a bit more of an OC than a 4970K at 4.6GHz. It might (should) do the same at a lower clock speed.

The thermal throttling temp for the non-E Haswell processors is 100C. My 4670K thermal throttled running AIDA64 with a Corsair H60, I forget the OC, probably 4.4GHz.

Intel is normally conservative about their products, so if thermal throttling occurs there is little if any danger of damage if it happens a few times. If the CPU shut itself off due to high temperature, then I would be worried about potential damage, but that is just a guess.

Your specs list the water block you have, I'm curious what radiator and fans you are using. Just curious what your setup is.

You can see now why the "delidding" craze is a reality with these Haswell processors. I'm not suggesting it, but some swear by it. Given the payback of the few OCs we've done here, I don't see the point beyond reaching an OC speed simply to do so. That's a fine thing to do, but not what I care about.

[Ken429]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Cooling system used for 4790K in a Corsair 650D Case:

• Swiftech Apogee XL Waterblock
• Swiftech Maelstrom 5.25" Dual Bay Reservoir
• Swiftech MCP 35X Pump
• Black Ice Stealth GTS 280 Radiator
• Bitfenix 2 140MM PWM Fans

The Swiftech Reservoir and MCP 35X Pump have become extinct. Probably a good thing since their replacements are cheaper and the MCP 35X Pump is too powerful and hard to control via the ASR Z97 Extreme6 MB Fan control built into the BIOS. It want's to run the Pump at 100% once the Core Temps gets to 80+C. At 100% the Pump turns the cooling solution to foam! The Pump has a separate power source so I have not gone to the trouble of figuring out how to put a cap on it. If it just used a 4-pin connector I could use a voltage reducer that comes with Noctua Fans.

I got into the custom water cooling kick when I built the 3770K system and watched the temperatures go out of sight relative to my 2600K system! I went from a Corsair H50 to H60 to H100 and then to the custom cooling solution. However, it was an exercise in futility since I only ended up reducing the core temps by a few degrees C in the process. But then it's a hobby!

[parsec]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Thanks for the info Ken, I really wanted to know if you were just cooling the CPU with your water loop, or had other things like a video card in the loop. Seems to be just the CPU.

We should be able to tweak the PWM control for the MCP35X pump to stop the foaming problem when the CPU temp is 80C+. Since the pump has a four pin molex connector for power, and a four pin PWM connector for speed control, that gives you flexibility.

I don't know how you have your pump and radiator fans connected to the board, or if you do something else with the fans. Not to mention any case fans connected to the board. Since our board has two true PWM fan headers, CPU_FAN1 and CHA_FAN1, you can separate the pump and fans on their own PWM header.

I'll focus on the pump now, and once we know more about how your radiator fans are configured, we can take it from there.

First, the fan configuration settings in the UEFI. You know the main problem with the pump is the "Critical CPU Temperature" being set to 80C, and you can't increase/change that with the settings provided. But you can change that temperature in the A-Tuning utility, with the FAN-Tastic Tuning tool.

My idea is this: Use the CHA_FAN1 header for the pump's PWM connector. You can choose any of the fan speed profiles for the pump, including the Custom option that monitors the CPU temperature. I have the Custom option selected, but the following works for any of the speed profiles.

In Windows, you start A-Tuning and select FAN-Tastic Tuning. Select CHASSIS FAN 1 from the drop down list. My settings from the UEFI look like this:

<a href="http://tinypic.com?ref=i19n9h" target="_blank"><img src="http://i58.tinypic.com/i19n9h.jpg" border="0" alt="Image and video hosting by TinyPic"></a>

(I'm doing this on my Z87 OCF board PC, which has F-Stream instead of A-Tuning, but FAN-Tastic Tuning works the same in both programs!)

We can see in the graph the PWM speed jump to 100% when the CPU temperature is 80C. Find the two yellow dots at the very top of the display, at the 100% speed level. Those dots are only half visible but you can see them. One of those dots is aligned with the 80C point at the bottom of the graph. That is the one we will be changing.

Now move your mouse pointer over that dot, press and hold the left mouse button, and you should be able to move that dot to the right with the mouse, all the way over to the 100C point on the graph. Then the graph will look like this:

<a href="http://tinypic.com?ref=28vvk83" target="_blank"><img src="http://i59.tinypic.com/28vvk83.jpg" border="0" alt="Image and video hosting by TinyPic"></a>

I also reduced the speed to the 70% level, by grabbing and moving another dot that is not at the 100C level. But you can do whatever you want the pump's speed to be.

If you want this profile to be applied every time the PC starts, you must check the Auto apply when program starts option, and set A-Tuning to Auto-run when Windows boots. Another option for you is to just tweak the pump speed profile like this when stress testing the CPU.

So, does this make sense? Any help for you?

[Ken429]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Just to clarify, the pump has two wires going to a molex and two wires going to the PWM Connector.

I know I can use the Fantastic Tuning program to control the pump but I hate to use an add on program to control the pump/fans. I guess I got spoiled along the way somewhere, probably Gigabyte, where the Fan Tuning Program actually updated the BIOS. So...I just set an arbitrary cutoff for OC'ing of 79C!!

Now that you got me going on the Pump Speed control I think the best thing I can do (based on the ASR BIOS limitations) is change the temperature to monitor from CPU to MB for the connector (CPU_Fan1) used for the Pump and leave the Radiator Fans connected to CHA_Fan1 set to monitor the CPU Temperature. That way the pump will run at a constant speed and I can let the fans run based on the CPU temperature. The speed the pump runs at really has little or no effect on the CPU Temperatures anyway.

One minor change to Plan A. I had to switch the Pump to CHA_Fan1 and the Radiator Fans to the CPU_Fan1. The CPU_ Fan1 will not let you use Monitor MB but CHA_Fan1 will!

[parsec]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Your method will work fine too, since you don't want to change the pump's speed with changes in the CPU temperature, which was not clear to me in your earlier post.

Mobo manufactures have different philosophies regarding protecting users from themselves. ASRock makes you work a little bit to override the 100% fan speed at a CPU temperature of 80C. Apparently Gigabyte let you modify fan speed curves stored in the BIOS, which can be a bad thing if the user does not know what they are doing.

While we may be somewhat stuck with the 100% fan speed at 80C, OTOH we can set the fan speed to 0% at lower temperatures, virtually unheard of in fan speed control software.

[Ken429]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Back to my original problem that initiated this thread: I updated the system to W10 and updated the BiOS to 2.20. Then I got greedy and decided to update the boot SSD to a new Sandisk Extreme Pro 240GB. Once I started messing with the devices attached to the SATA ports everything went down hill again. So...after much playing around SATA Port 1 finally failed or at least when I connect the boot SSD to Port 1 the system tries to boot Windows and then shuts down. If I leave Port 1 empty all the other Ports work! So I guess what was happening is the bios detected all the devices on the SATA ports correctly but Windows could not read the device on Port 1. Making Port 1 the boot port highlighted the problem. I am finally RMA the MB. We'll see what the next one does. I'll even try putting the 2400 memory back in to see if it was not the problem all along!

[Ken429]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

I can tell you people are dying to hear how the replacement MB worked out! Anyway, I finally get all the SATA Ports with the new MB. However, a new twist appeared, I have to tell the BIOS that SATA Port 4 is for a SATA drive leaving it set to Auto makes the port unavailable to W10. I don't know is this is a BIOS 2.20 change or a W10 issue or what - all I care about at this stage is when I set Port 4 to SATA in the BIOS all is well.

Also, I tried using the OC settings provided by the BIOS and the G3258 won't run beyond 3.8GHz. When I go in and leave everything on Auto except the Core Ratio (40), Cpu Vcore Voltage Mode (Adaptive), Vcore Adaptave Voltage (1.120), Vcore Voltage Additional Offset (0.100), Cpu Input Voltage (Fixed), Fixed Voltage (1.900) and CPU Load Line Calibration (Enabled) the G3258 is stable at 4.0GHz. Seems strange that less of everything is better?!

[Ken429]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

parsec,

As I said above, the replacement Z97 Fatal1ty Killer MB solved all my Sata Port issues.

Now, I got another question/request - I'm trying to use the Killer MB and the G3258 processor running at 4.0GHz as a Plex Movie Server. I was using one of my Z97 Extreme6/4790K systems and of course it handled the job with no issues. However, the G3258 tends to get bogged down transposing movies to send over the Internet - remote user is trying to minimize the bandwidth "shortage" by playing with the compressing from the Plex Server. The G3258/Plex Server does not have a problem in-house since there is no compressing required. Anyway, since you got me involved with the G3258 processor, short of buying yet another 4790K processor, do you have any suggestions on what is a reasonably priced processor that is a step upward that will/may keep the Plex Server happy?

[profJim]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

parsec has been AWOL since last May.

He is a forum moderator at ASRock Forums

Be sure to give him the following message:

[Ken429]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

ProfJim,
Thanks for the information. I will head over there for my ASRock questions.

How are you making out with your Reflect backup software? I just used it to recover a system that got screwed up installing and uninstalling AnyDVDHD - it made W10 lose my Sata DVD drive when I uninstalled it - I think. Anyway, Reflect 6.0 with WinPE 5 Recovery Boot Option Enabled worked great. Took a little getting used to but I have not had any issues with the package - both the free version and the purchased 4-pack. Good find.

[profJim]

Re: Windows Only Sees Sata_0 and Sata_1 on ASR Z97X Killer MB?

Ken,
I'm glad to hear that your sata issues are now history with your replacement motherboard.

Old habits die hard and I'm still using Reflect's WinPE environment to manually make my system backups instead of letting Macrium Reflect automatically do backups while my system is running. I recently bought an Asus PB278Q 2560 x 1440 monitor (AHVA panel) for photo editing. It's a great monitor with virtually the same color quality as IPS and PLS monitors and it comes with an excellent monitor stand where I can easily pivot the screen from landscape mode to portrait mode. My poor little GTX460 video card is powering the new monitor along with my almost six year old Asus VH242H 1920 x 1080 monitor. That works out to 5.76 million total pixels. Needless to say I'm not a gamer.

Say hi to parsec for me.