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


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards


About Husky

  • Title
    Technology Enthusiast
  • Birthday 2002-01-22

Profile Information

  • Gender
  • Location
    Western Cape, South Africa
  • Interests
    Computers, tinkering with things and anything with an engine!


  • CPU
    Intel Core i7 6700K
  • Motherboard
  • RAM
    ADATA XPG Z1 16 GB @ 3000MHz
  • GPU
    MSI AMD Radeon R9 390X GAMING 8G
  • Case
    Corsair Graphite 760T V2 (Arctic White)
  • Storage
    Samsung 970 EVO M.2 NVMe
  • PSU
    Corsair AX860
  • Display(s)
    Samsung 27" Curved VA + Dell 24" IPS
  • Cooling
    Corsair Hydro H110i GTX
  • Keyboard
    Cooler Master Quickfire Rapid-i (Cherry MX Blue)
  • Mouse
    Razer Deathadder Elite
  • Sound
    Schiit Modi 2 Uber, Schiit Valhalla 2, Beyerdynamic DT 990 Edition (600 Ohm)
  • Operating System
    Microsoft Windows 10 Pro

Recent Profile Visitors

1,668 profile views
  1. Have you tried unplugging the monitor from power completely and plugging it back in?
  2. About the 30 day trial thing, there is a trick to reset it back to 30 days by deleting a file in ~/Library/Application Support/ called ".ffuserdata" (you need to show hidden files in Finder with Cmd+Shift+. This allows you to continue testing it. In terms of managing external drives, I don't often transfer files between my Windows and Mac machines. If I really have to use an external drive for that then I format it as exFAT which both Windows and macOS will read/write to but I don't like this method since exFAT isn't the best file system. I normally just use my file server to transfer files between the 2. I would highly recommend formatting your external drive as Mac OS Extended (Journaled) if you are going to use it for stuff like video editing on a Mac due to performance and reliability reasons. If you need to transfer files I would do it over the network and if you need to store files on an external drive from both your Windows and Mac machines then consider partitioning it into an NTFS and Mac OS Extended partitions. Paragon NTFS works reasonably well, but I would never use it for any performance or reliability critical work. I am not sure when the new MacBook Pros are coming out, might be the Apple Special Event coming up in a few days. I would get a MacBook Pro if you would appreciate portability rather than an iMac Pro. I just think that Mac laptops are a lot more useful than their desktops because of their portability.
  3. Yeah try Linux, then you can completely rule out whether it is Windows or your actual hardware. If it doesn't freeze in Linux then it may be time for a Windows reinstall.
  4. Yes, but it is not recommended. If you don't need to use any Windows-only programs then you could give a lightweight Linux distribution such as Lubuntu a try. But if you have to use Windows, and if you can only use the 32-bit version, then yes it will work but as I said it is not recommended.
  5. Simple test to see if it is OS or system drive is to download a Linux distribution (such as Linux Mint) and write it to a USB drive using a tool such as Etcher. Boot off of the USB and run Linux in live mode and use your computer for a bit in Linux. If it doesn't freeze, then it is either your Windows install or your system drive. You can try to open task manager and keep it up in Windows and monitor the Disk usage while using your computer, if it spikes to 100% while it is freezing then your system drive could be dying (seen this happen to a friend before).
  6. You could continue testing out the trial version for a while to see if you like it. I can say that Final Cut Pro X was extremely easy for me to start using compared to Sony Vegas, Adobe Premiere, DaVinci Resolve etc... Like I literally spent hours trying to edit some simple videos in the other programs and got very frustrated, then when I tried out Final Cut Pro X, it took maybe 15 mins for me to get the hang of everything and it just worked much better and made more sense, but that is just my opinion. You might also be surprised at the editing experience on that old MacBook you have, it might not be as bad as you think as Final Cut Pro X and macOS work very well together and are heavily optimized. You could also run macOS on your PC if you wanted to (Hackintosh) but keep in mind that it can be difficult and frustrating to do that and AFAIK it is illegal to run macOS on non-Apple hardware. If you decide that you like Final Cut Pro X, and you want to purchase a new MacBook Pro, I would wait until the new 16" models come out, unless you need one right now.
  7. If you are worried about performance losses, do 3 Cinebench runs or something, then turn it on and run 3 tests again, then compare the results to check if there are any major performance losses. If not - then I would leave it on.
  8. No need to run tests for me lol, just curious. You could be right about that ASUS Enhancement thing, because on both my tests the CPUs were OC'ed and locked to a specific frequency and voltage.
  9. Interesting... Source? I am interested. I have tested on an i7 6700K and a Ryzen 5 2600 and the performance in Cinebench was almost identical with virtualization on/off.
  10. It is needed to run virtual machines or Windows Sandbox which can be extremely useful. Even if you don't use those, you should turn it on anyway because AFAIK there are certain security features in Windows 10 (such as Core Isolation / Virtualization-Based Security / Memory Integrity) that require virtualization to be enabled. Also there is no harm or performance loss in enabling it. I am not sure why it is disabled by default on a lot of motherboards.
  11. Make sure that you are using the latest UEFI BIOS. Check your support page of your motherboard. You might also try downloading the latest version of Windows and doing a clean install using a USB drive from Microsoft's official page: https://www.microsoft.com/en-us/software-download/windows10ISO Also try unplugging all but the most basic peripherals such as mouse and keyboard.
  12. I remember that the Registry hacks did not work. There was another way that you had to do it which involved editing a file called something like "res32.dll" and then injecting the audio file that way, then it would work and play Logon, Logoff, Startup and Shutdown sounds. I used that method myself and it worked fine except for whenever there was a big Windows update and it overwrote the modified DLL with a newer version. You could also use another more easy (but probably slower with a bit of a delay) method by making use of the Task Scheduler to play an audio file at logon: https://www.tenforums.com/tutorials/94884-play-sound-logon-sign-windows-10-a.html AND also (slightly different with VBS script): https://winaero.com/blog/play-logon-sound-windows-10/
  13. It looks like GRUB may have been installed on your internal drive instead of the USB drive. If you installed GRUB on the USB drive, then you could have set your UEFI/BIOS to boot from USB first, then Internal Drive. Then when the drive is plugged in, it will boot from it (Linux), when unplugged, it will boot from the internal drive (Windows).
  14. Hi Everyone! I have a Windows Server AD Domain with DNS running at my main site (main.example.com). I have another site with a public IP address that dynamically changes (secondary.example.com). I want a DNS entry in place on the main site for secondary.example.com, but I often have to manually update the record to include the correct IP whenever the second site gets a new IP. Is there a solution to this? I thought of somehow allowing the router on the second site to connect the the main site's DNS server and update it's record automatically whenever it's IP changes (basically Dynamic DNS) but I don't know whether you can do this with Windows Server's DNS server. Any help will be appreciated.
  15. As the others have said, double check if the cooler is mounted correctly against the CPU (enough pressure) and check if the pump is plugged in and running. Remember that if you remove the block from the CPU, you must clean the CPU and reapply fresh thermal paste every time, even if it is a remount. But first try it and see if that was the problem, then reapply the paste.