@loadlover
on my two 960 PRO 1TB I have updated (via Magician v5.1) from 2B6QCXP7 to 3B6QCXP7.
I get no problem, However i have seen on the net (touslesdrivers.com) that some 960 PRO users have problems with 3B6QCXP7.
I have seen somewhere that Samsung Magician does no longer offer the suspect firmware now..
So, if you have 2B6QCXP7 keep it because you can never downgrade Samsung SSDs firmware !
I hope Samsung is working on the detected 'read' performance problems.

Hey, @Fernando
I have Asus P8Z77-V LK and Samsung 960 EVO 500GB.
And I'm about to flash my bios. I completed all steps and now I'm on step - flashing modded BIOS.

But I constatly have "Security Verification Failed" under Asus EZ flash 2.

EDIT: Found that issue lies under .rom and .cap file extension. Asus EX flash 2 rejects to read .rom files.

Any ideas?

Thanks!

@loadlover
Regarding the behavior of the system: Samsung recently recognized that the latest firmware for the 960 Pro and 960 Evo negatively affect the stability of the system.

@InsFi
What can I do without any problems: this mobo has a DIP BIOS chip. Since it can be programmed on the programmer simply by removing it from the socket, you must first convert from CAP to BIN using Asus CAP_to_BIN, and then download the firmware to the IC BIOS and it will work correctly.
Tested on several mobo.

@Fernando no luck so far.
My mobo doesn't have a USB Flashback feature. So I tried AFU approach. But it constantly shows me an error: "Secure Flash Rom verify failed" or "Secure Flash function is not supported on this file".
Maybe I misunderstood something?

My steps: take original .cap file -> add nvme module to file via UEFITool -> save it to modded file. Try to flash.
The same is with AFU. Make a backup -> add nvme module via UEFITool -> try to flash modded file.

Maybe UEFITool brokes file somehow?

@Morlock No success either.
My steps:
Convert .cap to .bin -> add nvme module via UEFITool -> save to .cap file -> try to flash.

Asus EZ Flash 2 tool shows me an error: "The file format is not correct. Ensure that the filname extension is .CAP"

Q: Am I mistaken in some of my steps?

Thanks guys.

P.S. Mobo: Asus P8Z77-V LK. And bios version - 1402

Read a private message.

Why wont nobody help

@cmoneytheman

Zitat von cmoneytheman im Beitrag #2438

---

Why wont nobody help

---

Hi Everybody,

Feedback:

First timer here. Thanks for this guide Fernando. I had a lot of difficulties understanding the guide in the OP because I thought the picture links were broken and not updated. Only now that I've signed up I realized that I needed to do so in order to see the pictures. Perhaps a word at the start of the guide saying "Log in to see pictures" would help out hapless fellows like me.

Because of that difficulty, I ended up following the guide here: http://www.overclock.net/t/1571271/tutor...n-intel-chipset And it worked. (I got MMTOOL from here in case anyone needs it http://voltground.com/haven/threads/13/ I found it very difficult to find it)

Information before questions:
I have the ASUS MAXIMUS V FORMULA Z77 motherboard and so I modded its latest .cap bios file with the Nvme.ffs, NVMEINT13.ffs and NvmeSmm.ffs extracted from the ASUS MAXIMUS VII FORMULA Z97 motherboard's latest .cap file. I flashed the modded bios using the usb flashback method which worked well.

Z77 doesn’t have the m.2 slot but it does have PCIE gen 3.0 support.

So, I installed my new Samsung 960 EVO Nvme m.2 ssd using an M.2 to PCI-E adapter. I installed it in the second PCI-E X8 slot, ie. the slot where the second GPU in SLi would go. This dropped my gpu pcie slot speed to x8 as verified using GPU-Z (and I know this doesn’t matter for performance).

Questions:

1. My Sequential Read speed is 1549 MB/s and Sequential Write speed is 1478 MB/s according to the performance test that comes with the latest version of Samsung Magician (V5.1.0). The speeds are supposed to be 3200 read and 1900 write.

So, my first question is what am I doing wrong that makes the speeds low?
I have already installed the driver from Samsung and checked in device manager under storage controllers for "Samsung NVMe Controller". But the "properties" of my new ssd under Device Manager>Disk drives shows that the driver provider is microsoft. Is this how it is supposed to be?

Here is a picture of the adapter I am using if that helps: https://i.imgur.com/2MbGLlA.jpg

2. Please take a look at this picture of the bios screen even before I installed the new ssd (before flashing or anything else): https://i.imgur.com/ehS7tlz.jpg
You can see that under Boot Override, I have three options: Windows Boot Manager, P6: M4 and P1: Samsung 840 EVO (the boot drive to be replaced).

Now take a look at this picture after installing the new drive, removing the old 840 EVO and flashing for NVME support: https://i.imgur.com/A2FJgRK.jpg
Now there are only two options under Boot Override: Windows Boot Manager and the P6: M4. I don’t see the NVME drive separately listed here. The same goes for Boot options.

I tried toggling CSM’s “Boot from PCIe/PCIE Expansion Devices” from “Legacy OpROM first” and “UEFI driver first” to see if the drive would be detected separately. But it did not work.

So, my question is: why is only the windows boot manager detected and not the drive? Did I get this working by fluke? What am I doing wrong?

@Mountainlifter

In answer to your first question, if you have an Ivy Bridge CPU, make sure the PCIe slot that you put the NVMe adapter card in is configured in the BIOS for PCIe 3.0. Sandy Bridge CPU’s won’t give you the PCIe 3.0 speed you need to get the full performance of the SSD. Also, if you purchased your 960 Pro recently and it has the 3B6QCXP7 firmware (3B7QCXE7 for the 960 EVO your picture shows), your performance issues may be related to the firmware. Many 960 Pro and EVO owners (but mostly PRO) have complained about performance issues after updating the firmware, or purchasing a 960 series SSD that had the latest firmware pre-installed. You can find Samsung’s official response here

https://us.community.samsung.com/t5/Memo...-p/221328#M1003

Regarding your second question, it looks like you had originally installed your 840 EVO in UEFI mode, which gave you “Windows Boot Manager”. If your BIOS shows the name of the SSD installed in UEFI mode separate from “Windows Boot Manager”, you must select “Windows Boot Manager” or you OS will not boot. Most people that do the BIOS mod get “PATA” (or some variant of it) instead of the name of the SSD. I’m assuming that you either cloned the UEFI OS from the 840 EVO to the 960 EVO, or you installed a fresh OS onto the 960 EVO in UEFI mode (?). Windows Boot Manager is installed by the OS in UEFI mode on the SSD, regardless of whether it’s NVMe or SATA (as it did with your 840 EVO). The 840 EVO is probably shown separately in the first pic because it is an SATA SSD (I’m guessing).

Zitat von Fernando im Beitrag #2442

---

Since we want active Forum members and no pure "leechers", guests can only read the text and have no further rights. This is valid for the complete Forum. So if I would follow your advice, I would have to add this notice to each post, which contains a picture or an attachment.

---

Zitat von Fernando im Beitrag #2442

---

Provided, that you have inserted the NVMe SSD into the fastest PCIe slot (you will have to check it yourself), you can boost the performance of your NVMe SSD by various actions/settings. Please have a look into the start post of >this< thread.

---

Zitat von Fernando im Beitrag #2442

---

Yes, only the generic in-box MS driver named disk.sys is able to manage the Disk Drives (especially the detection of the specific model and its abilities). On the other hand only the related Storage Controller (here: NVMe NVMe Controller) and its storage driver (here: NVMe) are responsable for the performance of the connected Disk Drive (here: NVMe SSD).
This is absolutely normal - you haven't done a mistake. The NMe SSD is not listed, because you are not able to boot into the SSD in LEGACY mode (using a Master Boot Record) due to the missing Option ROM module. So the only option you have is to boot the NVMe SSD in UEFI mode via "Windows Boot Manager", which is within a usually hidden partition of your NVMe SSD.

---

Zitat von Paulos7 im Beitrag #2443

---

In answer to your first question, if you have an Ivy Bridge CPU, make sure the PCIe slot that you put the NVMe adapter card in is configured in the BIOS for PCIe 3.0. Sandy Bridge CPU’s won’t give you the PCIe 3.0 speed you need to get the full performance of the SSD. Also, if you purchased your 960 Pro recently and it has the 3B6QCXP7 firmware (3B7QCXE7 for the 960 EVO your picture shows), your performance issues may be related to the firmware. Many 960 Pro and EVO owners (but mostly PRO) have complained about performance issues after updating the firmware, or purchasing a 960 series SSD that had the latest firmware pre-installed. You can find Samsung’s official response here
https://us.community.samsung.com/t5/Memo...-p/221328#M1003

---

Zitat von Paulos7 im Beitrag #2443

---

Regarding your second question, it looks like you had originally installed your 840 EVO in UEFI mode, which gave you “Windows Boot Manager”. If your BIOS shows the name of the SSD installed in UEFI mode separate from “Windows Boot Manager”, you must select “Windows Boot Manager” or you OS will not boot. Most people that do the BIOS mod get “PATA” (or some variant of it) instead of the name of the SSD. I’m assuming that you either cloned the UEFI OS from the 840 EVO to the 960 EVO, or you installed a fresh OS onto the 960 EVO in UEFI mode (?). Windows Boot Manager is installed by the OS in UEFI mode on the SSD, regardless of whether it’s NVMe or SATA (as it did with your 840 EVO). The 840 EVO is probably shown separately in the first pic because it is an SATA SSD (I’m guessing).

---