Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My windows server crashed overnight last night with a BSOD. I managed to get a log of the dump file which is here, it appears as if google chrome was the culprit, was wondering if anyone with more knowledge than me could dig out any more from this dump:

share|improve this question

closed as not a real question by Evan Anderson, Jim B, TomTom, MDMarra, mfinni Jul 20 '12 at 20:23

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

I'm voting to close on this one because it's not a real question (and, possibly, not constructive). If this were edited to talk about the crash dump analysis process I could see it being useful. Otherwise I think it's just a posting asking somebody to perform crash dump analysis pro bono. – Evan Anderson Jul 20 '12 at 12:06
Chrome On a server?? – MDMarra Jul 20 '12 at 12:14
well the site is called ServerFault...i have a fault on my server...i don't see the problem? – Paul Hinett Jul 20 '12 at 13:07
@PaulHinett: The intent of the site is to build a useful knowledge base for the sysadmin community. Your question and the response may well be helpful to you, but doesn't build anything for the community to use as reference. To my mind, the fact that the Server Fault site provides technical support is just a secondary artifact of the site's real mission. Your question and the answer amount to a technical support task and not a piece of knowledge that can be used by the community for future reference. That's my problem with it. – Evan Anderson Jul 20 '12 at 17:48
I agree with @EvanAnderson on this. "Here's a crash dump, someone analyze it for me" is not what this site is here for. How to Ask will outline some requirements for asking a "good" question that include listing what you've already tried, where you're stuck, etc. Just saying "I have a problem, someone fix it" is insulting and implies that our time is less valuable than yours since you can't be bothered to even dig into your own problem yourself. – MDMarra Jul 20 '12 at 19:37
up vote 2 down vote accepted

IMAGE_NAME:  pci.sys


FAILURE_BUCKET_ID:  X64_0x122_pci!ExpressRootPortAerInterruptRoutine+27f

BUCKET_ID:  X64_0x122_pci!ExpressRootPortAerInterruptRoutine+27f

This looks like a graphics card / chip hardware failure.

share|improve this answer
Or a driver issue, a power fluctuation or a memory error that just hits that damn thing. – TomTom Jul 20 '12 at 13:17
so basically, very difficult to find the route cause unless it's reproducible. – Paul Hinett Jul 20 '12 at 13:22
Yeah just replace PCIe card, this is pretty much simple. This could be another card to with dodgy driver. – Andrew Smith Jul 20 '12 at 14:05
I would simply wait to see if the error returns. It could be the card or it could be the driver. My bet would be the driver. – Jim B Jul 20 '12 at 15:25
Thank you, this lead me into the right the end it was down to my power settings being set to 'Balanced' instead of 'High performance'. In effect this turned the PCI-Express link state power management from 'Moderate power savings' to 'no power savings'. I had thousands of errors in my error log before, now i have none. – Paul Hinett Jul 20 '12 at 20:54

Not the answer you're looking for? Browse other questions tagged or ask your own question.