- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi guys,
We have a NUC8I7BEH and we are having the issue that the Intel Iris Plus Graphics 655 keeps crashing all the time.
Right now I am just connected with Microsoft RDP and it has crashed, so we do nothing fancy.
There is only Windows 10 Pro x64 installed, nothing else except the Intel drivers.
Device Manager Reports
Windows has stopped this device because it has reported problems. (Code 43)
Intel Driver Tool says we have the latest drivers installed, right now it is 24.20.100.6286
This is a reoccuring issue, anyone having the same issue or a solution?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello,
1. Please check if the Bios and Drivers version corresponds to the versions listed in Intel Download site: https://downloadcenter.intel.com/product/126148/Intel-NUC-Kit-NUC8i5BEH Downloads for Intel® NUC Kit NUC8i5BEH . In some cases the Intel Driver Tool have some problems. Please uninstall the graphic driver and install the driver from Intel site: https://downloadcenter.intel.com/download/28233/Intel-HD-Graphics-Driver-for-Windows-10-for-Intel-NU... Download Intel® HD Graphics Driver for Windows® 10 for Intel® NUC
2. If still you have crashes, please download Intel System Support Utility: https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows- Download Intel® System Support Utility for Windows* , run system Scan and attach the .txt file with the results to your post.
3. Some time, the crashes are caused by failed/uncompatible memory module. Try to work with one module at time.
Leon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi @sschm13
I've got the same box and the same issue, Did installing these drivers (6519?) resolve the issue ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Actually a few days after I posted this I found a new driver on the Intel Website, the version number was just slightly higher and with the new one it worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I'd appreciate your help - could you tell me exactly what version you are using e.g.
26.20.100.6912 (Latest)
26.20.100.6890
26.20.100.6861
26.20.100.6708
26.20.100.6709
25.20.100.6618
25.20.100.6577
25.20.100.6471
25.20.100.6444
25.20.100.6519
and has it worked well for some time that that version ?
I've tried a bunch of them and things did seem to settle down after I disabled WiFi / Bluetooth in Device Manager with 6519. But I upgraded to 6912 a few days ago (became the recommended version in IDSA) and instability is back.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Right now I am using 25.20.100.6444 with Intel Audio Driver 10.26.0.3
WiFi is turned off as I use an ethernet cable, Bluetooth is on.
I use it as an HTPC with MediaPortal so it uses the graphics card for hardware decoding and showing the UI, so far no more crashes of the graphics driver.
Hope you can fix it!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Many thanks for you assistance - I shall try that version next.!
Forgot to ask, are you on the original 51 BIOS or have you upgraded? My problems started when I upgraded to Windows 1903 and as a prepartory step I ran IDSA and it upgraded loads of things including the BIOS, which appears to be locked to 71 - I've tried everything to downgrade it to 51 using the various methods on the Intel website (including jumper method) to see if that was causing my problems, but it appears locked (probably due to the several "bad" versions released in the interim.
I've broken the cardinal rule of "if it ain't broke, don't fix it" :-(

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page