Jump to content

Daniel Davis

Member
  • Posts

    117
  • Joined

  • Last visited

Awards

This user doesn't have any awards

1 Follower

Recent Profile Visitors

912 profile views
  1. I sorta cheated my way out of the problem, by just returning it and getting a new one, that its functioning 100% normal so far.
  2. Im just concerned about wasting my money in all honesty... if buying a new one after returning it can fix it I will do It, Im just not sure if it will label the SSD the same as my current one?
  3. Sadly I know very little/have very little experince when it comes to doing software troubleshooting... Would you be able to help me with that, if not does returning the SSD and getting a new one even though its the same model works as well?
  4. Doing what you said with an extra shut down step instead of just two we got the following results... [Note the "Not Initialized" and 2GB instead of 1.98, sadly still not TB]
  5. If windows storage space = hard drive: c/ then no We are talking about this one specific drive that I wanted to set up, where I mistakenly set the volume significantly lower than what it really is.
  6. For some reason its just a PrimaryPartition with the same ammount of storage, with still no option to increase to 1.80 TB
  7. Basically, when I was setting up my SSD I was being a goof, wasnt paying attention and made a partition that is only 2GB instead of two TB.
  8. So today I was talking to a friend about frame rate, and how I overclocked my monitor to edge out a couple of more frames since I am planning to get a new monitor soon and am not to concerned about the warranty. As I do this I go to Overwatch and raise the FPS limit above the display setting out of curiosity from 74FPS to 140FPS and suddenly the game feels ALOT more smoother. Where my question lies is... Why does the in game frame rate (140FPS) affect the way I perceive the game on monitor (74 FPS) as more smoothly though it is above the cap?
  9. I went to install the driver not from the motherboard company but the actually company that manages the ethernet portion of my motherboard and I got it to work again... so basically the mobo company fucked up... [Tip to future humans type in the ethernet adapter name for the drivers not the mobo company... I feel stupid]
×