Fix sign test against an unsigned integer

It turns out that DWORD64 (as well as DWORD) is actually UNSIGNED!

This fixes what should have been fixed by commit 9941b412240c1c9e2f650168362023bdac10fcdb (Possible fix for overly long stack trace on Windows)