hasn't anyone has a problem like this before? any idea what exactly 'ntdll.dll' is?