We have a windows 2008 server sp2 that hosts a SQl server 2008.
Recently the server has an automatically restart at a night and a weekend.
In the HP Proliant Integrated Management Log viewer I can see the
Operating system failure bug check 0x00000050, see detail in the attachment screenshot.
I assume this is a blue screen restart, it crashed then it restart itself and run fine after that.
What could be the reason that crashes and how can we dignostic it and fix it?
It's telling you exactly what the problem is and the Operating System errors are probably just a symptom of a much larger problem. Either memory module 3 or memory module 4 or both have a serious problem. It could be a failure of one of the chips or it could be that they're just not seated properly. I'd try the reseating thing (take them all the way out and then put them back), fire the system up, and see if you get the same critical errors. If you do, you're going to need to replace some memory modules. Depending on the warranty that HP provided you (or not), it might be fully covered and HP might replace the modules for free.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs