ATuning crashes on Win10

I meant Z97 Extreme6 mobo.

As I've received no answers to this problem, I am wondering if this is the official forum for ASRock technical support or just a "community" of users helping each other?

Jojo110 wrote: I am running ATuning 2.0.271 dated 11/16/2015 on an Extreme Z6 mobo.  There does not seem to be a later version than 2.0.271. Since moving to Win10 Pro X64, I have started getting various errors from ATuning such as this: "Access violation at address at 007E0797 in module ATuning.exe.  Read of address 00000000." causing the ATuning app to terminate once I click on the repeating message a few times. How to fix this problem?

Is your Windows 10 installation an upgrade installation, or a new, fresh installation of Windows 10?

Do you know which build of Windows 10 Pro you are using? Is it the new Anniversary version?

What UEFI version are you using?

Do you run A-Tuning automatically when Windows starts, or manually?

We aren't seeing many complaints about A-Tuning not working with Windows 10 on your board.

Windows 10 has caused problems for many programs and drivers, some that have not been solved for months by the provider of the driver, Intel's networking driver for example. The new way Microsoft is releasing the updates/changes to their product (Windows 10) as a new package rather than small updates, seems to be causing more issues with existing software than in the past.

parsec wrote: Is your Windows 10 installation an upgrade installation, or a new, fresh installation of Windows 10? Do you know which build of Windows 10 Pro you are using? Is it the new Anniversary version? What UEFI version are you using? Do you run A-Tuning automatically when Windows starts, or manually? We aren't seeing many complaints about A-Tuning not working with Windows 10 on your board. Windows 10 has caused problems for many programs and drivers, some that have not been solved for months by the provider of the driver, Intel's networking driver for example. The new way Microsoft is releasing the updates/changes to their product (Windows 10) as a new package rather than small updates, seems to be causing more issues with existing software than in the past.

1. Upgrade installation
2. Anniversary. Build 14393.rs1_release.160715-1616
3. 2.50 UEFI
4. AT runs automatically

So far, I only had one driver that needed to be reinstalled and that was a Cirque touchpad driver, which is the style mouse I use on the desktop.

I can't seem to find where the old AT module is.  Where can I download it from?

I am surprised AT hasn't been updated since late 2015!

Xaltar wrote: parsec wrote: Is your Windows 10 installation an upgrade installation, or a new, fresh installation of Windows 10? This^ Many of the complaints we see here on the forums regarding Windows 10 seem to be occurring with upgraded copies. MS really didn't get the upgrade setup right, so many issues with driver and app compatibility.

I have people asking me how to prevent the automatic, basically forced upgrade to Windows 10 that is being sucked into their PCs by an update service program that runs on their PCs. The update service program is a resource hog, which is one of the main objections of most people that ask me about this.

They are also worried that their older PC hardware won't be compatible with Windows 10. While they are not 100% wrong, these people are not the PC hardware enthusiast type that install drivers, etc, on their own. They just want their PC to work and not be broken by outside intervention that they did not ask for.

Microsoft has been sued successfully (at least in one case) for their forced Windows 10 "upgrade", but that does not seem to have stopped them from continuing this practice. It may take a while for governments to catch up with this. I imagine the EU will be the one that is the first to step in, if they can legally.

The transition point for hardware when Windows 10 starts to become questionable, at least for Intel platforms, seems to be anything before the 7 series chipsets, like a Z77.  This is for new, clean Windows 10 installations with manual, controlled driver and software installation. That means with the PC not connected to the Internet until the basic driver and software installation is complete. That's how I do it, and have a clean Windows 10 installation on an ASRock Z77 board working fine.

Windows 10 upgrade installations have the added (apparently huge) variable of the Windows version currently on the PC. Who knows how that works. Are the drivers that are used in the Windows 10 upgrade based upon those that are currently used on the PC, for example? Or the INF files? I cannot begin to comment on this situation, mainly from lack of experience, but the number of variables involved make it impossible for me to even guess about it.

The six series chipsets like P67 and Z68 seem to have both success and failures with Windows 10. You'll notice that the number of Windows 10 compatible drivers for boards with these chipsets become much more scarce then newer chipsets.

Once you get older than the six series, meaning the 5 series (P55, etc), X58, and earlier Intel chipsets, we don't see any drivers beyond Windows 7 on the download pages of these boards. Do the Microsoft Windows 10 drivers, etc, work with these boards? I can't say they won't, but I also can't say that they will.

Possibly a coincidence, but the use of UEFI firmware began with the Intel six series chipset boards. The only capability used at that time was the GUI type interface for the firmware options. The seven series chipset boards began letting us actually use other UEFI capabilities. Is that one of the major factors in the wall between Windows 10 compatibility and not?