raster status bug in HD 5500 and HD 520 chipsets

[Forster__Jonathan]

I develop scientific testing software called DMDX that for all intents and purposes looks like a game to the OS.  It needs to track the raster so it hammers either pd3dDevice->GetRasterStatus() or in legacy cases lpDD2->GetVerticalBlankStatus() for milliseconds at a time till it either sees a retrace begin or decides it's missed it.  This has been working on other chipsets for donkey's years however on recent MS Surface Pros (Surface Pro 3 I suspect, will have to verify it if matters with the HD 520 chipset under win10) and HP EliteBooks (HP EliteBook 820 G2 with the HD 5500 chipset under win7) the machines will lock up unless I only poll this function periodically.  Eventually control will return to my process after a number of seconds but will probably loose focus again after a short while.  Interestingly my Dell Inspiron 15 5566 with an HD 620 chipset in it is just fine (win10).  More interestingly on the HP it happens with with legacy DirectDraw interfaces or the Direct3D interface so it's something common to both.  I can pull more details from the users however I have no access to any of the machines currently reporting the issues.  It first popped up several years ago with an early Surface Pro (probably running win7, don't think win10 was released back then) so this has been going on for a while.

If you need to reproduce the bug the DMDX software is available here: http://www.u.arizona.edu/~jforster/dmdx/DMDX.ZIP

You will need a script to run, various RTF testing scripts are available, all of them will produce the error: http://www.u.arizona.edu/~jforster/dmdx/testmodes/

Test mode descriptions if you're interested are here: http://www.u.arizona.edu/~jforster/dmdx/help/dmdxhtestmodes.htm