I recently installed a slipstreamed WindowsXP Pro SP3 and started getting this BSoD.

The Event Viewer reports the following details:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 100000d1, parameter1 0000000c, parameter2 00000002, parameter3 00000000, parameter4 a91f0f29.

Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 64 100000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 63 2c 20 00000c,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 61 39 31 66 00, a91f
0050: 30 66 32 39 0f29


Any solutions or references are most welcomed as this BSoD is occuring every other day.

0xD1 errors are caused by either a faulty driver or buggy software. The problem is there really isn't any information at this time that tells us which driver, etc.

So, go to the Windows OS form and read the sticky by Julio entitled "Before posting your minidumps..." and follow the advice there.

Coincidentally, I already taken all the steps mentioned in that sticky post.

Formatted my HDD twice and reinstalled the OS but the problem persist.

So I am assuming that its a Device Driver problem and hence attaching 4 latest minidumps from the current OS.

I hope someone would surely have a clue on this.

Attached Files

	Mini061108-01.dmp (88.0 KB, 2 views)
	Mini061208-01.dmp (88.0 KB, 2 views)
	Mini061308-01.dmp (88.0 KB, 2 views)
	Mini061608-01.dmp (88.0 KB, 2 views)

All MiniDumps Mention these errors with a different 4th parameter
BugCheck 100000D1, {c, 2, 0, a8fc6f29}
Probably caused by : tcpip.sys ( tcpip!ReadNextTCB+d2 )
MiniDump2 Parameter 4 - a8f63f29
MiniDump3 Parameter 4 - a91f5f29
MiniDump4 Parameter 4 - a91f5f29

These errors are caused by the Network Driver for Windows tcpip.sys. If you haven't already try this
Run a Memory test either Memtest86 - http://www.memtest.org/ or Windows Memory Diagnostic Tools - http://oca.microsoft.com/en/windiag.asp

If you find no problems with the RAM try increasing your pagefile size a bit, having done a quick search on Google someone with a similar problem to you said they increased the pagefile and this sorted the problem out.

woody1191 beat me by 2 seconds! It certainly has to do with network connections. Since it has only occured since slipstreaming SP3 my first advice would be to update your drivers for your NIC/Wireless card. Plus, what woody1191 said.

I did both the memory test with no errors. Thanks for the tool links.
I have 2Gb DDR2 666 RAM, so increased my Pagefile size to 3072Mb, lets see if that makes any difference.

BTW, I found the following Warning events in the log file mentioning Tcpip:

Event Type: Warning
Event Source: Tcpip
Event Category: None
Description:
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

These error warnings are seen every 5 to 10 minutes in the event viewer.


I am having Intel D945GNT Motherboard with the latest NIC drivers from Intel website (Intel® PRO Network Connections Driver 13.0).

How do I check if NIC Device Driver is causing this error? Are there any tools available for such troubleshooting?

I'm not any good with Event Viewer logs so I'll leave that to someone else on here. What Route44 is saying is update the drivers because the drivers mentioned in the MiniDumps are network drivers for Windows so there maybe a problem with your Network Card drivers.

Have you updated the Drivers?
Go to Device Manager if you haven't, follow this path ( Start > Run > devmgmt.msc > Ok) and go to Network Adaptors and Right click on every device in there and click on update drivers

Yes, I am already having the latest NIC drivers from Intel website.

Ok sorry just read that post before again. Didn't catch the part where you said you had the latest updates.
Have you had anymore problems since you increased the pagefile?

Havent got any BSoD after changing Pagefile size. Lets see if this is a permanent cure for this error.

Again got BSoD, still no luck after changing the Pagefile size.

Is there anything else I can do about this error? I even installed latest updates via Windows Update.

Attached Files

Mini071008-01.dmp (88.0 KB, 1 views)

Same error as before
BugCheck 100000D1, {c, 2, 0, a91c8fa9}
Probably caused by : tcpip.sys ( tcpip!ReadNextTCB+d2 )

Even though these errors aren't associated with a damaged HDD try running your HDD manufacturers test and also using Disk Check in Windows.

And keep in mind sometimes hardware goes bad. You might find that you need to change out your NIC card.

woody1191:
I already did Disk Check soon after i got the frist BSoD, no problem there.

Route44:
I guess not as it was running perfectly fine on WinXP SP2 for 1.5 years and as soon as I installed SP3 it started getting this error. I will try reverting back to SP2 and check for couple of days if there really some problem with NIC card.

Reverting back is what some people have had to do. Let us know if it brings you stability.

Didnt get time to revert back to SP2 so I continued using the current OS and got a new type of BSoD error.

Attached is the minidump for this error.

Attached Files

Mini071108-01.dmp (88.0 KB, 1 views)

MiniDump071108-01:
BugCheck 19, {20, 882d86c0, 882d88d8, a430001}
Unable to load image nadim.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nadim.sys
*** ERROR: Module load completed but symbols could not be loaded for nadim.sys
Unable to load image e100b325.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e100b325.sys
*** ERROR: Module load completed but symbols could not be loaded for e100b325.sys
Probably caused by : nadim.sys ( nadim+20a3 )

Ok the driver cited "nadim.sys" is part of a Program called "Network Activity Diagram" from what i can find on Google.
The Bugcheck 0x19 are caused by Device Driver issues, Bad Sectors Or Disk Write Issues with the HDD as well as Problems with some Routers.

Try if possible using a different HDD with Windows on.

woody1191:
Thanks for the debug info. I will troubleshoot HDD issue and let you know.