none
Windows Server 2008 R2 STD BSOD crash reason RRS feed

  • Question

  • Hi Everyone, 

    Recently our Server started to crash. I have managed to get DMP file analized, but now i am not sure what is actually causing it to crash, can anyone help me with this DMP file, i need to find out is this specialized software we use "TP Shell" is causing crashes or this file win32k.sys is causing problems. If this win32k.sys file crashes, i please for help what is this file about? And possible fix senarios. Thank you. I cant really restore server to earlier point of time it will cause all production a hassle.

    Here is my dmp file:


    Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*f:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (16 procs) Free x64
    Product: LanManNt, suite: TerminalServer
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`01856000 PsLoadedModuleList = 0xfffff800`01a9a670
    Debug session time: Sun Oct  7 07:22:32.513 2012 (UTC + 3:00)
    System Uptime: 2 days 9:56:46.865
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000007ff`fffdd018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 3B, {c0000005, fffff960000bd010, fffff8800e684c10, 0}

    Page 1632 not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : win32k.sys ( win32k!xxxProcessEventMessage+1c0 )

    Followup: MachineOwner
    ---------

    12: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960000bd010, Address of the instruction which caused the bugcheck
    Arg3: fffff8800e684c10, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    CONTEXT:  fffff8800e684c10 -- (.cxr 0xfffff8800e684c10)
    rax=fffff8800e685640 rbx=0000000000000000 rcx=fffff8800e685598
    rdx=fffff900c0a0c010 rsi=0000000000000001 rdi=0000000000000000
    rip=fffff960000bd010 rsp=fffff8800e6855f0 rbp=fffff8800e685790
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffff8800e685510 r12=fffff900c2059c20 r13=fffff8800e685b68
    r14=fffff900c2059c20 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    win32k!xxxProcessEventMessage+0x1c0:
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi ds:002b:00000000`00000008=????????
    Resetting default scope

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x3B

    PROCESS_NAME:  TP.Shell.XAF.W

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff960000d0b6d to fffff960000bd010

    STACK_TEXT:  
    fffff880`0e6855f0 fffff960`000d0b6d : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000018 : win32k!xxxProcessEventMessage+0x1c0
    fffff880`0e6856c0 fffff960`0010b747 : fffff900`c2059c20 fffff880`0e685b68 fffff900`c0a066e0 00000000`00000400 : win32k!xxxScanSysQueue+0x575
    fffff880`0e685a00 fffff960`0010bbd5 : 00000000`00000400 fffff800`000020c8 00000000`00000400 fffffa80`00007fff : win32k!xxxRealInternalGetMessage+0x453
    fffff880`0e685ae0 fffff960`00104627 : 00000000`00000000 00000000`00000000 fffff900`c0a09c30 fffff900`c01194a0 : win32k!xxxInternalGetMessage+0x35
    fffff880`0e685b20 fffff800`018d4453 : fffffa80`13d75b00 00000000`001dc6b8 fffff880`0e685bc8 00000000`00000000 : win32k!NtUserPeekMessage+0x77
    fffff880`0e685bb0 00000000`772f908a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`001dc698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772f908a


    FOLLOWUP_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  win32k!xxxProcessEventMessage+1c0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME:  win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5006fd0d

    STACK_COMMAND:  .cxr 0xfffff8800e684c10 ; kb

    FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    Followup: MachineOwner
    ---------

    12: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960000bd010, Address of the instruction which caused the bugcheck
    Arg3: fffff8800e684c10, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    CONTEXT:  fffff8800e684c10 -- (.cxr 0xfffff8800e684c10)
    rax=fffff8800e685640 rbx=0000000000000000 rcx=fffff8800e685598
    rdx=fffff900c0a0c010 rsi=0000000000000001 rdi=0000000000000000
    rip=fffff960000bd010 rsp=fffff8800e6855f0 rbp=fffff8800e685790
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffff8800e685510 r12=fffff900c2059c20 r13=fffff8800e685b68
    r14=fffff900c2059c20 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    win32k!xxxProcessEventMessage+0x1c0:
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi ds:002b:00000000`00000008=????????
    Resetting default scope

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x3B

    PROCESS_NAME:  TP.Shell.XAF.W

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff960000d0b6d to fffff960000bd010

    STACK_TEXT:  
    fffff880`0e6855f0 fffff960`000d0b6d : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000018 : win32k!xxxProcessEventMessage+0x1c0
    fffff880`0e6856c0 fffff960`0010b747 : fffff900`c2059c20 fffff880`0e685b68 fffff900`c0a066e0 00000000`00000400 : win32k!xxxScanSysQueue+0x575
    fffff880`0e685a00 fffff960`0010bbd5 : 00000000`00000400 fffff800`000020c8 00000000`00000400 fffffa80`00007fff : win32k!xxxRealInternalGetMessage+0x453
    fffff880`0e685ae0 fffff960`00104627 : 00000000`00000000 00000000`00000000 fffff900`c0a09c30 fffff900`c01194a0 : win32k!xxxInternalGetMessage+0x35
    fffff880`0e685b20 fffff800`018d4453 : fffffa80`13d75b00 00000000`001dc6b8 fffff880`0e685bc8 00000000`00000000 : win32k!NtUserPeekMessage+0x77
    fffff880`0e685bb0 00000000`772f908a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`001dc698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772f908a


    FOLLOWUP_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  win32k!xxxProcessEventMessage+1c0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME:  win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5006fd0d

    STACK_COMMAND:  .cxr 0xfffff8800e684c10 ; kb

    FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    Followup: MachineOwner
    ---------

    12: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960000bd010, Address of the instruction which caused the bugcheck
    Arg3: fffff8800e684c10, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    CONTEXT:  fffff8800e684c10 -- (.cxr 0xfffff8800e684c10)
    rax=fffff8800e685640 rbx=0000000000000000 rcx=fffff8800e685598
    rdx=fffff900c0a0c010 rsi=0000000000000001 rdi=0000000000000000
    rip=fffff960000bd010 rsp=fffff8800e6855f0 rbp=fffff8800e685790
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffff8800e685510 r12=fffff900c2059c20 r13=fffff8800e685b68
    r14=fffff900c2059c20 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    win32k!xxxProcessEventMessage+0x1c0:
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi ds:002b:00000000`00000008=????????
    Resetting default scope

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x3B

    PROCESS_NAME:  TP.Shell.XAF.W

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff960000d0b6d to fffff960000bd010

    STACK_TEXT:  
    fffff880`0e6855f0 fffff960`000d0b6d : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000018 : win32k!xxxProcessEventMessage+0x1c0
    fffff880`0e6856c0 fffff960`0010b747 : fffff900`c2059c20 fffff880`0e685b68 fffff900`c0a066e0 00000000`00000400 : win32k!xxxScanSysQueue+0x575
    fffff880`0e685a00 fffff960`0010bbd5 : 00000000`00000400 fffff800`000020c8 00000000`00000400 fffffa80`00007fff : win32k!xxxRealInternalGetMessage+0x453
    fffff880`0e685ae0 fffff960`00104627 : 00000000`00000000 00000000`00000000 fffff900`c0a09c30 fffff900`c01194a0 : win32k!xxxInternalGetMessage+0x35
    fffff880`0e685b20 fffff800`018d4453 : fffffa80`13d75b00 00000000`001dc6b8 fffff880`0e685bc8 00000000`00000000 : win32k!NtUserPeekMessage+0x77
    fffff880`0e685bb0 00000000`772f908a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`001dc698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772f908a


    FOLLOWUP_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  win32k!xxxProcessEventMessage+1c0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME:  win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5006fd0d

    STACK_COMMAND:  .cxr 0xfffff8800e684c10 ; kb

    FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    Followup: MachineOwner
    ---------

    12: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960000bd010, Address of the instruction which caused the bugcheck
    Arg3: fffff8800e684c10, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    CONTEXT:  fffff8800e684c10 -- (.cxr 0xfffff8800e684c10)
    rax=fffff8800e685640 rbx=0000000000000000 rcx=fffff8800e685598
    rdx=fffff900c0a0c010 rsi=0000000000000001 rdi=0000000000000000
    rip=fffff960000bd010 rsp=fffff8800e6855f0 rbp=fffff8800e685790
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffff8800e685510 r12=fffff900c2059c20 r13=fffff8800e685b68
    r14=fffff900c2059c20 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    win32k!xxxProcessEventMessage+0x1c0:
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi ds:002b:00000000`00000008=????????
    Resetting default scope

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x3B

    PROCESS_NAME:  TP.Shell.XAF.W

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff960000d0b6d to fffff960000bd010

    STACK_TEXT:  
    fffff880`0e6855f0 fffff960`000d0b6d : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000018 : win32k!xxxProcessEventMessage+0x1c0
    fffff880`0e6856c0 fffff960`0010b747 : fffff900`c2059c20 fffff880`0e685b68 fffff900`c0a066e0 00000000`00000400 : win32k!xxxScanSysQueue+0x575
    fffff880`0e685a00 fffff960`0010bbd5 : 00000000`00000400 fffff800`000020c8 00000000`00000400 fffffa80`00007fff : win32k!xxxRealInternalGetMessage+0x453
    fffff880`0e685ae0 fffff960`00104627 : 00000000`00000000 00000000`00000000 fffff900`c0a09c30 fffff900`c01194a0 : win32k!xxxInternalGetMessage+0x35
    fffff880`0e685b20 fffff800`018d4453 : fffffa80`13d75b00 00000000`001dc6b8 fffff880`0e685bc8 00000000`00000000 : win32k!NtUserPeekMessage+0x77
    fffff880`0e685bb0 00000000`772f908a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`001dc698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772f908a


    FOLLOWUP_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  win32k!xxxProcessEventMessage+1c0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME:  win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5006fd0d

    STACK_COMMAND:  .cxr 0xfffff8800e684c10 ; kb

    FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    Followup: MachineOwner
    ---------

    12: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960000bd010, Address of the instruction which caused the bugcheck
    Arg3: fffff8800e684c10, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    CONTEXT:  fffff8800e684c10 -- (.cxr 0xfffff8800e684c10)
    rax=fffff8800e685640 rbx=0000000000000000 rcx=fffff8800e685598
    rdx=fffff900c0a0c010 rsi=0000000000000001 rdi=0000000000000000
    rip=fffff960000bd010 rsp=fffff8800e6855f0 rbp=fffff8800e685790
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffff8800e685510 r12=fffff900c2059c20 r13=fffff8800e685b68
    r14=fffff900c2059c20 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    win32k!xxxProcessEventMessage+0x1c0:
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi ds:002b:00000000`00000008=????????
    Resetting default scope

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x3B

    PROCESS_NAME:  TP.Shell.XAF.W

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff960000d0b6d to fffff960000bd010

    STACK_TEXT:  
    fffff880`0e6855f0 fffff960`000d0b6d : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000018 : win32k!xxxProcessEventMessage+0x1c0
    fffff880`0e6856c0 fffff960`0010b747 : fffff900`c2059c20 fffff880`0e685b68 fffff900`c0a066e0 00000000`00000400 : win32k!xxxScanSysQueue+0x575
    fffff880`0e685a00 fffff960`0010bbd5 : 00000000`00000400 fffff800`000020c8 00000000`00000400 fffffa80`00007fff : win32k!xxxRealInternalGetMessage+0x453
    fffff880`0e685ae0 fffff960`00104627 : 00000000`00000000 00000000`00000000 fffff900`c0a09c30 fffff900`c01194a0 : win32k!xxxInternalGetMessage+0x35
    fffff880`0e685b20 fffff800`018d4453 : fffffa80`13d75b00 00000000`001dc6b8 fffff880`0e685bc8 00000000`00000000 : win32k!NtUserPeekMessage+0x77
    fffff880`0e685bb0 00000000`772f908a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`001dc698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772f908a


    FOLLOWUP_IP: 
    win32k!xxxProcessEventMessage+1c0
    fffff960`000bd010 017308          add     dword ptr [rbx+8],esi

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  win32k!xxxProcessEventMessage+1c0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME:  win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5006fd0d

    STACK_COMMAND:  .cxr 0xfffff8800e684c10 ; kb

    FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    BUCKET_ID:  X64_0x3B_win32k!xxxProcessEventMessage+1c0

    Followup: MachineOwner
    ---------

    Looking forward to your comments, if we agree that its Tp Shell software fault, i will handle problem to vendor of this software, but i need to be sure, if its not, i will have to contact MS support, but i rather not.


    Saturday, October 13, 2012 3:13 PM

All replies

  • TP.Shell.XAF.exe is a .Net C#  application that I wrote. 

    It is being executed as a Remote app.

    To my understanding - the dump says, that the process cannot access a page in memory. 
    Since it's a .Net app, and by it's definition, is a managed application (meaning that .Net framework take's care of managing resources)
    I find it highly doubtful, that there might be something inside the app causing this.

    I must mention that the app is hungry on resources, and 1 instance of it use 500-700Mb of RAM, and usually we have like 5 instances of it running daily.

    Can it be so, that .Net framework got corrupted ? or has some sort of the bug ? 

    Monday, October 15, 2012 7:16 AM