4390, 4391, 4932, and 4393 are the same controller, the device ID's are different so the correct drivers can be installed. I don't know why there are 3 bios rom images though...




http://support.amd.com/TechDocs/45483.pdf

Zitat von Bugger Vance im Beitrag #361

---

the "old" (and maybe faster) >64bit AMD AHCI Driver v1.2.1.359 WHQL for Win7 x64< does not boot my windows 7. it's stuck at windows starting screen. the "new" one does booting completely. so i have to choose between standard windows ahci driver or the "new" one. i did a benchmark with my sshd. yeah, i know, it's difficult to benchmark a sshd because of judgement of often used files layed on the flash area of the sshd. but the results are quite equal. some values were faster, the other slower...all tests are running on SATA II

---

Zitat

---

1.2.001.0402

- Fix CZ_Win7: System BSOD:0x9F when run S3/S4
- Work around for slumber exit fail cause BSOD for Bastrop
- Fix the CPU high utilization issue when CCC enable

1.2.001.0396

- Fix OS loading screen hang if skip password of hard disk, skip load security locked hard disk
- Work around Carrizo hardware issue for slumber exit fail and cause BSOD

1.2.001.0376

- Fix the SB700 A12 boot hang issue if PM is enabled

1.2.001.0371

- Fix the OS hang issue if CCC is enabled from BIOS (specific for SB7xx/SB8xx)

1.2.001.0368

- Fix W7 359 issue that is enable command Completion coalescing in bios, system not booting to OS
- Add DID for Carrizo

---

Btw PM is Port Multiplier, not Power Management.

Hello!

Zitat von Pill Monster im Beitrag #393

---

Zitat von Bugger Vance im Beitrag #361

---

the "old" (and maybe faster) >64bit AMD AHCI Driver v1.2.1.359 WHQL for Win7 x64< does not boot my windows 7. it's stuck at windows starting screen. the "new" one does booting completely. so i have to choose between standard windows ahci driver or the "new" one. ...

---

AMD released newer drivers which fix the boot bug.

---

Zitat von Pill Monster im Beitrag #393

---

Btw PM is Port Multiplier, not Power Management.

---

Hello, I have just been "awarded" my third RMA in as many weeks for an ASUS Z170-Deluxe motherboard. On this third go around, I had the system up and running with Win7 Pro 64Bit, updated the OS and installed Chrome and Skype. Everything was normal. BIOS accessible on Boot, no problem.

THEN...upon installing the driver for a Samsung 950Pro NVME SSD - the BIOS got corrupted. I planned to use Samsung's Migration Tool to move the Win7 64 Bit OS from the HDD to the 950Pro. Today, after over 2 hours of tech effort with a good ASUS tech person we could not recover from the BLACK SCREEN OF DEATH. Loading into BIOS would work, but the screen would go black in 1 sec. Sometimes the UEFI BIOS was accessible for a short time. At the final stage the BIOS no longer could recognize the 2TB HDD boot drive, or the DVD player.

I used Samsung's download for the driver.

What is the speciality of the drivers on this forum? Why would the BIOS get corrupted in this way?? Windows 7 was fully installed and updated and working just fine.

I have another new Asus Z170-Deluxe ready for the fourth attempt. Would appreciate some guidance to make this system build work.

thanks
RMM

Hello Fernando..
Really thanks. I am happy to find a solid technical resource to deal with this issue.

Here are answers to your questions...
-1- How did I install the driver
ANS- I placed the latest Samsung Driver for the 950Pro in a folder of the C drive. After that I installed the 950Pro into the M.2 slot on the motherboard and rebooted. Windows then presented a dialogue box saying there is a new PCI device but no driver. I clicked the driver option and went to the folder. The Samsung Driver was run as administrator and by all appearances installed normally.

-2- Did you install the Win7 x64 driver
ANS- The Samsung Website only has one NVME driver shown. They note this driver like this * Notice : The driver operates in Windows 7/8.1/10 x86/x64. Web link is here....
http://www.samsung.com/global/business/semiconductor/minisite/SSD/global/html/support/downloads.html
So YES, I believe the driver was the proper driver. Hence my question about the drivers mentioned here.

-3- Win 10 Install
No, I did not use a trial installation of Win10. Due to intended use, I prefer to have the Win7 OS>
Also...As the BIOS became corrupted a Win10 trial seems to no longer be an option. No way to boot as the HDD cannot be seen by the BIOS now. Very strange.

Your thoughts? I really don't understand why the most direct BIOS flash method could not restore the BIOS to normal condition. We used three different BIOS versions and all were flashed by a USB and a motherboard button. This supposed to be the means to assure 100% rewrite of the entire BIOS. Instead the problem got worse and ultimately could not even boot to Windows.

Much appreciated.
RMM

Hi Fernando..
You are correct. This was an application file (.exe). So definitely not a "pure" driver.
I have downloaded the pure file. But as of now, the mobo is inoperable due to no recognition of any boot devices.

Yes, the CMOS was cleared. Then several BIOS versions hot flashed as described in my earlier email.

Three RMA's on this model. Two with the Black Screen of Death, and the 2nd on refused to boot to the UEFI Bios, a type of DOA condition.

RMM

@Fernando,
Many thanks for the status on AHCI protocol.

Referring to your 'this' thread, about nvme driver i see a new comer is Toshiba XG3 1TB SSD M.2/PCIe NVMe with a specific driver.
Seems a SM950 competitor..