December 1, 2013 at 1:23 pm
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?
Thanks much
December 1, 2013 at 6:04 pm
sqlfriends (12/1/2013)
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?
Thanks much
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.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2013 at 3:33 pm
Thanks much, Jeff.
Could you tell me where you can see it could be issue with memory module 3 or 4 in the attachment?
Oh, I see - I accidently highligted in blue, I actually meant the newest two records on the top which happend last week.
The blue highted is something happened in 2011.
December 4, 2013 at 2:06 am
sqlfriends (12/3/2013)
Thanks much, Jeff.Could you tell me where you can see it could be issue with memory module 3 or 4 in the attachment?
Oh, I see - I accidently highligted in blue, I actually meant the newest two records on the top which happend last week.
The blue highted is something happened in 2011.
Crud. Sorry about that. When I blew it up big enough to read, I couldn't see the dates anymore and didn't realize that I was looking at old entries. My apologies.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2013 at 9:46 am
Thanks,
So for the first top 2 records, can we see it is a hardware problem or not?
December 4, 2013 at 4:19 pm
sqlfriends (12/4/2013)
Thanks,So for the first top 2 records, can we see it is a hardware problem or not?
I don't know the answer to that question. I'm thinking a call to MS might be the right thing to do.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2013 at 4:32 pm
Thanks, will do
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply