- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- BSOD on DL385 Gen10 after updating from Service Pa...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2023 02:36 PM - last edited on тАО07-25-2023 10:21 PM by support_s
тАО07-25-2023 02:36 PM - last edited on тАО07-25-2023 10:21 PM by support_s
BSOD on DL385 Gen10 after updating from Service Pack ISO version 2023.03.00.00
Hi,
I recently updated a DL385 running Server 2019 as Hyper-V cluster node using the Gen10 support ISO version 2023.03.00.00.
The update process seemed to work fine, but after a reboot, the server did not start anymore. Its just running into a BSOD showing "system thread exception not handled".
I checked support area for new firmware updates released after the ISO and updated them using ILO, but the problem was not solved.
I tried reinstalling the OS using Intelligent Provisioning, but after the first login into Windows and the scripts installing the drivers and rebooting the server, the BSOD came back.
I installed the server again from the Server 2019 ISO instead of using intelligent Provisioning and it worked without having drivers installed. As soon as I install the drivers and reboot, again BSOD.
Any ideas? Thanks in advance
Embedded Video Controller 02. Mai
HPE Eth 10Gb 2p 535FLR-T Adptr 225.1.095000
HPE Eth 10Gb 2p 535T Adptr 225.1.095000
HPE Ethernet 1Gb 4-port 331i Adapter - NIC 20.24.41
HPE Smart Array P408i-a SR Gen10 Mai 61
HPE Smart Storage Energy Pack 1 Firmware 0.70
HPE SN1100Q 16Gb 2P FC HBA 02.00.01
iLO 5 2.95 Jul 19 2023
Intelligent Platform Abstraction Data 16.2.0 Build 26
Intelligent Provisioning 3.86.5
Power Management Controller Firmware 01.01.2000
Power Management Controller FW Bootloader 01. Jan
Redundant System ROM A40 v2.68 (02/02/2023)
System Programmable Logic Device 0x10
System ROM A40 v2.72 (04/20/2023)
- Tags:
- Port
- Prolaint server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2023 09:42 PM
тАО07-25-2023 09:42 PM
Re: BSOD on DL385 Gen10 after updating from Service Pack ISO version 2023.03.00.00
Hi,
During the BSOD, does it specify any driver file name or a Code?
Here is an example, but its an old advisory.
Thank You!
I work with HPE but opinions expressed here are mine.
HPE Tech Tips videos on How To and Troubleshooting topics
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2023 05:42 AM - last edited on тАО07-26-2023 08:07 PM by Sunitha_Mod
тАО07-26-2023 05:42 AM - last edited on тАО07-26-2023 08:07 PM by Sunitha_Mod
Re: BSOD on DL385 Gen10 after updating from Service Pack ISO version 2023.03.00.00
Hi @Suman_1978 ,
thanks for your reply.
I already found the article you linked, when searching the knowledgebase.
I checked the Gen10 Service Pack ISO for this driver. It includes version 7.13.206.0(B), which is newer then the one mentioned in the article, so I don't think that this is the problem.
I also tried disabling the network adapters in the bios, but this didn't change anything.
Unfortunately it does not show any specific code or driver in the BSOD screen.
I tried enableing boot logging, but when I check the windows directory using the recovery console, I can't find ntbtlog.txt. Also debug mode and safe mode end up in BSOD.
One strange thing: around 50% of the time, when starting the server, it stops at the "hpe smart memory initialization" stage. Resetting the server via ILO usually "resolves" this problem.
I did a hardware diagnosis, but it did not show any errors. I also made a memory test over night, but it won't show any errors either...
I ordered some new memory modules and will try to replace them one by one and check if the problem persists.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2023 05:51 AM
тАО07-27-2023 05:51 AM
Betreff: BSOD on DL385 Gen10 after updating from Service Pack ISO version 2023.03.00.00
Fyi: I installed Server 2019 again and installed the drivers from an older driver ISO from 2021 (P45316_001_gen10spp-2021.10.0-SPP2021100.2021_1012.13).
This was succesfully. After that I installed the drivers from last years ISO (P52575_001_gen10spp-2022.03.0-SPP2022030.2022_0326.24) and it's still running fine.
At the moment I don't dare to install the new drivers again, but maybe I'll try it again after replacing RAM modules this weekend.