Maledetta schermata blu!

[donfranco77]

Spero che qualche anima pia mi possa illuminare sull'accaduto.
Di tanto in tanto e quando li pare a lui, windows decide di inchiodarsi...ho fatto il debug del dump che vado a postarvi:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Fri Apr 6 16:23:10.718 2007 (GMT+2)
System Uptime: 2 days 19:51:29.283
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..........................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 80543e1d, a7567ba8, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for a347bus.sys
*** ERROR: Module load completed but symbols could not be loaded for a347bus.sys
Probably caused by : a347bus.sys ( a347bus+db42 )

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

kd> .reload
Loading Kernel Symbols
..........................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
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: 80543e1d, The address that the exception occurred at
Arg3: a7567ba8, Trap Frame
Arg4: 00000000

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

Unable to load image a347bus.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for a347bus.sys
*** ERROR: Module load completed but symbols could not be loaded for a347bus.sys

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:
nt!ExFreePoolWithTag+237
80543e1d 668b4efa mov cx,word ptr [esi-6]

TRAP_FRAME: a7567ba8 -- (.trap ffffffffa7567ba8)
ErrCode = 00000000
eax=00001600 ebx=00000000 ecx=863b4168 edx=000d959c esi=0000ee65 edi=84b9c146
eip=80543e1d esp=a7567c1c ebp=a7567c50 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ExFreePoolWithTag+0x237:
80543e1d 668b4efa mov cx,word ptr [esi-6] ds:0023:0000ee5f=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: Skype.exe

LAST_CONTROL_TRANSFER: from 805b5605 to 80543e1d

STACK_TEXT:
a7567c50 805b5605 0000ee65 00000000 00000000 nt!ExFreePoolWithTag+0x237
a7567c80 805af817 84b9c148 00000000 00000000 nt!ObpFreeObject+0x147
a7567c98 8052201d 84b9c160 00000000 000009a4 nt!ObpRemoveObjectRoutine+0xe7
a7567cbc 805b080f 84e65c08 e8f05a38 84af3da8 nt!ObfDereferenceObject+0x5f
a7567cd4 805b08a5 e8f05a38 84b9c160 000009a4 nt!ObpCloseHandleTableEntry+0x155
a7567d1c 805b09dd 000009a4 00000001 00000000 nt!ObpCloseHandle+0x87
a7567d30 f736cb42 000009a4 80535230 804d9ae0 nt!NtClose+0x1d
WARNING: Stack unwind information not available. Following frames may be wrong.
a7567d58 8053ca28 000009a4 0302fadc 7c91eb94 a347bus+0xdb42
a7567d58 7c91eb94 000009a4 0302fadc 7c91eb94 nt!KiFastCallEntry+0xf8
0302fadc 00000000 00000000 00000000 00000000 0x7c91eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
a347bus+db42
f736cb42 ?? ???

SYMBOL_STACK_INDEX: 7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: a347bus

IMAGE_NAME: a347bus.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4129c4d5

SYMBOL_NAME: a347bus+db42

FAILURE_BUCKET_ID: 0x8E_a347bus+db42

BUCKET_ID: 0x8E_a347bus+db42

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

Parla di Skype perchè a questo giro si è bloccato dopo una chiamata e sembra che il fulcro del "disagio" sia questo a347bus.sys che è riferito ad Alchool, come ho potuto vedere da altre discussioni....

A questo punto che devo fà?? Butto via Alchool o c'è un modo per evitare bordelli?

[donfranco77]

Nessuno abile nei file dump?