Spesifikasi Motherboard ASRock H370 Fatal1ty

ASRock akhirnya merilis motherboard berbasis Chipset Intel H370 untuk brand Fatal1ty yang mendukung Processor Intel Coffee Lake. ASRock H370 Fatal1ty ditujukan bagi para gamer dan overclocker guna mendapatkan performa seperti yang diinginkan. Dibangun dengan CPU Power 10 phase dan Memory Power 2 phase akan diperoleh stabilitas pada board ini.

ASRock H370 Fatal1ty dibekali 4 slot DIMM memory yang support sistem dual channel DDR4-2666 dan memiliki kemampuan kapasitas hingga 64 GB. Slot ekspansi menampilkan 2 slot PCI Express 3.0 x16. Sedangkan bagian storage terdapat 6 port SATA 6 Gbps dan 2 port M.2. Motherboard yang hadir dengan form factor ATX ini dipersenjatai dengan networking berupa Intel I219V.

Berikut spesifikasi lengkap motherboard ASRock H370 Fatal1ty :

CPU Support : Supports 8th Generation Intel Core Processors (Socket 1151, up to 95 W)
Power Design : CPU Power: 10 phase, Memory Power : 2 phase (single-phase control)
Chipset : Intel H370
Integrated Graphics : Depends on installed CPU
Memory : 4x DIMM, Support Dual Channel up to DDR4-2666/Max. 64 GB
BIOS : 128 MB AMI UEFI BIOS
Expansion Slots : 2x PCIe 3.0 x16 slots (single at x16 (PCIE2); dual at x16 (PCIE2) / x4 (PCIE4)), 4x PCIe 3.0 x1 slot
Storage : 6x SATA 6 Gb/s port (Intel H370), 2x M.2 port (2230/2242/2260/2280 devices (22110 on lower slot), PCIe 3.0 x4 and SATA 6 Gb/s), 1x Wi-Fi M.2 port
Networking : 1x Intel I219V
Rear Ports : 1x PS/2 Combo Port, 2x Antenna ports, 1x LAN (RJ45) ports, 1x USB 3.1 Gen2 Type-A ports (10 Gb/s), 1x USB 3.1 Gen1 Type-A ports, 2x USB 2.0 Type-A ports, 1x D-Sub Port, 1x HDMI port, 1x DisplayPort 1.2, 5x Audio jacks, 1x Optical SPDIF Out Port,
Audio : Realtek ALC1220 Audio Codec
Fan Headers : 5x 4-pin
Form Factor : ATX Form Factor: 12.0 inch x 9.6 inch, 30.5 cm x 24.4 cm
Exclusive Features : ASRock USB 3.1 Gen2, ASRock Super Alloy, Premium 50A Power Choke, Nichicon 12K Black Caps (100% Japan-made high quality conductive polymer capacitors), I/O Armor, Matte Black PCB, High Density Glass Fabric PCB, ASRock Polychrome RGB, ASRock Ultra M.2 (PCIe Gen3 x4 & SATA3), ASRock Full Spike Protection (for all USB, Audio, LAN Ports), ASRock APP Shop, ASRock F-Stream, ASRock XFast LAN

Cara Paksa Masuk BIOS Semua Merek Laptop

Beberapa kejadian sering terjadi pada laptop dimana kita kesulitan untuk masuk (akses) BIOS. Mungkin BIOS terpassword dan kita lupa kata kuncinya, seperti laptop ASUS yang harus direset passwordnya. Kali ini pengalaman datang kembali saat selesai instal laptop dengan Windows 7 kemudian melakukan aktivasi dengan aplikasi pihak ketiga, ternyata setelah proses restart laptop hanya diam seribu bahasa dan hanya tampil logo vendor.

Terpaksa laptop tersebut harus dibongkar untuk melakukan clear CMOS agar kondisi BIOS kembali seperti semula atau default. Sebetulnya untuk masuk ke BIOS laptop yang mengalami problem dapat kita pakai trik berikut :

1. Bongkar casing laptop dengan hati-hati. Perhatikan jumlah sekrupnya, jangan
    sampai setelah mau pasang ternyata komponen ini kurang atau malah sisa.

2. Lepas Hard Disk kemudian hidupkan laptop, maka BIOS akan muncul dan
    segera lakukan setting ke default dengan menekan tombol F9.

3. Simpan pengaturan BIOS dengan menekan tombol F10 (save and restart).

4. Setelah restart, matikan laptop kemudian pasang kembali Hard Disk. Jangan
    lupa pasang sekrupnya.

5. Hidupkan lagi laptop maka anda akan bisa mengakses BIOS dengan menekan
    tombol F2 atau Delete sesuai dengan merk laptop.

Demikianlah cara mudah untuk memaksa laptop masuk ke BIOS. Cara ini dapat anda gunakan pada semua merk laptop. Selain melepas Hard Disk sebetulnya anda bisa juga hanya melepas modul RAM, hanya saja ada beberapa model laptop yang memasang RAM secara permanen di motherboard sehingga tidak mungkin kita melepasnya. Semoga bermanfaat.

Download IDM 6.31 Build 1 dan Patch

Internet Download Manager kembali merilis aplikasi terbaru IDM 6.31 Build 1 untuk membantu anda dalam mengunduh konten di jaringan internet secara cepat. IDM 6.31 Build 1 membawa beberapa perubahan mendasar, khususnya permasalahan kompabilitas dengan sistem operasi Windows 10.

Berikut fitur update IDM 6.31 Build 1 :

- Added support of Unicode only languages to latest Windows 10
- Fixed compatibility problems with foreign language translations when using
  "Use Unicode UTF-8 for worldwide language support" feature of Windows 10
- Fixed bugs

Pada kesempatan ini juga ada Patch untuk menjadikan IDM 6.31 Full Version, tersedia untuk versi 32-bit maupun 64-bit.

Download :
- IDM 6.31 Build 1
- Patch IDM 6.31 Build 1

Update Untuk Windows 10 Build yang Lama

Microsoft merilis update untuk Windows 10 Build yang lama, bukan untuk Windows 10 Build 1803. Update ini ditujukan bagi Windows 10 Anniversary Update (Build 1670), Creators Update (Build 1703) dan Fall Creators Update (Build 1709). Update ini dapat anda peroleh melalui Windows Update.

Berikut ini adalah update yang bisa anda dapatkan :

Fall Creators Update (build 16299.522)

• Addresses an application performance degradation issue in operating system functions. This degradation locks and frees large blocks of memory (such as VirtualLock and Heapfree) after installing KB4056892 and superseding fixes
• Addresses performance regression in App-V that slows many actions in Windows 10
• Adds a new MDM Policy, "DisallowCloudNotification", for enterprises to turn off Windows Notification traffic
• Changes the music metadata service provider used by Windows Media Player
• Addresses an issue with the placement of text symbols in right-to-left languages
• Addresses an issue with editing web password fields using a touch keyboard
• Adds a Group Policy that provides the ability to hide recently added apps from the Start menu
• Updates the Segoe UI Emoji font to use a water gun to represent a pistol emoji
• Addresses a reliability issue with resuming from hibernation
• Addresses an issue where SmartHeap doesn't work with UCRT
• Addresses an issue to ensure that Windows Defender Application Guard endpoints comply with regional policies
• Increases the user account minimum password length in Group Policy from 14 to 20 characters
• Addresses an issue that causes sporadic authentication issues when using Windows Authentication Manager
• Addresses an issue where an Azure Active Directory account domain change prevents customers from logging on
• Addresses an issue that displays unnecessary "Credential Required" and "Do you want to allow the app to access your private key?" messages. This issue occurs when running a Universal Windows Platform (UWP) application
• Addresses an issue that causes the LSASS service to become unresponsive, and the system needs to be restarted to recover
• Addresses an issue where client applications running in a container image don't conform to the dynamic port range
• Adds a new registry key that prevents access to the Internet using WWAN if a non-routable ethernet is connected
To use this new registry key, add IgnoreNonRoutableEthernet" (Dword) on HKEY_LOCAL_MACHINE\Software\Microsoft\Wcmsvc using regedit, and set it to 1
• Adds a new registry key that allows customers to control access to the Internet using WWAN without using the default connection manager. To use this new registry key, fMinimizeConnections" (Dword) on HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\WcmSvc\Local using regedit, and set it to 0
• Addresses an issue that prevented ISO/DVD mounts and eject from working using VM settings and Powershell because of menu transition issues in VMConnect
• Addresses an issue where restarting the Hyper-V host with Hyper-V Replica (HVR) enabled could cause replication to stop. It may also require a manual restart to resume the replication from a suspended state. The replication state should be normal after the Hyper-V host/VMMS is restarted
• Addresses an issue that might cause the Mitigation Options Group Policy client-side extension to fail during GPO processing. The possible errors are "Windows failed to apply the MitigationOptions settings. MitigationOptions settings might have its own log file" or "ProcessGPOList: Extension MitigationOptions returned 0xea." This issue occurs when Mitigation Options have been defined using Group Policy, the Windows Defender Security Center, or the PowerShell Set-ProcessMitigation cmdlet
• Addresses an issue that causes a connection failure when a Remote Desktop connection doesn't read the bypass list for a proxy that has multiple entries
• Addresses an issue where Windows Defender Security Center and the Firewall Pillar app stop working when opened. This is caused by a race condition that occurs if third-party antivirus software has been installed

Creators Update (build 15063.1182)

• Addresses performance regression in App-V that slows many actions in Windows 10
• Addresses an issue with the soft keyboard's input modes in WPF applications
• Addresses an issue where SmartHeap doesn't work with UCRT
• Addresses an issue that causes sporadic authentication issues when using Windows Authentication Manager
• Addresses an issue that displays unnecessary "Credential Required" and "Do you want to allow the app to access your private key?" messages. This issue occurs when running a Universal Windows Platform (UWP) application
• Addresses an issue that causes the LSASS service to become unresponsive, and the system must be restarted to recover
• Addresses an issue where client applications running in a container image don't conform to the dynamic port range
• Addresses an issue in MSXML 3.0 that causes the body of the request to be empty when the IXMLHTTPRequest send() method is called. This issue occurs when URL redirection causes the send() method to be invoked a second time with a different URL
• Adds a new MDM Policy "DisallowCloudNotification" for enterprises to turn off Windows Notification traffic

Anniversary Update (build 14393.2339)

• Addresses a performance regression in App-V that slows many actions in Windows 10
• Addresses an issue with the placement of text symbols in right-to-left languages
• Addresses a system crash (Stop 3B) in win32kfull.sys when cancelling journal hook operations or disconnecting a remote session
• Addresses an unexpected logon termination issue with a third-party Remote Desktop Service (RDS) application
• Addresses an issue where customers had to press Ctrl+Alt+Delete twice to exit assigned access mode when autologon was enabled
• Addresses an issue that causes the full-screen Start menu to stop working when logging in
• Addresses an issue that causes the system to log negative events for valid binaries that should be trusted. This issue occurs when running the Windows Defender Application Control (Device Guard) in audit mode
• Addresses an issue that causes sporadic authentication issues when using Windows Authentication Manager
• Addresses an issue that displays unnecessary "Credential Required" and "Do you want to allow the app to access your private key?" messages. This issue occurs when running a Universal Windows Platform (UWP) application
• Addresses an issue that causes the LSASS service to become unresponsive, and the system needs to be restarted to recover
• Addresses an issue where client applications running in a container image don't conform to the dynamic port range
• Addresses a memory leak in RtlDosPathNameToRelativeNtPathName. The leak occurs when you turn on LongPathsEnabled in the registry and you call CreateFile or any other name-based Win32 API using a path that is longer than 260 characters
• Addresses an issue where chkdsk doesn't update the file size and the valid data length when it needs to shrink the Master File Table (MFT) attribute list. This prevents the mounting of the next volume because NTFS considers the volume damaged, and rerunning chkdsk won't fix this
• Addresses an issue that causes poor CPU performance when Virtual Switch Ports leaked during a machine's live migration from one host to another
• Addresses an issue where certain VMs with dynamic and startup RAM set at 32 GB restart with a blue screen
The error that appears is "PFN_List_Corrupt 0x4e"
• Addresses a Windows 2016 Hyper-V environment issue in which creating a VM on a Server Message Block (SMB) 3.0 share may cause automatic registration to Hyper-V Manager to fail
This issue occurs when performing a backup for restoration to an alternate location. The error is "The Hyper-V Virtual Machine Management service encountered an unexpected error: The file or directory is corrupted and unreadable (0x80070570)"
• Addresses a Windows Server 2016 Hyper-V host and guest migration issue in which a 2016 SQL file stream restoration fails with an "Event ID 11" error. The issue also causes the SQL process to stop working
• Addresses an issue in which restarting the Hyper-V host with Hyper-V Replica (HVR) enabled could cause replication to stop
It may also require a manual restart to "resume the replication" from a suspended state. The replication state should be normal after the Hyper-V host/VMMS is restarted
• Addresses an issue that sometimes prevents users from starting Microsoft Outlook after logging on to a Remote Desktop session
• Addresses an issue in dfsutil
exe that occurs when exporting a DFS namespace as an XML file. The issue occurs when the namespace contains a link with a target that points to a shared folder that has an "&" character in its name. As a result, the generated XML does not correctly escape the "&" character, and dfsutil.exe cannot export the namespace
• Addresses an issue that causes a connection failure when a Remote Desktop connection doesn't read the bypass list for a proxy that has multiple entries
• Addresses an issue that prevents VMs in an RD Pooled Desktop Collection from being recreated if the VMs are Gen2
• Addresses an issue in a Remote Desktop VDI deployment that prevents a mounted UPD from disconnecting, which results in the creation of temp files
• Addresses an issue in which the user interface for Windows Server 2016 Server Manager > File and Storage services displays the NVDIMM-N (memory) bus type as UNKNOWN
• Addresses an issue in which the system event log receives many error events for IPRIP 29031 when the system receives the ERROR_OBJECT_ALREADY_EXISTS error
• Addresses an issue that occurs when running Test-SRTopology between two clusters and their CSV paths. You may receive the error "Could not find file"

Spesifikasi GeForce GTX 1170 Preliminary

NVIDIA pada tahun ini menyiapkan dua buah VGA Card GeForce GTX 11 Series yaitu GeForce GTX 1170 Preliminary dan GeForce GTX 1180 Founders Editions. Kedua kartu grafis kelas premium dibangun berdasar arsitektur terbaru Turing dengan teknologi litografi 12nm FinFET sebagai pengganti arsitektur sebelumnya yakni Pascal.

NVIDIA GeForce GTX 1170 Preliminary dibekali 2688 CUDA Core yang dikemas dalam die berukuran 400 mm², mampu berkerja pada frekuensi dasar 1500 MHz dan dapat digenjot hingga 1800 MHz melalui fitur Boost. Kekuatan GTX 1170 didukung memory GDDR6 dengan kapasitas antara 8 sampai 16 GB, juga kecepatan memory mencapai 12 Gbps melalui bandwith 384 GBps.

Berikut spesifikasi lengkap GeForce GTX 1170 Preliminary :
- Architecture : Turing
- Lithography : 12nm FinFET
- GPU : GT104
- Die Size : ~400mm²
- CUDA Cores : 2688
- TMUs : 168
- ROPs : 64
- Core Clock : ~1500MHz
- Boost Clock : ~1800MHz
- FP32 Performance : ~9.75 TFLOPS
- Memory Interface : 256-bit
- Memory : 8-16 GB GDDR6
- Memory Speed : 12Gbps
- Memory Bandwidth : 384GB/s
- TDP : 140-160W
- Launch : Q3 (August) 2018
- Launch MSRP : ~$499