Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited

Everything posted by Dzhimen

  1. That's what I want. I would like to convert my case aRGB to normal 12V RGB, just to sync up with everything else in my system.I don't need the addressable part. This adapter sorta does that, but there are some weird issues with flickering. And I was just wondering if It's just me (maybe faulty adapter) or others have experienced a similar issue. Some people in this thread are stating that it "just simply works", so I wanted to know what exactly this means... ?
  2. Hey guys. I stumbled upon this thread because I have a similar issue with addressable vs non-addressable RGB. My case is Phantex ECLIPSE P350X and my motherboard is Asus B450F Gaming. The case has addressable RGB built-in, but the motherboard only supports non-addressable RGB (4-pin). So when I saw the DeepCool adapter which was linked in this topic, I thought I'd give it a shot to see if I can sync my case RGB with my ASUS Aura Sync ecosystem. I connected the adapter accorging to the attached image: 1 - Into the motherboard's 4-pin non-addressable RGB header 2 - Into SATA power from the PSU 3 - Case RGB connector (3-pin addressable RGB) 4 - Here I plugged in 2 daisy-chained non-addressable RGB strips (4 pin 12V) The non-addressable RGB strips work flawlessly (as before when they were connected directly to the motherboard's RGB header). The problem is with the case's addressable RGB. This DeppCool convertor doesn't seem to "convert" the 12V non-addressable signal quite correctly to the 5V addressble RGB. I control the RGB with the Asus Aura software. 1) When I set it to solid color RED (255, 0, 0), GREEN (0, 255, 0) or BLUE (0, 0, 255) it works fine. 2) When I set it to mixture of the 3 main colors (0, 255, 255) or (255, 0, 255) etc, it mostly works fine. 3) But some combinations of colors just dont work. For example if I set it to (0, 255, 100), the color flickers between two different shades of the blue-ish green color. 4) Some other colors also flicker, but between two completely different colors. For example (255, 32, 0) flickers between orange-red color and a shade of violet. 5) This flickering effect is also not always the same, if I restart the computer the flickering from two different colors turns into flickering between two shades of the same color, for example. Or the flickering even stops. The effect varies greatly from time to time. Now the issue described above is when the color is set to static. This means that If I use any other effect (breathing, rainbow etc.), there is always flickering involved, because most of the colors I set are flickering. Even if solid red is working fine, if I set to breathing red, there is flickering in between. I tried to capture this on video, but unfortunately it's just impossible to capture and show you the flickering. It's happening too fast I guess... And the problem is only with the addressable case RGB. The non-addressable strip I have connected to the same DeepCool adapter works perfectly fine, no issue whatsoever. So the bottom line is I am now limited only to like 10 static colors and I cannot use any effects (even simple breathing), if I want to sync my case RGB with the rest of the system. You could say it's better than before when I had to sync it manualy, but still it's a shame that I am limited to this extent. My question is for the ones who also bought this adapter: Have you experienced similar issues to the one described above, or it just simply works for you?
  3. I recently purchased the same case and am also experiencing some "inconveniences". I have an Asus motherboard (Asus ROG Strix B450-F Gaming) and I purchased this Phantex P350X case because it was supposed to be compatible with Asus Aura Sync and I wanted the case RGB to be synced with everything else in my build. While assembling the build I realized that my motherboard has 2 traditional 4-pin RGB headers (non addressable), but the case requires 3-pin addressable header. This is the case connector, which is supposed to go into the motherboard (3-pin addressable): As it turns out it is not enough to check that the product (LED strip, case lightning etc.) is compatible with Asus AuraSync, you need to make sure that it is the same "type" of RGB. I have non-adressable RGB strips from Phantex (Aura Sync compatible) and they connect to my 4 pin RGB header on motherboard just fine. But for the Phantex case RGB I would need a 3-pin addressable RGB header, which my motherboard unfortunately doesn't have. So I didn't realize that before and now it's really bothering me. I can control everthing in my case from Asus AuraSync software, except for the case LEDs, which i must control with the physical buttons on the top of the case. It really bothers me more than it should. ? The way I see it, there is no way to connect the case LEDs to my motherboard. Some kind of adapter or any other solution simply doesn't exist. Idealy I would like to convert my case RGB to non-addressable and connect them to the motherboard 4-pin header, but this cannot be done. The only way is for me to either change the case (which I otherwise really like), or to replace the motherboard with one that has both 4-pin non-addressable RGB headers (for my LED strips) and 3-pin addressable headers for the case RGB. If anyone has any other solution that I could try out, please let me know. This thing is driving me crazy. ?
  4. Wow! Just... wow! I searched the web and tried to figure this out for more than an hour. Nowhere did I come across this solution. Clicked, installed and after 30s, the thinng works. I can't thank you enough! Amazing! And You're right, my previous laptop was upgraded to Fall Creators Update, this one was a fresh install. So I guess that has something to do with it. Still dont know why does this functionality need to be intalled separately though... But nevermind, I'm just glad it works now. Thanks again, You're awesome!
  5. Hello. I am having a small problem (more like an inconvenience) and was hoping somebody would help me indentify the problem, because im all out of ideas. I am trying to get Microsoft Edge browser to play HEVC videos. As far as i understand, MS Edge does support HEVC playback if there is hardware support for it. It did work on my previous laptop (i5-5200U and AMD R5 M255 disccrete GPU). I currently have Acer Laptop with Intel UHD 620 graphics (i5-8250U) and whenever I try to play HEVC videos in mp4 contanter in MS Edge, i get the message "Invalid source" and the video doesnt play. My new laptop does not have a discrete GPU. For example, the first video from this site was working on my old laptop, but now i get the "Invalid source" message on my new one. Intel UHD 620 iGPU supports h265/HEVC hardware acceleration. I have the installed and updated GPU drivers (in windows 10 device manager, the driver for Intel(R) UHD Graphics 620 is version, I am running latest windows 10 version (FCU - 1709-16299.98, MS Edge version is "Microsoft Edge 41.16299.15.0" and "Microsoft EdgeHTML 16.16299". Where is the problem? Can anyone with same CPU test the linked video and report if it works? I am experiencing some other minor GPU glitches and am starting to suspect that there is something wrong with the driver or the chip... Thank You very much in advance. Have a nice day.
  6. Hello guys. I built a small hobby mining rig (nothing serious, mostly from the parts I had on hand) and I'm having a strange issue with the 2 GPUs I'm using and I was hoping that someone would be able to tell me what's the source of the problem I'm experiencing. The build is: - Gigabyte GA-H110M-S2H - i3-6100 - 2x4GB DDR3-1600 RAM - XFX 550W 80+ Bronze PSU - KFA2 GTX 1060 3GB - PowerColor RedDevil RX580 8GB Now I know the parts kinda don't make sense for mining, but that's what I had from before and I'm not currently interested in investing into a new motherboard, for example, with the current state of things regarding mining... So I'm specifically looking for the source of the issue. The system is running on a SSD with Windows 10 and the latest NVidia and AMD drivers installed. So the motherboard has one PCIe 3.0 x16 slot and two PCIe x1 slots. I put the RX580 directly into the x16 slot, and GTX 1060 on a riser (x1-->x16) on the bottom x1 slot (the other x1 slot was being covered by the RX580 fan cooler. RX580 requires a 8pin+6pin, the 1060 requires a 6pin. Bacause the PSU only has one PCIe power cable, I plugged that into the RX580, and for the 1060, I used the adapter (2xmolex-->PCIe 6pin) that came with the KFA2 1060. From all the online calculators I found, the 550W should be fine for those two GPU-s at stock speeds (again, I would buy bigger, but that's what I had at home), but just in case, I tried supplying the 1060 with 6pin PCIe power kable from a secondary PSU (Seasonic 360W 80+ Gold), and the problem was the same, so I think I can eliminate the PSU as the source of the problem. Both cards get detected just fine, and are working. When I open NiceHash miner and mine with only the RX580 (plugged directly into x16 slot), it mines fine, load goes to 100%, no problem there. When I mine only with the 1060 on a riser, it also Works fine, load to 100%. But when I try to mine with both of them at the same time, either none of them work (load goes up for 2sec, then back to idle, then after 5s idle, the load goes back up, but only for one or two secs, then back to idle etc. and NiceHash, displays 0 $/day and 0 MH/s), or one card mines fine, as it does when I mine only with that card, but the other one doesnt work (as previously described). I can't get them to mine at the same time. I tried swapping them (1060 directly onto x16 slot and 580 on a riser into x1 slot), no difference. Separately they worked fine, but together, they didn't. I tried supplying the 1060 with a secondary PSU wihtout the adapter, so directly from PCIe cable, still no difference. I tried two NiceHash instances, made no difference. I am currently mining with the 580 in that system and the 1060 in my personal PC, and they both work fine, runnung for 3 days now, no problem. But I would like to run them both on one system. Would anyone happen to know any apparent reason why this is happening? A Google search revealed that some people have no problem mining with both AMD and NVidia in NiceHash at the same time. Is it the problem with the PCIe slots on my motherboard? Maybe problem with the riser? Or is it a NiceHash problem? Any help would be greatly appreciated. Thanks in advance!