mini crash dump!!

[white.devils]

ciao a tutti!! è da un po di giorni ke puntualmenti il pc mi mostra la sua bella schermata blu di crash, per capire ho aperto i minidump con windbg e questo è il risultato:
c'è scritto che il colpevole è messenger o sn babbo io??grazie x l'aiuto!!

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


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

Symbol search path is: f:\BusObjSymbols;SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Kernel base = 0x81c49000 PsLoadedModuleList = 0x81d60c70
Debug session time: Sun Jun 22 13:38:59.626 2008 (GMT+2)
System Uptime: 0 days 0:31:05.163
Loading Kernel Symbols
......................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, 88914120, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 88914120, The PRCB address of the hung processor.
Arg4: 00000002, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 1c

STACK_TEXT:
998ae660 81d01321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
998ae694 81d0102d 998ae61b 000000d1 998ae728 nt!KeUpdateRunTime+0xd5
998ae694 81d052f3 998ae61b 000000d1 998ae728 nt!KeUpdateSystemTime+0xed
998ae728 81d050ed 00000002 00000001 95414d70 nt!KeFlushTb+0x162
998ae744 81c667c8 998ae7ac 00000002 00000001 nt!KeFlushMultipleRangeTb+0x91
998ae834 81dfccf9 fd900000 00000000 85fcea50 nt!MiRemoveMappedPtes+0x745
998ae870 81dfcd96 fd800000 00000001 00000010 nt!MiRemoveFromSystemSpace+0x16c
998ae884 81dfcdb0 fd800000 00000010 998ae8a4 nt!MmUnmapViewInSystemSpace+0x76
998ae894 94907e02 fd800000 998aea74 998ae8c0 nt!MmUnmapViewInSessionSpace+0xe
998ae8a4 94973e75 fd800008 998ae8f0 fe0a3bd0 win32k!vFreeKernelSection+0x2b
998ae8c0 94975dca ffb058b8 fdeb21c8 fdeb21d8 win32k!SURFMEM::~SURFMEM+0xb8
998aeac4 9496e102 fe0a3bd0 ffa008f8 998aeaf4 win32k!EngAlphaBlend+0xe1
998aed0c 81ca0a7a 18011bf4 00ffffff fdd2d358 win32k!NtGdiAlphaBlend+0xbca
998aed0c 77699a94 18011bf4 00ffffff fdd2d358 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006ed7c 00000000 00000000 00000000 00000000 0x77699a94


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 88914120, The PRCB address of the hung processor.
Arg4: 00000002, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 1c

STACK_TEXT:
998ae660 81d01321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
998ae694 81d0102d 998ae61b 000000d1 998ae728 nt!KeUpdateRunTime+0xd5
998ae694 81d052f3 998ae61b 000000d1 998ae728 nt!KeUpdateSystemTime+0xed
998ae728 81d050ed 00000002 00000001 95414d70 nt!KeFlushTb+0x162
998ae744 81c667c8 998ae7ac 00000002 00000001 nt!KeFlushMultipleRangeTb+0x91
998ae834 81dfccf9 fd900000 00000000 85fcea50 nt!MiRemoveMappedPtes+0x745
998ae870 81dfcd96 fd800000 00000001 00000010 nt!MiRemoveFromSystemSpace+0x16c
998ae884 81dfcdb0 fd800000 00000010 998ae8a4 nt!MmUnmapViewInSystemSpace+0x76
998ae894 94907e02 fd800000 998aea74 998ae8c0 nt!MmUnmapViewInSessionSpace+0xe
998ae8a4 94973e75 fd800008 998ae8f0 fe0a3bd0 win32k!vFreeKernelSection+0x2b
998ae8c0 94975dca ffb058b8 fdeb21c8 fdeb21d8 win32k!SURFMEM::~SURFMEM+0xb8
998aeac4 9496e102 fe0a3bd0 ffa008f8 998aeaf4 win32k!EngAlphaBlend+0xe1
998aed0c 81ca0a7a 18011bf4 00ffffff fdd2d358 win32k!NtGdiAlphaBlend+0xbca
998aed0c 77699a94 18011bf4 00ffffff fdd2d358 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006ed7c 00000000 00000000 00000000 00000000 0x77699a94


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

[yeppala]

Originariamente inviato da white.devils

PROCESS_NAME: msnmsgr.exe

ti crasha il messenger ?

[white.devils]

no nn è ke mi crasha a un certo punto magari sto usando msn e mi crasha, ma tt il pc!boh....

[ArCH85]

prova a installare la versione live di msn e eliminare quella..

[white.devils]

io ho live messenger

[bgpop]

Dal dump sembra un problema del gestore processi, uno dei core resta fermo, non risponde.
Temperature CPU? (usa speedfan)

[white.devils]

le temp della cpu sono fisse intorno ai 49 50

[mattia.pascal]

Non penso sia sempre il messenger, a far scattare il riavvio. Controlla gli altri dump files. Hai installato periferiche nuove o aggiornato i driver di qualche periferica. Che scheda di rete hai?

[white.devils]

allora ho controllato gli ultimi 4 dump e sn tutti simili, la scheda madre è una m2nsli deluxe quindi la scheda di rete è quella integrata, comunque di recente mi pare di aver messo solo i catalyst nuovi 8.6

[white.devils]

stavolta è uscito questo


CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 88914120, The PRCB address of the hung processor.
Arg4: 00000002, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 1c

STACK_TEXT:
97a243a4 81d04321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
97a243d8 81d0402d 83b3831b 000000d1 97a2448c nt!KeUpdateRunTime+0xd5
97a243d8 81d03cc0 83b3831b 000000d1 97a2448c nt!KeUpdateSystemTime+0xed
97a24464 81d08115 0000000e 81c8958d 00000000 nt!KiIpiSendPacket+0xac
97a2448c 81ce42ce 97a244e0 00000002 00000001 nt!KeFlushMultipleRangeTb+0xb9
97a2456c 81ce93d8 c07ebc28 00000005 00000002 nt!MiFlushTbAsNeeded+0x61
97a245ac 81d3b024 fd780000 94200dc0 00000021 nt!MiAllocatePagedPoolPages+0x655
97a24608 81c8814a 00000021 00004630 00004630 nt!MiAllocatePoolPages+0x1f
97a24660 81d394cd 00000000 00000021 00004630 nt!ExpAllocateBigPool+0x97
97a246c4 94af368a 00000021 00004628 34316847 nt!ExAllocatePoolWithTag+0x116
97a246d8 94af3b94 00004628 34316847 97a24734 win32k!Win32AllocPool+0x13
97a246f4 94ab718f 00004628 00000004 00000000 win32k!AllocateObject+0xa6
97a247a0 94ab706f 97a24d34 00000010 97a247c0 win32k!RGNMEMOBJ::bFastFill+0x102
97a24914 94ab6d87 00000000 00000000 00000000 win32k!RGNMEMOBJ::bFastFillWrapper+0xbf
97a24cb4 94ab7e72 97a24d34 00000001 00000000 win32k!RGNMEMOBJ::vCreate+0x84
97a24d44 81ca3a7a 00000000 00000001 000004ec win32k!NtGdiCreateRoundRectRgn+0xdc
97a24d44 76f19a94 00000000 00000001 000004ec nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0024f9c8 00000000 00000000 00000000 00000000 0x76f19a94


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

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

[yurassik]

Qual'è la tua configurazione?

[Crown85]

white.devils anche a me capita sta schermata blu, mi dici per favore come si fa questo windbg?

[white.devils]

yurassik: cosa intendi x configurazione

crown: devi mettere in symbol file path questa roba:
f:\BusObjSymbols;SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
poi fai open crash dump

[Crown85]

ci sono riuscito, mi dice ke è il tdx.sys
sapete cosa comporta?
ke soluzioni devo usare?