errore con crash!!aiuto!

[white.devils]

ciao a tutti volevo chiedere aiuto su un problema che mi si presenta molto spesso e senza soluzione, spesso facendo cose normali sul pc (internet, scrivere ecc) il pc si riavvia dopo ke mi è uscita una schermata blu. Al riavvio mi esce la finestrella con scritto di cercare una soluzione tra l'altro mai trovata. Vi Posso dire che ho windows vista home premium e tutti i driver forniti dalla casa madre del mio notebook. ecco le immagini:

[white.devils]

nessuno sa niente?

[yeppala]

dovresti farci vedere cosa c'è scritto prima della scritta "ulteriori informazioni sul problema" cioè in "Firma del problema". E' in "Firma del problema" che sono elencati i nomi dei moduli o i driver che hanno crashato

[white.devils]

azz e allora la prossima volta ke crasha lo posto, cmq pensavo ke i codici scritti servivano a qlcosa

[white.devils]

ecco la prima parte della finestra


sapete aiutarmi????

[cristian5]

prova un po' così: scarica il debugging tools da qui http://msdl.microsoft.com/download/s...86_6.8.4.0.msi
poi avvialo come amministratore e metti in "Symbols File Path" sotto il menu File questo: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
infine fai "Open Crash Dump" e seleziona il file che sta nella cartella Minidump che si vede nell'immagine che hai postato, poi vedi cosa ti dice

[white.devils]

è uscito questo
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini022608-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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Feb 26 10:21:30.733 2008 (GMT+1)
System Uptime: 0 days 0:31:47.519
Loading Kernel Symbols
..........................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {19c3d8cc, 1b, 0, 81c29144}



Probably caused by : ntkrpamp.exe ( nt!KeWaitForSingleObject+1b5 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 19c3d8cc, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81c29144, address which referenced memory

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




OVERLAPPED_MODULE: Address regions for 'amon' and 'parport.sys' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
19c3d8cc

CURRENT_IRQL: 1b

FAULTING_IP:
nt!KeWaitForSingleObject+1b5
81c29144 803902 cmp byte ptr [ecx],2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: SearchIndexer.e

TRAP_FRAME: 99c3d744 -- (.trap 0xffffffff99c3d744)
ErrCode = 00000000
eax=00000000 ebx=84570e30 ecx=19c3d8cc edx=81d32300 esi=84570d78 edi=84570e00
eip=81c29144 esp=99c3d7b8 ebp=99c3d80c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KeWaitForSingleObject+0x1b5:
81c29144 803902 cmp byte ptr [ecx],2 ds:0023:19c3d8cc=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c29144 to 81c8fd84

STACK_TEXT:
99c3d744 81c29144 badb0d00 81d32300 844eed30 nt!KiTrap0E+0x2ac
99c3d80c 81c3b553 19c3d8cc 00000013 00000000 nt!KeWaitForSingleObject+0x1b5
99c3d810 19c3d8cc 00000013 00000000 00000000 nt!MiFlushSectionInternal+0x8bd
WARNING: Frame IP not in any known module. Following frames may be wrong.
99c3d814 00000000 00000000 00000000 00000000 0x19c3d8cc


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeWaitForSingleObject+1b5
81c29144 803902 cmp byte ptr [ecx],2

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KeWaitForSingleObject+1b5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 470c2f52

FAILURE_BUCKET_ID: 0xA_nt!KeWaitForSingleObject+1b5

BUCKET_ID: 0xA_nt!KeWaitForSingleObject+1b5

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 19c3d8cc, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81c29144, address which referenced memory

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




OVERLAPPED_MODULE: Address regions for 'amon' and 'parport.sys' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
19c3d8cc

CURRENT_IRQL: 1b

FAULTING_IP:
nt!KeWaitForSingleObject+1b5
81c29144 803902 cmp byte ptr [ecx],2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: SearchIndexer.e

TRAP_FRAME: 99c3d744 -- (.trap 0xffffffff99c3d744)
ErrCode = 00000000
eax=00000000 ebx=84570e30 ecx=19c3d8cc edx=81d32300 esi=84570d78 edi=84570e00
eip=81c29144 esp=99c3d7b8 ebp=99c3d80c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KeWaitForSingleObject+0x1b5:
81c29144 803902 cmp byte ptr [ecx],2 ds:0023:19c3d8cc=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c29144 to 81c8fd84

STACK_TEXT:
99c3d744 81c29144 badb0d00 81d32300 844eed30 nt!KiTrap0E+0x2ac
99c3d80c 81c3b553 19c3d8cc 00000013 00000000 nt!KeWaitForSingleObject+0x1b5
99c3d810 19c3d8cc 00000013 00000000 00000000 nt!MiFlushSectionInternal+0x8bd
WARNING: Frame IP not in any known module. Following frames may be wrong.
99c3d814 00000000 00000000 00000000 00000000 0x19c3d8cc


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeWaitForSingleObject+1b5
81c29144 803902 cmp byte ptr [ecx],2

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KeWaitForSingleObject+1b5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 470c2f52

FAILURE_BUCKET_ID: 0xA_nt!KeWaitForSingleObject+1b5

BUCKET_ID: 0xA_nt!KeWaitForSingleObject+1b5

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 19c3d8cc, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81c29144, address which referenced memory

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




OVERLAPPED_MODULE: Address regions for 'amon' and 'parport.sys' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
19c3d8cc

CURRENT_IRQL: 1b

FAULTING_IP:
nt!KeWaitForSingleObject+1b5
81c29144 803902 cmp byte ptr [ecx],2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: SearchIndexer.e

TRAP_FRAME: 99c3d744 -- (.trap 0xffffffff99c3d744)
ErrCode = 00000000
eax=00000000 ebx=84570e30 ecx=19c3d8cc edx=81d32300 esi=84570d78 edi=84570e00
eip=81c29144 esp=99c3d7b8 ebp=99c3d80c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KeWaitForSingleObject+0x1b5:
81c29144 803902 cmp byte ptr [ecx],2 ds:0023:19c3d8cc=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c29144 to 81c8fd84

STACK_TEXT:
99c3d744 81c29144 badb0d00 81d32300 844eed30 nt!KiTrap0E+0x2ac
99c3d80c 81c3b553 19c3d8cc 00000013 00000000 nt!KeWaitForSingleObject+0x1b5
99c3d810 19c3d8cc 00000013 00000000 00000000 nt!MiFlushSectionInternal+0x8bd
WARNING: Frame IP not in any known module. Following frames may be wrong.
99c3d814 00000000 00000000 00000000 00000000 0x19c3d8cc


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeWaitForSingleObject+1b5
81c29144 803902 cmp byte ptr [ecx],2

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KeWaitForSingleObject+1b5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 470c2f52

FAILURE_BUCKET_ID: 0xA_nt!KeWaitForSingleObject+1b5

BUCKET_ID: 0xA_nt!KeWaitForSingleObject+1b5

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 19c3d8cc, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81c29144, address which referenced memory

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




OVERLAPPED_MODULE: Address regions for 'amon' and 'parport.sys' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
19c3d8cc

CURRENT_IRQL: 1b

FAULTING_IP:
nt!KeWaitForSingleObject+1b5
81c29144 803902 cmp byte ptr [ecx],2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: SearchIndexer.e

TRAP_FRAME: 99c3d744 -- (.trap 0xffffffff99c3d744)
ErrCode = 00000000
eax=00000000 ebx=84570e30 ecx=19c3d8cc edx=81d32300 esi=84570d78 edi=84570e00
eip=81c29144 esp=99c3d7b8 ebp=99c3d80c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KeWaitForSingleObject+0x1b5:
81c29144 803902 cmp byte ptr [ecx],2 ds:0023:19c3d8cc=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c29144 to 81c8fd84

STACK_TEXT:
99c3d744 81c29144 badb0d00 81d32300 844eed30 nt!KiTrap0E+0x2ac
99c3d80c 81c3b553 19c3d8cc 00000013 00000000 nt!KeWaitForSingleObject+0x1b5
99c3d810 19c3d8cc 00000013 00000000 00000000 nt!MiFlushSectionInternal+0x8bd
WARNING: Frame IP not in any known module. Following frames may be wrong.
99c3d814 00000000 00000000 00000000 00000000 0x19c3d8cc


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeWaitForSingleObject+1b5
81c29144 803902 cmp byte ptr [ecx],2

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KeWaitForSingleObject+1b5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 470c2f52

FAILURE_BUCKET_ID: 0xA_nt!KeWaitForSingleObject+1b5

BUCKET_ID: 0xA_nt!KeWaitForSingleObject+1b5

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

[giannola]

è un problema di ram.

nel migliore dei casi occorre settare i timings, nel peggiore un banco può essere danneggiato.

[white.devils]

azz, cm posso settare i timing, mi sai dare una mano?

[giannola]

Originariamente inviato da white.devils

azz, cm posso settare i timing, mi sai dare una mano?

devi conoscere i valori dei singoli banchi e, nel caso fossero differenti, settarli nel bios uno ad uno.

usa cpu-z.

[white.devils]

questo è il mio pc

[giannola]

le ram sono identiche (finestre 2 e 3 in alto da sinistra) e il sistema le riconosce automaticamente senza problemi.

Per tagliare la testa al toro vai nel bios e nel menù exit, cerca l'opzione load setup defaults (o similare).

Vedi come va.

Nel caso (come credo) i problemi persistano fai un controllo della ram con memtest.

[white.devils]

x la cronaca a volte qnd scarico dei file grossi, e li estraggo mi esce errore crc, mi dissero ke era un problema di ram, cosi ho fatto il memtest x circa 4 ore e gli errori sono stati zero...

[giannola]

Originariamente inviato da white.devils

x la cronaca a volte qnd scarico dei file grossi, e li estraggo mi esce errore crc, mi dissero ke era un problema di ram, cosi ho fatto il memtest x circa 4 ore e gli errori sono stati zero...

il crc acronimo di Cyclic redundancy check (controllo di ridondanza ciclico) è un controllo per verificare la correttezza dei dati; questo controllo di norma vien fatto dall'hd sui dati in trasferimento per verificarne la correttezza.

Se vi sono errori il crc li rileva.

A volte la causa può essere l'eccessivo riscaldamento dell'hd.

Cmq fai una scansione dettagliata con hd tune per vedere che non ci siano settori danneggiati.

[white.devils]

ma x la questione delle ram come devo fare?

[giannola]

Originariamente inviato da white.devils

ma x la questione delle ram come devo fare?

scaricati memtest, crea un disco di avvio con il programma, setta il bios per far partire il cd e poi fa tutto da solo.

[white.devils]

l'ho fatto e dopo 3 ore zero errori

[giannola]

Originariamente inviato da white.devils

l'ho fatto e dopo 3 ore zero errori

e quindi torniamo al nostro crc.

verifica la temperatura dell'hd, può essere quella che da problemi

[white.devils]

devo usare hd tune quindi?

[giannola]

Originariamente inviato da white.devils

devo usare hd tune quindi?

sisi.

Controlla temperatura e parametri.