I just recently went from an AMD Phenom II to an I7-7700K with 16GB DDR4 and a fresh install of Windows 10, and nothing in DOSBox will run at all, whether it's via GOG installed games or my separate DOSBox installation. Everything stops at the first window, and freezes (see the attached image). Anyone else had any similar issues? I'm guessing it's CPU related but I'm at a loss as to what to do about it.

That being said, I am kind of tickled by the fact that a nearly £700 upgrade has left me unable to play games that are more than 20 years old.

Guess I will stick to my Phenom II for a while longer :-)

No joy I'm afraid - I should have added, I'm using the same GPU as before my upgrade, which is an Nvidia 1060, and I didn't have these issues before - I don't think it's a renderer issue. This is why I'm thinking it's more CPU than anything else, as it's the main thing that has changed.

Don't use output surface, use ddraw (recommended) or overlay

See my previous post. It's not a renderer issue - I've tried all the variables one by one. I've also tried the previous version of DOSBox, resetting the config file, and it's the same at every attempt. It'll be CPU related, probably, because that's the significant change in my set up. I suppose I was hoping that perhaps it's a common issue but I'm having no luck at all with forums. I even raised a ticket with GOG. The VOGON/DOSBox forums haven't yielded much, though I haven't bothered posting it there - they seem unfriendly.

In this case, rebuild/compile your own DOSBox may help. If it is really an CPU issue, compiler may optimize the code for the specific CPU.

Are your games and DosBox saved in a different location now? Like a system folder?
Maybe it's locking up on some system protection of some sort?

Or maybe it's not playing friendly with an Anti-virus/Malware protection? Could try turning those off one by one (preferably while disconnected from the web to be safe) to see if it's a conflict based on the new install.

Can also check if there is a problem with Data Execution Prevention (DEP). You can add programs to be exempted or turn it off entirely.

Hope one of these helps...

I'm leaning more to an issue induced with the fresh install of Windows 10 than the CPU itself...

The GOG titles are where they were before, so no changes there. DOSBox is installed to C, with the standard location for the config file after installing. Both the GOG titles and standalone DOSBox have the same issue, which also makes me think it's not config related.

I've tried adding DOSBox.exe to the DEP list, no change. Temporarily turning off anti-virus also didn't have an effect.

You're probably right that it's more Windows 10 than CPU. I'm also finding that Kodi crashes after starting playback, after a few seconds, as well, so something is amiss there (I also tried a previous version of that to no avail). Windows is apparently up to date, I've got the latest Nvidia drivers installed, and I've installed all the relevant motherboard drivers and the like as well. I am flummoxed!

Off-topic, but how do you like your GTX 1060? Satisfied with the performance ( on modern games )? I don't really need an upgrade just yet, but I've been considering this particular GPU as a potential future replacement.

I've had it for several months, and I'm very happy with it, it made a big difference in pretty much everything. I only decided to upgrade the rest because I'm in a new job and can afford it now, and I'm increasingly finding support for Phenom CPU's is on the way out, so it seemed the time to get set up for the next (hopefully) several years.
You're going to have an increasingly hard time with new titles if you're choosing to stick to Windows 7. I can understand, I was a big fan of 7 and used it for years, but by and large my experience of 10 has been smoother and simpler. It's only this last week I've been having any particular issues with it.

It doesn't hurt that it takes considerably less time to install Windows 10 than it does any other version of Windows I've used in the past. I did two separate installs on two systems (put my old parts into a spare case, for my parents to use) last week and both were surprisingly simple affairs, even with the older gear only installing to an old 70 gig HDD. It's slower to boot than my SSD, but it runs fine.

There really isn't much to DOSBox and it's very easy to troubleshoot since it uses SDL.

If you ask for help at VOGONS make sure that you are using DOSBox 0.74 from the DOSBox site.

Make sure you are changing the right configuration file (the shortcut in the start menu to change the config is the one you want).

The picture you posted is usually because of "output" being set to the default of surface and the latest drivers not supporting that setting but the "Not responding" seems to point to something else.

To troubleshoot launch msconfig and click "Diagnostic startup", click Apply and then reboot. (Before you do that clear your event logs).

On reboot check your even logs for errors and try DOSBox again.

Do you have any controller (joystick or pad) plugged in?

Well, that was mystifying.

I did as you suggested, and changed to diagnostic startup, which wound up locking me out of Windows, as the login screen wasn't presenting properly at start up. Went into safe mode, set it to default, and restarted Windows. DOSBox seems to load now.

I'm none the wiser as to what's really changed, but I have you to thank for it I think - so, thanks!
Just my Steam Controller dongle (shameless plug, I love my Steam Controller).