System Error causing reboot

Hi Sloppy,

Can you copy paste the exact log, or post the event id of the log file ?

Miguel

Event Type:      Error
Event Source:      System Error
Event Category:      (102)
Event ID:      1003
Date:            05/02/2006
Time:            17:11:13
User:            N/A
Computer:      SLOPPY
Description:
Error code 100000d1, parameter1 61436d4d, parameter2 00000002, parameter3 00000000, parameter4 eeaf315d.

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 31   eters 61
0030: 34 33 36 64 34 64 2c 20   436d4d,
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 65 65 61 66   00, eeaf
0050: 33 31 35 64               315d    

Hi,

Most of the problems leading to this event indicate faulty hardware, bugs in device drivers or incompatible hardware.

Go to C:\WINDOWS\Minidump take the last 2 or 3 minidump files and post them in a webspace (like http://www.rapidshare.de ).

Post the link to the dump files here.

Miguel

efb2237f is the failing instruction address. If you attach the minidumps at webspace, I can find out the culprit.

I've uploaded my Minidump folder to http://mike.ultrateq.co.uk/Minidump

yes, although it's currently set to 'off'

Your crash may have multiple culprit. The first culprit is nVidia Firewall. The second culprit is hardware as one of the minidump has double fault.

Mini020406-01.dmp BugCheck 100000D1, {2000ec, 2, 1, b9ac58d4}
Mini020406-01.dmp Probably caused by : HTTP.sys ( HTTP!UlInitializeConnectionTimerInfo+22 )

Mini020406-02.dmp BugCheck 1000000A, {166, 2, 0, 804fa726}
Mini020406-02.dmp Probably caused by : NVTcp.sys ( NVTcp+40c1 )

Mini020406-03.dmp BugCheck 100000D1, {334, 2, 0, ecf8b08c}
Mini020406-03.dmp Probably caused by : NVTcp.sys ( NVTcp+408c )

Mini020506-01.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Mini020506-01.dmp Probably caused by : portcls.sys ( portcls!_SEH_prolog+1a )

Mini020506-02.dmp BugCheck 100000D1, {1580705, 2, 0, efb2237f}
Mini020506-02.dmp Probably caused by : NVTcp.sys ( NVTcp+237f )

Mini020506-03.dmp BugCheck 100000D1, {61436d4d, 2, 0, eeaf315d}
Mini020506-03.dmp Probably caused by : NVTcp.sys ( NVTcp+415d )

5 minidumps are crashed by nVidia Firewall. nVidia Firewall always causes blue screen. You had better uninstall nVidia Firewall.  Install Sygate Firewall and it is stable firewall.

Hi sloppy,

I agree with cpc2004 about the uninstallation of Nvidia Firewall.

About a new firewall if you want an option also is Zone Alarm.

Miguel

One minidump is crashed with double fault and probaly it is caused by faulty ram. You had better run memtest to stress test the ram. If you have more dumps, attach them at webspace. I want to confirm whether your windows has hidden hardware problem or not.

Mini020506-01.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Mini020506-01.dmp Probably caused by : portcls.sys ( portcls!_SEH_prolog+1a ) <--- faulty ram

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------
BUGCHECK_STR:  0x7f_8
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  DRIVER_FAULT
LAST_CONTROL_TRANSFER:  from b9a5399c to f68c0d08

STACK_TEXT:  
b9a53984 b9a5399c f689c495 b9a539b4 00000000 portcls!_SEH_prolog+0x1a
WARNING: Frame IP not in any known module. Following frames may be wrong.
b9a53988 f689c495 b9a539b4 00000000 00000010 0xb9a5399c
b9a5399c f68a540a 00000001 865f327c f689ca55 ks!PerformLockedOperation+0xea
b9a539c4 f68d1d92 84f4a008 865f3274 00000001 ks!KsDisableEvent+0x51
b9a539dc f68d1d69 84f4a008 b9a539f4 8669a8c0 portcls!PcHandleDisableEventWithTable+0x1f
b9a53a08 f68cf69d 85290218 8669a8c0 84f4a008 portcls!CPortFilterTopology::DeviceIoControl+0x65
b9a53a24 f68a4f0f 8669a8c0 84f4a008 b9a53a4c portcls!DispatchDeviceIoControl+0x49
b9a53a34 f68cf880 8669a8c0 84f4a008 84f4a150 ks!KsDispatchIrp+0x126
b9a53a4c f68cf841 8669a8c0 84f4a008 b9a53a78 portcls!KsoDispatchIrp+0x43
b9a53a5c f68e4f6f 8669a8c0 84f4a008 00000000 portcls!PcDispatchIrp+0x5f
b9a53a78 804eddf9 8669a8c0 002f000b 84f4a008 ALCXWDM+0x1f6f
b9a53a88 b9dd0774 00000000 00000000 84f4a008 nt!IopfCallDriver+0x31
b9a53ad8 b9dd218e 84f4a008 00000000 e16e5e58 sysaudio!ForwardIrpNode+0x1b2
b9a53b2c f68a4f85 852ad528 84f4a008 b9a53b78 sysaudio!CFilterInstance::FilterDispatchIoControl+0x14c
b9a53b3c 804eddf9 852ad528 84f4a008 84f4a008 ks!DispatchDeviceIoControl+0x28
b9a53b4c f68a5c47 85214510 00000000 8675be70 nt!IopfCallDriver+0x31
b9a53b78 b9d64b20 8667f900 00000000 002f000b ks!KsSynchronousIoControlDevice+0xbd
b9a53ba0 b9d64ae0 8667f900 00000015 85214550 wdmaud!kmxlDisableControlChange+0x21
b9a53bc0 b9d6473b e29fe2f8 00000000 85397b8c wdmaud!kmxlDisableControlChangeNotifications+0x49
b9a53bd8 b9d60407 e29fe2f8 85396000 85398b8c wdmaud!kmxlFreeControl+0x10
b9a53bf0 b9d646c0 85397b8c 85398b8c 85396000 wdmaud!kmxlDeInit+0x47
b9a53c20 b9d5bcd4 853960c0 e32711d0 00000004 wdmaud!RemoveDevNode+0x174
b9a53c4c b9d5f9c4 e32711d0 86628558 85c517e0 wdmaud!WdmaContextCleanup+0x72
b9a53c60 804eddf9 852b1f10 84d8f008 84d8f008 wdmaud!SoundDispatchCleanup+0x31
b9a53c70 80577ad6 86628540 867b2560 00000001 nt!IopfCallDriver+0x31
b9a53ca4 805b0beb 852ca950 852b1f10 0012019f nt!IopCloseFile+0x27c
b9a53cd4 805b053f 852ca950 86628558 867b2560 nt!ObpDecrementHandleCount+0x119
b9a53cfc 805b05dd e1726f80 86628558 000002a4 nt!ObpCloseHandleTableEntry+0x14d
b9a53d44 805b0715 000002a4 00000001 00000000 nt!ObpCloseHandle+0x87
b9a53d58 8053c808 000002a4 0007fd40 7c90eb94 nt!NtClose+0x1d
b9a53d58 7c90eb94 000002a4 0007fd40 7c90eb94 nt!KiFastCallEntry+0xf8
0007fd40 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
portcls!_SEH_prolog+1a
f68c0d08 53               push    ebx

SYMBOL_STACK_INDEX:  0
FOLLOWUP_NAME:  MachineOwner
SYMBOL_NAME:  portcls!_SEH_prolog+1a
MODULE_NAME:  portcls
IMAGE_NAME:  portcls.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  41107f13
STACK_COMMAND:  kb
FAILURE_BUCKET_ID:  0x7f_8_portcls!_SEH_prolog+1a
BUCKET_ID:  0x7f_8_portcls!_SEH_prolog+1a

Followup: MachineOwner
---------
kd> r
eax=8657f558 ebx=00000000 ecx=f68c0d02 edx=8657f558 esi=865f3274 edi=86641920
eip=f68c0d08 esp=334d441c ebp=b9a53984 iopl=0         nv up ei pl nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010212
portcls!_SEH_prolog+0x1a:
f68c0d08 53               push    ebx

Thanks Both; i'll uninstall nvida forceware network manager (i assume this is the firewall) and leave my computer on all day tommorow (with MSN on and email checking at regular intervals so as to make some IP traffic.)

If the problem doesn't re-occur while i'm in work i'll close and accept answer.

Thanks!

System has been up all day with no errors;

Increasing points to  250 and splitting evenly between both (125 each).

Thanks both.

hi, I also have same problem. Can you help me?