2013-08-08, 04:20
Hey Guys,
To give a bit of history/context my set up
Intel NUC i3
Windows 7 Ultimate
XMBC Frodo 12.1
I had my NUC wired to an access point and streamed my movies from a NAS box. I connect to a Samsung home theatre through HDMI with pass through audio.I was having some issues when playing 1080p and 720 vids where it buffer. I then changed and put in a wireless card and connected to my modem direct which solved that. In the process of looking for drivers on the intel site I thought it a good idea to up date the graphics drivers as well.
Now when I open XBMC on the screen there are dots and lines all over the place. For example along the menu bar in the home page there is a line all the way through it. It can be a think black line or a has been a coloured one as well. It still plays video fine (with no buffering yeah!) but i miss my clean looking skin before.
I assume its to do with the latest graphics drivers i just downloaded however I wanted to check if anyone else has come across this issue before I tried to roll back the driver.
cheers
To give a bit of history/context my set up
Intel NUC i3
Windows 7 Ultimate
XMBC Frodo 12.1
I had my NUC wired to an access point and streamed my movies from a NAS box. I connect to a Samsung home theatre through HDMI with pass through audio.I was having some issues when playing 1080p and 720 vids where it buffer. I then changed and put in a wireless card and connected to my modem direct which solved that. In the process of looking for drivers on the intel site I thought it a good idea to up date the graphics drivers as well.
Now when I open XBMC on the screen there are dots and lines all over the place. For example along the menu bar in the home page there is a line all the way through it. It can be a think black line or a has been a coloured one as well. It still plays video fine (with no buffering yeah!) but i miss my clean looking skin before.
I assume its to do with the latest graphics drivers i just downloaded however I wanted to check if anyone else has come across this issue before I tried to roll back the driver.
cheers