Tech Support Forum banner
Cancel

BSOD 0x44 & 0xb8 [moved from Server 2008]

3098 Views 8 Replies 2 Participants Last post by  RikD, 
R
I'm running 2 identical Windows 2008 server systems, both crashing occasionally. See attachments for all info.

Attachments

Save
Like
Status
Not open for further replies.
1 - 9 of 9 Posts
R
Re: BSOD 0x44

After installing the latest Intel NIC drivers the BSOD message has changed, but both servers still crash.

The attachment contains the last 2 minidumps.

Attachments

Save
Like
jcgriff2
Re: BSOD 0x44

Hi -

The bugchecks on the 2 most recent dumps following the Intel NIC update did change -

0xb8 = an illegal operation was attempted by a delayed procedure call (DPC) routine

Intel NIC is still listed among the probable causes along with the Microsoft networking component driver tcpip.sys and the Microsoft SMB network drivers mrxsmb10.sys and mrxsmb10.sys

Run the Driver Verifier as it may help ID a rogue 3rd party driver, assuming one exists -

Driver Verifier --> http://jcgriff2.com/driver_verifier.htm

Check the Reliability Monitor - see what installations took place prior to BSODs starting -
START | type perfmon /rel

Windbg Logs
--> http://jcgriff2.com/dbug_logs/_99-dbug_RikD_Server2008-6002_07-10-2010_jcgriff2_.txt
--> http://jcgriff2.com/dbug_logs/_99-dbug_RikD_Server2008-6002_07-10-2010_jcgriff2_.txt.zip

Regards. . .

jcgriff2

.

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Tue Jul  6 04:37:46.539 2010 (GMT-4)
System Uptime: 0 days 0:19:34.546
BugCheck 100000B8, {81916640, 8628d928, 81910000, 0}
*** WARNING: Unable to verify timestamp for mrxsmb.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
*** WARNING: Unable to verify timestamp for mrxsmb10.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb10.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : mrxsmb.sys ( mrxsmb+1a83 )
BUGCHECK_STR:  0xB8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Tue Jul  6 04:16:29.137 2010 (GMT-4)
System Uptime: 0 days 20:59:15.781
BugCheck 100000B8, {8190a640, 85e9f030, 81904000, 0}
*** WARNING: Unable to verify timestamp for mrxsmb.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
*** WARNING: Unable to verify timestamp for mrxsmb10.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb10.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : mrxsmb.sys ( mrxsmb+1a83 )
BUGCHECK_STR:  0xB8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Mon Jul  5 07:15:31.303 2010 (GMT-4)
System Uptime: 0 days 3:40:15.968
BugCheck 44, {86599200, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Sat Jul  3 10:12:15.202 2010 (GMT-4)
System Uptime: 1 days 2:55:50.093
BugCheck 44, {865e4918, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul  2 07:14:42.546 2010 (GMT-4)
System Uptime: 0 days 5:40:25.437
BugCheck 44, {86684af8, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul  2 01:32:35.466 2010 (GMT-4)
System Uptime: 0 days 0:19:55.406
BugCheck D1, {903e14b6, 2, 8, 903e14b6}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : rdbss.sys ( rdbss!RxCancelBlockingOperation+0 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul  2 01:10:57.688 2010 (GMT-4)
System Uptime: 0 days 23:58:23.015
BugCheck 44, {860b8280, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Thu Jul  1 01:10:53.484 2010 (GMT-4)
System Uptime: 0 days 14:55:13.375
BugCheck 44, {86006c28, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Wed Jun 30 10:13:58.082 2010 (GMT-4)
System Uptime: 0 days 23:39:22.203
BugCheck 44, {86ae0798, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Tue Jun 29 10:33:23.505 2010 (GMT-4)
System Uptime: 5 days 2:40:44.421
BugCheck A, {30001a, 2, 1, 81bcaede}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Tue Jun 22 10:13:42.498 2010 (GMT-4)
System Uptime: 0 days 21:53:03.671
BugCheck 44, {85dfe5a0, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Mon Jun 21 12:18:57.295 2010 (GMT-4)
System Uptime: 2 days 11:00:41.093
BugCheck 44, {86d2c5a0, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Sat Jun 19 01:16:33.869 2010 (GMT-4)
System Uptime: 3 days 15:44:31.921
BugCheck D1, {39, 2, 1, 908d95f1}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+59 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Tue Jun 15 09:30:18.139 2010 (GMT-4)
System Uptime: 5 days 23:01:23.743
BugCheck 44, {871308c8, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Wed Jun  9 10:27:41.734 2010 (GMT-4)
System Uptime: 0 days 17:29:12.625
BugCheck 44, {869cb708, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Sun May 23 04:07:38.578 2010 (GMT-4)
System Uptime: 5 days 23:39:52.468
BugCheck 44, {86b41638, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Sat May 15 16:50:55.590 2010 (GMT-4)
System Uptime: 25 days 5:06:21.984
BugCheck A, {a5f92000, 2, 0, 81be2f04}
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+3d )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Tue Apr 20 11:43:16.719 2010 (GMT-4)
System Uptime: 0 days 7:39:07.906
BugCheck 100000B8, {818fe640, 86425b80, 818f8000, 0}
*** WARNING: Unable to verify timestamp for mrxsmb.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
*** WARNING: Unable to verify timestamp for mrxsmb10.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb10.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : mrxsmb.sys ( mrxsmb+1a83 )
BUGCHECK_STR:  0xB8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18160.x86fre.vistasp2_gdr.091208-0542
Debug session time: Tue Apr 13 07:07:54.765 2010 (GMT-4)
System Uptime: 0 days 3:07:33.656
BugCheck 44, {86aab5c8, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339
Debug session time: Tue Mar  9 08:11:34.746 2010 (GMT-4)
System Uptime: 62 days 2:18:00.250
BugCheck 44, {868d9150, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339
Debug session time: Fri Nov 20 07:15:46.458 2009 (GMT-4)
System Uptime: 9 days 0:00:05.765
BugCheck 44, {86b353d8, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339
Debug session time: Wed Nov 11 07:13:56.043 2009 (GMT-4)
System Uptime: 1 days 2:12:41.687
BugCheck 44, {8693b398, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339
Debug session time: Tue Nov 10 04:59:30.167 2009 (GMT-4)
System Uptime: 12 days 16:39:10.703
BugCheck 44, {86169ab0, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Wed Oct 28 12:01:31.859 2009 (GMT-4)
System Uptime: 1 days 2:32:37.703
BugCheck 44, {85eae760, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Tue Oct 27 09:27:11.717 2009 (GMT-4)
System Uptime: 2 days 7:25:06.453
BugCheck 44, {869e0438, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Sun Oct 25 02:00:23.093 2009 (GMT-4)
System Uptime: 0 days 2:51:01.984
BugCheck D1, {8ffd84b6, 2, 8, 8ffd84b6}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : rdbss.sys ( rdbss!RxCancelBlockingOperation+0 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Sat Oct 24 23:07:39.771 2009 (GMT-4)
System Uptime: 0 days 1:02:15.515
BugCheck 44, {86631e28, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Sat Oct 24 22:03:42.740 2009 (GMT-4)
System Uptime: 0 days 0:37:30.359
BugCheck 44, {86864810, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Sat Oct 24 21:24:30.938 2009 (GMT-4)
System Uptime: 0 days 0:18:28.093
BugCheck D1, {907dc4b6, 2, 8, 907dc4b6}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : rdbss.sys ( rdbss!RxCancelBlockingOperation+0 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Sat Oct 24 21:04:47.051 2009 (GMT-4)
System Uptime: 45 days 9:46:25.906
BugCheck 44, {86c4bc78, e7a, 0, 0}
*** WARNING: Unable to verify timestamp for e1e6032.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnectionTlRequestComplete+bc )
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 

by [color=navy]jcgriff2     
             
         J. C. Griffith, Microsoft MVP[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055]https://mvp.support.microsoft.com/profile/Griffith[/color][/url]   
             
           [url=www.jcgriff2.com][color=#000055]www.jcgriff2.com[/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/font]
See less See more
Save
Like
R
Hi

Thanks for your reply!

I'm running the driver verifier now as described on your page. I don't see anything strange, but I don't really know what I'm looking for either. I understand it needs to run for at least 24 hours.


This machine was installed in august 2009.
* 10/25/2009: 3x 0x44 + 2x 0xd1
* 10/26/2009: installed debugging tools
* 10/27/2009: 0x44
* 10/28/2009: 0x44 + installed windows updates
* 10/11/2009: 0x44
* 11/11/2009: 0x44
* 11/20/2009: 0x44
* 1/6/2010: windows updates
* 3/9/2010: 0x44
* 3/24/2010: windows updates
* 4/13/2010: 0x44 + windows updates
* 4/20/2010: 0x44 + windows updates
* 5/15/2010: 0x0a
* 5/17/2010: driver installs (monitor, mouse, keyboard)
* 5/23/2010: 0x44 + driver installs mouse, keyboard
* 6/7/2010: windows updates
* 6/9/2010: 0x44
* 6/15/2010: 0x44
* 6/19/2010: 0xd1
* 6/21/2010: 0x44
* 6/22/2010: 0x44 + windows updates
* 6/24/2010: windows updates
* 6/29/2010: 0x0a
* 6/30/2010: 0x44
* 7/1/2010: 0x44
* 7/2/2010: 2x 0x44 + 0xd1
* 7/3/2010: 0x44
* 7/5/2010: 0x44 + install new intel pro/1000 pl drivers
* 7/6/2010: 2x 0xb8
* 7/8/2010: 3x 0x44
* 7/10/2010: 0xb8
* 7/11/2010: 0x44 + 0xd1
* 7/12/2010: 0x44 + 2x 0xd1

This machine runs IIS with 1 website and an FTP server (about 10-50 simultaneous connections). It is connected to an Open-E file server using a shared network drive. It is also running about 10 services we developed ourselves, these services query a database on another machine and perform tasks like create/delete/copy files.

Part4 of the logfiles in the attachment contain the BSOD information between 7/8/2010 and 7/12/2010.

Attachments

See less See more
Save
Like
jcgriff2
Hi -

Please keep Driver Verifier running.

Your log shows -
Code: 
 7/5/2010: 0x44 + install new intel pro/1000 pl drivers
Intel download center shows drivers for XP only for the Intel Pro/1000 PL Ethernet -

http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword="intel+pro/1000+pl"

Are these XP drivers the ones you are using?

Is this your NIC?
Code: 
[FONT=Lucida Console]
Intel® 82573L Gigabit Ethernet Controller 
[/FONT]
I also noticed 100's entries in the Event Viewer logs similar to this (different PID's) -
Code: 
[FONT=Lucida Console]
Event[34996]:
  Log Name: System
  Source: Microsoft-Windows-WAS
  Date: 2010-05-05T03:09:24.000
  Description: 
A worker process with process id of '6068' serving application 
pool 'DefaultAppPool' has requested a recycle because [COLOR=Red]it reached
 its virtual memory limit[/COLOR].
[/FONT]
WMI reports a page file present, but shows -0- virtual memory usage usage.

Regards. . .

jcgriff2

.
See less See more
Save
Like
R
Machine just crashed again, attaching part5 to this message, which should now have the Driver Verifier info.

The driver I recently installed is downloaded from http://www.intel.com/support/network/sb/CS-006120.htm (PROWIN32.EXE). At the time I didn't realise the PL version wasn't listed, should I try to install another version?

The hardware ID for the NIC shows PCI\VEN_8086&DEV_109A&SUBSYS_109A15D9&REV_00

Regarding the application pool recycles, I noticed them too about 2 months ago so I changed the "Private Memory Limit" and "Virtual Memory Limit" to 0 (unlimited) in IIS7.

Attachments

Save
Like
R
I found some more info about the specific hardware in this machine.

The motherboard is a SuperMicro X7SBi-LN4 (http://www.supermicro.com/products/motherboard/Xeon3000/3200/X7SBi-LN4.cfm) with onboard network controllers.
4x Single-port Intel® 82573V/L Gigabit PCI-Express Ethernet Controllers
Save
Like
jcgriff2
RikD said:
Machine just crashed again, attaching part5 to this message, which should now have the Driver Verifier info.

The driver I recently installed is downloaded from http://www.intel.com/support/network/sb/CS-006120.htm (PROWIN32.EXE). At the time I didn't realise the PL version wasn't listed, should I try to install another version?

The hardware ID for the NIC shows PCI\VEN_8086&DEV_109A&SUBSYS_109A15D9&REV_00

Regarding the application pool recycles, I noticed them too about 2 months ago so I changed the "Private Memory Limit" and "Virtual Memory Limit" to 0 (unlimited) in IIS7.
Click to expand...
Hi -

The BSOD was VERIFIER _ENABLED, however no specific 3rd party driver mentioned. The usual suspects were indirectly noted - Intel Ethernet and MS tcpip.sys

Found in the dumps - what is it for?
Code: 
[font=lucida console]
iqvw32.sys      Tue Dec 23 10:10:43 [COLOR=Red]2008[/COLOR] (4950FF73) - Intel(R) Network Adapter Diagnostic Driver
[/font]
If the paged pool limits were set to unlimited because of paged pool depletion and now with unlimited set, the situation still occurs. Obviously, something is wrong here.

This was the app running at the time of BSOD -
Code: 
[font=lucida console]
PROCESS_NAME:  HDScheduleEngin  
[/font]
Any ideas?

RikD said:
I found some more info about the specific hardware in this machine.

The motherboard is a SuperMicro X7SBi-LN4 (http://www.supermicro.com/products/motherboard/Xeon3000/3200/X7SBi-LN4.cfm) with onboard network controllers.
4x Single-port Intel® 82573V/L Gigabit PCI-Express Ethernet Controllers
Click to expand...
Here is screenshot from that site -



Try another Intel driver.

Regards. . .

jcgriff2

.
See less See more
Save
Like
R
I uninstalled the drivers which were installed on july 5th and then installed the drivers I downloaded from the SuperMicro site. During installation the IP settings were lost so we had to physically go to the server to set them again.

When I view the driver details it still shows the version 9.13.41.0 (date 3/26/2010) so I suspect the file from SuperMicro installs the same driver.

iqvw32.sys - No idea, installed by default when installing the Intel driver perhaps?

Application pool, since I set it to unlimited I don't see any recycle events any more.

HDScheduleEngine, that's one of the services we programmed ourselves in c# .net.

If BSOD's will continue this weekend we will install a new NIC next week and turn off the onboard one.

Regards,
Rik.
See less See more
Save
Like
1 - 9 of 9 Posts
Status
Not open for further replies.
Tech Support Forum
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!
Full Forum Listing
Explore Our Forums
Windows XP Support Windows 7 , Windows Vista Support Motherboards, Bios|UEFI & CPU Networking Support Laptop Support
Top