Windows 10 : Blank (white screen) after maximising

Yes, I’m hoping for a fix for this too. Roon doesn’t play nicely with certain (widely used) graphic chipsets. I’ve never had this problem with other software.

I am running Roon 1.2 Build 165 64 bit on a Win 10 Pro computer with an Intel i-5-3450 CPU @ 2.8GHz and 8.0 GB RAM. My music is stored on a WDMYCLOUDDL2100 NAS device and I play the music through either a PS Audio Directstream DAC, back to the computer, or on a couple of networked HiFiBerrys in the sunroom or the garage. My collection is over 1200 Albums, 700 artists and close to 18,000 tracks.

The specific issue or crash is that when I minimize Roon to the taskbar and then try and call it back, Roon displays a Blank white screen that still has some function, i.e. I can stop the music if I click in the right spot, the program continues to play music but can see nothing. I need to close out the program, which stops the music and restart to enable video functionality…a pain. So long as I don’t minimize the program to the taskbar I am ok The issue started prior to the recent update. I have been a member since October, 2016. So far Roon is the only program that behaves this way. Any help or suggestions would be appreciated. Thanks.

Hi William_Koch,

I’ve merged your post into this topic, most likely this is a graphic driver issue. Can you check to see if your PC has the latest drivers loaded.

Have a read of this topic for more information …

Mike, I have same problem, also intel 4000 graphics card. never seen this with any other application. have updated driver to nov 16 driver, problem persists.

There are 3 different sources for this driver. The PC / Laptop manufacturer website, Intel website or Microsoft Update.

Sometimes the most current driver does not necessarily means this would fix a particular issue, therefore using a older driver is a better way to go.

With regard to the Intel website there are 7 different versions of the driver.

Sometimes the manufacturer of the PC / Laptop also would have multiple versions of a driver.

When I installed Windows 10 on my machine I let Windows select it’s own default driver and then updated it from the Windows update.


Hi @Mark_Sherman ----- Thank you for the feedback. Sorry for the troubles here, have you read through Mike’s post mentioned above?

Unfortunately, this issue that you are experiencing is symptom of a bad driver update. There is very little we can do in this scenario as the driver is not refreshing the screen properly.


Sorry, but all of my other applications run perfectly, perhaps your choice of opengl is at the root of the problem. My other client on my Nexus 6p also has issues, so you are 0/2 with me despite now having over 100$ of my money. Seems that you are a well financed spin off of Meridian/Sonos, out to conquer the universe. To do so you should have client performance that is up to the measure of your parent company’s brand and not going 0/2 with your new customers. Sorry that’s a Windows driver issue is just not acceptable. You need to be providing stable clients that operate across all platforms to succeed. Why not just give us a html interface that will work on any machine?

I agree that this Intel driver situation stinks, and there are other technology decisions we could have made that might have let a 4.5 year old graphics chip work a bit better. But it is noteworthy that this is the second disastrous chip by Intel, the first was the Sandy Bridge HD 3000.

[quote=“Mark_Sherman, post:4, topic:16711”]
Sorry, but all of my other applications run perfectly[/quote]

This Intel driver is notoriously bad on WIndows. Here is an example of it failing on EXCEL. Yes, Microsoft Excel is screwing up on the Intel Driver:

Roon pushes quite a bit of textures to the GPU – this pushes the Intel Driver pretty hard and causing it to mess up. We’ve seen this over and over with certain drivers, and not with others.

Unsure what other apps you are running, but Photoshop and Lightroom are also known to screw up on Windows with the Intel HD 3000 and 4000, both which push the GPU.

Most our team are actually Android fans, and the most popular phone we use is the Nexus 6p. Besides a problem with a unreleased developer preview build of Android 7.1.1, there have been no problems there. Also, even though we have worked around some of the issues on 7.1.1, it looks like many other developers are having issues with 7.1.1’s changes in the area of screen sizing. I hope they fix this for the planned release (maybe this week?), but it doesn’t look hopeful.

It sucks that you ran into 2 issues, one with old hardware and one with too new of software.

We are a self-boostrapped startup formed by a team that split out of Meridian, with no ownership, share, or influence by Meridian. Before Meridian, our exact team that created Sooloos, that Meridian acquired back in Dec 2008.

I think you meant to write Sooloos, and not Sonos, as we have nothing to do with Sonos. However, we ARE the Sooloos team. I personally invented the name Sooloos back in the late 1990s and it was my personal project that Enno took to market. The rest of the Roon team (minus a few new hires) that you see here worked on the Sooloos project post launch, and built Sooloos 2.x while at Meridian.

Sooloos was Direct3D based, meaning it only ran on Windows (the Control ran XP Embedded), which worked fine on that hardware, but it also used quite a few UI tricks that are no longer acceptable in 2016 (no smooth scrolling anywhere).

As for OpenGL – it’s the only performant option available across Android/iOS/MacOS/Windows.

HTML would fall over, especially on a machine with 4+ year old gear. We know this, because we did this experiment. The browser just doesn’t scale on memory consumption or performance when it comes to long lived applications that are graphically heavy. It’s getting better daily, but not for an app like Roon.

Most of Roon was developed on the Intel HD 4000 on a MacBookPro Retina (early 2013), as it was the machine of choice for 2 major developers. MacOS’s graphics drivers are known to be slower and more limited that the Windows equivalents, but they also doesn’t fail like the Windows drivers by Intel on these older chips. However, this chip CAN work. The Mac driver clearly demonstrates that. Note that the exact same OpenGL code runs on Windows and Mac, so it’s a great A/B test where the driver is the only relevant difference.

Agreed, but there is only so much we can do here… the real question is do we spend time finding workarounds for half-decade-old GPUs and their buggy drivers or work on future features? Please don’t be upset with us, it is Intel that has forsaken you. We have tens of thousands of members, and only a few handfuls of people have run into this chipset’s issues. It’s unfortunate, but we have to look forward, not backward, especially when some of those people did driver changes and got things working.

As for your Android 7.1.1 issue on the Nexus 6p, we addressed it pretty quickly, because we could – just awaiting release right now. This Intel issue has been plaguing us for years. It’s one of the reasons we offer a trial. This issue usually comes up pretty quickly if the machine with this configuration is your primary Roon machine.

We said Ivy Bridge+ in our hardware requirements back when we launched in early 2015. Although we do run on the earlier Sandy Bridge, it is unbearable due to these types of issues (there is another CPU pipeline / RAM bottlenecking issue with Sandy Bridge). Ivy Bridge is starting to feel that way now. @mike, maybe time to update that to Broadwell?

Danny, thank you for your detailed response. It is very appreciated and shows your passion for a great product. Yes, I meant Sooloos, not Sonos. If I didn’t appreciate the innovation of your platform…I wouldn’t have shared my frustration.

I’m a bit surprised that you characterized my graphics card as 4.5 years old, but I’ll take your word for it. It runs on my Thinkpad X1 which may in fact be more than 3 years old but still rocks and refuses to slow down…just not realistic for me to upgrade over this issue. I guess I have to make a choice whether to work around the white screen/openGL redraw issue. Hoping that the final build of Android 7.1.1, due any minute will resolve the sizing issue on my 6p and if not your next release.

I am enthusiastic about your system and considering a new tablet to sit in my media room specifically to run Roon. Any recco?

You said you updated the driver, how exactly? We’ve seen people get around these issues with a little trial and error, so I’m wondering if there’s a method you haven’t tried yet (ie, going via the Intel site vs going via the Lenovo site, manual driver update vs automatic, etc).

Most of our team runs Android phones, but I think it’s safe to say that general consensus is that iPads make the best tablet remotes. If you don’t need audio from the tablet in your media room, that would be my recommendation.

Mike, I keep my system up to date, so the problem presented itself against the latest drivers from Lenovo. Then after reading your forums I went to the Intel site and downloaded and installed their latest driver…issue persists. While there may be some older driver that is compatible, trial and error of the last 10 drivers is not what I’m up to. There seems to be limited configurability, switching antialiasing, etc. I’ve tried all that to no avail.

just maximize or if already maximized click the “restore down” gadget, this will force a redraw…

Restore down gadget??

I agree I did not know what the gadget was called until I hovered over it!. if you hover over the maximize gadget it says “maximize”. if you hover over it again after maximizing, it says “restore down”…so just resize the window and it will redraw

Thats not woking for me.
i can minimize / maximize / restore forever - once it’s gone white - it stays white


br Ronni

not minimize, that doesn’t force a redraw… you need to resize

Lee, thanx for pitching in here. The problem is that once the window is minimized, it will never again redraw. The application is quite usable so long as the user doesn’t Minimize, restore down works just fine.

OK , I have read these posts and I do have the same nasty driver problem. I have the most up to date driver and going backwards has not gotten me any improvement. I could build a new computer but this is the only program that I use with this issue.
So, I have been thinking about replacing my WD server with a QNAP or, more likely a SONICTRANSPORTER I5 that is USB connected to my music hard drives. If I do this I would move the Roon Core to the Sonictransporter or QNAP ?
If I do this does that solve my redraw problem with my windows machine?

Unfortunately, it will have no effect. You would be moving RoonServer to another machine, but to access the Core Server you would still need to run Roon on the Windows machine. What would solve your problem would be to install a video card if you have the space in your computer. Describe your computer, make, model, motherboard and I could suggest one.

Hi William,

This problem is down the graphics card / graphics driver combination rendering Roon’s GUI, so it does not really matter where the Roon Core is running (it is headless, no direct user interface) … it’s where the GUI is running. So if you still wish to run Roon (as a remote) on this PC you would still run into the same issue.