Qt installer fails on Windows 7, exception Code: c0000005



  • The Qt installer (version 3.0.0) crashes while apparently trying to access a null pointer on Windows 7 x64.

    0_1501604944317_1.jpg
    0_1501604969322_2.jpg
    0_1501604975379_3.jpg

    Problem signature:
    Problem Event Name: BEX
    Application Name: qt-unified-windows-x86-3.0.0-online.exe
    Application Version: 0.0.0.0
    Application Timestamp: 59240861
    Fault Module Name: StackHash_0a9e
    Fault Module Version: 0.0.0.0
    Fault Module Timestamp: 00000000
    Exception Offset: 00000000
    Exception Code: c0000005
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 3082
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

    Does anybody experience this problem?


  • Lifetime Qt Champion

    Hi,

    Did you check that you have enough space on your hard drive ?



  • @SGaist said in Qt installer fails on Windows 7, exception Code: c0000005:

    Hi,

    Did you check that you have enough space on your hard drive ?

    Yeap, I have enough space. I also tried the offline installer but I get the same error.



  • Hi, looks like DEP fault (Stackhash_0a9e), try disable it in a CMD window (started as a Administrator):

    bcdedit.exe /set {current} nx AlwaysOff
    

    More here



  • @hskoglund said in Qt installer fails on Windows 7, exception Code: c0000005:

    Hi, looks like DEP fault (Stackhash_0a9e), try disable it in a CMD window (started as a Administrator):

    bcdedit.exe /set {current} nx AlwaysOff
    

    More here

    I tried that but it didn't work. I don't think that's the problem anyway, the installer is clearly trying to reference a null pointer.

    0_1501630872533_4.jpg



  • Hi, the code is legit, however in the .exe file those bytes can be found pretty close to the start of the file (around offset 0xaaaa0). Also on my Win7 that code at 0x0118B1AF isn't the same as yours (when I break the installer at 0%).
    Hmmm could it be an anti-virus program like Avast that's reshuffling your Qt installer?



  • Ok, after some research I found the problem. The installer was failing to load the module kernel32. To load the module it first calls the Windows function LoadLibrary passing the filename “kernel32.dll.dll” for some reason. When this fails it tries again with “kernel32.dll”, except that it only does so when the function GetLastError returns ERROR_MOD_NOT_FOUND (0x7E). If the first call to LoadLibrary fails for some other reason the installer doesn’t retry. In my case GetLastError was returning ERROR_NOT_READY (0x15). This occurred because my PATH contained a reference to a folder on the D drive that used to be a disk partition but now is a DVD drive that was empty at the time:

    0_1501646081888_5.jpg

    After removing that folder from my PATH the installation completes successfully.

    This is probably a bug. The installer shouldn't use the value returned by GetLastError to determine if LoadLibrary failed.



  • Good catch! I can easily reproduce the bug on my Windows 7, by adding a non-valid directory into the path list and then trying to install Qt. And I also get that same "StackHash..." error.

    You can report the bug here


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.