Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

What, other than magic, could cause multiple similarly configured XP Pro machines (non-domain joined, windows update disabled, no scheduled tasks) to bugcheck within 15 minutes of each other? The error message recorded in the event log is reproduced below:

Error code 10000050, parameter1 bc6ffff0, parameter2 00000000, parameter3 bf84cd45, parameter4 00000000.

Note: Windows update being disabled is not my choice. These are not under my control and are used in factory automation.

Note: I have considered a power anomaly, but there are many other similarly configured machines that had no apparent issues.

share|improve this question
Some kind of un-patched vulnerability that permits a basic Denial of Service? – Zoredache Aug 17 '12 at 7:14
Factory automation, and no updates. That's going to cost your company big time when somebody gets in to those boxes and wreaks havoc. – Michael Hampton Aug 17 '12 at 7:58
Gets in? My guess is they're already in. – John Gardeniers Aug 17 '12 at 9:42
What common software do the machines have? Norton AV by any chance? – David Schwartz Aug 17 '12 at 10:07
I am well aware of the reasons that updates should be performed. Your arguments are the same used when convincing business owners that the system should be replaced. The replacement is in development. – Mitch Aug 17 '12 at 14:59
up vote 3 down vote accepted

I think the first thing to do is to look up the reason for the bluescreens - I swear by whocrashed and bluescreen view - these either interpret or look up the precise errors easily. I'd look at each system seperately - It might be a co-incidence that these systems crashed together. If its a one off incident it may not be worth following up on - else, well thats the right place to start.

Once you've looked at individual systems then hunting down a common cause is easier.

share|improve this answer
RDPDD.DLL at RDPDD!DrvDisableSurface+0x63. Looks like a bug with XP SP3 and changing resolutions with RDP Clients. See… – Mitch Aug 17 '12 at 15:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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