Jump to content

TheTurk

Member
  • Posts

    5
  • Joined

  • Last visited

Awards

This user doesn't have any awards

TheTurk's Achievements

  1. At over $1300USD the price is pretty steep, but that's to be expected with new tech like this. Other than the price, this looks like the perfect solution to playing games or even watching films during a party with a decent viewing angle, high resolution image, and a very small requirement for space. If the price were more around $1000USD, I'd actually buy this.
  2. I'll have to sit on this for a couple of days, but I think I'll get a quote on checking the motherboard out before I go ahead and do it, I don't want to spend near double the price of the board to have it checked, come back as broken, then buy another when I can just buy a new one outright and replace it, you know what I mean? I'll update the thread once I do something, in case someone in the future needs the info, for some reason. Thanks again.
  3. That's what I'm afraid of, I just ran the Windows Memory Diagnostics Tool on both sticks of RAM separately and both tests came back with no errors, so, that's not good for my wallet if it is the motherboard. Any suggestions for testing the motherboard? Google doesn't return many suggestions, nor does the manual. Thanks for responding by the way.
  4. I built a new system about a month ago, I'll include the specs below. It worked fine up until last week while I was playing GTAV, it blue screened and I was given a Clock_Watchdog_Timeout error. I've poked around on forums around the internet and I've not gotten a proper explanation. Recently it's not been blue-screening at all, but rather shutting down randomly and then immediately starting back up except none of the hardware, except the motherboard, HDD/SSD, and fans function, I get a 00 code on the motherboard and am forced to force it to shut down and start it again. When I do, I still get the 00 code and nothing working. I've found the only way to fix it is to either swap the memory sticks or remove the second one entirely. It then boots up normally, no error messages, etc. I wore an ESD strap and made sure to take all precautions to avoid blowing parts when building it (I built it myself). I was on an FRC (robotics) team in high school and dealt with electronics daily, so I'm well read in on how to handle hardware, so ESD unlikely, but possible. I'm going to run the machine on one stick of memory for a while and then swap out to my second stick and see if either of them crash the machine, hopefully it's just a dead stick, but I'm probably wrong. Can anybody help me find what's causing this? System Specs: OS: Windows 10 CPU: Intel I7 6700k GPU: Gigabyte 980ti Windforce G1 Gaming Motherboard: MSI Z170A Gaming M5 RAM: 16GB Kingston HyperX Fury DDR4 2133MHz HDD (Storage Drive): Western Digital Black Drive- 2TB SSD (Primary Drive): Samsung 850 Evo CPU Cooler: Corsair H100i GTX PSU: Corsair RM1000x (it's overkill, but it was on sale at the time) Case: Corsair 780T Intake Fans: 2 Noctua NF-A14 140mm industrailPPC-2000 PWM 107.4 CFM (front mount) Exhaust Fans: 2 Noctua NF-F12 120mm PWM 55 CFM (mounted on CPU cooler/pull config), 1 Noctua NF-A14 120mm PWM 82.5 CFM (rear mount)
×