I'm experiencing a problem when stepping over some API calls, the following messagebox is shown:

No response from injected code

In order to perform action that is not supported by OS, OllyDbg has injected short piece of code into the debugged application, but received no response within 5 seconds. Do you want to wait for another 5 seconds? (If you answer No, the consistency and stability of program is not guaranteed and you should restart it as soon as possible).

Did anyone else have this problem? What could be the cause of it?

Thanks in advance

Decode SSE registers
If option is on, OllyDbg displays 128-bit SSE registers of actual thread in Registers pane of CPU window and decodes value of registers in the Information pane. Notice that this operation is slow and requires injection of small programs into the debugged application. Do not use this option unless absolutely necessary!

Quit this mark and in debugging options

Allow code injection to get address of WinProc
On NT-based systems, enables code injection to get address of window procedure. Code injection is time-consuming and internally unsafe, especially for multithreading applications

Quit this too and try

Ricardo

there is a pretty long thread here by the name of code injections errors
you should be able to find it by searching the most active topics from the start if you require any further info on the phenomemon
apart from disabling the above two things that ricardo mentions

edit here is the link

http://ollydbg.win32asmcommunity.net/?action=vthread&forum=1& topic=158
("http://ollydbg.win32asmcommunity.net/?action=vthread&forum=1&topic=158
")

as you can see if all the threads are sleeping suspended the QueueUserApc kinda fails it seems and doesnt send a reply to ollydbg back

Disadvantage of "oh me anon" posted thread is that is to long and (boring) for Joe Average and very easy to not see answer to your question.

Hint: Search for SSE/SSE2 on above thread

The problem was indeed the "decode SSE registers" options. To be honest I hadn't searched the board for the solution... so my apologies for being so lazy.

Thanks!