Debe estar conectado para participar
Buscar en los foros:


 






Uso de Comodín:
*    coincide cualquier número de caracteres
%    coincide exactamente un caracter

Bsod

No hay Etiquetas
Entrada
High End Level

agustin2004

entradas: 973

21:39 20/12/2008

1

bue no se que pasa. ya van dos veces que me aparece la sigueinte pantalla azul:
una fue hace 2 semanas y la otra hoy:
segun windbug:
la de hoy:

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

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

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Kernel base = 0x82811000 PsLoadedModuleList = 0x8291e930
Debug session time: Sat Dec 20 21:13:26.807 2008 (GMT-2)
System Uptime: 0 days 0:57:20.807
Loading Kernel Symbols
………………………………………….. ………………………………………….. ………………………………………….. ….
Loading User Symbols
Loading unloaded module list
….
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {e454, 2, 1, 8289442b}

Probably caused by : memory_corruption ( nt!MiComputeFlushRange+22d )

Followup: MachineOwner
———

0: 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: 0000e454, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8289442b, address which referenced memory

Debugging Details:
——————

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8293d6d8
Unable to read MiSystemVaType memory at 8291e2e0
0000e454

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiComputeFlushRange+22d
8289442b 890a mov dword ptr [edx],ecx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: VSSVC.exe

TRAP_FRAME: ae5728e4 — (.trap 0xffffffffae5728e4)
ErrCode = 00000002
eax=86131f10 ebx=86131f58 ecx=86132d7c edx=0000e454 esi=86131f58 edi=00000002
eip=8289442b esp=ae572958 ebp=ae572980 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!MiComputeFlushRange+0x22d:
8289442b 890a mov dword ptr [edx],ecx ds:0023:0000e454=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8289442b to 8286bc84

STACK_TEXT:
ae5728e4 8289442b badb0d00 0000e454 ae5729f4 nt!KiTrap0E+0x2ac
ae572980 828930b4 00000000 00000000 8ebe36c8 nt!MiComputeFlushRange+0x22d
ae5729d4 82848953 86130514 00000000 00000001 nt!MmFlushSection+0x3b
ae572a68 8c0857f7 86130514 00000000 00000000 nt!CcFlushCache+0x239
ae572abc 8c07f377 01996aa8 8ebc7488 00000000 Ntfs!NtfsFlushUserStream+0x7b
ae572b58 8c086f47 87996aa8 863250d8 00000001 Ntfs!NtfsFlushVolume+0x272
ae572bd4 8c08743d 87996aa8 86be3b48 2253169e Ntfs!NtfsCommonFlushBuffers+0x1bc
ae572c3c 828571cd 86325020 86be3b48 86be3b48 Ntfs!NtfsFsdFlushBuffers+0xf4
ae572c54 8bca4ba7 861474e0 86be3b48 00000000 nt!IofCallDriver+0x63
ae572c78 8bca4d64 ae572c98 861474e0 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksComple ted+0x251
ae572cb0 828571cd 861474e0 86be3b48 86be3b48 fltmgr!FltpDispatch+0xc2
ae572cc8 82a04054 86be3b48 00000000 873609a8 nt!IofCallDriver+0x63
ae572ce8 829e8a10 861474e0 873609a8 00000000 nt!IopSynchronousServiceTail+0x1d9
ae572d54 8286897a 00000401 00b5f6d4 00b5f6f8 nt!NtFlushBuffersFile+0x1e6
ae572d54 77909a94 00000401 00b5f6d4 00b5f6f8 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00b5f6f8 00000000 00000000 00000000 00000000 0x77909a94

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiComputeFlushRange+22d
8289442b 890a mov dword ptr [edx],ecx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiComputeFlushRange+22d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiComputeFlushRange+22d

BUCKET_ID: 0xA_W_nt!MiComputeFlushRange+22d

Followup: MachineOwner

por la pantalla azul anterior pregunte en el foro de microsft, pero como la pc estaba oceada me trataron de delincuente

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

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

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Kernel base = 0x82810000 PsLoadedModuleList = 0x8291d930
Debug session time: Tue Dec 9 11:14:46.322 2008 (GMT-2)
System Uptime: 0 days 1:27:46.379
Loading Kernel Symbols
………………………………………….. ………………………………………….. ………………………………………….. …….
Loading User Symbols
Loading unloaded module list
….
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {72fc, 2, 1, 8289342b}

Probably caused by : memory_corruption ( nt!MiComputeFlushRange+22d )

Followup: MachineOwner
———

0: 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: 000072fc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8289342b, address which referenced memory

Debugging Details:
——————

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8293c6d8
Unable to read MiSystemVaType memory at 8291d2e0
000072fc

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiComputeFlushRange+22d
8289342b 890a mov dword ptr [edx],ecx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: VSSVC.exe

TRAP_FRAME: ac8c08e4 — (.trap 0xffffffffac8c08e4)
ErrCode = 00000002
eax=86137f10 ebx=86137f58 ecx=8613aeb4 edx=000072fc esi=86137f58 edi=00000002
eip=8289342b esp=ac8c0958 ebp=ac8c0980 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!MiComputeFlushRange+0x22d:
8289342b 890a mov dword ptr [edx],ecx ds:0023:000072fc=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8289342b to 8286ac84

STACK_TEXT:
ac8c08e4 8289342b badb0d00 000072fc ac8c09f4 nt!KiTrap0E+0x2ac
ac8c0980 828920b4 00000000 00000000 8ebfec88 nt!MiComputeFlushRange+0x22d
ac8c09d4 82847953 861366cc 00000000 00000001 nt!MmFlushSection+0x3b
ac8c0a68 8c0827f7 861366cc 00000000 00000000 nt!CcFlushCache+0x239
ac8c0abc 8c07c377 01d10ee8 8ebe8d80 00000000 Ntfs!NtfsFlushUserStream+0x7b
ac8c0b58 8c083f47 87d10ee8 85da40d8 00000001 Ntfs!NtfsFlushVolume+0x272
ac8c0bd4 8c08443d 87d10ee8 87ce8690 2088069b Ntfs!NtfsCommonFlushBuffers+0x1bc
ac8c0c3c 828561cd 85da4020 87ce8690 87ce8690 Ntfs!NtfsFsdFlushBuffers+0xf4
ac8c0c54 8bc9aba7 8631d5e8 87ce8690 00000000 nt!IofCallDriver+0x63
ac8c0c78 8bc9ad64 ac8c0c98 8631d5e8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksComple ted+0x251
ac8c0cb0 828561cd 8631d5e8 87ce8690 87ce8690 fltmgr!FltpDispatch+0xc2
ac8c0cc8 82a03054 87ce8690 00000000 87a1fbd8 nt!IofCallDriver+0x63
ac8c0ce8 829e7a10 8631d5e8 87a1fbd8 00000000 nt!IopSynchronousServiceTail+0x1d9
ac8c0d54 8286797a 00000401 039df9bc 039df9e0 nt!NtFlushBuffersFile+0x1e6
ac8c0d54 77159a94 00000401 039df9bc 039df9e0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
039df9e0 00000000 00000000 00000000 00000000 0x77159a94

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiComputeFlushRange+22d
8289342b 890a mov dword ptr [edx],ecx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiComputeFlushRange+22d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiComputeFlushRange+22d

BUCKET_ID: 0xA_W_nt!MiComputeFlushRange+22d

Followup: MachineOwner

por lo que parece el error lo genera Volume Shadow Copy
pero no tengo la mas puta idea de como arreglar esto.
formateo?

Extreme Level

aledb12

entradas: 2461

21:44 20/12/2008

2

parece que tenes problemas los drivers/ disco rigido. Busque un poco sobre el VSSVC.exe y es un servicio que permite a los archivos que son modificados, sean respaldados automaticamente por el sistema operativo. Espero que alguien que sepa en el tema te ayude .

Hardcore Extreme Level

ivan quaglia

entradas: 14363

12:01 21/12/2008

3

que estabas haciendo cuando sucedio?

High End Level

agustin2004

entradas: 973

12:33 21/12/2008

4
Cita Iniciado por ivan quaglia
Ver Mensaje
que estabas haciendo cuando sucedio?

las dos veces nada.

Hardcore Extreme Level

ivan quaglia

entradas: 14363

13:24 21/12/2008

5

de casualidad testeaste la memoria?

High End Level

agustin2004

entradas: 973

13:43 21/12/2008

6

nop, que programa me conviene usar?

Hardcore Extreme Level

ivan quaglia

entradas: 14363

13:47 21/12/2008

7

memtest, en los cd de instalacion de ubuntu viene, tambien podes bajarte el hiren boot tiene varios testeadores

High End Level

agustin2004

entradas: 973

14:18 21/12/2008

8

ahora hago eso, pero por ser un proceso relacionado con los discos rigidos, hay alguna posibilidad de que uno de estos este dañado?

Hardcore Extreme Level

ivan quaglia

entradas: 14363

16:33 21/12/2008

9

si existe la posibilidad pero en este mundo hay que trabajar por descarte. es mas probable que sea algo insignificante primero… por ejemplo un cable. habria que probar cambiando el cable de datos y/o el puerto usado

High End Level

agustin2004

entradas: 973

17:16 21/12/2008

10
Cita Iniciado por ivan quaglia
Ver Mensaje
si existe la posibilidad pero en este mundo hay que trabajar por descarte. es mas probable que sea algo insignificante primero… por ejemplo un cable. habria que probar cambiando el cable de datos y/o el puerto usado

cambie el cable del disco seagate que estaba muy doblado. voy a dejar la pc encendida 24 horas para ver que onda

Hardcore Extreme Level

Fede777

CapFed

entradas: 4718

17:26 21/12/2008

11
Cita Iniciado por agustin2004
Ver Mensaje
formatia, y seguro que funca todo de nuevo

……………

Nuevo miembro

makakoloco

entradas: 36

07:29 22/12/2008

12

Probaste usando driver verifier?
http://support.microsoft.com/kb/244617