- last edited on by
ROGBot
UPDATE 25th OCT 2017
Samsung's Site has hit the limit for SSD Downloads, so here:
https://github.com/NeoBeum/ASUS-G751JY
updated title for the thread
=================================================================
Hi, I'm posting this here just for a heads up for some people - who may or may not experience problems with Samsung drives on the ASUS Notebook range.
Errors should only start to manifest if the device is attempting to use secure boot with the current NVMe 2.2 driver from Samsung.
This driver can be loaded multiple ways - Windows will use it's own NVME driver until the Operating System is online, then load the Samsung Driver - however if Windows has installed it in such a way where the notebook attempts to load the driver during POST or prior to Windows Operating System - the device may fail to boot.
I'm going to be sending Samsung an email too - to see if they can get the driver signed. Fairly simple process... I was going to do it myself - but it needs Samsung's certificate, not mine.
I haven't been able to get this driver working properly in the PE while Secure Boot is enabled in my G751 Recovery Tinker Project - https://rog.asus.com/forum/showthread.php?94784-G751JY-Windows-Server-2016-All-Drivers-amp-Hardware-...
If you're not having issues - don't worry about this - but if you have experienced problems using a NVMe Storage device, this may be one of the factors attributing to the fault.
Thread in Hardware section for mod/admins
Samsung released WHQL Signed NVMe Drivers a few hours ago...
http://www.samsung.com/semiconductor/minisite/ssd/download/tools.html
They are still 2.2, but actually signed now
Samsung's Site has hit the limit for SSD Downloads, so here:
https://github.com/NeoBeum/ASUS-G751JY
updated title for the thread
=================================================================
Hi, I'm posting this here just for a heads up for some people - who may or may not experience problems with Samsung drives on the ASUS Notebook range.
Errors should only start to manifest if the device is attempting to use secure boot with the current NVMe 2.2 driver from Samsung.
This driver can be loaded multiple ways - Windows will use it's own NVME driver until the Operating System is online, then load the Samsung Driver - however if Windows has installed it in such a way where the notebook attempts to load the driver during POST or prior to Windows Operating System - the device may fail to boot.
I'm going to be sending Samsung an email too - to see if they can get the driver signed. Fairly simple process... I was going to do it myself - but it needs Samsung's certificate, not mine.
I haven't been able to get this driver working properly in the PE while Secure Boot is enabled in my G751 Recovery Tinker Project - https://rog.asus.com/forum/showthread.php?94784-G751JY-Windows-Server-2016-All-Drivers-amp-Hardware-...
If you're not having issues - don't worry about this - but if you have experienced problems using a NVMe Storage device, this may be one of the factors attributing to the fault.
Thread in Hardware section for mod/admins
Just an update for the Samsung 2.2 Drivers -
Samsung just called a few minutes ago - and they've escalated the ticket I raised to HQ.
I should have something by 2 weeks maybe - they didn't give me a turnaround.
Samsung just called a few minutes ago - and they've escalated the ticket I raised to HQ.
I should have something by 2 weeks maybe - they didn't give me a turnaround.
oh, if anyone is reading this, and you're using another vendors PCIE NVME that's not samsung, can you tell me the driver set you have for the nvme controller, I may as well do all major brands while im at it
If you can read the NVME in BIOS, it won't need the Signing like on the G751, because AMI/Aptio will have signed it for you - (as a result of adding it for native support).
There's 3 stages where the driver can get injected - Windows PE (straight after POST/BIOS), then Windows itself, then in Recovery (Winre.wim in Hidden Partition C:\Recovery)
On the newer 960, the controller changed from on board, to another chip - i can't remember what it's called - but it changed where/how Windows sees the drive and it's controller - so the 960s will be OK - but for the older people using the 950 - if Windows tries to load the 2.2 driver - it may cause the Invalid signature.
If you have the 1.4.7 (1.1) driver still in the WinSxS directory - Windows will fall back to that during one of those 3 stages. I had the invalid signature when I purged my windows driver store - some people may experience other faults, or not at all.
The IRQ for the NVME and the SATA in AHCI/RAID should occupy the highest portion of the Negative IRQ (Closest to Zero) Starting at -2. This is where the problem can manifest - where Windows will set a different affinity for one of the drives - and then you'll encounter a BSOD or something
IRQL_NOT_LESS_OR_EQUAL
This is why you can't switch out in BIOS between AHCI or RAID once Windows is Installed. The AHCI on the HM87 is categorised as IDE/SATA ACHI Controller, and the RAID is SCSI SATA RAID Controller.
I had some spare time, so I wiped the default Windows AHCI RAID disks I had, and set them up in Bios as RAID, and I have it working while Samsung Magician is installed.
The drives I had was the stock HGST 1TB 7kRPM - and they have a 60% increase in performance. I would recommend doing a Hardware Raid, if users are going to use a RAID set up - but it would only be worth while - doing so at a New Install - trying to do this conversion on an Installed Online OS, is impossible - well .... (not really I did it just before - but I had to preload and install the IaStorAC.inf, before loading the IaAHCIC.inf in the Windows PE, OS and Recovery) - but I didn't bother with recovering data from the original RAID 0, and just chose to wipe. (I'll link you to the posts with my Bench) https://rog.asus.com/forum/showthread.php?95544-G751JY-Windows-10-1703-Creators-Update-2017-Driver-L...
I haven't heard back from Samsung yet - but I'm assuming that it's not an issue for their future product line - so there's no need for them to Sign the driver for what they would now consider a Legacy device for their NVMe Range.
There's 3 stages where the driver can get injected - Windows PE (straight after POST/BIOS), then Windows itself, then in Recovery (Winre.wim in Hidden Partition C:\Recovery)
On the newer 960, the controller changed from on board, to another chip - i can't remember what it's called - but it changed where/how Windows sees the drive and it's controller - so the 960s will be OK - but for the older people using the 950 - if Windows tries to load the 2.2 driver - it may cause the Invalid signature.
If you have the 1.4.7 (1.1) driver still in the WinSxS directory - Windows will fall back to that during one of those 3 stages. I had the invalid signature when I purged my windows driver store - some people may experience other faults, or not at all.
The IRQ for the NVME and the SATA in AHCI/RAID should occupy the highest portion of the Negative IRQ (Closest to Zero) Starting at -2. This is where the problem can manifest - where Windows will set a different affinity for one of the drives - and then you'll encounter a BSOD or something
IRQL_NOT_LESS_OR_EQUAL
This is why you can't switch out in BIOS between AHCI or RAID once Windows is Installed. The AHCI on the HM87 is categorised as IDE/SATA ACHI Controller, and the RAID is SCSI SATA RAID Controller.
I had some spare time, so I wiped the default Windows AHCI RAID disks I had, and set them up in Bios as RAID, and I have it working while Samsung Magician is installed.
The drives I had was the stock HGST 1TB 7kRPM - and they have a 60% increase in performance. I would recommend doing a Hardware Raid, if users are going to use a RAID set up - but it would only be worth while - doing so at a New Install - trying to do this conversion on an Installed Online OS, is impossible - well .... (not really I did it just before - but I had to preload and install the IaStorAC.inf, before loading the IaAHCIC.inf in the Windows PE, OS and Recovery) - but I didn't bother with recovering data from the original RAID 0, and just chose to wipe. (I'll link you to the posts with my Bench) https://rog.asus.com/forum/showthread.php?95544-G751JY-Windows-10-1703-Creators-Update-2017-Driver-L...
I haven't heard back from Samsung yet - but I'm assuming that it's not an issue for their future product line - so there's no need for them to Sign the driver for what they would now consider a Legacy device for their NVMe Range.
Honestly I don’t bother with all the hoopla over Samsung drivers. We have beaten this horse to the grave and back multiple times. There is no tangible difference from running the Samsung drivers. They only work on the consumer version drives, won’t even work on an SM961 which is a Samsung Drive, just OEM. Then you have to have the raid disabled aka bios setting of AHCI or Raid which is inaccurate and should be labeled raid enabled/disabled as NVMe is not AHCI. Why must you do this? It’s a shortcoming on Samsung’s part where their software can’t see past a raid controller. It’s been this way since the 840 EVO was introduced and the same on all platforms, laptop or decktop.*
So save yourself the trouble and just use the native drivers and load IRST on install. *
So save yourself the trouble and just use the native drivers and load IRST on install. *
