• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 106
  • Last Modified:

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
0
Krister Hultberg
Asked:
Krister Hultberg
  • 4
  • 2
1 Solution
 
AmitIT ArchitectCommented:
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.
0
 
TjnoNetwork AdministratorCommented:
Did you update all security patches?
0
 
Krister HultbergAuthor Commented:
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
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Krister HultbergAuthor Commented:
we are using Infoblox DNS and then we dont tick the Register this connection’s addresses in dns, it looks possible that is what cause the BSOD.
Have to wait a while but will respond if that did the trick or not.

Regards
Krister
0
 
Krister HultbergAuthor Commented:
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
0
 
AmitIT ArchitectCommented:
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.
1
 
Krister HultbergAuthor Commented:
Trial and error
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

IT Degree with Certifications Included

Aspire to become a network administrator, network security analyst, or computer and information systems manager? Make the most of your experience as an IT professional by earning your B.S. in Network Operations and Security.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now