I'm running a fairly new machine (about 2 months old). It's running XP Pro
SP2. Haven't had a problem until a couple of weeks ago when started taking
various BSOD abends.

According to Event Viewer, the abends were different categories and event
ids. Suspecting memory, I downloaded the MS memory tester and Memtest86+.
Both confirmed memory problems. Ordered new memory. I wanted to try and
figure out which memory stick was bad, so I moved them to slot 1 to run
memory tests against them. You know the story - no problems found. Probably
just needed to reset the boards. I thought problem was solved.....

Tonight, I had another BSOD. System wouldn't reboot until I powered down
the box. Here's the first error found in the Event Log:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/1/2008
Time: 5:53:37 PM
User: N/A
Computer: TOGNETTI01
Description:
Error code 100000d1, parameter1 66666a74, parameter2 00000002, parameter3
00000001, parameter4 b9663242.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
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 36 36 eters 66
0030: 36 36 36 61 37 34 2c 20 666a74,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 62 39 36 36 01, b966
0050: 33 32 34 32 3242


Searching Microsoft found a hit in Article 925922. It references Hotfix
6294451 for module tcpip.sys. Did some other searching and found references
to updating to latest BIOS and drivers.

Hotfix 6294451 replaces tcpip.sys. It's attributes are:


tcpip.sys 360,704 26 Sep 2006 9:21

The one currently on my system has attributes:

tcpip.sys 352K 30 Oct 2007 12:20 PM

I have 2 question about this Hotfix:

1) The Hotfix module is older than the one I'm running with. Shouldn't the
update from the Hotfix already be included in the one I'm running?

2) Is it possible to backout this Hotfix should it not resolve my issue?

I'm a bit concerned about updating the BIOS. I could be wrong, but these
can't be backed out? Being a mainframer, I'm very careful to introduce any
change that could make matters worse. At this point I don't have high
confidence that either change will fix my issue. I don't like shooting in
the dark.

Is there any other information I can obtain/provide that will help nail down
the problem?

Thanks in Advance!

<QP>
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL
that was too high. The most typical cause is a bad device driver (one that
uses improper addresses). It can also be caused by caused by faulty or
mismatched RAM, or a damaged pagefile.
</QP>
Source & more: http://aumha.org/a/stop.htm

Try this Hotfix instead:

Stop error message on a Windows XP-based computer: "STOP 0x000000D1"
http://support.microsoft.com/?kbid=916595

Download (Validation required):
http://www.microsoft.com/downloads/d...B-5566599E1926
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/



Mainframer wrote:
> I'm running a fairly new machine (about 2 months old). It's running XP
> Pro
> SP2. Haven't had a problem until a couple of weeks ago when started
> taking
> various BSOD abends.
>
> According to Event Viewer, the abends were different categories and event
> ids. Suspecting memory, I downloaded the MS memory tester and Memtest86+.
> Both confirmed memory problems. Ordered new memory. I wanted to try and
> figure out which memory stick was bad, so I moved them to slot 1 to run
> memory tests against them. You know the story - no problems found.
> Probably just needed to reset the boards. I thought problem was
> solved.....
>
> Tonight, I had another BSOD. System wouldn't reboot until I powered down
> the box. Here's the first error found in the Event Log:
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 5/1/2008
> Time: 5:53:37 PM
> User: N/A
> Computer: TOGNETTI01
> Description:
> Error code 100000d1, parameter1 66666a74, parameter2 00000002, parameter3
> 00000001, parameter4 b9663242.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> 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 36 36 eters 66
> 0030: 36 36 36 61 37 34 2c 20 666a74,
> 0038: 30 30 30 30 30 30 30 32 00000002
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 31 2c 20 62 39 36 36 01, b966
> 0050: 33 32 34 32 3242
>
>
> Searching Microsoft found a hit in Article 925922. It references Hotfix
> 6294451 for module tcpip.sys. Did some other searching and found
> references
> to updating to latest BIOS and drivers.
>
> Hotfix 6294451 replaces tcpip.sys. It's attributes are:
>
>
> tcpip.sys 360,704 26 Sep 2006 9:21
>
> The one currently on my system has attributes:
>
> tcpip.sys 352K 30 Oct 2007 12:20 PM
>
> I have 2 question about this Hotfix:
>
> 1) The Hotfix module is older than the one I'm running with. Shouldn't
> the
> update from the Hotfix already be included in the one I'm running?
>
> 2) Is it possible to backout this Hotfix should it not resolve my issue?
>
> I'm a bit concerned about updating the BIOS. I could be wrong, but these
> can't be backed out? Being a mainframer, I'm very careful to introduce
> any
> change that could make matters worse. At this point I don't have high
> confidence that either change will fix my issue. I don't like shooting in
> the dark.
>
> Is there any other information I can obtain/provide that will help nail
> down
> the problem?
>
> Thanks in Advance!

"Mainframer" <(E-Mail Removed)> wrote in message
news:6EF28D50-AC1A-46B1-BFE0-(E-Mail Removed)...
> I'm running a fairly new machine (about 2 months old). It's running XP
> Pro
> SP2. Haven't had a problem until a couple of weeks ago when started
> taking
> various BSOD abends.
>
> According to Event Viewer, the abends were different categories and event
> ids. Suspecting memory, I downloaded the MS memory tester and Memtest86+.
> Both confirmed memory problems. Ordered new memory. I wanted to try and
> figure out which memory stick was bad, so I moved them to slot 1 to run
> memory tests against them. You know the story - no problems found.
> Probably
> just needed to reset the boards. I thought problem was solved.....
>
> Tonight, I had another BSOD. System wouldn't reboot until I powered down
> the box. Here's the first error found in the Event Log:
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 5/1/2008
> Time: 5:53:37 PM
> User: N/A
> Computer: TOGNETTI01
> Description:
> Error code 100000d1, parameter1 66666a74, parameter2 00000002, parameter3
> 00000001, parameter4 b9663242.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> 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 36 36 eters 66
> 0030: 36 36 36 61 37 34 2c 20 666a74,
> 0038: 30 30 30 30 30 30 30 32 00000002
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 31 2c 20 62 39 36 36 01, b966
> 0050: 33 32 34 32 3242
>
>
> Searching Microsoft found a hit in Article 925922. It references Hotfix
> 6294451 for module tcpip.sys. Did some other searching and found
> references
> to updating to latest BIOS and drivers.
>
> Hotfix 6294451 replaces tcpip.sys. It's attributes are:
>
>
> tcpip.sys 360,704 26 Sep 2006 9:21
>
> The one currently on my system has attributes:
>
> tcpip.sys 352K 30 Oct 2007 12:20 PM
>
> I have 2 question about this Hotfix:
>
> 1) The Hotfix module is older than the one I'm running with. Shouldn't
> the
> update from the Hotfix already be included in the one I'm running?
>
> 2) Is it possible to backout this Hotfix should it not resolve my issue?
>
> I'm a bit concerned about updating the BIOS. I could be wrong, but these
> can't be backed out? Being a mainframer, I'm very careful to introduce
> any
> change that could make matters worse. At this point I don't have high
> confidence that either change will fix my issue. I don't like shooting in
> the dark.
>
> Is there any other information I can obtain/provide that will help nail
> down
> the problem?
>
> Thanks in Advance!
>
There seem to be lots of drivers which can cause this problem. Just search
Google to find some more. Thus, your problem may not be caused by
tcpip.sys.
My answers to your questions are:
1) Perhaps. Hotfixes are not thoroughly tested; the version of tcpip.sys
may be a more completely tested version.
2) Not unless there is an uninstall folder for this hotfix.

Jim

"PA Bear [MS MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> <QP>
> 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
> The system attempted to access pageable memory using a kernel process IRQL
> that was too high. The most typical cause is a bad device driver (one that
> uses improper addresses). It can also be caused by caused by faulty or
> mismatched RAM, or a damaged pagefile.
> </QP>
> Source & more: http://aumha.org/a/stop.htm
>
> Try this Hotfix instead:
>
> Stop error message on a Windows XP-based computer: "STOP 0x000000D1"
> http://support.microsoft.com/?kbid=916595
>
> Download (Validation required):
> http://www.microsoft.com/downloads/d...B-5566599E1926
> --
> ~Robear Dyer (PA Bear)
> MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
> AumHa VSOP & Admin http://aumha.net
> DTS-L http://dts-l.net/
>
>
>
> Mainframer wrote:
>> I'm running a fairly new machine (about 2 months old). It's running XP
>> Pro
>> SP2. Haven't had a problem until a couple of weeks ago when started
>> taking
>> various BSOD abends.
>>
>> According to Event Viewer, the abends were different categories and event
>> ids. Suspecting memory, I downloaded the MS memory tester and
>> Memtest86+.
>> Both confirmed memory problems. Ordered new memory. I wanted to try and
>> figure out which memory stick was bad, so I moved them to slot 1 to run
>> memory tests against them. You know the story - no problems found.
>> Probably just needed to reset the boards. I thought problem was
>> solved.....
>>
>> Tonight, I had another BSOD. System wouldn't reboot until I powered down
>> the box. Here's the first error found in the Event Log:
>>
>> Event Type: Error
>> Event Source: System Error
>> Event Category: (102)
>> Event ID: 1003
>> Date: 5/1/2008
>> Time: 5:53:37 PM
>> User: N/A
>> Computer: TOGNETTI01
>> Description:
>> Error code 100000d1, parameter1 66666a74, parameter2 00000002, parameter3
>> 00000001, parameter4 b9663242.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> 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 36 36 eters 66
>> 0030: 36 36 36 61 37 34 2c 20 666a74,
>> 0038: 30 30 30 30 30 30 30 32 00000002
>> 0040: 2c 20 30 30 30 30 30 30 , 000000
>> 0048: 30 31 2c 20 62 39 36 36 01, b966
>> 0050: 33 32 34 32 3242
>>
>>
>> Searching Microsoft found a hit in Article 925922. It references Hotfix
>> 6294451 for module tcpip.sys. Did some other searching and found
>> references
>> to updating to latest BIOS and drivers.
>>
>> Hotfix 6294451 replaces tcpip.sys. It's attributes are:
>>
>>
>> tcpip.sys 360,704 26 Sep 2006 9:21
>>
>> The one currently on my system has attributes:
>>
>> tcpip.sys 352K 30 Oct 2007 12:20 PM
>>
>> I have 2 question about this Hotfix:
>>
>> 1) The Hotfix module is older than the one I'm running with. Shouldn't
>> the
>> update from the Hotfix already be included in the one I'm running?
>>
>> 2) Is it possible to backout this Hotfix should it not resolve my issue?
>>
>> I'm a bit concerned about updating the BIOS. I could be wrong, but these
>> can't be backed out? Being a mainframer, I'm very careful to introduce
>> any
>> change that could make matters worse. At this point I don't have high
>> confidence that either change will fix my issue. I don't like shooting
>> in
>> the dark.
>>
>> Is there any other information I can obtain/provide that will help nail
>> down
>> the problem?
>>
>> Thanks in Advance!
>
The OP referenced error 100000D1 not 000000D1. It is still a driver problem
though.
Jim

Jim wrote:
> "PA Bear [MS MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> <QP>
>> 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
>> The system attempted to access pageable memory using a kernel process
>> IRQL
>> that was too high. The most typical cause is a bad device driver (one
>> that
>> uses improper addresses). It can also be caused by caused by faulty or
>> mismatched RAM, or a damaged pagefile.
>> </QP>
>> Source & more: http://aumha.org/a/stop.htm
>>
>> Try this Hotfix instead:
>>
>> Stop error message on a Windows XP-based computer: "STOP 0x000000D1"
>> http://support.microsoft.com/?kbid=916595
>>
>> Download (Validation required):
>> http://www.microsoft.com/downloads/d...B-5566599E1926
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
>> AumHa VSOP & Admin http://aumha.net
>> DTS-L http://dts-l.net/
>>
>>
>>
>> Mainframer wrote:
>>> I'm running a fairly new machine (about 2 months old). It's running XP
>>> Pro
>>> SP2. Haven't had a problem until a couple of weeks ago when started
>>> taking
>>> various BSOD abends.
>>>
>>> According to Event Viewer, the abends were different categories and
>>> event
>>> ids. Suspecting memory, I downloaded the MS memory tester and
>>> Memtest86+.
>>> Both confirmed memory problems. Ordered new memory. I wanted to try
>>> and
>>> figure out which memory stick was bad, so I moved them to slot 1 to run
>>> memory tests against them. You know the story - no problems found.
>>> Probably just needed to reset the boards. I thought problem was
>>> solved.....
>>>
>>> Tonight, I had another BSOD. System wouldn't reboot until I powered
>>> down
>>> the box. Here's the first error found in the Event Log:
>>>
>>> Event Type: Error
>>> Event Source: System Error
>>> Event Category: (102)
>>> Event ID: 1003
>>> Date: 5/1/2008
>>> Time: 5:53:37 PM
>>> User: N/A
>>> Computer: TOGNETTI01
>>> Description:
>>> Error code 100000d1, parameter1 66666a74, parameter2 00000002,
>>> parameter3
>>> 00000001, parameter4 b9663242.
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> 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 36 36 eters 66
>>> 0030: 36 36 36 61 37 34 2c 20 666a74,
>>> 0038: 30 30 30 30 30 30 30 32 00000002
>>> 0040: 2c 20 30 30 30 30 30 30 , 000000
>>> 0048: 30 31 2c 20 62 39 36 36 01, b966
>>> 0050: 33 32 34 32 3242
>>>
>>>
>>> Searching Microsoft found a hit in Article 925922. It references Hotfix
>>> 6294451 for module tcpip.sys. Did some other searching and found
>>> references
>>> to updating to latest BIOS and drivers.
>>>
>>> Hotfix 6294451 replaces tcpip.sys. It's attributes are:
>>>
>>>
>>> tcpip.sys 360,704 26 Sep 2006 9:21
>>>
>>> The one currently on my system has attributes:
>>>
>>> tcpip.sys 352K 30 Oct 2007 12:20 PM
>>>
>>> I have 2 question about this Hotfix:
>>>
>>> 1) The Hotfix module is older than the one I'm running with. Shouldn't
>>> the
>>> update from the Hotfix already be included in the one I'm running?
>>>
>>> 2) Is it possible to backout this Hotfix should it not resolve my issue?
>>>
>>> I'm a bit concerned about updating the BIOS. I could be wrong, but
>>> these
>>> can't be backed out? Being a mainframer, I'm very careful to introduce
>>> any
>>> change that could make matters worse. At this point I don't have high
>>> confidence that either change will fix my issue. I don't like shooting
>>> in
>>> the dark.
>>>
>>> Is there any other information I can obtain/provide that will help nail
>>> down
>>> the problem?
>>>
>>> Thanks in Advance!
>>
> The OP referenced error 100000D1 not 000000D1. It is still a driver
> problem
> though.

Give it a whirl anyway.