Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Windows 11 Insider build - Suddenly cannot start QtCreator
Forum Updated to NodeBB v4.3 + New Features

Windows 11 Insider build - Suddenly cannot start QtCreator

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
14 Posts 4 Posters 904 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • ldraconusL Offline
    ldraconusL Offline
    ldraconus
    wrote on last edited by
    #4

    Ok, it looks like it doesn't even fully start before something happens. I get absolutely no change no matter what I put on the command line.

    1 Reply Last reply
    0
    • JonBJ Offline
      JonBJ Offline
      JonB
      wrote on last edited by JonB
      #5

      Not getting any output at all sounds odd. In your Command Prompt enter set QT_DEBUG_PLUGINS=1 as a command and then try running a Qt program or Creator from there, still no output?

      My understanding (could be incorrect) is that Creator comes with its own self-contained Qt libraries, so whether it runs or not ought be independent of whether a Qt program you have built runs or not, I didn't think they shared an environment. Which might indicate a system problem?

      Worth checking Windows Event Viewer for anything?

      1 Reply Last reply
      1
      • ldraconusL Offline
        ldraconusL Offline
        ldraconus
        wrote on last edited by
        #6

        Ok, this is interesting, but how to fix it:

        Faulting application name: qtcreator.exe, version: 15.0.84.0, time stamp: 0x67bdb829
        Faulting module name: d3d9.dll, version: 10.0.27802.1000, time stamp: 0x3e395b13
        Exception code: 0xc0000005
        Fault offset: 0x0000000000016121
        Faulting process id: 0x48D4
        Faulting application start time: 0x1DB8D13FD9638C3
        Faulting application path: D:\ProgramFiles\Qt\Tools\Qt Creator 16.0.0-rc1\bin\qtcreator.exe
        Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
        Report Id: fbd2b50a-88b6-443f-a637-2219ab5ab361
        Faulting package full name: 
        Faulting package-relative application ID: 
        
        jsulmJ 1 Reply Last reply
        0
        • hskoglundH Offline
          hskoglundH Offline
          hskoglund
          wrote on last edited by
          #7

          Crash in d3d9.dll huh? Just guessing but it reminds me of an old bug with MSI Afterburner och Riva Tuner, to get around it you had to change the setting from low to off.

          1 Reply Last reply
          0
          • ldraconusL Offline
            ldraconusL Offline
            ldraconus
            wrote on last edited by
            #8

            I saw those reports when I looked up that particular crash, and the only app that was running was some killer stuff (bad ACER bloatware) for the network, and I re-nuked those processes and set them to not start (again, really improves the network bandwidth).

            As a side note, the nvidia settings app is also crashing now when I select the performance tab ... hmm. Going to try and reboot and see what happens. Maybe the things that got messed with will be miraculously reset (or fixed from the fiddling... me thinks a reboot is required).

            1 Reply Last reply
            0
            • ldraconusL Offline
              ldraconusL Offline
              ldraconus
              wrote on last edited by
              #9

              Whelp. When I told windows to run qtcreator with the motherboard graphics only, it works. This might be a slight pain to do for each Qt application, but it did work.

              1 Reply Last reply
              0
              • ldraconusL ldraconus

                Ok, this is interesting, but how to fix it:

                Faulting application name: qtcreator.exe, version: 15.0.84.0, time stamp: 0x67bdb829
                Faulting module name: d3d9.dll, version: 10.0.27802.1000, time stamp: 0x3e395b13
                Exception code: 0xc0000005
                Fault offset: 0x0000000000016121
                Faulting process id: 0x48D4
                Faulting application start time: 0x1DB8D13FD9638C3
                Faulting application path: D:\ProgramFiles\Qt\Tools\Qt Creator 16.0.0-rc1\bin\qtcreator.exe
                Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
                Report Id: fbd2b50a-88b6-443f-a637-2219ab5ab361
                Faulting package full name: 
                Faulting package-relative application ID: 
                
                jsulmJ Offline
                jsulmJ Offline
                jsulm
                Lifetime Qt Champion
                wrote on last edited by
                #10

                @ldraconus said in Windows 11 Insider build - Suddenly cannot start QtCreator:

                Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll

                There seems to be an issue with the graphics driver.
                Did you try to install latest graphics driver?

                https://forum.qt.io/topic/113070/qt-code-of-conduct

                1 Reply Last reply
                0
                • ldraconusL Offline
                  ldraconusL Offline
                  ldraconus
                  wrote on last edited by
                  #11

                  Good call. Frustrated, so I didn't even think of it... Time to visit Nvidia...

                  1 Reply Last reply
                  0
                  • ldraconusL Offline
                    ldraconusL Offline
                    ldraconus
                    wrote on last edited by
                    #12

                    ... and that wasn't it. Installed the latest drivers, still no beans...

                    JonBJ 1 Reply Last reply
                    0
                    • ldraconusL ldraconus

                      ... and that wasn't it. Installed the latest drivers, still no beans...

                      JonBJ Offline
                      JonBJ Offline
                      JonB
                      wrote on last edited by
                      #13

                      @ldraconus
                      You said "Insider build", right? Isn't https://forum.paradoxplaza.com/forum/threads/stellaris-doesnt-start-anymore.1730338/ from one day ago reporting the same? An Insider build issue??

                      ldraconusL 1 Reply Last reply
                      1
                      • JonBJ JonB

                        @ldraconus
                        You said "Insider build", right? Isn't https://forum.paradoxplaza.com/forum/threads/stellaris-doesnt-start-anymore.1730338/ from one day ago reporting the same? An Insider build issue??

                        ldraconusL Offline
                        ldraconusL Offline
                        ldraconus
                        wrote on last edited by
                        #14

                        @JonB Yup, that's the issue. By re-installing an manually telling it which driver to user, it works ... for every application that fails to run.

                        1 Reply Last reply
                        0

                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Users
                        • Groups
                        • Search
                        • Get Qt Extensions
                        • Unsolved