dude, reading 7 pages was frustrating...
I am using Intel duo core e8400, Radeon 4890, and 4 GB DDR2 ram, running windows 7 32-bit... and i have encountered the bug few times, which technically kinda solved itself on later tries, meaning i go do some other stuff and then try that specific location again and it just goes fine
so, let me try to sum this up
It happens on AMD processores, it happens on Nvidia cards, happens with Intel CPUs, both old and new ones, happens with pretty good Radeon cards too, even a guy had the error after 30+ hours of playing in XBox(unlike what Larian QA thought the xbox guy didnt had it at starting Rhode dialouge)... Also happens on High end settings and low end settings, and different versions of windows and so I think its pretty safe to assume it has nothing to do with the machines or OS(atleast pretty sure abour machines part)
only lead so far is that there are no reports of this bug so far on german version.
Thinking about the wierd methods some people offered here to solve the problem like "hit num pad 8" or "hit some key in the middle of your keyboard" makes me wonder maybe the problem is pretty small and obvious in the game code, something that just "doesnt happen" when you do stuff different or some small thing change, so small that people doesnt notice it and they think they solved the problem by hitting 8 on their numpad... maybe that could explain devs not being able to find the problem... not looking in right place? not checking the obvious things?
other day my sister was shouting and making a mess in house looking for her glasses, when she entered my room and asked me have i seen her glasses, i looked at her and i saw she has them on her eyes