Jmicron Jmb36x Ide Drivers For Mac

Posted on  by admin

Under device manager, Then under SCSI and RAID controllers, I had a device titled 'GIGABYTE GBB36X CONTROLLER' which was not digitally signed. After downloading a Microsoft update referencing this I now have the same device which is now 'digitally signed'. BUT now I also have a 2nd entry titled 'JMicron JMB36X Controller' which has a Code 10 and can't start. It has the same driver date and same driver version # as the Gigabyte driver & is also digitally signed. What should I do? (for now it's been disabled).

Under disk management it shows Drive D: as Gigabyte, but it is actually my Pioneer DVD player. I don't know what is going on, but I'm lost.

Jmb36x

If I use AHCI in the BIOS then device manager shows no DVD drive. If I switch back to IDE it reappears. It used to work under AHCI. It also seems quite slow now. I tried it with the Microsoft patch which updates the driver, and now I've gone back to the original driver from the Gigabyte software. Still not working. It stopped working after I unplugged the hard drive a couple days ago and then plugged it back in.

Jmicron Jmb36x Driver Windows 10

I don't know why this would have screwed things up, but it did. If anyone else has this problem with the JMicron controller and a Gigabyte motherboard, I found this solution from another forumn: If you do Windows hardware updates and end up with 2 Gigabyte JMicron controllers, delete the one with the yellow sign by it that says it's not working. Download the driver on the Gigabyte website to your desktop. On the remaining driver update it using device manager and telling it to look in the folder on your desktop. Now when you reboot you should be able to see your DVD drive even when using AHCI in the bios. At this point you can go to device manager again and use Windows update to update the driver again to the same one that's on the Windows update site. (the cause of my mess was going to the Windows update site and downloading the updates from there; if I would have used device manager for the update I'm told this would not have happened).