Posts: 10310 | Last online: 05.28.2017
Retired Vet
Tennis, Walking, Computer
Date registered
    • Zitat von FirstEver im Beitrag #1982
      I found that the ASUS MAXIMUS IV EXTREME and ASUS TUF SABERTOOTH P67 doesn't have any 'Volume Free Space' like other UEFI's from ASUS.
      I can insert the NVMe module after last 'DXE driver' but it this cases the last 'PEI module' will be Rebuilded - is it ok?
      Yes, the usage of CodeRush's UEFITool is very safe (contrary to AMI's Aptio V MMTool). If any desired BIOS modification is impossible or goes wrong, you will get an error message.
      In your case the following PEI module obviously had to be rebuilt and recompressed to give the inserted DXE module the required space.

      Off topic:
      Please stop inserting oversized images, which take more place than required resp. available. It is much better to use the Forum Software according [url=http://www.win-raid.com/t971f35-Guide-How-to-insert-pictures-or-attach-files-to-a-post.html]>this<[]/url] guide.

    • @YuriyCN:

      Zitat von YuriyCN im Beitrag #6
      I need the USB driver for Windows XP (motherboard Gigabyte GA-H110M-DS2, Intel® H110 Express Chipset) USB Device - VEN_8086&DEV_A12F
      Please try the attached XP compatible mod+signed 32bit Renesas/Intel USB 3.0 drivers, which have just been composed by me for being usable with all modern Intel chipsets from 7-Series up and their on-board Intel USB 3.0 Controller and Hub devices.
      Don't forget to give us your feedback regarding your test result.
      Good luck!
      Zitat von YuriyCN im Beitrag #6
      "32bit Intel USB 3.0 + 3.1 Drivers v5.0.3.42 mod + signed by Fernando.rar" - this driver does not work (Error: Code 39)
      As I have stated within the start post of >this< thread, these modern Intel USB 3.0 drivers will only support Windows Operating Systems from Win7 up and cannot be used with Windows XP..

    • @DriveByPoster:
      Welcome at Win-RAID Forum and thanks for your feedback!
      It is fine, that you got your NVMe SSD bootable.

      Zitat von DriveByPoster im Beitrag #83
      a) whether this will somehow interfere with the use of Samsung's drivers for the SSD vs. those that come vanilla with Windows.
      This question should better be answered by a Clover expert.
      Zitat von DriveByPoster im Beitrag #83
      b) when I add a couple of extra drives I have lying around, I need to make sure the system doesn't start trying to boot from them. I'm sure this will be manageable.
      Yes, you can manage it by using the Boot Manager hot key.

      Enjoy your NVMe SSD as bootable system drive!
      Dieter (alias Fernando)

    • Fernando has written a new post "Adding NVMe selection in ASUS GL752VW Bios possible?" Today

      Welcome at Win-RAID Forum!

      Ferrous's answer is correct.
      The BIOSes of older mainboards are able to detect an NVMe SSD (otherwise the Windows Disk Management wouldn't show it as connected Disk Drive). Although the name of ithe NVMe SSD is not visible within such BIOSes, it is possible to boot off the NVMe SSD, if the related LEGACY/UEFI mode pre-conditions are fulfilled (LEGACY mode: NVMe Option ROM present within the SSD Controller chip, UEFI mode: matching NVMe EFI module present within the mainboard BIOS).

      Dieter (alias Fernando)

    • Zitat von vegasnight9 im Beitrag #1980
      I found on the YT fast mod in 3 steps:
      Has anyone tried this method?
      It is exactly the same method as written within my guide (= start post of this thread).

    • Zitat von m1from im Beitrag #1978
      I changed filename with and without ASUS BRenamer to the proper one of course, and formatted USB sticks with rufus MBR partitioning, FAT32 fs.
      Ok, but this doesn't automaticly mean, that the USB Flashback feature doesn't work with your mainboard. I suspect, that you have used one or more not matching USB Flash Drives (look [url=http://www.win-raid.com/t871f16-Guide-How-to-get-full-NVMe-support-for-all-Systems-with-an-AMI-UEFI-BIOS-130.html#msg38828]>here<[/url).

    • Fernando has written a new post "Intel Chipset Device "Drivers" (= INF files)" Yesterday

      @ all:
      Since there are brandnew (but wrongly dated) Intel Chipset Device INF files v10.1.1.44 available since a few days, I decided to update my AIO package with the latest Intel Chipset Device INF files, but with corrected dates.

      Update of the Start post

      • updated: "Latest pure Intel Chipset Device INF Files v10.1.x.xx mod+signed by Fernando" with corrected dates (04/19/2017 for the included INF files v10.1.1.44 and 02/01/2017 for the v10.1.2.85 ones), the v10.1.1.44 INF files were modified and digitally signed by me today (05/27/2017).

      This is what I got with my MS Surface Pro 3 (Intel 8-Series Chipset Mobile system) after having updated the related INF files:
      [[File:mod+signed INF file v10.1.1.44 - Pic1.png|none|auto]][[File:mod+signed INF file v10.1.1.44 - Pic2.png|none|auto]]

      Any feedback is much appreciated.
      If you should find any Intel chipset device, which is not supported by my updated "All-in-One package", please let me know it.

      Dieter (alias Fernando)

    • @vegasnight9:
      Welcome at Win-RAID Forum and thanks for posting the video.
      Did you make the video yourself? Where is it published?

      Zitat von vegasnight9 im Beitrag #1973
      Is it working ?
      Whom did you ask?
      Where do the users can find and download the UEFITool and the required NVMe BIOS module? I couldn't find the links.
      Dieter (alias Fernando)

      Thanks for your final report. It is fine, that you succeeded.
      It may be a good idea to offer your already modded BIOS within >this< Sub-Forum.
      This way users with a similar mainboard and the wish to get full NVMe support, will find it easier.

      The NvmExpressDxE_2.ffs, which I am offering within the start post of this thread, fully supports the Samsung 960 EVO and 960 Pro NVMe SSDs. So a later NVMe module version is not required to get them working.

      Thanks for your report. It is fine, that you got the modded BIOS flashed by using the AMI AFU tools and got the OS installed onto the NVMe SSD.
      By the way: It is no wonder, that the USB Flashback method didn't work with the original ASUS BIOS file. This method requires a special BIOS file name, which is not identical with the original one.

    • Fernando has written a new post "How to keep a Samsung M.2 SSD cool" Yesterday

      Since this info/discussion has nothing to do with the topic "How to get full NVMe support for all Systems with an AMI UEFI BIOS" and the Sub-Forum "BIOS Modding", I have created a new thread within the Sub-Forum "Solid State Drives" and moved all your related posts into it.
      Furthermore I have resized the pictures and insereted them by using the Forum software.

    • Fernando has written a new post "[OFFER] Asus Rampage IV Extreme - Nvme Bios mod (4901)" Yesterday

      Welcome at Win-RAID Forum and congratulations for having succeeded to get full NVMe support for your X79 chipset mainboard!
      On behalf of other users with a similar mainboard I want to thank you for offering your modded BIOS inclusive a description of the procedure how you got everything working.

      Off topic:

      As you probably have realized, I have slightly re-formatted and customized the content of your post for a better readability and hope, that this is ok for you. If not, you can change it yourself bay editing the post.
      Furthermore I have moved this thread into the better matching Sub-Forum, where the users can offer their successfully modded BIOS for other users with a similar mainboard.

      Dieter (alias Fernando)

    • Fernando has written a new post "WIN XP USB 2.0 / 3.0 Drivers Database for eHCI & xHCI Controllers" Yesterday

      Zitat von XPLives im Beitrag #3
      Title shortened as much as I could.
      Thanks for having done that.
      Another tip: Your start post would be much clearer arranged, if you put the details into "spoilers".

    • Fernando has written a new post "NVIDIA: Optimized nForce Driverpacks for Vista/Win7-10" 05.26.2017

      Zitat von Amatorcomp im Beitrag #504
      Zitat von Fernando im Beitrag #503
      By the way: Haven't you imported the Win-RAID CA Certificate, before you installed the mod+signed drivers?
      No. Was it necessary to do this?
      Yes, if you want to prevent messages regarding the missing signature. The Win-RAID CA Certificate has to be imported, before you are going to install any of my mod+signed drivers.

    • Zitat von Confused im Beitrag #26
      Just a thought for anyone else who is determined, might the best and the safe way to achieve a change from IDE to AHCI in the earlier circumstances be to follow the above procedure with an identical image of the existing OS and install over the top in a non-destructive reinstall as per this guide?. The two versions have to be identical or you will get an error when trying to reinstall.
      What do you think Dieter?
      As I said, I recommend to do a fresh install of Win10 x64 and nothing else.

      I do have one other question: my BIOS doesn't have separate raid/ahci settings - it runs AHCI only when set to RAID.

      It would be much better to set the Intel SATA Controller to "AHCI" (provided, that the BIOS offers this option).
      Which is the manufacturer and the exact name of your mainboard?

      If I am running two drives but as single disks without setting up a RAID array, do I need to worry about the RAID ROM version in the BIOS to get TRIM etc. working?

      As long as the SSD is not a member of a RAID array, TRIM should be active within your SSD.

      If so, how do I find out my version?

      After having set the Intel SATA Controller to "RAID" mode, you can see the Intel RAID ROM version of your BIOS, when you hit CTRL+I while rebooting.

    • @Confused:
      Welcome at Win-RAID Forum!

      Although it is possible (but risky) to switch the Intel SATA Controller from IDE to AHCI mode from within a running OS, I do not recommend to try it.
      My recommendation is to do a fresh install of the desired OS in AHCI mode onto your Samsung 850 EVO SSD. This way is much safer and will give you the benefit of a slim OS without garbage from the past.

      Zitat von Confused im Beitrag #24
      How can I update the driver when the system is running in IDE non AHCI mode and it says the best driver is already installed?
      If you really want to install a "wrong" (not matching) Intel AHCI driver for an Intel SATA Controller, which is running in IDE mode, you have to force the driver installation by using the "Let me pick..." > "Have Disk" options.

      Can it be done in safe mode?

      Yes, but it will not make any difference.

      Also, do I need to update both controllers or if only one, which one?

      You have to update just the driver of the Intel SATA Controller, to which your system drive is connected. So you have to check this and to UNINSTALL the other listed Intel SATA Storage Controller.

      When I get it working, will the driver fully support the SSD in AHCI mode with TRIM etc.?

      Yes, if you really should succeed with your plans.
      As I already stated above, I recommend a fresh OS install instead. Before you start it, don't forget to save your important data from your current system drive.

      Dieter (alias Fernando)

    • Fernando has written a new post "USB 3.0/3.1 Drivers (original and modded)" 05.25.2017

      I agree with you. The Intel USB 3.0 Controller will not work with a Renesas USB driver.

    • Fernando has written a new post "NVIDIA: Optimized nForce Driverpacks for Vista/Win7-10" 05.25.2017

      Welcome at Win-RAID Forum!

      Zitat von Amatorcomp im Beitrag #502
      1. Should I worry about "Not digitally signed" in the Device Manager?
      No, this wrong and misleading message has no impact on the function of the related driver and the performance resp. stability of the system.
      By the way: Haven't you imported the Win-RAID CA Certificate, before you installed the mod+signed drivers?
      Zitat von Amatorcomp im Beitrag #502
      Which driver of the chipset would you recommend to use for Windows 10 pro x86 (ASRock the SMU Driver "AllIn1_Win7 (15.45) or the SMU Driver (v1.71) modified from your "Latest nForce Driverpacks for Win7-10") ?
      Since I cannot test it myself (due to a missing nForce chipset system), you have to find it out yourself. If not, you should have done it.
      Zitat von Amatorcomp im Beitrag #502
      2. After installing your Ethernet Driver (v73.3.5) modified (from Your "Latest nForce Driverpacks for Win7-10"), Windows 10 through windows update automatically installs the network controller driver (v7.3.1.7336) from 23.02.2012. Which of these two drivers do you think will be more relevant for my network controller (your Ethernet Driver (v73.3.5) modified from Your "Latest nForce Driverpacks for Win7-10" or installed through windows update network controller driver (v7.3.1.7336) from 23.02.2012)?
      I am sorry, but I cannot give you an answer, because I have never used my nForce system with Win10 as OS.

      Dieter (alias Fernando)

    • Zitat von woofer im Beitrag #16
      It's the same with Jeff
      Maybe it is the same problem.
      Just to make it as clear as possible:
      1. If you want to flash an original (=untouched) BIOS, you can use the standard BIOS flashing procedure, but you should not rename the BIOS file, not even the extension of it.
      2. If you have modified the AMI UEFI BIOS of an ASUS mainboard in any way, you have
      a) to rename it according the ASUS rules and
      b) to flash it by using the ASUS USB Flashback feature.

    • @woofer:
      Welcome at Win-RAID Forum!

      You cannot flash a modded BIOS the normal way into the BIOS chip of your ASUS mainboard. You have to use the special ASUS feature named “USB Flashback“.

      Dieter (alias Fernando)

    • @iX-9:
      Welcome at Win-RAID Forum!
      This is what I would do (resp. what I have already done with great success:
      1. Buy the 250 GB Samsung 960 EVO.
      2. Insert the NvmExpressDxE_2.ffs into the BIOS of your mainboard.
      3. Let the tool Rufus prepare a FAT32 formatted bootable Win10 x64 image for a clean installation in UEFI mode (using the GUI-mode Partition Table).
      4. Insert the Samsung 960 EVO and remove all other storage Disk Drives.
      5. Enter the BIOS and do the settings, which are recommended within the start post.
      6. Boot off the prepared USB Flash Drive in UEFI mode and install the OS onto the NVMe SSD.
      7. Once the OS incl. the latest MS Updates are installed and running fine, you can reconnect you other Disk Drives.
      8. If you want to boost the Performance of your new system drive, I recommend to follow my tips, which I have given for AHCI systems, but are valid for NVMe systems as well.

      Good luck!
      Dieter (alias Fernando)

    • Fernando has written a new post "[SOLVED] Unable to install the Samsung NVMe driver" 05.25.2017

      Yesterday I got a PM from the Forum member Bruno_3, where he wrote, that he was able to solve his problem by simply disabling the Norton Antivirus program before trying to install the NVMe driver.
      Since he didn't follow my advice to publish his solution into this thread, I have done it myself.



Xobor Forum Software von Xobor