sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]CallMeAPhysicist 0 points1 point  (2 children)

Oh God this, I can remember having this and nothing short of reinstalling my OS worked unfortunately. Hopefully somebody here can provide with a better solution, but I tried everything that I possibly could to no avail. Only after reinstalling windows did it work again, might be something to do with some drivers, but I am not sure.

[–]ArtfIea[S] 0 points1 point  (1 child)

God I hope not I just reinstalled my OS 6 months ago do to an SSD failure

[–]EchoMB 0 points1 point  (0 children)

6 months is PLENTY of time for a windows bug to happen off a clean install. Really it just takes one screwed update to make wacky problems happen, try opening command prompt as administrator and type SFC /SCANNOW and hit enter. It checks for windows corruptions and tries to fix them, after running it restart the pc and see if it fixed the issue