Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About Monstieur

  • Title

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. AFAIK professional displays including Dolby's own reference monitors do not support Dolby Vision. They follow PQ strictly with hard clipping. The mastering workstation must perform all processing including Dolby Vision tone mapping for preview, Dolby Vision metadata generation for export, and outputs a plain HDR10 PQ signal to the reference monitor. The operating system is aware only of a HDR10 display. Dolby Vision on the consumer side is to tone map Dolby Vision exported content to an unknown display. I believe a license is required on the source device just to bit stream Dolby V
  2. It works only on Dolby Vision licensed pre-built systems.
  3. With NVMe ATA Security / Class 0, the entire physical disk is locked, similar to old school HDD ATA passwords. The bootloader will not be readable at all unless the BIOS supports NVMe ATA Security, detects that the disk is locked, and prompts you for the password. TCG Opal 2.0 supports locking individual address ranges (effectively partitions) on the disk. It can leave an unlocked partition at the beginning to hold the bootloader / PBA like SEDutil or BitLocker, while locking the OS and data partitions. Thus the BIOS can boot into the PBA, which unlocks and chain loads the OS parti
  4. Those are drives which support NVMe ATA Security / Class 0. They are bootable only in certain laptops which have BIOS support for NVMe ATA Security. The password prompt comes from the BIOS. There are Linux tools to set the NVMe ATA password and lock / unlock the drive on any PC, but you can't boot from it without BIOS support. Some drives like the Intel Optane 900p claim AES support because the data is encrypted at rest on the chips, which is completely useless. They do not support NVMe ATA Security commands to actually set a password and protect the key. Encryption with a factory
  5. That's right. EFI_STORAGE_SECURITY_COMMAND_PROTOCOL is required to boot from a BitLocker hardware encrypted drive. BitLocker hardware encryption is essentially dead. I don't think SEDutil has this requirement.
  6. Only some laptop UEFIs support the NVMe ATA Security / Class 0 password. This method isn't recommended, as once the password is set, it may be impossible to remove without the same model motherboard or specialized hardware, rendering the drive unusable if the PC fails, even if you know the password. TCG Opal 2.0 drives must be managed by pre-boot authentication software like SEDutil / BitLocker. The method of authentication such as password / TPM is entirely up to the PBA software. The drive itself does not "support" passwords or any particular means of authentication.
  7. Drives with TCG Opal 2.0 can be used with SEDutil. Drives that also have IEEE 1667 can be used with BitLocker. Windows no longer supports hardware BitLocker by default as most drives are insecure - you have to force enable it even if the drive is supported. Software encryption is now the recommended configuration, just like Apple never bothered with SED support in FileVault 2. You can't trust random manufacturers with this stuff.
  8. Your OS is probably installed in legacy BIOS mode. You need to convert it to boot from UEFI (CSM off). The Windows disk should appear and be bootable after conversion to GPT. https://www.intel.com/content/www/us/en/support/articles/000024558/memory-and-storage/intel-optane-memory.html With CSM on, the UEFI is probably trying to initialize the new SSD in legacy mode. It's possible this isn't working correctly and it's causing the freezing / corruption. Either way, this problem won't occur with CSM off. The Windows drive not appearing with CSM off is a different problem - the di
  9. It's probably Disable CSM in the UEFI. If that doesn't work, try modding the BIOS to add NVMe boot support. It shouldn't be required, but correct detection of the NVMe drive in the UEFI may resolve the freezing issue. https://www.win-raid.com/t871f50-Guide-How-to-get-full-NVMe-support-for-all-Systems-with-an-AMI-UEFI-BIOS.html It could also be the adapter - try a different one.
  10. Single drives will work. It may not be bootable if the UEFI doesn't support NVMe - all X79 and some X99 board's don't. However, they can be easily BIOS modded to add NVMe boot support.
  11. I have a 10900X at 5 GHz with an Optane 900P 280 GB. Software BitLocker reduces 4K Q1T1 read & write down from 300 MiB/s & 275 MiB/s to 100 MiB/s & 80 MiB/s. 4K Q32T16 write is reduced from 2200 MiB/s to 1700 MiB/s. Other values are about the same. IIRC latency did not increase with software BitLocker - only throughput reduced. The AES throughput of the CPU seems to be the bottleneck. The consume Optane drives don't support hardware BitLocker.
  12. Reference, Founders, Strix, and maybe FTW3 will be the most popular blocks going by the 20-series cards.
  13. What is the version number on the label? Older v4.3 kits had B-Die. When newer versions without B-Die proliferated in the market, the Z part numbers had the highest probability of being v4.3 with B-Die, as they were designed for 1st gen Ryzen which had poor memory compatibility.
  14. I wouldn't even bother OCing non-B-Die. It's too much effort for a small increase over XMP.
  15. I sold mine and got the T-Force XTREEM DDR4 4500 MT/s kits. They are top tier B-Die at bottom barrel prices. Mine do 4000 C16 at 1.45 V, and 4000 C15 at 1.5 V. You should be able to get really good timings at 3600 MT/s.