NUC11PAKi5とIntel 660p SSDPEKNW010T8X1で相性問題が発生し、Windows10起動後5分～10分でRebootを繰り返す。
メモリ ：W4N2666PS-8G * 2
SSD ：660p SSDPEKNW010T8X1
Winodws10 20H2をインストール →しばらく放置でRebootを繰り返す。
Windows Updateを実施 →しばらく放置でRebootを繰り返す。
メモリをノートPCで利用している16GB * 1に交換し →しばらく放置でRebootを繰り返す。
TOSHIBA KSG60ZMV256G M.2 2280 256GB(SATA)に付け替え、OS及びDriverインストール
NUC11PAKi5 Updated: 2021-02-17
1TB 660p Series NVMe
In order to get better information about your system, please download the Intel System Support Utility (SSU). Run the SSU scan and save the results. The .txt file with the results please attach to your post.
After installing Chipset Device Software, I rebooted.
After that, I installed all the other drivers as well.
The errors are an unexpected Down and a DUMP creation failure.
If a problem occurs, it will not be BSOD and will reboot suddenly.
エラー 2021/4/18 16:19 volmgr 161 ダンプ作成中のエラーのため、ダンプ ファイルの作成が失敗しました。
エラー 2021/4/18 16:19 EventLog 6008 以前のシステム シャットダウン ( 2021/04/18 16:16:12) は予期されていませんでした。
1. Since you have tested with an other RAM and other drives, probably there are not causing this rebooting problem.
2. I understand that you have 14GB I-O Data USB Drive connected to your NUC. Please disconnect this drive and see how does it work.
3. Although you mentioned that you have installed all other drivers after installing the Chipset Device Software, it looks to me that the Intel Bluetooth Driver and the Intel Wifi Driver are not updated. So, please download and install both drivers, starting with the Bluetooth Driver.
4. The correct Ethernet (LAN) Driver is also missing from your report. So please download and install it.
5. To be on the safe side, please download the Intel Graphics Driver. Then disconnect the internet. From the Device Manager, uninstall the currently installed Graphics Driver (check the "Delete device software..." option) and reboot your NUC. Finally install the previously downloaded intel Graphics Driver, reconnect the internet and reboot your NUC.
Hope this will help.
- I installed the Intel 660p to collect the Log, so the problem now reappears.
- 14GB I-O Data USB Drive was connected to get Log.
The problem still occurs without the 14GB I-O Data USB Drive.
- I have installed WiFi_22.40.0_Driver64_Win10.exe, but the Wifi driver is not updated.
I tried it several times, but it seems that I can't change it with the Windows Native Driver.
- Ethernet (LAN) Driver is included.
Intel(R) Ethernet Controller (3) I225-V
- I re-installed the Graphics Driver, but the situation remains the same.
The Memory and Storage Tool did not find any issues, but guided me to use the Intel NVMe Driver.
I installed SetupNVME.exe and updated the NVMe controller driver, but the problem persists.
I'm a little confused.
I installed the same WiFi Driver package (wifi_22.40.0_driver64_win10.exe).
However, if the SSD is different, the Wifi driver is different.
-> Intel(R) Wi-Fi 6 AX201 160MHz Netwtw08.sys 184.108.40.206
-> Intel(R) Wi-Fi 6 AX201 160MHz Netwtw10.sys 220.127.116.11
You are little confused? I'm confused too. I hope that some body from Intel will step in and help us to help us with this problem.
Any way I've compared both SSD (with the Toshiba drive and Intel drive) and I thing that the differences are as result of correct installation on the Toshiba drive. Did you installed the correct Chipset Device Software on the Intel Drive as well?
Any way the correct WiFi Driver (18.104.22.168) was extracted from the driver package on the Toshiba Drive. Please read the Release Notes.
I can see also the differences in INF file: oem28.inf on Toshiba and oem6.inf on Intel drive
In the Graphics Adapter: oem43.inf for Toshiba and oem23.inf on Intel drive.
However, the most disturbing fact is the Processor Current voltage: 1.6 volts on Toshiba installation (which is normal limit), while on Intel installation I see 7. volts (in my opinion much to high). I want however emphasize that I'm not an expert in the CPU field.
So, in the end, lets see an other input (may be from Intel) and better recheck your installation on the Intel Drive.
As far as measured by HWiNFO64, the CPU voltage is the same.
However, when I got it again with SSU, it was displayed in 1.6v and 7v.
Also, when I replaced the NVMe and SSD and rebooted, the correct WiFi driver was loaded.
This is expected to be due to system instability when NVMe is installed.
I looked at the both log files you attached above. Still there are important differences between both installations: on Intel drive and Toshib Drive. In addition to the differences in hardware - SATA vs NVMe drive, I can see that the installation on Toshiba looks better than on Intel. I'm attaching a file showing the differences. For example:
In line 8 Windows build 19042.631 for Intel vs 19042.928 for Toshiba (Toshiba is more updated)
In line 988 Processor voltage 0.7V vs 1.0V (this is probably correct value)
Most important difference you may see in line 2152 Intel Management Engine Interface: Driver Version: 2035.15.0.1807 for Intel and Driver Version: 2040.100.0.1029 on Toshiba drive. The driver on Toshiba drive is the correct driver, while the other is not. The Intel ME installer detects the Intel NUC capabilities and installs the relevant drivers. This driver can be downloaded here.
If I will you, I would reinstall Windows from scratch, and than I would install the correct drivers, starting with the Chipset Device Software and then Intel Management Engine Interface Driver. All drivers, you may download from this page.
I am very grateful for all the advice.
The difference in Windows version is that NVMe and SSD are exchanged many times and Update is performed, so it just happened that the difference occurred at the timing.
Now I have the same version.
The Intel Management Engine and WiFi Driver have repeatedly tried to install the latest versions.
However, with Intel NVMe, there was a problem that the version did not change even if the installation was completed successfully.
However, when I unplugged it several times and repeated Reset and re-installation, the update was completed successfully.
In the last few days I have re-installed Windows more than 10 times.
With Toshiba Drive, the installation was successful once, and the environment was set up.
However, even if you proceed with the same procedure, if Intel NVMe is installed, it will not proceed normally at all.
This is clearly a result of problems with NVMe.
I will install Intel NVMe on another PC and check if it can be used normally.
I installed SSDPEKNW010T8X1 on Asus X99-AII and confirmed it.
The Windows installation completed successfully and it doesn't look like there is a problem.
This issue is not a physical failure, it seems to be caused by compatibility, so I will contact Intel support.
@LeonWaksman Thank you for your suppor
I'm glad that you have verified there is no hardware problem in your Intel 660P SSD. I'm sorry, but I can't agree that there is combability problem with your NUC. In my opinion you should try again the installation. After finishing Windows installation, install the Chipset Device Software and then The Management Engine Interface Driver. Reboot your NUC and only then continue with other drivers.
I would suggest also that before starting Windows installation, update your BIOS, but this time using BIOS Recovery from the Power Button Menu method:
1. Prepare USB stick fully formatted to FAT32 (disable quick format option during format). Format your USB on Windows machine (rather than Linux or MAC).
2. Download PATGL357.0039.RECOVERY.zip and extract the PATGL357.cap file from this archive. Copy the PATGL357.cap to the root of the previously prepared USB stick. Insert this USB stick into rear USB port on your NUC. Reconnect the Power Adapter.
3. Press and hold Power Button for about 3 seconds. Count 1001, 1002, 1003. Release the Power Button. NUC should reboot into Power Button Menu (this will take about 60 seconds). You should release the Power Button before 4-sec shut down override or when the Power Button LED changes color from blue to amber.
4. Press F4 and the recovery shall start (it can take up to 30 seconds for messages to appear on the screen). When the recovery finishes, press on Power Button and hold it, until NUC switches OFF. Pull out the power cord. Remove the USB stick.
5. Replace the power cord and press Power Button to switch the computer to ON. Let the NUC fully reboot.
6. Reboot the NUC again and enter BIOS. Reset the BIOS settings to default (click on F9) and then click on F10 to save default settings and exit from BIOS.
Hope this will help
When you ran the Intel Memory and Storage tool, did you see if there was any firmware update for the 660p SSD? Intel has been update a bunch of their SSDs lately.
Also, When you are installing Windows, are you manually installing the drivers before connecting to the internet or are you letting Windows Update do the driver install? If it is the latter, try installing drivers without connecting to the internet first. Sometimes Windows Update will install drivers out of order and cause issues.
I installed the Storage Tool and confirmed that the 660p Firmware is up to date.
After installing Windows, I also tried Driver Install with the network disconnected. However, I also confirmed that the driver is not updated even after installation and that an unexpected reboot occurs.
I can understand the problem caused by applying drivers in random order.
However, if you install Toshiba SSD, you can install Driver without any problem, and unexpected reboot does not occur.
Thank you for posting on the Intel® communities.
We understand you have opened a chat with us and we will continue to help you through that channel now. We will therefore close this community case from our end. Thank you.
Intel Customer Support Technician
NUC: intel NUC11PAKi5
MEMORY: G.Skill F4-3200C18D-32GRS
SSD: SAMSUNG 980 PRO 1TB PCIe 4.0 NVMe M.2
OS: Windows 10 Pro 20H2
ドライバと BIOS は共に DSA の最新版を使用しています。
アプリケーションは OS のみインストールした状態ですが、突然フリーズし再起動することがあります。
あと LED の表示が BIOS の設定通りになりません。（NUC Software Studio が自動インストールされてからおかしな動作になりました。しかもアンインストールしても正常に戻りません。）
メモリ診断、intel の CPU チェック、SSD のツールでのチェックをかけましたが、ハードウェアのエラーは見つかりませんでした。
何度か OS を再クリーンインストールしましたが、インストール時にエラーが起こらないので BIOS かドライバが原因ではないかと思っています。