none
Multiple crashes from bcryp.dll RRS feed

  • Question

  • At the first config (RAM based registry, ddi_null, minimal GDI and GWES) I got following crash from brypt
     
    FSDMGR!FSDMGR_FindFirstFileW(MountedVolume_t * 0xc4411290, void * 0x00400002, const wchar_t * 0xc4413730, _WIN32_FIND_DATAW * 0xc450ec90, unsigned long 0x00000630)  line 402 + 36 bytes
    KERNEL!MDCallKernelHAPI + 60 bytes
    KERNEL!NKHandleCall(unsigned long 0x00000001, _DHCALL_STRUCT * 0x00000372)  line 2499 + 40 bytes
    K.COREDLL!DirectHandleCall(unsigned long 0x00000010)  line 94 + 20 bytes
    K.COREDLL!xxx_AFS_FindFirstFileW(void * 0x01110003, void * 0x00400002, const wchar_t * 0xc4413730, _WIN32_FIND_DATAW * 0xc450ec90, unsigned long 0x00000630)  line 182 + 60 bytes
    FSDMGR!InternalFindFirstFileW(const wchar_t * 0x00000630, void * 0xffffffff, _WIN32_FIND_DATAW * 0x01110003, unsigned long 0x00000000)  line 766 + 28 bytes
    FSDMGR!FSINT_FindFirstFileW(const wchar_t * 0xc450e9fc, _WIN32_FIND_DATAW * 0xc450ec90, unsigned long 0x00000630)  line 781 + 20 bytes
    K.COREDLL!FindFirstDevice(DeviceSearchType DeviceSearchByLegacyName, const void * 0xc4410a62, _DevmgrDeviceInformation_tag * 0xc450ec90)  line 291 + 32 bytes
    FSDMGR!TranslateLegacyDeviceName(const wchar_t * 0xc4410a62, wchar_t * 0xc4413110, unsigned int 0x00000104)  line 51 + 24 bytes
    FSDMGR!SafeGetCanonicalPathW(const wchar_t * 0x00000000, unsigned int * 0xc4410a60)  line 124 + 16 bytes
    FSDMGR!InternalCreateFileW(const wchar_t * 0xc450f704, void * 0x00000001, unsigned long 0x00000000, unsigned long 0xc450f5b0, _SECURITY_ATTRIBUTES * 0xc450f564, unsigned long 0xcc5e2e8c, unsigned long 0xcc5e4150, void * 0x6000011f)  line 816 + 12 bytes
    FSDMGR!FSINT_CreateFileW(const wchar_t * 0xcc5c2048, unsigned long 0x00000000, unsigned long 0x00000000, _SECURITY_ATTRIBUTES * 0x00000000, unsigned long 0x00000003, unsigned long 0x00000080, void * 0x00000000)  line 1044 + 52 bytes
    K.COREDLL!xxx_CreateFileW(const wchar_t * 0xcc5c2048, unsigned long 0x00000000, unsigned long 0x00000000, _SECURITY_ATTRIBUTES * 0x00000000, unsigned long 0x00000003, unsigned long 0x00000080, void * 0x00000000)  line 88 + 60 bytes
    BCRYPT!_IoOpenDevice()  line 3157 + 44 bytes
    BCRYPT!IoCallKernelDriver(unsigned long 0xc450f538, unsigned char * 0x00000000, unsigned long 0x00020000, unsigned char * 0x00000000, unsigned long * 0xc450f538)  line 3246 + 4 bytes
    BCRYPT!IoCallKernelDriverQueryLoop(unsigned long 0xc450f704, unsigned char * 0xc450f57c, unsigned long 0x00000000, unsigned char * * 0xc450f588, unsigned long * 0xc450f704, int * 0xc450f57c)  line 3427 + 24 bytes
    BCRYPT!BCryptResolveProviders(const wchar_t * 0x00000001, unsigned long 0x00000000, const wchar_t * 0xc450f704, const wchar_t * 0xc450f700, unsigned long 0x00000001, unsigned long 0x00000000, unsigned long * 0xc450f704, _CRYPT_PROVIDER_REFS * * 0xc450f700)  line 2561 + 32 bytes
    BCRYPT!BCryptOpenAlgorithmProvider(void * * 0xc4440710, const wchar_t * 0xefd32cfc, const wchar_t * 0x00004444, unsigned long 0xc450f964)  line 530 + 48 bytes
    FILESYS!BCryptOpenAlgorithmProvider(void * * 0xc4440724, const wchar_t * 0xefcea98c, const wchar_t * 0x00000000, unsigned long 0x00000000)  line 29 + 80 bytes
    FILESYS!CryptCNG::CryptCNG()  line 485 + 24 bytes
    FILESYS!CryptSelector::InitCapi()  line 797 + 40 bytes
    FILESYS!CryptSelector::Select(DPAPIAlgID, DPAPIAlgID)  line 769
    FILESYS!CryptSelector::Select(DPAPIAlgID)  line 752 + 16 bytes
    FILESYS!CryptSelector::Select()  line 742 + 16 bytes
    FILESYS!dpapi_init()  line 1430
    FILESYS!DoGeneralInit(unsigned short *)  line 2147
    FILESYS!FileSysMain(HINSTANCE__ *)  line 2612 + 8 bytes
    K.COREDLL!ThreadBaseFunc(unsigned long (void *)*, void *)  line 1239 + 12 bytes
    I changed RAMinto Hive-based registry (as proposed here http://social.msdn.microsoft.com/Forums/en-AU/winembplatdev/thread/726c1c58-5679-4c2e-ab1c-a3aa47b5cecf)
    And got few different crashes but usual from
     
    BCRYPT!AesCtrRng_Instantiate(_AesCtrRng_State * 0x00000000, unsigned char * 0x00000000, unsigned long 0x0000000c, unsigned char * 0x00000000, unsigned long 0x00000000)  line 217 + 12 bytes
    BCRYPT!MSCryptGenerateRngState(_MSCRYPT_GENERIC_RNG * 0x00000000, _PERTHREAD_RNG_STATE * * 0xc4415880)  line 512
    BCRYPT!MSCryptAcquireRngState(_MSCRYPT_GENERIC_RNG * 0xc450f728, _PERTHREAD_RNG_STATE * * 0x00000000)  line 727 + 12 bytes
    BCRYPT!MSCryptGenRandom(void * 0xcc6ac01c, unsigned char * 0x00005555, unsigned long 0x00006666, unsigned long 0x00007777)  line 1458 + 12 bytes
    BCRYPT!BCryptGenRandom(void * 0xc450f760, unsigned char * 0xefef0e60, unsigned long 0xefd2a5d4, unsigned long 0xc450f770)  line 4244
    FILESYS!BCryptGenRandom(void * 0xc44157d0, unsigned char * 0xc4442200, unsigned long 0x00000020, unsigned long 0x00000000)  line 39 + 80 bytes
    FILESYS!CryptCNG::GenRandom(unsigned char * 0xc4442200, unsigned long 0x00000020)  line 542 + 28 bytes
    FILESYS!impl_Security_SetUserData(const wchar_t * 0xc44310d0, const unsigned char * 0x00000000, unsigned long 0x00000000, ICryptFunctions * 0xc4440a10)  line 987 + 44 bytes
    FILESYS!Security_SetUserData(const wchar_t * 0xc44310d0, const unsigned char * 0x00000000, unsigned long 0x00000000)  line 1051 + 20 bytes
    FILESYS!FSINT_SetCurrentUser(const wchar_t * 0x00000001, unsigned char * 0xc450f880, unsigned long 0x00000000, int 0x00000000)  line 168 + 16 bytes
    K.COREDLL!xxx_SetCurrentUser(const wchar_t * 0xc450fb9c, unsigned char * 0x00000000, unsigned long 0x00000000, int 0x00000001)  line 279 + 36 bytes
    FILESYS!FileSysMain(HINSTANCE__ * 0x00000000)  line 2652
    K.COREDLL!ThreadBaseFunc(unsigned long (void *)* 0xefd070f0, void * 0xc0403530)  line 1239 + 12 bytes 00000004()
    Has anyone experienced such problem?
    Monday, September 12, 2011 12:32 PM

All replies

  • I am at a loss.   What do you consider to be a "crash" and do you see something in this output that suggests a "crash" has occured?
    Bruce Eitman (eMVP)
    Senior Engineer
    Bruce.Eitman AT Eurotech DOT com
    My BLOG http://geekswithblogs.net/bruceeitman

    Eurotech Inc.
    www.Eurotech.com
    Monday, September 12, 2011 1:34 PM
    Moderator
  • Hi,

    This both call stacks are state when crash happens. The first one  is an illegal instruction crash, but ther is fix proposition which works

    http://social.msdn.microsoft.com/Forums/en-AU/winembplatdev/thread/726c1c58-5679-4c2e-ab1c-a3aa47b5cecf 

    One which I am experiencing now is data misalignment exception occuring in the AesCtrRng_Instantiate call.

    In both cases exceptions causes platform reset and makes kitl connection to be broken.

    BR,

    rysiekg

    Tuesday, September 13, 2011 7:51 AM