none
BSOD 0x 50 con TmPreFlt e tmcomm.sys su Windows Server 2008 Enterprise RRS feed

  • Discussione generale

  • Mi è apparso questo BSOD al riavvio di windows server 2008 ( che uso come terminal server):

     

    PAGE_FAULT_IN_NONPAGED_AREA

    STOP: 0X00000050 (0XE8E43608,0X00000000,=0X825C9299,0X00000000)

    Collecting data for crash dump.

     

    Dispongo di un file minidump...ma non riesco a leggerlo..  

    Qualcuno mi puo' aiutare??? 

    Grazie in anticipo

    • Modificato Anca Popa mercoledì 23 novembre 2011 11:50 titolo
    • Tipo modificato Anca Popa giovedì 24 novembre 2011 13:42 domanda inoltrata anche nel forum sysadmin
    lunedì 21 novembre 2011 14:23

Tutte le risposte

  • Sono riuscito a leggere il file nella cartella minidump.   Credo che non riesca ad individuare il "FAULTY" driver... eccolo qui:...

    =====================================================================================


    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini112111-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 6002 (Service Pack 2) MP (16 procs) Free x86 compatible
    Product: Server, suite: Enterprise TerminalServer
    Built by: 6002.18484.x86fre.vistasp2_gdr.110617-0336
    Kernel base = 0x8244d000 PsLoadedModuleList = 0x82564c70
    Debug session time: Sun Nov 20 16:45:35.383 2011 (GMT+1)
    System Uptime: 10 days 1:13:35.633
    Loading Kernel Symbols
    ..............................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 10000050, {e8e43608, 0, 825c9299, 0}


    Could not read faulting driver name
    Probably caused by : ntkrpamp.exe ( nt!CmpCheckKey+61b )

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e8e43608, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 825c9299, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name

    OVERLAPPED_MODULE: Address regions for 'TmPreFlt' and 'tmcomm.sys' overlap

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82584868
    Unable to read MiSystemVaType memory at 82564420
     e8e43608

    FAULTING_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 825cf7f4 to 825c9299

    STACK_TEXT: 
    97e27a8c 825cf7f4 01000001 005825e0 00000248 nt!CmpCheckKey+0x61b
    97e27abc 825cfe22 c4896198 01000001 00000004 nt!CmpCheckRegistry2+0x8c
    97e27b04 825ca848 01000001 97e27c60 800029a4 nt!CmCheckRegistry+0xf5
    97e27b60 825ccfb7 97e27bb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
    97e27bd8 825cf257 97e27c60 00000000 97e27c4c nt!CmpInitHiveFromFile+0x19e
    97e27c18 825c549f 97e27c60 00000000 97e27c7b nt!CmpCmdHiveOpen+0x36
    97e27d14 825c56d4 00000002 825455a0 00000002 nt!CmpFlushBackupHive+0x2fd
    97e27d38 826a4b01 8254f13c 8ed8e828 824f2e22 nt!CmpSyncBackupHives+0x90
    97e27d44 824f2e22 00000000 00000000 8ed8e828 nt!CmpPeriodicBackupFlushWorker+0x32
    97e27d7c 82622fe2 00000000 f635cdf9 00000000 nt!ExpWorkerThread+0xfd
    97e27dc0 8248befe 824f2d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!CmpCheckKey+61b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb5603

    FAILURE_BUCKET_ID:  0x50_nt!CmpCheckKey+61b

    BUCKET_ID:  0x50_nt!CmpCheckKey+61b

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e8e43608, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 825c9299, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name

    OVERLAPPED_MODULE: Address regions for 'TmPreFlt' and 'tmcomm.sys' overlap

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82584868
    Unable to read MiSystemVaType memory at 82564420
     e8e43608

    FAULTING_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 825cf7f4 to 825c9299

    STACK_TEXT: 
    97e27a8c 825cf7f4 01000001 005825e0 00000248 nt!CmpCheckKey+0x61b
    97e27abc 825cfe22 c4896198 01000001 00000004 nt!CmpCheckRegistry2+0x8c
    97e27b04 825ca848 01000001 97e27c60 800029a4 nt!CmCheckRegistry+0xf5
    97e27b60 825ccfb7 97e27bb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
    97e27bd8 825cf257 97e27c60 00000000 97e27c4c nt!CmpInitHiveFromFile+0x19e
    97e27c18 825c549f 97e27c60 00000000 97e27c7b nt!CmpCmdHiveOpen+0x36
    97e27d14 825c56d4 00000002 825455a0 00000002 nt!CmpFlushBackupHive+0x2fd
    97e27d38 826a4b01 8254f13c 8ed8e828 824f2e22 nt!CmpSyncBackupHives+0x90
    97e27d44 824f2e22 00000000 00000000 8ed8e828 nt!CmpPeriodicBackupFlushWorker+0x32
    97e27d7c 82622fe2 00000000 f635cdf9 00000000 nt!ExpWorkerThread+0xfd
    97e27dc0 8248befe 824f2d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!CmpCheckKey+61b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb5603

    FAILURE_BUCKET_ID:  0x50_nt!CmpCheckKey+61b

    BUCKET_ID:  0x50_nt!CmpCheckKey+61b

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e8e43608, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 825c9299, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name

    OVERLAPPED_MODULE: Address regions for 'TmPreFlt' and 'tmcomm.sys' overlap

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82584868
    Unable to read MiSystemVaType memory at 82564420
     e8e43608

    FAULTING_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 825cf7f4 to 825c9299

    STACK_TEXT: 
    97e27a8c 825cf7f4 01000001 005825e0 00000248 nt!CmpCheckKey+0x61b
    97e27abc 825cfe22 c4896198 01000001 00000004 nt!CmpCheckRegistry2+0x8c
    97e27b04 825ca848 01000001 97e27c60 800029a4 nt!CmCheckRegistry+0xf5
    97e27b60 825ccfb7 97e27bb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
    97e27bd8 825cf257 97e27c60 00000000 97e27c4c nt!CmpInitHiveFromFile+0x19e
    97e27c18 825c549f 97e27c60 00000000 97e27c7b nt!CmpCmdHiveOpen+0x36
    97e27d14 825c56d4 00000002 825455a0 00000002 nt!CmpFlushBackupHive+0x2fd
    97e27d38 826a4b01 8254f13c 8ed8e828 824f2e22 nt!CmpSyncBackupHives+0x90
    97e27d44 824f2e22 00000000 00000000 8ed8e828 nt!CmpPeriodicBackupFlushWorker+0x32
    97e27d7c 82622fe2 00000000 f635cdf9 00000000 nt!ExpWorkerThread+0xfd
    97e27dc0 8248befe 824f2d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!CmpCheckKey+61b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb5603

    FAILURE_BUCKET_ID:  0x50_nt!CmpCheckKey+61b

    BUCKET_ID:  0x50_nt!CmpCheckKey+61b

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e8e43608, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 825c9299, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name

    OVERLAPPED_MODULE: Address regions for 'TmPreFlt' and 'tmcomm.sys' overlap

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82584868
    Unable to read MiSystemVaType memory at 82564420
     e8e43608

    FAULTING_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 825cf7f4 to 825c9299

    STACK_TEXT: 
    97e27a8c 825cf7f4 01000001 005825e0 00000248 nt!CmpCheckKey+0x61b
    97e27abc 825cfe22 c4896198 01000001 00000004 nt!CmpCheckRegistry2+0x8c
    97e27b04 825ca848 01000001 97e27c60 800029a4 nt!CmCheckRegistry+0xf5
    97e27b60 825ccfb7 97e27bb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
    97e27bd8 825cf257 97e27c60 00000000 97e27c4c nt!CmpInitHiveFromFile+0x19e
    97e27c18 825c549f 97e27c60 00000000 97e27c7b nt!CmpCmdHiveOpen+0x36
    97e27d14 825c56d4 00000002 825455a0 00000002 nt!CmpFlushBackupHive+0x2fd
    97e27d38 826a4b01 8254f13c 8ed8e828 824f2e22 nt!CmpSyncBackupHives+0x90
    97e27d44 824f2e22 00000000 00000000 8ed8e828 nt!CmpPeriodicBackupFlushWorker+0x32
    97e27d7c 82622fe2 00000000 f635cdf9 00000000 nt!ExpWorkerThread+0xfd
    97e27dc0 8248befe 824f2d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!CmpCheckKey+61b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb5603

    FAILURE_BUCKET_ID:  0x50_nt!CmpCheckKey+61b

    BUCKET_ID:  0x50_nt!CmpCheckKey+61b

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e8e43608, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 825c9299, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name

    OVERLAPPED_MODULE: Address regions for 'TmPreFlt' and 'tmcomm.sys' overlap

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82584868
    Unable to read MiSystemVaType memory at 82564420
     e8e43608

    FAULTING_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 825cf7f4 to 825c9299

    STACK_TEXT: 
    97e27a8c 825cf7f4 01000001 005825e0 00000248 nt!CmpCheckKey+0x61b
    97e27abc 825cfe22 c4896198 01000001 00000004 nt!CmpCheckRegistry2+0x8c
    97e27b04 825ca848 01000001 97e27c60 800029a4 nt!CmCheckRegistry+0xf5
    97e27b60 825ccfb7 97e27bb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
    97e27bd8 825cf257 97e27c60 00000000 97e27c4c nt!CmpInitHiveFromFile+0x19e
    97e27c18 825c549f 97e27c60 00000000 97e27c7b nt!CmpCmdHiveOpen+0x36
    97e27d14 825c56d4 00000002 825455a0 00000002 nt!CmpFlushBackupHive+0x2fd
    97e27d38 826a4b01 8254f13c 8ed8e828 824f2e22 nt!CmpSyncBackupHives+0x90
    97e27d44 824f2e22 00000000 00000000 8ed8e828 nt!CmpPeriodicBackupFlushWorker+0x32
    97e27d7c 82622fe2 00000000 f635cdf9 00000000 nt!ExpWorkerThread+0xfd
    97e27dc0 8248befe 824f2d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!CmpCheckKey+61b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb5603

    FAILURE_BUCKET_ID:  0x50_nt!CmpCheckKey+61b

    BUCKET_ID:  0x50_nt!CmpCheckKey+61b

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e8e43608, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 825c9299, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name

    OVERLAPPED_MODULE: Address regions for 'TmPreFlt' and 'tmcomm.sys' overlap

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82584868
    Unable to read MiSystemVaType memory at 82564420
     e8e43608

    FAULTING_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 825cf7f4 to 825c9299

    STACK_TEXT: 
    97e27a8c 825cf7f4 01000001 005825e0 00000248 nt!CmpCheckKey+0x61b
    97e27abc 825cfe22 c4896198 01000001 00000004 nt!CmpCheckRegistry2+0x8c
    97e27b04 825ca848 01000001 97e27c60 800029a4 nt!CmCheckRegistry+0xf5
    97e27b60 825ccfb7 97e27bb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
    97e27bd8 825cf257 97e27c60 00000000 97e27c4c nt!CmpInitHiveFromFile+0x19e
    97e27c18 825c549f 97e27c60 00000000 97e27c7b nt!CmpCmdHiveOpen+0x36
    97e27d14 825c56d4 00000002 825455a0 00000002 nt!CmpFlushBackupHive+0x2fd
    97e27d38 826a4b01 8254f13c 8ed8e828 824f2e22 nt!CmpSyncBackupHives+0x90
    97e27d44 824f2e22 00000000 00000000 8ed8e828 nt!CmpPeriodicBackupFlushWorker+0x32
    97e27d7c 82622fe2 00000000 f635cdf9 00000000 nt!ExpWorkerThread+0xfd
    97e27dc0 8248befe 824f2d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!CmpCheckKey+61b
    825c9299 394724          cmp     dword ptr [edi+24h],eax

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!CmpCheckKey+61b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb5603

    FAILURE_BUCKET_ID:  0x50_nt!CmpCheckKey+61b

    BUCKET_ID:  0x50_nt!CmpCheckKey+61b

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

    =========================================================================================================

     

    Sper che qualcuno possa aiutarmio !!!!

     

    Grazie...

    lunedì 21 novembre 2011 14:43
  • Ciao aries,

    Dall'analisi del dump direi che siamo in uno scenario noto, e' uscito questo hotfix: Errore in Windows Vista, Windows 7, Windows Server 2008 o Windows Server 2008 R2 irreversibile: "0 x 00000050 PAGE_FAULT_IN_NONPAGED_AREA" 

    Tienici aggiornati su eventuali progressi,


    Anca Popa Follow ForumTechNetIt on Twitter

    Evento 36888 origine Schannel su Windows Server 2008 R2 con IIS

    Microsoft offre questo servizio gratuitamente, per aiutare gli utenti e aumentare il database dei prodotti e delle tecnologie. Il contenuto viene fornito “così come è” e non comporta alcuna responsabilità da parte dell'azienda

    martedì 22 novembre 2011 14:04
  • Ciao

    Non ho trovato al link che mi hai indicato una versione della hotfix per windows server 2008 ma solo per 2008 R2.

    A proposito, dal dump della memoria mi sembra di capire che sia coinvolto anche un processo dell'antivirus Officescan (tmcomm.sys e TmPreFlt). 

     

    Could not read faulting driver name

    OVERLAPPED_MODULE: Address regions for 'TmPreFlt' and 'tmcomm.sys' overlap

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82584868

    Tali dll sono riconducibili all'antivirus TrendMicro.

     

    Al che ho contattato la trend micro che mi ha suggerito di installare il SP 1 di Officescan 10 e una patch uscita a maggio. 

     

    Per concludere:  sono piuttosto confuso sul da farsi.....

     

    suggerimenti ??

     

    Grazie in anticipo

     

     

     

    mercoledì 23 novembre 2011 09:47
  • Ciao aries,

    Purtroppo il multi-postare non e' una pratica gradita nella community, siccome postando la stessa domanda su piu' di un forum si causa solo una perdita di tempo ai moderatori:

    BSOD su Windows server 2008 usato come terminal server

    Il consiglio che vorrei darti e' di proseguire la discussione li' e di tenerci aggiornati sul tuo percorso.

    Saluti,


    Anca Popa Follow ForumTechNetIt on Twitter

    Evento 36888 origine Schannel su Windows Server 2008 R2 con IIS

    Microsoft offre questo servizio gratuitamente, per aiutare gli utenti e aumentare il database dei prodotti e delle tecnologie. Il contenuto viene fornito “così come è” e non comporta alcuna responsabilità da parte dell'azienda

    mercoledì 23 novembre 2011 13:32
  • OK. ...cmq mi sembrava (la mia un'osservazione pertinente).   In ogni caso staro alle regole :)
    giovedì 24 novembre 2011 08:19
  • Bene, grazie!

    Anca Popa Follow ForumTechNetIt on Twitter

    Evento 36888 origine Schannel su Windows Server 2008 R2 con IIS

    Microsoft offre questo servizio gratuitamente, per aiutare gli utenti e aumentare il database dei prodotti e delle tecnologie. Il contenuto viene fornito “così come è” e non comporta alcuna responsabilità da parte dell'azienda

    giovedì 24 novembre 2011 13:58