Vista/7 - Schermate blu (bsod):individuazione cause dell'errore e possibili soluzioni

[MrPeppez]

I miei errori lì non ci sono, comunque ho tolto avast e messo kaspersky 2011, provo a fare una scansione, fin'ora nessuna schermata blu.

Con avast antirootkit ho anche rimosso un file .sys che in precedenza mi aveva causato una schermata blu, vediamo

[max60]

Ciao a tutti, ho installato seven sul pc di un amico che usava un dispositivo wireless usb della Dlink (dwl-g120) per connettersi tramite il router a internet.
Il prodotto è fuori produzione e Dlink non fornisce alcun driver per Vista/Seven.
Girando per i forum ho visto che veniva consigliato l'uso di una versione di driver presente sul sito di Taiwan della Dlink, con l'accortezza di non eseguire il setup, ma di assegnare solo i driver direttamente alla periferica sconosciuta.
Ho seguito queste indicazioni ed effettivamente la periferica funziona perfettamente anche con Seven, viene risconosiuta senza problemi e si può navigare in internet.
Il guaio però si verifica allo spegnimento del pc: ogni volta esce la schermata blu senza che vengano però fornite ullteriori spiegazioni (a parte la creazione del dump).
Eliminando quei driver il pc si spegne tranquillamente per cui il problema dipende da quello.
Cosa potrei fare ?

[Eress]

Ê possibile che tu abbia il sistema ancora infetto, per quello ti avevo consigliato quella guida

[MrPeppez]

Con kaspersky e dopo tante scansioni sembra andare tutto bene

[Eress]

Comunque continua a monitorare la faccenda...

[MrPeppez]

Si si, sto usando anche il pc senza batteria ora, forse poteva essere anche quello il problema

[deidara80]

salve a tutti. ho appena avuto un bsod. in windows non ho nessuna cartella minidump.
come faccio?

nella pagina dei download dei simboli per windows 7 64 c'è una versione retail e una checked. che differenza c'è?

[Eress]

Devi leggere la guida in prima pagina per ottenere il file dmp

[deidara80]

okay. non avevo capito. pensavo che ci dovesse già essere. allora installo questi simboli e il debugg tool.
grazie

[Eress]

Puoi anche postare qui i file dmp

[djalexal]

Ecco i file di due crash:

Primo file

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


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

Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`03093670
Debug session time: Fri Aug 12 19:00:03.767 2011 (UTC + 2:00)
System Uptime: 0 days 1:51:52.016
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff8800316db70, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+2c61 )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff8800316db70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

LAST_CONTROL_TRANSFER: from fffff80002e17818 to fffff80002ecac40

STACK_TEXT:
fffff880`0316db38 fffff800`02e17818 : 00000000`0000009c 00000000`00000000 fffff880`0316db70 00000000`00000000 : nt!KeBugCheckEx
fffff880`0316db40 fffff800`02e16f57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`0316dc90 fffff800`02e0ae88 : 00000000`00000001 fffff880`03165180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`0316dcc0 fffff800`02ec952c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0316dcf0 fffff800`02ec9393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0316de30 fffff880`05b47c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0318db58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61


STACK_COMMAND: kb

FOLLOWUP_IP:
intelppm+2c61
fffff880`05b47c61 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: intelppm+2c61

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd

FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+2c61

BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+2c61

Followup: MachineOwner




E questo è il secondo:


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


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

Mini Kernel Dump does not have process information
Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image Unknown_Module_284a0026`48002648, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_284a0026`48002648
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_284a0026`48002648
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`030a7670
Debug session time: Sat Aug 13 17:43:41.811 2011 (UTC + 2:00)
System Uptime: 0 days 5:25:11.059
Unable to load image Unknown_Module_284a0026`48002648, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_284a0026`48002648
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_284a0026`48002648
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff8800316db70, 0, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff8800316db70
Arg3: 0000000000000000
Arg4: 0000000000000000

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


BUGCHECK_STR: 0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002e2b818 to fffff80002edec40

STACK_TEXT:
fffff880`0316db38 fffff800`02e2b818 : 00000000`0000009c 00000000`00000000 fffff880`0316db70 00000000`00000000 : 0xfffff800`02edec40
fffff880`0316db40 00000000`0000009c : 00000000`00000000 fffff880`0316db70 00000000`00000000 00000000`00000000 : 0xfffff800`02e2b818
fffff880`0316db48 00000000`00000000 : fffff880`0316db70 00000000`00000000 00000000`00000000 00000000`00000000 : 0x9c


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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

[Eress]

L'unico elemento che appare dai log è questo intelppm.sys che sembra un problema relativo ai driver intel di alcuni processori di quella marca.
Un problema abbastanza insolito. Ho paura che sia un driver difettoso oppure qualche conflitto con del software installato.

[~Jaco~]

Allora il mio problema è questo: fino a qualche giorno fa ho installato 7 64 bit home su un desktop nuovo e un portatile. Ho fatto eseguire tutti gli aggiornamenti e ho collegato i 2 hd che ho per scaricare programmi da reinstallare e cartelle da rimettere. Inizialmente per qualche giorno ha funzionato tutto bene poi qualche giorno fa è cominciato il problema:
connetto gli hd poi li disconnetto con rimozione sicura e mi dice che la periferica non funziona correttamente, se stacco mouse anche quella periferica usb non va piu, provo a spegnere computer non si spegne e rimane per molto tempo la schermata arresto del sitema in corso e ad un certo punto si arresta. Al riavvvio di windows copmpare un messaggio che è stato generato un file per schermata blu con i dettagli.
Se collego delle chiavette usb questo non succede e tutto va tranquillo, solo con ha esterni da 80 Gb e 500 Gb mi succede.
Ho eseguito quanto riportato in primo post e il risultato è questo:

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


Loading Dump File [F:\Dati - Testo\081311-14218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e98670
Debug session time: Sat Aug 13 18:28:52.360 2011 (UTC + 2:00)
System Uptime: 0 days 0:14:40.704
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa80036dd040, fffff80000b9c510}

Unable to load image \SystemRoot\system32\drivers\rvsystem.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rvsystem.sys
*** ERROR: Module load completed but symbols could not be loaded for rvsystem.sys
Probably caused by : volmgr.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80036dd040, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510

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


DRVPOWERSTATE_SUBCODE:  4

IMAGE_NAME:  volmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792a0

MODULE_NAME: volmgr

FAULTING_MODULE: fffff88000f92000 volmgr

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`08af3a40 fffff800`02cd4f32 : fffffa80`036dd040 fffffa80`036dd040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`08af3b80 fffff800`02cd774f : fffff880`01263384 00000000`00000000 fffffa80`00000000 fffffa80`055caa40 : nt!KiCommitThreadWait+0x1d2
fffff880`08af3c10 fffff800`02dda925 : fffffa80`0635b400 fffff880`00000000 fffff880`01263300 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`08af3cb0 fffff880`0198774d : 00000000`00000000 fffffa80`05efd7c0 fffffa80`05efdbf0 fffffa80`05efd7c0 : nt!IoReleaseRemoveLockAndWaitEx+0x45
fffff880`08af3cf0 00000000`00000000 : fffffa80`05efd7c0 fffffa80`05efdbf0 fffffa80`05efd7c0 00000000`00000020 : rvsystem+0xf74d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_4_rvsystem_IMAGE_volmgr.sys

BUCKET_ID:  X64_0x9F_4_rvsystem_IMAGE_volmgr.sys

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

Un aiuto a voi guru perche credevo che con 7 non ci fossero questi problemi...

P.S.: il problema avviene su entrambi i computer: uno con 7 64 bit professional e uno con 7 64 bit home, comunque questo è il debug del desktop, adesso posto anche quello del notebook...

[~Jaco~]

Ecco il risultato del notebook con il solito problema:

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


Loading Dump File [F:\Dati - Testo\Marco\BSOD\Notebook\081311-14218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e98670
Debug session time: Sat Aug 13 18:28:52.360 2011 (UTC + 2:00)
System Uptime: 0 days 0:14:40.704
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa80036dd040, fffff80000b9c510}

Unable to load image \SystemRoot\system32\drivers\rvsystem.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rvsystem.sys
*** ERROR: Module load completed but symbols could not be loaded for rvsystem.sys
Probably caused by : volmgr.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80036dd040, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510

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


DRVPOWERSTATE_SUBCODE:  4

IMAGE_NAME:  volmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792a0

MODULE_NAME: volmgr

FAULTING_MODULE: fffff88000f92000 volmgr

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`08af3a40 fffff800`02cd4f32 : fffffa80`036dd040 fffffa80`036dd040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`08af3b80 fffff800`02cd774f : fffff880`01263384 00000000`00000000 fffffa80`00000000 fffffa80`055caa40 : nt!KiCommitThreadWait+0x1d2
fffff880`08af3c10 fffff800`02dda925 : fffffa80`0635b400 fffff880`00000000 fffff880`01263300 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`08af3cb0 fffff880`0198774d : 00000000`00000000 fffffa80`05efd7c0 fffffa80`05efdbf0 fffffa80`05efd7c0 : nt!IoReleaseRemoveLockAndWaitEx+0x45
fffff880`08af3cf0 00000000`00000000 : fffffa80`05efd7c0 fffffa80`05efdbf0 fffffa80`05efd7c0 00000000`00000020 : rvsystem+0xf74d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_4_rvsystem_IMAGE_volmgr.sys

BUCKET_ID:  X64_0x9F_4_rvsystem_IMAGE_volmgr.sys

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

[~Jaco~]

"A driver is causing an inconsistent power state"
mi sbaglio o sembra che dipenda dai driver di questi hd?
Se per favore mi indicate la procedura adatta a questo tipo di problema per risolvere e se secondo voi è grave o no il problema... Piu che altro perché su quei due hd ho file di backup e programmi e avendo solo pc con 7 adesso posso risolvere il problema o mi tocca buttare questi du e hd?

[Eress]

Il problema è causato da questo driver

http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

Qui una possibile soluzione

http://www.sevenforums.com/performan...ager-prob.html

[~Jaco~]

Grazie eress, però non ho capito molto su come debba fare per risolvere il problema, non sono un laureato in informatica e la cosa mi sembra complessa
Io ho questi 2 hd e mi creano problemi quando li inserisco causati dal driver di questi, uno in particolare; non capisco bene cosa indichi di fare gregrocker nel post: dovrei formattare i dischi in una maniera particolare?
Mi potresti indicare la procedura? E' un po problematico spostare tutti i dati di tali hd....

[~Jaco~]

Allora guardando meglio devo eseguire questa operazione: "Disk - Clean and Clean All with Diskpart Command" ?
- inserisco l'hd la prima volta (perche quando arrivo a toglierlo si creano i problemi e il s.o. non si arresta piu);
- vado a gestione disco e seguo quanto mi riporta nel post.
( mi conviene salvare tutti i dati sul pc prima di eseguire l'operazione? )

[Eress]

Ê una procedura che non ho mai eseguito, però è sempre meglio salvare il salvabile prima di questo tipo di operazioni piuttosto rischiose, però vista la situazione del tuo hd mi pare inevitabile farlo, tanto non credo che puoi andare avanti così

[~Jaco~]

Ok vediamo un po cosa mi riuscirà di fare la cosa strana è che andavano tutti senza problemi con 7 all'inizio e all'improvviso è saltato fuori questo problema vi farò sapere, grazie