schemata blue a go go

ciao a tutti ho questa schermata blue che appare in modo sporadico

questo è il result di windbg che ne pensate?

gtrazie ciccio


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


Loading Dump File [\\Server\dati\ircop\Mini063008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/
download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Thu Jun 26 09:28:54.187 2008 (GMT+2)
System Uptime: 0 days 0:55:21.904
Loading Kernel Symbols
.........................................................................
.........................................
Loading User Symbols
Loading unloaded module list
...........
***************************************************************************
****
*
*
*                        Bugcheck
Analysis                                    *
*
*
***************************************************************************
****

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81c9b731, eda4bc3c, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address
pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this
address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never
have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81c9b731, The address that the exception occurred at
Arg3: eda4bc3c, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha
fatto riferimento alla memoria a "0x%08lx". La memoria non poteva
essere "%s".

FAULTING_IP:
+ffffffff81c9b731
81c9b731 f3a7            repe cmps dword ptr [esi],dword ptr es:[edi]

TRAP_FRAME:  eda4bc3c -- (.trap ffffffffeda4bc3c)
ErrCode = 00000000
eax=00000000 ebx=02f80000 ecx=00000002 edx=00000004 esi=02f80000
edi=81c9b6fc
eip=81c9b731 esp=eda4bcb0 ebp=eda4bcd8 iopl=0     vif nv up ei pl z
r
na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000
efl=00090246
81c9b731 f3a7            repe cmps dword ptr [esi],dword ptr es:[edi]
ds:0023:02f80000=???????? es:0023:81c9b6fc=3c2b1aff
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  explorer.exe

LAST_CONTROL_TRANSFER:  from 81c9b89c to 81c9b731

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be
wrong.
eda4bcd8 81c9b89c 81c9badd 820d4b28 81a71268 0x81c9b731
eda4bdac 80576b24 00000000 00000000 00000000 0x81c9b89c
eda4bdac 80576b24 00000000 00000000 00000000 nt!PspSystemThreadStartup
+0x34
eda4bddc 804eed86 81c9bb42 00000000 00000000 nt!PspSystemThreadStartup
+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  .trap 0xffffffffeda4bc3c ; kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x8E_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  0x8E_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------
[ Auf dieses Posting antworten ]