Windows 2008 unexpected shutdown after adding DFS Folder.

We're experiencing an odd issue with our DFS servers, whereby, both servers unexpectedly reboot after adding a new DFS folder target/replication group.  Two servers, both running Windows 2008R2 sp1 with most recent updates.  Updating the firmware (BIOS, Chipset, SCSI...etc) on both servers did not resolve the issue.  Checked resources (disk space, cpu, ram) and everything appears ok. There are approximately 30 existing folder targets which have been working fine.

Checked minidump file, shows Unexpected_Kernal_Mode_Trap, with a code of 0x7F and a reference to ntoskrnl.exe.  Installed a potential Hotfix from Microsoft, KB2885978, which references the aforementioned stop error.  After a reboot, the issue still persists when attempting to add a new folder target.  Wondering if anyone else has ever experienced this issue.
KemimolIT EngineerAsked:
Who is Participating?
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.

MaheshArchitectCommented:
This issue is not related to DFS, DFS has nothing to do with unexpected reboot

Please check physical Memory for issues
Also sometimes SCSI / RAID driver upgrade creates new issues instead of resolving issues
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
To me this seems to be either RAID/SCSI drivers or issue with one of the updates.
KemimolIT EngineerAuthor Commented:
Issue was not hardware related.  Opened ticket with Microsoft and worked several days on the issue.  Ultimately ended up changing the default time-out value on the Service Control Manager and rebooting.  Both servers have been up for a few days without issue.  Time will tell if this is a permanent fix.

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
Become a CompTIA Certified Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

KemimolIT EngineerAuthor Commented:
Provided answers were short and did not provide any insight as to the actual solution.
MaheshArchitectCommented:
If you could just tell us how you alter service control manager time out value please
KemimolIT EngineerAuthor Commented:
We edited the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control.
Modified the existing WaitToKillService value from 20000 to 60000.
MaheshArchitectCommented:
ok
Thanks
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
Windows Server 2008

From novice to tech pro — start learning today.