Intel Graphics Software keeps Showing "Waiting for Windows to complete device reconfiguration..."

[Frank772]

Periodically I get the following message from Intel Iris Xe Graphics running on A NUC12WSHi7-1260P.

"Waiting for Windows to complete device reconfiguration...".

I have Windows 11 Pro 24H2 installed. 

I have a two monitor setup with a Dell S2722QC  and Dell P2414H.  The first is a 4K monitor and the second only HD.  They seem to work fine together after tweaking the settings on each individually. 

Once I get the message I can no longer get any other response from the graphics software.

Any suggestions on want to do? 

Thanks, Frank

[RandyT_Intel]

Hi @Frank772 ,

I would like to inform you that as of January 16, 2024, technical and warranty support for Intel’s NUC 7 through NUC 13 systems has transitioned to ASUS. For any assistance, please contact ASUS directly at ASUS Support. 

Customer Support Services for Intel® NUC Products Has Transitioned to...

Additionally, all software, firmware, BIOS support, and security advisories for these systems will now be managed by ASUS. 

Thank you for your understanding and cooperation. 

Regards,

Randy T.

Intel Customer Support Technician

[Frank772]

Thanks for the useless reply.  Asus has nothing to do with Intel's GPU's and their software.  The fact that it is running on a NUC should not effect whether I can find out why the software is having problems running in Windows 11 and creating problems for me.  It also runs on many other types and brands of computers including ones built at home.  Do you tell these home builders to check with them selves to fix the problems?

I need help with Intel Iris graphics, not my NUC.

Thanks

Frank

[GARY24]

Frank your funny, If your still looking for a solution i found one!  **Manually Update Drivers**: - Check the current driver version in Device Manager by right-clicking the component, selecting "Properties," and viewing the "Driver" tab. -For me it was "Intel Iris Xe Graphics" i updated it but if that doesn't work try to unistalling it then restarting your PC it's like a reset. (It does come back after a restart just don't check the box saying "Attempt to remove the driver for this device")

[Frank772]

Hello Gary24,  I had abandoned this site for help since I was told to contact ASUS.  That was useless, so I did a bunch of checking here, there, everywhere and finally found a fix for now.  I can't find my detailed notes, but basically Intel had issued an update. It is where the problem started.  I removed the Intel driver and started to wait.  After awhile they then issued an update ending in .6881 that corrected the problem. I'm happy about that. I also found Windows 11 kept kept backing up the driver to the bad one, so I blocked that.   The other day Intel offered a new update .6913. I blindly installed it.  Bad decision, the problem came back. So  I backed the driver up to the one that works. Everything is working fine for now and I'm looking for a Minicomputer with non Intel Hardware.  The NUC is going to Goodwill. 

Thanks for the help.

Frank

[J-Fo]

Just popping in to say thanks Frank for sharing the very specific update version that you used; I searched for the error, found this thread, and immediately hit a solution that worked for me. 🖖

[Foxyz]

I have the same issue, and it's the third time this happens to me but now I can't seem to manage to make it work again.

I really don't want to start trying a bunch of older drivers to see what the latest working one is, it's really stupid that I can't simply find a log that explains where the error is or why the app itself doens't just say what it's actually "waiting" for.

I assume it's caused by a bug in the driver that's triggered by having some registry configuration or some file that activates something in the driver that causes it to lock up.

I had it do this last year and it somehow worked again automatically after a couple days. Now it's doing it again and it hasn't gone away for a week, until today it suddenly worked, but then my driver updated to .6913, same version as you, and it's broken again. "Waiting for Windows to complete device configuration...". Super annoying! 

Why is waiting even necessary? Graphics Command Center works just fine and never waits for anything.

This has nothing to do with NUC and everything to do with an error in communication between Intel Graphics Software and the Intel Graphics driver. Frank explained it was a thing with the Iris Xe Graphics driver, which clearly means it's an issue that happens with all CPUs that come with Iris Xe Graphics and that the NUC part is completely irrelevant. This is not a task for Asus to solve, they have nothing to do with this and their support will definitely have no clue how to solve it and is in no way supposed to know and is not supposed to provide support for this, they will do anything meaningful to help at all.

Can we please get some information about where to find logs or how to get an idea of or inspect what's happening, what is the app stuck waiting for? Does it wait for a registry key to change? Does it wait for something else to change or a response from the driver? This is a bug that appears to happen quite often and it really needs to be fixed. Please let me talk to someone who has a deep understanding of how the software works, someone at Intel has to know how it works right? How about contact someone who works on the app, just hit them up with a quick little email to get some info right? 

Intel wouldn't release these drivers if they caused this issue out of the box on every machine, it has to be a specific configuration or so that triggers it, I want the latest version of the generic first party driver (6913) to work with the latest version of Intel Graphics Software.

If I can't get any support I'll have to reverse engineer, figure out what's happening and fix it myself, but at that point I'm paying you to do your job for you.

Thank you very much, have a nice day!

[Frank772]

Thanks for the response.  At least I'm not alone.

[Foxyz]

Yeah,

In Process Monitor I see it just endlessly loop 3 operations on a file in LocalLow with some hash as filename:

I don't think it's related to the cause of the issue though.

Still trying to figure out what it's really doing. Any ideas on what to try?

[Frank772]

Thanks for the update. 

windows 11 just did me again on this.  I did a repair on Windows for another reason and when it had finished it gave me an Intel driver from 2022 for the Iris driver.

Aren't computers wonderful.

Frank

[_del]

I fixed this by just installing the old command center off the microsoft store 

[Foxyz]

Command Center works indeed. I really like Command Center, but it's more of a Windows 10 design. I wish Graphics Software worked properly.

I've been decompiling and reverse engineering IGC with Visual Studio. I'm glad IGC is .NET, it makes this much easier. It doesn't even create the Display page. It gets stuck loading before that.

There are logs in 'Intel Graphics Software' (%SystemRoot%\System32\Winevt\Logs\Intel Graphics Software.evtx)

I had placed breakpoints at the spots it left the last logs by searching for those function names in the code in ILSpy but they didn't get hit for some reason. 
For me the last message left is '{"category":"Igcl","level":"Debug","message":"GetPowerDpstPerPowerSource","parameters":{"handle":"277006E5658","bklt":true,"opst":false}}' and then it stops doing anything probably async waiting for a response from the driver or something that never returns anything. I have yet to make Visual Studio break on the right spot I'm gonna just put a breakpoint on the Logger class implementation and look at the call stack or so as I'm probably putting my breakpoints in the wrong spot.

Would be handy for debugging if it also logged which function it's awaiting in if it takes longer than a minute to load or so. That way I'd know where it's happening and be able to step through it with debugger to see what's really happening.

I would really like some cooperation from the developers working on IGC at Intel they must know much more about what happens where and how to fix it.

If I figure out a solution or find out where it happens I'll post here and maybe the devs at Intel can solve it next driver update. If it were open source I'd try to fix it for them and do a pull request.

[Foxyz]

Yes Windows Update gives older 'targeted' drivers that are drivers your manufacturer hand picked and tested for stability on your device. It's older but more bug free and less large. The latest graphics driver from DSA or Intel's website is a 'generic' driver, just made to work for all supported devices and has more/newer features but probably less stable (as we see here with it simply not working).

Computers are wonderful and amazing and really fun, if they work.

If they don't work, I will eventually make them work.

[Frank772]

Thanks for the explanation.  I noticed my problem with the graphics started when I upgraded my two monitor setup to 4K monitors.  The later versions of the drivers have a lot of color, etc. control which did not exist in that old driver.  What a shock to me when the system came up after the repair.  

Thanks, Frank

[LT7879]

I have similar issue in the past, the only solution for me is to uninstall and reinstall the driver using clean install option