Olimpo Informatico

[leodis]

Salve a tutti,
scrivo perchè vorrei cancellare dal registro del pc i riferimenti agli HD caricati di solito, in modo da ricominciare da capo.
Ho due PC: uno che uso di solito (a cui collego vari HD esterni) e un altro che mi è stato dato, con poca ram e un HD piccolo, che uso solo se devo intervenire per riparare l'altro pc.
Montano entrambi Win Xp, il principale sp3 e l'altro sp1.
Il problema è che ho un HD esterno con tanti GB di film. Se lo carico sul pc principale mi manda in errore windows con la schermata blu che blocca il pc per un errore irreversibile e lo riavvia continuamente, se invece lo carico sull'altro pc piccolo si carica normalmente e ci posso accedere senza problema.
Mi ricordo che ogni volta che si collega un HD al pc viene scritta una chiave con i riferimenti allo stesso. In pratica penso che serva a ridare sempre la stessa lettera a quell'unità.
Vorrei ripulire quelle chiavi nel pc principale per vedere se dopo me lo carica.
Già un'altra volta mi era capitato con un altro HD, ma non mi ricordo assolutamente dove sono andato.

[chemicalbit]

Hai dettagli sull'errore?

[leodis]

Aggiungo che ho scaricato il progr di Micros. WinDebug che interpreta le schermate blu e questa è la risposta salvata in un file testo (magari può servire):

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


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

Symbol search path is: c:\windows\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Sun Sep 19 20:47:10.250 2010 (GMT+2)
System Uptime: 0 days 0:01:21.812
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, e1abb470, e1abb580, c22040a}

*** WARNING: Unable to verify timestamp for symsnap.sys
*** ERROR: Module load completed but symbols could not be loaded for symsnap.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
Unable to load image cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
Probably caused by : symsnap.sys ( symsnap+1834f )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: e1abb470, The pool entry we were looking for within the page.
Arg3: e1abb580, The next pool entry.
Arg4: 0c22040a, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: e1abb470

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LOCK_ADDRESS: 805591e0 -- (!locks 805591e0)

Resource @ nt!PiEngineLock (0x805591e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x805591e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80544b06 to 804f8cc5

STACK_TEXT:
f7a153f4 80544b06 00000019 00000020 e1abb470 nt!KeContextToKframes+0x1eb
f7a15444 f73bc34f e1abb478 00000000 e1b10684 nt!VfBuildMdlFromScatterGatherList+0xa0
WARNING: Stack unwind information not available. Following frames may be wrong.
f7a154d0 f73bb1e1 e1b093f8 e1b10684 e1b1068c symsnap+0x1834f
f7a154f4 f73bb4ef 85e15ef8 e1b10680 00140012 symsnap+0x171e1
f7a1553c f73bb0eb 85e15f04 e1b10680 f7a15580 symsnap+0x174ef
f7a15574 f73b9b64 01b093b8 f7a155a8 f7a155b8 symsnap+0x170eb
f7a155c8 f73b9cbf 85e15bc8 00000000 f7a155f0 symsnap+0x15b64
f7a155e8 f73b4af5 85e15bc8 f7a15618 00000000 symsnap+0x15cbf
f7a15630 f73b55f3 85e220d8 f73bfc00 85b828f0 symsnap+0x10af5
f7a15694 f73aef89 85b828f0 f7a156ea 00000000 symsnap+0x115f3
f7a156ec f73afbd0 85ca7c98 85e091b8 85e093d0 symsnap+0xaf89
f7a15708 f73a9cfc 85ca7c98 85e091b8 85f61a18 symsnap+0xbbd0
f7a1571c 804ee129 85ca7c98 85e091b8 85e093f4 symsnap+0x5cfc
f7a157a0 f73e77ba 85c55600 85e091b8 85dea588 nt!CcLazyWriteScan+0x398
f7a157d0 804ee129 85c55600 85e091b8 85e091b8 fltmgr!FltpFsControl+0x5a
f7a15830 804f4355 c0000001 f7a15900 00000000 nt!CcLazyWriteScan+0x398
f7a15860 8057804e 85d9f190 85dea588 f7a15994 nt!MiRemoveImageSectionObject+0x16
f7a15950 805b4d3c 85dea588 00000000 85cf6178 nt!NtCreateMutant+0x17
f7a159d8 805b10e5 00000000 f7a15a18 00000040 nt!PipQueryDeviceCapabilities+0x154
f7a15a2c 8056b295 00000000 00000000 76c00000 nt!NtPowerInformation+0xa3
f7a15aa8 8056bc0c f7a15c8c 00100001 f7a15c54 nt!CcPreparePinWrite+0xd3
f7a15b04 8056f433 f7a15c8c 00100001 f7a15c54 nt!NtQueryInformationThread+0x45b
f7a15b44 f2c40637 f7a15c8c 00100001 f7a15c54 nt!NtQueryInformationToken+0x137c
f7a15b98 8053d668 f7a15c8c 00100001 f7a15c54 cmdguard+0xa637
f7a15bb8 804fe6c9 badb0d00 f7a15c30 00000000 nt!PoRegisterDeviceNotify+0x15
f7a15d60 8056bd37 85b989b8 85ce8140 8055b17c nt!CcPfLogPageFault+0x2cd
f7a15d74 80534c32 85ce8140 00000000 85fc3020 nt!NtSetIoCompletion+0x1c
f7a15dac 805c61e0 85ce8140 00000000 00000000 nt!KeVdmInsertQueueApc+0x2a
f7a15ddc 80541e12 80534b32 00000001 00000000 nt!IopCmResourcesToIoResources+0x25
f7a15df8 00000000 00000000 00000000 00001f80 nt!RtlpTraceDatabaseInternalAdd+0xc0


STACK_COMMAND: kb

FOLLOWUP_IP:
symsnap+1834f
f73bc34f ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: symsnap+1834f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: symsnap

IMAGE_NAME: symsnap.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4aafff59

FAILURE_BUCKET_ID: 0x19_20_symsnap+1834f

BUCKET_ID: 0x19_20_symsnap+1834f

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