https://forum.asrock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Tue, 05 May 2026 15:36:26 +0000 Sat, 12 Mar 2016 16:36:34 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 https://forum.asrock.com/RSS_post_feed.asp?TID=2209 https://forum.asrock.com/forum_images/web_wiz_forums_black.png https://forum.asrock.com/ https://forum.asrock.com/forum_posts.asp?TID=2209&PID=11309&title=fm2a88m-extreme4-w10-problems-bios-2-90#11309 Author: ultravioletu
Subject: 2209
Posted: 12 Mar 2016 at 4:36pm

PS: I fixed the issue by reflashing v2.90, so that Windows starts again, then by installing the Logitech software (SetPoint), which brought in proper drivers for mouse and keyboard ( now they are displayed in control panel with their real names).

So I am good. As I said, before the BIOS update Windows was able to use generic drivers, afterwads it wasn't... ]]> Sat, 12 Mar 2016 16:36:34 +0000 https://forum.asrock.com/forum_posts.asp?TID=2209&PID=11309&title=fm2a88m-extreme4-w10-problems-bios-2-90#11309 https://forum.asrock.com/forum_posts.asp?TID=2209&PID=11297&title=fm2a88m-extreme4-w10-problems-bios-2-90#11297 Author: ultravioletu
Subject: 2209
Posted: 12 Mar 2016 at 2:17am

Hi,

In an attempt to fix some stability problems (which in the meanwhile seem to have been caused by power source) I flashed a couple of days ago the latest BIOS version (2.90).

Beside the "bios freeze" problems experienced by owners of "bigger" brother FM2A88M (which in my case occured  - albeit rarely - before the BIOS update as well), I noticed that the keyboard does not work anymore (in Windows 10). It is a Logitech wireless, connected to PC via an Unifying receiver (USB). Curiously, the mouse connected to the very same receiver worked.

The keyboard worked very well in BIOS or in Linus, only W10 seemed to have a problem with the unifying receiver. Again: immediately after BIOS update. I tried with a different set of Logitech devices (different model) - the same.

Even nastier, after downgrading the BIOS to 1.10, W10 wouldn't boot anymore (THREAD_STUCK_IN_DEVICE_DRIVER, even the built in Restore feature crashes with some sort of SECURITY message). I admitedly made the mistake to use the "normal" W10 restart, instead of the proper shut down with SHIFT. Now I hope that a previous Clonezilla image will straighten things up (this is a different issue, sorry for offtopic).

However, I think the issue of the Unifying receiver must be followed up. As said, it occured immediately after BIOS upgrade.

It is a month old W10 installation (a clean W7 install + upgrade, no settings or application preserved during it), relatively light (still not much software on it). All drivers were installed via Windows Update (altough as a alternative I tried installing the latest chipset drivers from AMD website). The only additional device in the system is a Digital Devices tuner (which worked properly even after the BIOS upgrade), everything else is onboard.

CPU is A10-7850K, RAM is G-Skill Trident X DDR3-2400 (16 GB).




Edited by ultravioletu - 12 Mar 2016 at 2:54am]]> Sat, 12 Mar 2016 02:17:57 +0000 https://forum.asrock.com/forum_posts.asp?TID=2209&PID=11297&title=fm2a88m-extreme4-w10-problems-bios-2-90#11297