Sorry, I have to correct myself. The driver was not up to date. I was relying on MS Windows automatic detection feature, which was wrong. To make sure I went to Intel website and found the newest driver, downloaded and installed it - the problem's gone!