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
Krister HultbergAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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
DP230Network 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
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.