Krister Hultberg
asked on
Exchange 2016 BSOD
Hi all Experts!
For about 3 weeks ago we installed 3 new Cisco servers and Exchange 2016 CU7. C: is local disk and the rest where the databases are are on SAN. OS is Windows server 2016
After the SAN disk was configured/connected to the servers they started to BSOD. So far i have seen ntoskrnl.exe and msexchnageworker in the dump files.
Have googled arround for some days now but cant find any good answers.
Anybody here that can advice?
Regards
Krister
For about 3 weeks ago we installed 3 new Cisco servers and Exchange 2016 CU7. C: is local disk and the rest where the databases are are on SAN. OS is Windows server 2016
After the SAN disk was configured/connected to the servers they started to BSOD. So far i have seen ntoskrnl.exe and msexchnageworker in the dump files.
Have googled arround for some days now but cant find any good answers.
Anybody here that can advice?
Regards
Krister
Amit
I advise you to open case with MS. You might need to run full memory dump to find the root cause. I suspect drive issue.
Did you update all security patches?
ASKER
Hi!
Also suspect driver.
The latest patch, 2017-12 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4053579), is not applied but it is in the loop.
Regards
Krister
Also suspect driver.
The latest patch, 2017-12 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4053579), is not applied but it is in the loop.
Regards
Krister
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
It now has been 24h with no BSOD so it seems that Register this connection’s addresses in dns tick box did the thing.
I am a litle bit pusseld why it did it but there are many things in Exchange that I dont have controll of YET.
Thanks for all input!
And if any has an explanation of why please write it in.
Regards
Krister
I am a litle bit pusseld why it did it but there are many things in Exchange that I dont have controll of YET.
Thanks for all input!
And if any has an explanation of why please write it in.
Regards
Krister
I am surprised for the BSOD fix you mentioned. I still doubt, registering DNS could cause or fix BSOD. I would advise you to enabled full memory dump for this server. In case it comes again, you have dump to analyze it.
ASKER
Trial and error