Jump to content

LainVonDark

Member
  • Posts

    70
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

LainVonDark's Achievements

  1. I'd suspect a dying motherboard over a dying PSU in this case, but the suggestions above are still valid.
  2. Hi My PC is logging into a black screen after the latest updates. I type in my password on the windows login, it takes an unusually long time, and then the screen just stays black forever. I can open the task manager, but not much else. Trying to force explorer to start won’t work thoughts? EDIT: So, turns out it is not fixed at all. Still booting into a black screen unless I start it in safe mode EDIT 2: The machine will consistently start if I disable the startup items in msconfig
  3. I got the cable from a store deemed reputable here in Portugal, and I've had no issues with this cable until now, and I've been using it for almost a year. It is, however, a DP to miniDP cable, as mentioned on the topic you posted, which worries me somewhat. Unfortunately, I have no other DP devices I can use to test if I fried something or not. And what I meant was that the display won't show up on the nVidia control panel, unless it's plugged into this last, and currently, only working, DP.
  4. Hi, I am having a really strange issue whose cause I am absolutely clueless about. I currently have a Cintiq display connected over DisplayPort to my GTX1070. A couple of days ago, I randomly got a "No Signal" on it, and even after unplugging it and plugging it back in, it still wouldn't come back online. I swapped to the second DP port, and it turned back on again, but the port it was originally connected to still won't detect it. Now, the second port is behaving the same way, and I am down to my last port, and neither of the other two show any sign of working. The tablet won't even get picked up on the nVidia control panel when plugged into one of the first two ports. Thoughts? Thanks
  5. Only if it physically restricts your bends
  6. My licenses are retail, not OEM. The issue here is something within windows itself, not with the keys I tried that, and it still failed upon activation. I have the creators update as well.
  7. Hi, So, my motherboard failed and I had to swap it out. Upon returning to windows, I get the dreaded "Activate windows" on the bottom right corner of my screen. Things I have tried so far: Using the troubleshooter's "I recently changed hardware on this device option" Removing my previous machine from my Microsoft account Removing and inserting my key via the command line Trying another, unused retail W10 Pro key, and it still won't activate. As of right now, this is what I see. , Thoughts?
  8. Yes, I am currently in manual voltage mode. I can't shut LLC off completely in this board, I am limited to a minimum of 25% for some reason.
  9. So the experiment didn't work. Regardless of anything, the CPU still overvolts. The only current "fix" is to simply set the target voltage to a lower value to compensate for that offset
  10. I just updated it, and tried with the secondary, un-updated bios again just as a sanity check. I will try clearing cmos and OCing again, I'll get back with some info soon. Thanks so far
  11. LLC doesn't seem to be influencing this, oddly. Whether it's 25 or 75%, the same effect persists.
  12. Hi I just changed motherboard, to an MSI X99A Carbon, and I am redoing the OC I had on my old board on my 6800K. For starters, I have set my Override voltage to 1,29v with a multiplier of 41x. At idle, the VID is 1,29v and the vcore is at its usual lower state, but as soon as I run prime, the voltage shoots past 1,29v and both VID and Vcore go up to 1,35v. What is determining this behavior, and how can I cap it to the override value in all circumstances? Thanks
×