thanks stufflord & espio, i might do that later though because now i'm actually worried about turning on my pc
apparently some people running driver version 355.60 are having this issue as well; i think i might have that version. i knew the driver i was on started with a 3 but that was pretty much it lmao. will check that out as well as the solution that people found to that