Server Reboot Issue

Hello Experts,

We have Dell R610 servers in our network, last few days i am getting unexpected server reboot issue, i try to find issue but unable to find out.
please help me out i am attaching 2 servers log files.

OS - Windows Server 2008 R2 Stranded SP1
121418-13478-01.dmp
121418-16426-01.dmp
LVL 1
Rajat SehgalFounder Enhance TechnologyAsked:
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.

Fethi ABASSIWindows system administratorCommented:
hello,
could you please check in Event Time Viewer the boot time
systeminfo | find "System Boot Time"
and try to find this time if you found something strange
link how to debugging dump file:
https://www.sevenforums.com/crash-lockup-debug-how/26584-configuring-debugging-tools.html
KimputerIT ManagerCommented:
You have 2 different dump files with 2 different reasons for now. More dump files are appreciated.
But for now, when it's different every time, it's usually not a driver issue, but more in the direction of PSU/mobo/mem
If possible do a memtest for a whole day.
If that's not possible due to work load, try half the memory first (physically remove half the DIMMs). If same happens, replace the half with the other half. If still happening, you already ruled out the memory as a problem causer.
After that, if possible, replace PSU. The last step is of  course the most difficult part, replace mobo.
andyalderSaggar maker's framemakerCommented:
Check the server event log on the system board via iDRAC or OMSA, that will identify most hardware errors.

https://www.dell.com/support/article/uk/en/ukdhs1/sln305828/poweredge-how-to-generate-servers-logs-with-the-idrac-?lang=en
DrDave242Senior Support EngineerCommented:
Those dump files show two different stopcodes, but they appear to be related. The likely culprits, according to WinDbg, are srv.sys and srvnet.sys, both of which are built-in Windows drivers.

Is this server up to date in terms of Windows updates? I suspect it's not, because both of those files are dated Nov 20, 2010. I know the OS is 2008 R2, but I'm almost certain there are more recent versions of srv.sys and srvnet.sys available via updates.

Installing all available updates would be the first thing I'd do. Well, check that - I'd back everything up first, then install all updates.

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
Rajat SehgalFounder Enhance TechnologyAuthor Commented:
Thanks to all for you valuable suggestion.
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
Server Hardware

From novice to tech pro — start learning today.