Resolume hanging on startup

[EBMCreative]

Integrated graphics don't get disabled when you insert another card.

In your first post you write you have Intel i7 10700
that has integrated graphics. (Intel® UHD Graphics 630)

I agree with you.

But many times people order a F or KF version of the processor not knowing that those dont have integrated graphics available but look at that it's cheaper. I had it happen with the machine I currently am using. The purchasing agent saw a cheaper version and bought that not understanding that there are reasons for certain specifications. Lol that was a costly mistake.

[RPWILLIAM]

Yes I've tried a couple of times to install updated integrated drivers however the system confirms there is nothing to install.

[RPWILLIAM]

Update: I've completed a fresh install of the system, wiped everything and started again.

Latest Graphics drivers have been installed and latest resolume release.

The issue still persists. Logs are the same as original issue.

[EBMCreative]

Yes I've tried a couple of times to install updated integrated drivers however the system confirms there is nothing to install.

Opera Snapshot_2024-12-11_071836_www.intel.com.png

The only way to know for sure is to go into your bios and see what it says as the processor and also there will be an option to turn on or off the Integrated graphics as well as choose the what is the first startup screen. I have a gigabyte motherboard and whenever I update the bios I have to go back to the settings and reselect the integrated graphics as the initial display. It's a PITA! Lol

[RPWILLIAM]

Update: I've gone through my BIOS line by line and there is no option to enable integrated graphics.

I've also ran Memtest86 and my RAM is fine, I thought it could be a RAM issue as there is no pattern to how far Resolume loads before it crashes.

I guess next step is to start removing hardware.

[RPWILLIAM]

Update:

Today I removed my RAM individually and booted. no change.
I physically removed both Nvidia cards and as suspected, the integrated graphics then became available to me. I was then able to complete an update on these drivers. I ran resolume at this point and it repeatedly opened fine without any problems.

I then reintroduced each Nvidia card individually and tested and the same issues occurred.

I am now running as many tests as I can with DDU removal with different variations of driver versions and resolume versions to no avail (thus far!)

At this point I have run out of ideas which is extremely concerning to me as I have several resolume setups I use and this sudden catastrophic failure to work on one machine without any current resolution makes me wonder when is this going to happen to my other machines..

[EBMCreative]

Update: I've gone through my BIOS line by line and there is no option to enable integrated graphics.

I've also ran Memtest86 and my RAM is fine, I thought it could be a RAM issue as there is no pattern to how far Resolume loads before it crashes.

I guess next step is to start removing hardware.

So you have gone to advanced, system agent, graphics configuration and have not seen any options to select integrated graphics or chose which is the first boot or multi monitor support?

[RPWILLIAM]

Yes but regardless as noted above the integrated graphics have since been activated and upgraded.

I’m now looking at next possible solutions.

[RPWILLIAM]

Update:

Completed fresh installs on windows on both hard drives respectively to see if there was any issue on either one.

I then updated the BIOS and new options became available and was able to enable options in SA configuration.

I also tried both my graphics cards in a different machine entirely to ensure they were both working properly and resolume ran fine on the other machine.

Resolume will still not run, original issue persists.

[RPWILLIAM]

Update,

As a test I've just installed Windows 10 home edition rather than LTSC. This isn't a viable solution for me but I thought it made sense to check if it works on a different edition.

Resolume now runs fine. So it would appear I can localise the issue now to the LTSC version.