My ps/2 mouse has an I/O range conflict

In my motherboard ASUS M4A88T-M USB3, there's only one ps/2 port.
In the device manager it shows that there's an I/O range conflict with the "motherboard resources".

It says:

Input/Output Range 0060 - 0060 used by:
Motherboard resources
Input/Output Range 0064 - 0064 used by:
Motherboard resources





I managed to track down that "motherboard resources" device.
In device manager i selected: view -> resources by type -> input/output (IO)

It's the one highlighted in the image:





I double-clicked it and selected "resources" tab and this is what i got:





I have no idea what that device 0800-089F does, i tried to uninstall it but with no luck, i tried to reset cmos but with no luck, i tried to flash bios but with no luck, i contacted asus customer support but they were unable to solve the problem.

The problem is not with the mouse itself that's for sure, i plugged a ps/2 keyboard and the conflict still exists.

This conflict exists with both the manufacturer's drivers and the new drivers from AMD.

I only noticed this problem because sometimes my mouse doesn't work after i log in to windows, everything works fine including the keyboard, but sometimes my mouse doesn't work at all, so i have to shut down and press the power button again.

This problem still exists when booting in safe-mode, and there are no pci slots that i use.

Any help ?

My system specs:

Motherboard: ASUS M4A88T-M USB3
CPU: AMD Phenom II x2 560 black Edition
Graphics: Integrated ATI HD 4250
Windows: 7 Ultimate x64

I have exactly the same problem. Your screen shots are what mine show. But if I use the mouse in the usb I start getting disconnect/reconnect sounds and the mouse pauses. Sometimes I would end up unplugging and plugging the mouse back into the usb. I thought the ps/2 wouldn't have that problem, but sometimes it quits also. Then I have to reboot for it to start working again. This only started about a month ago. I don't know if it had to do with one of the window updates or not. I've looked for solutions online, but nothing helps. I've also seen that others have had this problem from back as far as 2009. I know your post is almost 2 yrs old, so I was wondering if you had any luck.

John K