[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7473
  • Last Modified:

Error code 100000d1 - PCs blue screening, rebooting and crashing

I have two PCs that are experiencing regular blue screens, crashes and reboots.

They are Windows XP Professional woth Service Pack 2, and they logon to a Windows 2003 domain via a 108mbps wireless network.

In the Event Logs for each, the following is logged each time a crash occurs:

Source: System Error
Event ID: 1003
Category: (102)


Error code 100000d1, parameter1 effe6088, parameter2 00000002, parameter3 00000000, parameter4 eff8fdf0

The error code is always 100000d1, and parameter2 ans parameter3 are always the same, but the following codes have also been displayed:

Error code 100000d1, parameter1 f0536088, parameter2 00000002, parameter3 00000000, parameter4 f04dfdf
Error code 100000d1, parameter1 f6a03088, parameter2 00000002, parameter3 00000000, parameter4 f69acdf0
Error code 100000d1, parameter1 f69c8088, parameter2 00000002, parameter3 00000000, parameter4 f6971df0

There could also be other variants, but these are the only ones that I have noted.

I thought at first that it might be the type of wireless network cards I was using (Netgear) but I have changed both PCs to DLink and the same problems occur.

Can anyone give me an idea as to what might be causing this?  I am happy to provide further details from the PC or logs if need be.



  • 5
  • 4
1 Solution
Could you please upload the .dmp files (normally found in c:\windows\minidump) to www.ee-stuff.com
peterkennedyAuthor Commented:
Hi and235100,

Will do.  I was thinking after I posted this that those may be useful.

I will not get a chance to get back to the client office until Monday but I will post the .dmp files for all machines that are being affected to this site as soon as I have them.  

Thanks for that.

peterkennedyAuthor Commented:
Hi there,

Here are two ZIP files that contain multiple .dmp files for each of the PCs that seems to be encountering the same problem.  If you could look into these and let me know what particular component seems to be causing the crash I would be most grateful!


Also, as a side note - how do you actually open these DMP files?  Is there a special "viewer" that puts it into a more readable format for future reference?

Thanks very much for your help,

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

I would first recommend updating wireless drivers and/or firmware - a chipset driver update for your computers seems like a good first step - if available - while I check out the dmp files...
A3AB.sys seems to crash a few PCs - your hardware may have an incompatibility with this driver.

I have checked through these dmp files - there is definitely a hardware incompatibility issue here.

This problem with d-link cards operating at 108mbps has been reported before.

As I said - make sure that the drivers are up to date - but this looks to be bad Atheros drivers...

I would recommend not using D-Link wireless with your current hardware.

As to the Netgear problem - I take it that you have tried rebuilding the stations from known good images - then reinstall the drivers? Other than that - I can't really narrow this down further at this point - have you tried reinstalling SP2 on these stations - then reinstalling the drivers?
peterkennedyAuthor Commented:
Thanks very much and235100,

I appreciate you looking into this for me.  The same problem seemed to exist with the Netgear wg311t wireless NICs that I used too, hence my move to the D-Link DWL-G520s, but alas, same issues.

When you say "bad Atheros drivers", are these drivers part of XP or the wireless card?

I might try the following:

- Remove the drivers altogether for the D-link cards and uninstall them
- Re-install SP2 on both PCs
- Get the latest drivers and firmware for the Netgear cards
- Re-install the Netgear cards with the latest drivers and firmware
- Cross my fingers

Other than that, are there any 108mbps cards that are actually reliable?  Would I be better of setting them to 54mbps instead of 108mbps, or would that make no difference?

Thanks very much,

What I meant about the bad drivers was that D-Link (as far as I am aware) tend not to write their own drivers - often Atheros do it for them.

The only thing I would say in your list of "to-do" - once you have removed the drivers, run a registry cleaner, such as Registry Mechanic (http://www.pctools.com/registry-mechanic/), then proceed with the SP2 reinstall.

The issue is - 108mbps is not an official wireless standard - and so-called "108mbps" equipment is normally hard to match up from different manufacturers. What APs are you using, btw?

Being on a domain means that good network connectivity is a must - and with wireless networking this is especially important - I would recommend using standard 802.11g for the time being in a corporate environment.

peterkennedyAuthor Commented:
Thanks again,

I am using a Netgear Rangemax wireless router as the access point, hence me buying the Netgear NICs that I thought would go well with it.  Your suggestion to run 802.11g is a great idea - I will set this up once I have gone back a few steps and run the registry cleaner, etc then re-installed SP2 and the Netgear cards.

Thanks again and I will let you know how I get on.

peterkennedyAuthor Commented:
Hi again,

So far so good on the suggested steps for fixing this.  We have gone two days without a crash on either PC which is very rare.  What I did was:

- Uninstalled the DLink cards totally from each PC
- Ran a registry checker/fix over both PCs and addressed all problems
- Re-installed XP SP2 on both PCs
- Changed the router settigs to "G" wireless only (54mbps), not "Auto" 108mbps
- Re-installed the two original Netgear 311t wireless cards into both PCs with the most up to date drivers

I have also configured each PC to give a "Complete Log" in the event that they crash again so that if it happens we have more to look at.

As I said though, so far so good.  I will give it a few more days then accept a solution here.

Thanks again for your suggestions and help.


Featured Post


Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now