locked
BugcheckCode 127 RRS feed

  • Question

  • I keep getting random BSOD's..and have tried Replacing the power pack for a 1000 watt.. it wasnt that, ive changed the paist on the PCU with no afect..and it's happning nearly daily witch cant be good for my system..havnt got a clue what is causen it..got this from Event viewer ..

     

    Log Name:      System

    Source:        Microsoft-Windows-Kernel-Power

    Date:          20/02/2011 17:03:43

    Event ID:      41

    Task Category: (63)

    Level:         Critical

    Keywords:      (2)

    User:          SYSTEM

    Computer:      B1gg5y-PC

    Description:

    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />

        <EventID>41</EventID>

        <Version>2</Version>

        <Level>1</Level>

        <Task>63</Task>

        <Opcode>0</Opcode>

        <Keywords>0x8000000000000002</Keywords>

        <TimeCreated SystemTime="2011-02-20T17:03:43.777200000Z" />

        <EventRecordID>83908</EventRecordID>

        <Correlation />

        <Execution ProcessID="4" ThreadID="8" />

        <Channel>System</Channel>

        <Computer>B1gg5y-PC</Computer>

        <Security UserID="S-1-5-18" />

      </System>

      <EventData>

        <Data Name="BugcheckCode">127</Data>

        <Data Name="BugcheckParameter1">0x8</Data>

        <Data Name="BugcheckParameter2">0x80050031</Data>

        <Data Name="BugcheckParameter3">0x6f8</Data>

        <Data Name="BugcheckParameter4">0xfffff80002e83e3b</Data>

        <Data Name="SleepInProgress">false</Data>

        <Data Name="PowerButtonTimestamp">0</Data>

      </EventData>

    </Event>

     

     

    any help would be greatful

    Sunday, February 20, 2011 7:31 PM

Answers

  • I was right. It is ZoneAlarm. vsdatant = ZoneAlarm

    1: kd> k
    Child-SP          RetAddr           Call Site
    fffff880`009edc68 fffff800`02e7cca9 nt!KeBugCheckEx
    fffff880`009edc70 fffff800`02e7b172 nt!KiBugCheckDispatch+0x69
    fffff880`009eddb0 fffff800`02e83e3b nt!KiDoubleFaultAbort+0xb2
    fffff880`14820000 fffff800`02e831e4 nt!SepNormalAccessCheck+0xb
    fffff880`14820010 fffff800`02e82c10 nt!SepAccessCheck+0x1d4
    fffff880`14820140 fffff800`02e45f5a nt!SeAccessCheckWithHint+0x180
    fffff880`14820220 fffff880`01706c5a nt!SeAccessCheckFromState+0x102
    fffff880`14820910 fffff880`0170494f NETIO!CompareSecurityContexts+0x6a
    fffff880`14820980 fffff880`017069b5 NETIO!MatchValues+0xef
    fffff880`148209d0 fffff880`01706845 NETIO!FilterMatch+0x95
    fffff880`14820a20 fffff880`01707ccb NETIO!IndexListClassify+0x69
    fffff880`14820aa0 fffff880`0183d417 NETIO!KfdClassify+0xa4e
    fffff880`14820e10 fffff880`0183683e tcpip!WfpAleClassify+0x57
    fffff880`14820e50 fffff880`01835cd5 tcpip!WfpAlepAuthorizeSend+0x94e
    fffff880`14821560 fffff880`01839886 tcpip!WfpAleAuthorizeSend+0x325
    fffff880`14821830 fffff880`0183c5e4 tcpip!WfpAleConnectAcceptIndicate+0x106
    fffff880`14821920 fffff880`01835019 tcpip!ProcessALEForTransportPacket+0x664
    fffff880`14821b90 fffff880`01863ef6 tcpip!WfpProcessOutTransportStackIndication+0x329
    fffff880`14821d60 fffff880`018691ee tcpip!IppSendDatagramsCommon+0x526
    fffff880`14822030 fffff880`01833db8 tcpip!IpNlpSendDatagrams+0x3e
    fffff880`14822070 fffff880`0183432d tcpip!UdpSendMessagesOnPathCreation+0x688
    fffff880`148223f0 fffff880`01833fb5 tcpip!UdpSendMessages+0x35d
    fffff880`148227e0 fffff800`02e8ce5a tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
    fffff880`14822810 fffff880`01834578 nt!KeExpandKernelStackAndCalloutEx+0xda
    fffff880`148228f0 fffff880`02ceff45 tcpip!UdpTlProviderSendMessages+0x78
    fffff880`14822970 fffff880`02cefff2 tdx!TdxSendDatagramTransportAddress+0x2f5
    fffff880`14822a50 fffff880`02d1a542 tdx!TdxTdiDispatchInternalDeviceControl+0x52
    fffff880`14822a80 fffff880`02d1af61 netbt!TdiSendDatagram+0x187
    fffff880`14822af0 fffff880`02d27329 netbt!UdpSendDatagram+0x1b1
    fffff880`14822b80 fffff880`02d270e6 netbt!UdpSendResponse+0x4e0
    fffff880`14822c00 fffff880`02d1bbe7 netbt!QueryFromNet+0xb11
    fffff880`14822d30 fffff880`02d19b47 netbt!NameSrvHndlrNotOs+0xca
    fffff880`14822d70 fffff880`02cee325 netbt!TdiRcvNameSrvHandler+0x367
    fffff880`14822e10 fffff880`0183f395 tdx!TdxEventReceiveMessagesTransportAddress+0x315
    fffff880`14823000 fffff880`0183f8a4 tcpip!UdpDeliverDatagrams+0x155
    fffff880`14823190 fffff880`0185d727 tcpip!UdpReceiveDatagrams+0x324
    fffff880`14823280 fffff880`0185d799 tcpip!IppDeliverListToProtocol+0xf7
    fffff880`14823340 fffff880`0185dc90 tcpip!IppProcessDeliverList+0x59
    fffff880`148233b0 fffff880`0185cb21 tcpip!IppReceiveHeaderBatch+0x231
    fffff880`14823490 fffff880`01934542 tcpip!IpFlcReceivePackets+0x651
    fffff880`14823690 fffff880`01794afa tcpip!IppInspectInjectReceive+0xf2
    fffff880`148236d0 fffff880`02c1637f fwpkclnt!FwpsInjectTransportReceiveAsync0+0x256
    fffff880`14823780 fffff880`02c1559c vsdatant+0x1637f
    fffff880`14823810 fffff880`02c0eca1 vsdatant+0x1559c
    fffff880`14823910 fffff880`0171d57f vsdatant+0xeca1

    fffff880`14823a40 fffff880`01706619 NETIO! ?? ::FNODOBFM::`string'+0x7267
    fffff880`14823b60 fffff880`01707bb1 NETIO!ArbitrateAndEnforce+0x2a9
    fffff880`14823c30 fffff880`018fefbb NETIO!KfdClassify+0x934
    fffff880`14823fa0 fffff880`01802d10 tcpip!WFPDatagramDataShimV4+0x49b
    fffff880`14824300 fffff880`0187e73d tcpip! ?? ::FNODOBFM::`string'+0x2b43f
    fffff880`14824570 fffff880`0183e050 tcpip!ProcessAleForNonTcpIn+0x1ad
    fffff880`14824690 fffff880`0186efe1 tcpip!WfpProcessInTransportStackIndication+0xb10
    fffff880`14824a00 fffff880`0183ef63 tcpip!InetInspectReceiveDatagram+0x121
    fffff880`14824aa0 fffff880`0183f315 tcpip!UdpBeginMessageIndication+0x83
    fffff880`14824bf0 fffff880`0183f8a4 tcpip!UdpDeliverDatagrams+0xd5
    fffff880`14824d80 fffff880`0185d727 tcpip!UdpReceiveDatagrams+0x324
    fffff880`14824e70 fffff880`0185d799 tcpip!IppDeliverListToProtocol+0xf7
    fffff880`14824f30 fffff880`0185dc90 tcpip!IppProcessDeliverList+0x59
    fffff880`14824fa0 fffff880`0185cb21 tcpip!IppReceiveHeaderBatch+0x231
    fffff880`14825080 fffff880`0185b592 tcpip!IpFlcReceivePackets+0x651
    fffff880`14825280 fffff880`01874e5a tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`14825360 fffff800`02e8ce5a tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`148253b0 fffff880`01874882 nt!KeExpandKernelStackAndCalloutEx+0xda
    fffff880`14825490 fffff880`016cc0eb tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`14825500 fffff880`01695fc6 ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`14825570 fffff880`0160fef1 ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    fffff880`148259f0 fffff880`03d7dd58 ndis!NdisMIndicateReceiveNetBufferLists+0xc1
    fffff880`14825a40 fffff880`03da2fbc nvmf6264 +0x4d58
    fffff880`14825a90 fffff880`03da2ae2 nvmf6264!PARAM_InitClient+0x1bfdc
    fffff880`14825b50 fffff880`01698d02 nvmf6264!PARAM_InitClient+0x1bb02
    fffff880`14825ba0 fffff880`01620bfd ndis!ndisMiniportDpc+0xe2

        Image path: \SystemRoot\system32\DRIVERS\vsdatant.sys
        Image name: vsdatant.sys
        Timestamp:        Sun May 09 18:28:58 2010 (4BE6E2CA)
        CheckSum:         0007FD21
        ImageSize:        00095000
        File version:     9.2.31.0
        Product version:  9.2.31.0
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.0 Driver
        File date:        00000000.00000000
        Translations:     0409.04e4
        CompanyName:      Check Point Software Technologies LTD
        ProductName:      ZoneAlarm Firewalling Driver
        InternalName:     VSDATANT.SYS
        OriginalFilename: VSDATANT.SYS
        ProductVersion:   9.2.031.000
        FileVersion:      9.2.031.000
        FileDescription:  ZoneAlarm Firewalling Driver
        LegalCopyright:   Copyright ? 1998-2010, Check Point, LTD

    update the network card driver:

        Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
        Image name: nvmf6264.sys
        Timestamp:        Thu Aug 12 13:46:06 2010

    install the hotfix and disable NetBIOS over TCPIP. the latest ZA version is 9.2.102, update ZA. If this all doesn't work, REMOVE ZA .

    Now everything is said from my site. Accept it or life with the crashes!

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Monday, February 21, 2011 4:14 PM
    • Marked as answer by Arthur Xie Friday, February 25, 2011 9:57 AM
    Monday, February 21, 2011 4:14 PM

All replies

  • 127 = 0x7F = Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP

    0x00000008 , or Double Fault , indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:

        * A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault.
        * A hardware problem.

    It may caused by ZoneAlarm, if you have it installed, update the network card drivers first.

    You can also try this Hotfix (if you use Windows 7 RTM) if updating the network driver doesn't fix it:

    Stop error message when you run an application that transfers data by using the UDP protocol in Windows Server 2008 R2 or in Windows 7: "STOP 0x0000007F"

    http://support.microsoft.com/kb/981180/en-us

    When this doesn't fix it, disable NetBIOS over TCP/IP.

    If this also doesn't fix it, remove ZoneAlarm.

    The minidumps are not useful for UNEXPECTED_KERNEL_MODE_TRAP bug checks.

    Configure your Windows to create a kernel dump [1] and upload the zipped dump (C:\Windows\memory.dmp) to your SkyDrive [2] and post a link here when the PC still crashes after removing ZoneAlarm and updating the drivers.

    André

    [1] http://www.brighthub.com/computing/windows-platform/articles/81867.aspx
    [2] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Monday, February 21, 2011 2:16 PM
    Sunday, February 20, 2011 8:18 PM
  • Well i dont think it is Zonealrm, as ive only had in installed for nearly a year and it's only the firwall.. but the PC has been doing this since i built it, it done it on the first day i had it running..

     

    but i will update drivers and stuf and see...but can only find Minidump file...is that the 1 you need ?

    Sunday, February 20, 2011 11:01 PM
  • A small update, i ran memtest and it found no errors.. but i was thinking, it has been doing this ever since i built it and even after i changed cases. im starting to think it might be my HDD, im using the below HDD for my windows 7 installation..i think that might be the issue, i'll replace it in 4 weeks when i get paid and see if it is that,here's hoping !!

     

     

    FUJITSU MHV2080BH PL ATA Device

    Manufacturer Unknown manufacturer

    SATA type SATA-II 3.0Gb/s

    Device type Fixed

    ATA Standard ATA/ATAPI-7

    48-bit LBA Supported

    Serial Number NWAFT692AVFJ

    Interface SATA

    Capacity 78GB

    Real size 80,025,280,000 bytes

     

    Monday, February 21, 2011 12:57 PM
  • It IS ZoneAlarm which causes your issue. Try all 3 steps. Your hardware is ok.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, February 21, 2011 2:17 PM
  • but like i said, ive had the pc for 4 years with the same issue. even when i changed cases... i have only had Zonealarm on the PC for the last year...so i dont see how it cn be Zonealarm when it was doing it befor i installed it..

     

    The only thing that hasnt changed is the HDD...

    Monday, February 21, 2011 2:28 PM
  • have you made the 3 steps? Also change the Dump to to kernel dump and upload the larger dump, so I can say more.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, February 21, 2011 2:32 PM
  • Windows is set to Kernal memory dump already, but i cant find were the file is ...never done this sort of thing..were do i find the file ?
    Monday, February 21, 2011 2:40 PM
  • the filename is C:\Windows\Memory.dmp .

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, February 21, 2011 2:55 PM
  • OK...sorted, hope this is it ..

     

    http://rapidshare.com/files/449124976/Crash_dump.rar

    Monday, February 21, 2011 3:57 PM
  • I was right. It is ZoneAlarm. vsdatant = ZoneAlarm

    1: kd> k
    Child-SP          RetAddr           Call Site
    fffff880`009edc68 fffff800`02e7cca9 nt!KeBugCheckEx
    fffff880`009edc70 fffff800`02e7b172 nt!KiBugCheckDispatch+0x69
    fffff880`009eddb0 fffff800`02e83e3b nt!KiDoubleFaultAbort+0xb2
    fffff880`14820000 fffff800`02e831e4 nt!SepNormalAccessCheck+0xb
    fffff880`14820010 fffff800`02e82c10 nt!SepAccessCheck+0x1d4
    fffff880`14820140 fffff800`02e45f5a nt!SeAccessCheckWithHint+0x180
    fffff880`14820220 fffff880`01706c5a nt!SeAccessCheckFromState+0x102
    fffff880`14820910 fffff880`0170494f NETIO!CompareSecurityContexts+0x6a
    fffff880`14820980 fffff880`017069b5 NETIO!MatchValues+0xef
    fffff880`148209d0 fffff880`01706845 NETIO!FilterMatch+0x95
    fffff880`14820a20 fffff880`01707ccb NETIO!IndexListClassify+0x69
    fffff880`14820aa0 fffff880`0183d417 NETIO!KfdClassify+0xa4e
    fffff880`14820e10 fffff880`0183683e tcpip!WfpAleClassify+0x57
    fffff880`14820e50 fffff880`01835cd5 tcpip!WfpAlepAuthorizeSend+0x94e
    fffff880`14821560 fffff880`01839886 tcpip!WfpAleAuthorizeSend+0x325
    fffff880`14821830 fffff880`0183c5e4 tcpip!WfpAleConnectAcceptIndicate+0x106
    fffff880`14821920 fffff880`01835019 tcpip!ProcessALEForTransportPacket+0x664
    fffff880`14821b90 fffff880`01863ef6 tcpip!WfpProcessOutTransportStackIndication+0x329
    fffff880`14821d60 fffff880`018691ee tcpip!IppSendDatagramsCommon+0x526
    fffff880`14822030 fffff880`01833db8 tcpip!IpNlpSendDatagrams+0x3e
    fffff880`14822070 fffff880`0183432d tcpip!UdpSendMessagesOnPathCreation+0x688
    fffff880`148223f0 fffff880`01833fb5 tcpip!UdpSendMessages+0x35d
    fffff880`148227e0 fffff800`02e8ce5a tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
    fffff880`14822810 fffff880`01834578 nt!KeExpandKernelStackAndCalloutEx+0xda
    fffff880`148228f0 fffff880`02ceff45 tcpip!UdpTlProviderSendMessages+0x78
    fffff880`14822970 fffff880`02cefff2 tdx!TdxSendDatagramTransportAddress+0x2f5
    fffff880`14822a50 fffff880`02d1a542 tdx!TdxTdiDispatchInternalDeviceControl+0x52
    fffff880`14822a80 fffff880`02d1af61 netbt!TdiSendDatagram+0x187
    fffff880`14822af0 fffff880`02d27329 netbt!UdpSendDatagram+0x1b1
    fffff880`14822b80 fffff880`02d270e6 netbt!UdpSendResponse+0x4e0
    fffff880`14822c00 fffff880`02d1bbe7 netbt!QueryFromNet+0xb11
    fffff880`14822d30 fffff880`02d19b47 netbt!NameSrvHndlrNotOs+0xca
    fffff880`14822d70 fffff880`02cee325 netbt!TdiRcvNameSrvHandler+0x367
    fffff880`14822e10 fffff880`0183f395 tdx!TdxEventReceiveMessagesTransportAddress+0x315
    fffff880`14823000 fffff880`0183f8a4 tcpip!UdpDeliverDatagrams+0x155
    fffff880`14823190 fffff880`0185d727 tcpip!UdpReceiveDatagrams+0x324
    fffff880`14823280 fffff880`0185d799 tcpip!IppDeliverListToProtocol+0xf7
    fffff880`14823340 fffff880`0185dc90 tcpip!IppProcessDeliverList+0x59
    fffff880`148233b0 fffff880`0185cb21 tcpip!IppReceiveHeaderBatch+0x231
    fffff880`14823490 fffff880`01934542 tcpip!IpFlcReceivePackets+0x651
    fffff880`14823690 fffff880`01794afa tcpip!IppInspectInjectReceive+0xf2
    fffff880`148236d0 fffff880`02c1637f fwpkclnt!FwpsInjectTransportReceiveAsync0+0x256
    fffff880`14823780 fffff880`02c1559c vsdatant+0x1637f
    fffff880`14823810 fffff880`02c0eca1 vsdatant+0x1559c
    fffff880`14823910 fffff880`0171d57f vsdatant+0xeca1

    fffff880`14823a40 fffff880`01706619 NETIO! ?? ::FNODOBFM::`string'+0x7267
    fffff880`14823b60 fffff880`01707bb1 NETIO!ArbitrateAndEnforce+0x2a9
    fffff880`14823c30 fffff880`018fefbb NETIO!KfdClassify+0x934
    fffff880`14823fa0 fffff880`01802d10 tcpip!WFPDatagramDataShimV4+0x49b
    fffff880`14824300 fffff880`0187e73d tcpip! ?? ::FNODOBFM::`string'+0x2b43f
    fffff880`14824570 fffff880`0183e050 tcpip!ProcessAleForNonTcpIn+0x1ad
    fffff880`14824690 fffff880`0186efe1 tcpip!WfpProcessInTransportStackIndication+0xb10
    fffff880`14824a00 fffff880`0183ef63 tcpip!InetInspectReceiveDatagram+0x121
    fffff880`14824aa0 fffff880`0183f315 tcpip!UdpBeginMessageIndication+0x83
    fffff880`14824bf0 fffff880`0183f8a4 tcpip!UdpDeliverDatagrams+0xd5
    fffff880`14824d80 fffff880`0185d727 tcpip!UdpReceiveDatagrams+0x324
    fffff880`14824e70 fffff880`0185d799 tcpip!IppDeliverListToProtocol+0xf7
    fffff880`14824f30 fffff880`0185dc90 tcpip!IppProcessDeliverList+0x59
    fffff880`14824fa0 fffff880`0185cb21 tcpip!IppReceiveHeaderBatch+0x231
    fffff880`14825080 fffff880`0185b592 tcpip!IpFlcReceivePackets+0x651
    fffff880`14825280 fffff880`01874e5a tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`14825360 fffff800`02e8ce5a tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`148253b0 fffff880`01874882 nt!KeExpandKernelStackAndCalloutEx+0xda
    fffff880`14825490 fffff880`016cc0eb tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`14825500 fffff880`01695fc6 ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`14825570 fffff880`0160fef1 ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    fffff880`148259f0 fffff880`03d7dd58 ndis!NdisMIndicateReceiveNetBufferLists+0xc1
    fffff880`14825a40 fffff880`03da2fbc nvmf6264 +0x4d58
    fffff880`14825a90 fffff880`03da2ae2 nvmf6264!PARAM_InitClient+0x1bfdc
    fffff880`14825b50 fffff880`01698d02 nvmf6264!PARAM_InitClient+0x1bb02
    fffff880`14825ba0 fffff880`01620bfd ndis!ndisMiniportDpc+0xe2

        Image path: \SystemRoot\system32\DRIVERS\vsdatant.sys
        Image name: vsdatant.sys
        Timestamp:        Sun May 09 18:28:58 2010 (4BE6E2CA)
        CheckSum:         0007FD21
        ImageSize:        00095000
        File version:     9.2.31.0
        Product version:  9.2.31.0
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.0 Driver
        File date:        00000000.00000000
        Translations:     0409.04e4
        CompanyName:      Check Point Software Technologies LTD
        ProductName:      ZoneAlarm Firewalling Driver
        InternalName:     VSDATANT.SYS
        OriginalFilename: VSDATANT.SYS
        ProductVersion:   9.2.031.000
        FileVersion:      9.2.031.000
        FileDescription:  ZoneAlarm Firewalling Driver
        LegalCopyright:   Copyright ? 1998-2010, Check Point, LTD

    update the network card driver:

        Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
        Image name: nvmf6264.sys
        Timestamp:        Thu Aug 12 13:46:06 2010

    install the hotfix and disable NetBIOS over TCPIP. the latest ZA version is 9.2.102, update ZA. If this all doesn't work, REMOVE ZA .

    Now everything is said from my site. Accept it or life with the crashes!

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Monday, February 21, 2011 4:14 PM
    • Marked as answer by Arthur Xie Friday, February 25, 2011 9:57 AM
    Monday, February 21, 2011 4:14 PM
  • OK...just to be safe i have uninstalled ZA and updated the Nforce drivers.. and ive now installed Comodo Firewall...so only time will tell !
    Monday, February 21, 2011 5:56 PM
  • Quick update !! 

     

    DUDE..you are the man, all sorted.

     

    Thanx alot : )

    Friday, March 4, 2011 2:17 PM