PDA

View Full Version : Win 7 dump :(


Pablo74rm
12-11-2009, 17:56
Ciao a tutti non so se sto postando nel posto giusto chiedo scusa se così non fosse.
Allora a tutti i guru ecco il mio dump ho capito che forse è un driver
ma quale? attualmente ho disabilitato la scheda audio i driver per win 7 non sono ancora molti.Aiutatemi Grazie a tutti.

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


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

Symbol search path is: C:\localsymbols*http://msdl.microsoft.com/download/symbols SRV *;symsrv*symsrv.dll*c:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82841000 PsLoadedModuleList = 0x82989810
Debug session time: Thu Nov 12 18:32:20.352 2009 (GMT+1)
System Uptime: 0 days 0:06:35.350
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82420811, a2207c2c, 0}

Probably caused by : win32k.sys ( win32k!SleepInputIdle+8 )

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

0: 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: 82420811, The address that the exception occurred at
Arg3: a2207c2c, 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:
win32k!SleepInputIdle+8
82420811 f780d800000000100000 test dword ptr [eax+0D8h],1000h

TRAP_FRAME: a2207c2c -- (.trap 0xffffffffa2207c2c)
ErrCode = 00000000
eax=7d9345d0 ebx=00000001 ecx=00000000 edx=00000000 esi=7d9345d0 edi=00000000
eip=82420811 esp=a2207ca0 ebp=a2207ca0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!SleepInputIdle+0x8:
82420811 f780d800000000100000 test dword ptr [eax+0D8h],1000h ds:0023:7d9346a8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82420d83 to 82420811

STACK_TEXT:
a2207ca0 82420d83 7d9345d0 20761c70 0241fa5c win32k!SleepInputIdle+0x8
a2207cec 82420e10 000024ff 00000000 00000001 win32k!xxxRealSleepThread+0x1e5
a2207d08 823dbd56 000024ff 00000000 00000001 win32k!xxxSleepThread+0x2d
a2207d1c 82411eba 000024ff 00000000 0241f9f0 win32k!xxxRealWaitMessageEx+0x12
a2207d2c 8288442a 0241fa5c 772364f4 badb0d00 win32k!NtUserWaitMessage+0x14
a2207d2c 772364f4 0241fa5c 772364f4 badb0d00 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0241fa5c 00000000 00000000 00000000 00000000 0x772364f4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!SleepInputIdle+8
82420811 f780d800000000100000 test dword ptr [eax+0D8h],1000h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!SleepInputIdle+8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc2a2

FAILURE_BUCKET_ID: 0x8E_win32k!SleepInputIdle+8

BUCKET_ID: 0x8E_win32k!SleepInputIdle+8

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

Marinelli
12-11-2009, 19:44
Spostato nella sezione dedicata a Windows 7.

Ciao ;)

Pablo74rm
12-11-2009, 20:50
Scusate se ho postato nella discussione sbagliata,
la cosa strana è che ogni tanto va in dump, credevo fossero i driver della scheda audio ma li ho aggiornati,idem per i video.. che puo essere?
:(


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


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

Symbol search path is: C:\localsymbols*http://msdl.microsoft.com/download/symbols SRV *;symsrv*symsrv.dll*c:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82803000 PsLoadedModuleList = 0x8294b810
Debug session time: Thu Nov 12 21:20:01.637 2009 (GMT+1)
System Uptime: 0 days 1:57:02.635
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 97210811, ac21bc2c, 0}

Probably caused by : win32k.sys ( win32k!SleepInputIdle+8 )

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: 97210811, The address that the exception occurred at
Arg3: ac21bc2c, 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:
win32k!SleepInputIdle+8
97210811 f780d800000000100000 test dword ptr [eax+0D8h],1000h

TRAP_FRAME: ac21bc2c -- (.trap 0xffffffffac21bc2c)
ErrCode = 00000000
eax=7dcf9958 ebx=00000001 ecx=00000000 edx=00000000 esi=7dcf9958 edi=00000000
eip=97210811 esp=ac21bca0 ebp=ac21bca0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!SleepInputIdle+0x8:
97210811 f780d800000000100000 test dword ptr [eax+0D8h],1000h ds:0023:7dcf9a30=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 97210d83 to 97210811

STACK_TEXT:
ac21bca0 97210d83 7dcf9958 3b14dabe 05b8fac0 win32k!SleepInputIdle+0x8
ac21bcec 97210e10 000024ff 00000000 00000001 win32k!xxxRealSleepThread+0x1e5
ac21bd08 971cbd56 000024ff 00000000 00000001 win32k!xxxSleepThread+0x2d
ac21bd1c 97201eba 000024ff 00000000 05b8fa54 win32k!xxxRealWaitMessageEx+0x12
ac21bd2c 8284642a 05b8fac0 777464f4 badb0d00 win32k!NtUserWaitMessage+0x14
ac21bd2c 777464f4 05b8fac0 777464f4 badb0d00 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
05b8fac0 00000000 00000000 00000000 00000000 0x777464f4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!SleepInputIdle+8
97210811 f780d800000000100000 test dword ptr [eax+0D8h],1000h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!SleepInputIdle+8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc2a2

FAILURE_BUCKET_ID: 0x8E_win32k!SleepInputIdle+8

BUCKET_ID: 0x8E_win32k!SleepInputIdle+8

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

ezio
12-11-2009, 21:13
Usa il tag testo per postare il risultato del debug, ho corretto i tuoi post precedenti ;)

In merito al tuo problema, prova a disattivare le schede di rete e utilizza normalmente il PC, se il problema non dovesse ripresentarsi potrebbero essere i relativi driver (sono frequentemente causa di bsod sul file win32k.sys).
Effettua anche un controllo della RAM con Memtest, QUI (http://www.hwupgrade.it/forum/showpost.php?p=25062288&postcount=38) i dettagli.
Disattiva eventuali overclock di memoria e cpu, e prova a disabilitare le feature di risparmio energetico (c1e, Speedstep, C&Q).
Effettua anche un controllo del disco con almeno uno scandisk completo, e prova ad aggiornare i driver del controller ide/sata/raid del tuo sistema.
Prova anche a disattivare e riattivare il file di paging (memoria virtuale), in modo da assicurarti che pagefile.sys non sia corrotto e causi il bsod
Prova anche a disattivare, se presenti, eventuali antispyware, antimalware o moduli Hips (vedi Comodo) che agiscono in background.

Pablo74rm
12-11-2009, 21:27
Grazie mille per avermi risposto ora provo quello che mi hai detto.
ti aggiornero ;)

Pablo74rm
13-11-2009, 12:46
Grazie ancora per i consigli preziosi :D
il debug del dump non è proprio parlante, comunque
ieri ho disabilitato i driver della scheda audio e abilitato quelli della piastra madre aggiornandoli all'ultimaversione compatibile di win7.
Ho effettuato il disable/enable del paging
effettuato stress test di win7 con memtest e benchmark.
Tutta la notte è rimasto acceso nessun messaggio di Errore.

Gli unici driver che non sono riuscito a trovare sono scheda di rete che per adesso funge con i sui riconosciuti plug and play e stampante che ho disattivato.

Che dire un grazie e spero di non postare piu per questo tipo di problema.

Ciao
;)