IB> If to increase the size of the notification message, that is probability that the user will note UI. IB> the Problem is shown only on some computers. Can twist any adjustments Windows? I even did not begin to think of it. Well i.e. a problem with a multithreading, what adjustments in Windows can be twisted, that it remained to work like clock-work, but spat on synchronization? Application here should be twisted. I.e. purely hypothetically, we assume at you on the screen in which cells are updated in rial-time. And as something most likely changes arrive many times in a second. What the critical changes from the point of view of the ultimate user if you update not each time, and for example on the timer of times in 500 milliseconds or second? most likely ceases. Or the most frequent scenario when at loading of the data it is updated on change of each data field. I.e. You think, what you change one cell, and except it that else is updated much, whether is enumerated etc. it Is necessary actually, or if 100 records from basis are read easier to read them, and then UI to Update once? I.e. if at the beginning of data reading from basis to disconnect all notification messages and as stopped to read - to update all at once normally it treats the majority of problems with hang. And that by it it is not treated - it is necessary to search . Otherwise you do not solve a problem, and hide to a pore. Adjustments Windows here hardly help. Always there will be a user at which bad videocard and only software rendering, or on the contrary many very fast processors.