Break where the error HRESULT occurs using WinDbg

When debugging, I found an error HRESULT returned: 0x80020003, but I do not know which function is producing this error. Instead of going through the call stack, there is a simple way if you use WinDbg. I can start the application and when WinDbg breaks use the following command (on 64 bit machine):

t; z(@rax != 0x0000000080020003)

The application will break where the function returns the error HRESULT.