Página 1 de 2 12 ÚltimoÚltimo
Resultados 1 al 20 de 30

Error en VIsta - Pantalla AZUl!!!

Esta es una discusión para el tema Error en VIsta - Pantalla AZUl!!! en el foro Ayuda Técnica, bajo la categoría Tecnologia; Desde hace unos dias me salen pantallas azules repentinas y se reinicia mi pc alguna ayuda de porque?? Tengo windows ...
Página: 1


  1. #1
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Error en VIsta - Pantalla AZUl!!!

    Desde hace unos dias me salen pantallas azules repentinas y se reinicia mi pc alguna ayuda de porque??
    Tengo windows Vista Ultimate 64 bits, la pc es relativamente nueva, empezando por la ram que tiene un par de dias. Recien instale el SO y no habia tenido ningun problema.
    HDD 500GB Seagate
    Placa Gigabyte Gigabyte EP45-UD3R
    Procesador CPU C2Q Q8200
    Fuente CM RealPower Pro 650W
    Video ATI RHD4850 ICEQ4TURBO 512MB
    Lo unico nuevo son las ram que las tengo 2 dias... 2x2GB OCZ Reaper de 1066mhz
    PD: Ya antes de comprar las RAM me habian salido una que otra vez las pantallas azules, pero ahora son mas frecuentes.
    (En XP no me pasaba esto u.u, pero XP 64 bits no me ha ido muy bien)

    Firma con problemas:
    Nombre del evento de problema: BlueScreen
    Versión del sistema operativo: 6.0.6001.2.1.0.256.1
    Id. de configuración regional: 10250
    Información adicional del problema:
    BCCode: a
    BCP1: 0000000000000040
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF80001F426F2
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 256_1
    Archivos que ayudan a describir el problema:
    C:\Windows\Minidump\Mini040509-01.dmp
    C:\Users\Juan\AppData\Local\Temp\WER-66487-0.sysdata.xml
    C:\Users\Juan\AppData\Local\Temp\WER76F3.tmp.versi on.txt
    Lea nuestra declaración de privacidad:
    http://go.microsoft.com/fwlink/?link...3&clcid=0x0c0a
    Última edición por dhetox; 05/04/2009 a las 15:15

  2. #2
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Aca mas detalle del error
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini040509-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0xfffff800`01e5d000 PsLoadedModuleList = 0xfffff800`02022db0
    Debug session time: Sun Apr 5 11:35:18.916 2009 (GMT-5)
    System Uptime: 0 days 0:04:03.728
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    ...................
    Loading User Symbols
    Loading unloaded module list
    .....
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {40, 2, 0, fffff80001f426f2}

    Probably caused by : memory_corruption ( nt!MiIdentifyPfn+6f2 )

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

    3: 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: 0000000000000040, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff80001f426f2, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002086080
    0000000000000040

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiIdentifyPfn+6f2
    fffff800`01f426f2 498b5b40 mov rbx,qword ptr [r11+40h]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: svchost.exe

    TRAP_FRAME: fffffa60044a4630 -- (.trap 0xfffffa60044a4630)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0200000000000000 rbx=0000000000000000 rcx=0000000000000002
    rdx=00000000002674f0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80001f426f2 rsp=fffffa60044a47c0 rbp=fffffa60044a4800
    r8=0200000000000000 r9=0000000000000542 r10=fffffa8006fce7b0
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    nt!MiIdentifyPfn+0x6f2:
    fffff800`01f426f2 498b5b40 mov rbx,qword ptr [r11+40h] ds:18c0:00000000`00000040=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80001eb20ee to fffff80001eb2350

    STACK_TEXT:
    fffffa60`044a44e8 fffff800`01eb20ee : 00000000`0000000a 00000000`00000040 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffffa60`044a44f0 fffff800`01eb0fcb : 00000000`00000000 fffffa60`044a46b0 fffffa80`03a1c000 00000580`00000000 : nt!KiBugCheckDispatch+0x6e
    fffffa60`044a4630 fffff800`01f426f2 : fffffa80`03a1c000 00000000`000018c0 fffff800`01ff0160 00000000`00000001 : nt!KiPageFault+0x20b
    fffffa60`044a47c0 fffff800`01f5cffe : 00000000`0004ce9e fffffa80`03a1c658 fffffa80`071d1bb0 00000000`00000000 : nt!MiIdentifyPfn+0x6f2
    fffffa60`044a4860 fffff800`0224bd75 : fffffa80`03a1c000 fffffa60`044a4ca0 fffffa60`044a4928 00000000`00000000 : nt!MmQueryPfnList+0x13e
    fffffa60`044a48a0 fffff800`021932dc : 00000000`000000a8 00000000`00000000 fffffa80`03a1c000 00000000`0379ef01 : nt!PfpPfnPrioRequest+0x115
    fffffa60`044a48f0 fffff800`0212854a : 00000000`00000000 00000000`0379eff0 00000000`0207e9f0 fffffa60`044a4901 : nt! ?? ::NNGAKEGL::`string'+0x46bea
    fffffa60`044a4960 fffff800`01eb1df3 : fffffa80`071d1bb0 00000000`0379eff0 00000000`02e70570 00000000`00000000 : nt!NtQuerySystemInformation+0xd0a
    fffffa60`044a4c20 00000000`772f5dda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0207e948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772f5dda


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiIdentifyPfn+6f2
    fffff800`01f426f2 498b5b40 mov rbx,qword ptr [r11+40h]

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!MiIdentifyPfn+6f2

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+6f2

    BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+6f2

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

  3. #3
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Me salio otro pantallazo azu....
    Firma con problemas:
    Nombre del evento de problema: BlueScreen
    Versión del sistema operativo: 6.0.6001.2.1.0.256.1
    Id. de configuración regional: 10250

    Información adicional del problema:
    BCCode: d1
    BCP1: FFFFF800010FEC80
    BCP2: 0000000000000000
    BCP3: 0000000000000008
    BCP4: FFFFF800010FEC80
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 256_1

    Archivos que ayudan a describir el problema:
    C:\Windows\Minidump\Mini040509-02.dmp
    C:\Users\Juan\AppData\Local\Temp\WER-125159-0.sysdata.xml
    C:\Users\Juan\AppData\Local\Temp\WER1831.tmp.versi on.txt

    Lea nuestra declaración de privacidad:
    http://go.microsoft.com/fwlink/?link...3&clcid=0x0c0a

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


    Loading Dump File [C:\Windows\Minidump\Mini040509-02.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0xfffff800`02063000 PsLoadedModuleList = 0xfffff800`02228db0
    Debug session time: Sun Apr 5 12:23:17.868 2009 (GMT-5)
    System Uptime: 0 days 0:47:15.094
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    ...................
    Loading User Symbols
    Loading unloaded module list
    .............
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {fffff800010fec80, 0, 8, fffff800010fec80}

    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+20b )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff800010fec80, memory referenced
    Arg2: 0000000000000000, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff800010fec80, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000228c080
    fffff800010fec80

    CURRENT_IRQL: 0

    FAULTING_IP:
    +0
    fffff800`010fec80 ?? ???

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: avp.exe

    TRAP_FRAME: fffffa60066637c0 -- (.trap 0xfffffa60066637c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000003650000 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffa8007217c10 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000231cefa rsp=fffffa6006663950 rbp=fffffa8007217d88
    r8=0000000000000002 r9=00000000ffffffff r10=0400000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nt!MiSecureVirtualMemory+0xea:
    fffff800`0231cefa 0fb600 movzx eax,byte ptr [rax] ds:5940:00000000`03650000=??
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff800020b80ee to fffff800020b8350

    FAILED_INSTRUCTION_ADDRESS:
    +0
    fffff800`010fec80 ?? ???

    STACK_TEXT:
    fffffa60`066630f8 fffff800`020b80ee : 00000000`0000000a fffff800`010fec80 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
    fffffa60`06663100 fffff800`020b6fcb : 00000000`00000008 fffffa60`06663410 00000000`00000700 00000000`00000020 : nt!KiBugCheckDispatch+0x6e
    fffffa60`06663240 fffff800`010fec80 : fffff800`020deec6 fffffa80`07f66158 fffffa60`06663520 fffff800`02063000 : nt!KiPageFault+0x20b
    fffffa60`066633d8 fffff800`020deec6 : fffffa80`07f66158 fffffa60`06663520 fffff800`02063000 00000000`00000001 : 0xfffff800`010fec80
    fffffa60`066633e0 fffff800`020da943 : 00000000`00000000 80000000`4980a963 00000000`03650000 fffffa80`00dc81e0 : nt!MiCompleteProtoPteFault+0x216
    fffffa60`06663460 fffff800`020dec2b : 00000000`00000000 00000000`03650000 00000000`03650000 ffffffff`fffffb80 : nt!MiResolveDemandZeroFault+0x763
    fffffa60`066634f0 fffff800`020de190 : 00000000`00000002 00000000`00000020 00000000`00000080 fffffa80`04027ac0 : nt!MiResolveProtoPteFault+0x42b
    fffffa60`06663570 fffff800`020c8a4a : fffffa80`07f66060 00000000`03650000 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x640
    fffffa60`066636d0 fffff800`020b6ed9 : 00000000`00000000 fffff6fb`400000d8 fffffa60`06663800 00000000`03651fff : nt!MmAccessFault+0x2a5a
    fffffa60`066637c0 fffff800`0231cefa : fffffa80`07217c10 00000000`03651fff fffff880`00000002 fffff880`08d178c8 : nt!KiPageFault+0x119
    fffffa60`06663950 fffff800`02353650 : 00000000`03650000 fffffa80`07217c10 fffffa60`06663b70 fffffa80`00000001 : nt!MiSecureVirtualMemory+0xea
    fffffa60`066639c0 fffff800`022fb05b : 00000000`00000004 fffffa80`07217c10 fffffa60`06663b70 00000000`00000000 : nt!MiMapViewOfSection+0x240
    fffffa60`06663ab0 fffff800`022e6ff3 : 00000000`03650000 00000000`00002000 fffffa60`06663ba0 00000000`00000000 : nt!AlpcpCreateView+0x1cb
    fffffa60`06663b70 fffff800`020b7df3 : fffffa80`07f66060 00000000`7efa0000 00000000`02966390 fffff880`0b1ab130 : nt!NtAlpcCreateSectionView+0x2c2
    fffffa60`06663c20 00000000`776e61fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`038ce7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776e61fa


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiPageFault+20b
    fffff800`020b6fcb 488d058e320000 lea rax,[nt!ExpInterlockedPopEntrySList (fffff800`020ba260)]

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt!KiPageFault+20b

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

    FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+20b

    BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+20b

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

  4. #4
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    nadie que me pueda ayudaR?

  5. #5
    Senior Member Avatar de ryohnosuke
    Fecha de ingreso
    09 dic, 03
    Mensajes
    1,052

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Tienes más minidmp para revisar? que si los análisis siguen siendo así de 'aleatorios' tiene más pinta de ser un problema de hardware que de software.

    Has revisado tus memorias con memtest86? has hecho algún tipo de OC?.
    ccc

  6. #6
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Cita Iniciado por ryohnosuke Ver mensaje
    Tienes más minidmp para revisar? que si los análisis siguen siendo así de 'aleatorios' tiene más pinta de ser un problema de hardware que de software.

    Has revisado tus memorias con memtest86? has hecho algún tipo de OC?.
    Ya revise las memorias con el memtest y no salio ningun error, no he hecho ningun OC. Acabo de desinstalar todos los driver de la placa y instale los drivers de vista 64 bits de la web de gigabyte, aca pongo el ultimo minidmp que me salio.
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\Mini040509-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*rutalocal*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18000.amd64fre.longhorn_rtm.080118-1840
    Machine Name:
    Kernel base = 0xfffff800`01c1c000 PsLoadedModuleList = 0xfffff800`01de1db0
    Debug session time: Sun Apr 5 14:34:34.699 2009 (GMT-5)
    System Uptime: 0 days 0:32:05.499
    Loading Kernel Symbols
    .
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    .................................................. ............
    .................................................. ..............
    ..............
    Loading User Symbols
    Loading unloaded module list
    .......
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {fffffa3005bfb840, 2, 1, fffff80001c7ee02}
    Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+22 )
    Followup: MachineOwner
    ---------
    3: 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: fffffa3005bfb840, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80001c7ee02, address which referenced memory
    Debugging Details:
    ------------------

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e45080
    fffffa3005bfb840
    CURRENT_IRQL: 2
    FAULTING_IP:
    nt!KeAcquireInStackQueuedSpinLock+22
    fffff800`01c7ee02 488711 xchg rdx,qword ptr [rcx]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    BUGCHECK_STR: 0xA
    PROCESS_NAME: avp.exe
    TRAP_FRAME: fffffa6006c45640 -- (.trap 0xfffffa6006c45640)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa3005bfb840
    rdx=fffffa6006c45800 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80001c7ee02 rsp=fffffa6006c457d8 rbp=fffffa3005bfb840
    r8=fffffa6006c45800 r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    nt!KeAcquireInStackQueuedSpinLock+0x22:
    fffff800`01c7ee02 488711 xchg rdx,qword ptr [rcx] ds:fffffa30`05bfb840=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80001c7112e to fffff80001c71390
    STACK_TEXT:
    fffffa60`06c454f8 fffff800`01c7112e : 00000000`0000000a fffffa30`05bfb840 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffffa60`06c45500 fffff800`01c7000b : 00000000`00000001 00000000`00000000 fffff880`0e4c3400 fffffa80`043c52c0 : nt!KiBugCheckDispatch+0x6e
    fffffa60`06c45640 fffff800`01c7ee02 : fffffa60`00a52746 fffffa80`043c5240 00000000`00000000 00000000`00000390 : nt!KiPageFault+0x20b
    fffffa60`06c457d8 fffffa60`00a52746 : fffffa80`043c5240 00000000`00000000 00000000`00000390 fffffa80`04955010 : nt!KeAcquireInStackQueuedSpinLock+0x22
    fffffa60`06c457e0 fffffa60`00a4d535 : fffffa80`043c50f0 00000000`00000000 fffffa80`05d907d0 00000000`00000000 : fltmgr!FltpLinkCompletionNodeToInstance+0x96
    fffffa60`06c45830 fffffa60`00a4c6a2 : fffffa60`06c45900 00000000`00000000 fffffa80`06fb4f12 fffffa80`00000000 : fltmgr!FltpPerformPreCallbacks+0x765
    fffffa60`06c45910 fffffa60`00a4b0c5 : fffffa80`078646d0 fffffa80`061b6d10 fffffa80`0493bf40 00000000`00000000 : fltmgr!FltpPassThrough+0x292
    fffffa60`06c459b0 fffff800`01ef2224 : fffffa80`06fb4f20 00000000`03680003 00000000`036ac002 fffff800`01c3f98c : fltmgr!FltpDispatch+0xb5
    fffffa60`06c45a10 fffff800`01eef890 : 00000000`00000000 fffffa80`06fb4f20 fffff880`0e6c1e70 fffffa80`06dcfc10 : nt!IopCloseFile+0x184
    fffffa60`06c45aa0 fffff800`01eefc47 : fffff880`0e6c1e70 fffffa80`00000001 fffffa80`06dcfc10 00000000`00000000 : nt!ObpDecrementHandleCount+0xc0
    fffffa60`06c45b30 fffff800`01eefe04 : fffff880`06c24ae0 fffff880`06c24a00 00000000`00000001 00000000`00001f9c : nt!ObpCloseHandleTableEntry+0xb7
    fffffa60`06c45bd0 fffff800`01c70e33 : fffffa80`056c3bb0 fffffa60`06c45ca0 00000000`7ef1c000 00000000`00008000 : nt!ObpCloseHandle+0x94
    fffffa60`06c45c20 00000000`77525b6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`07ade848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77525b6a

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!KeAcquireInStackQueuedSpinLock+22
    fffff800`01c7ee02 488711 xchg rdx,qword ptr [rcx]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nt!KeAcquireInStackQueuedSpinLock+22
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7
    FAILURE_BUCKET_ID: X64_0xA_nt!KeAcquireInStackQueuedSpinLock+22
    BUCKET_ID: X64_0xA_nt!KeAcquireInStackQueuedSpinLock+22
    Followup: MachineOwner
    ---------

  7. #7
    Senior Member Avatar de imp85
    Fecha de ingreso
    23 jul, 07
    Mensajes
    691

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    ¿Actualizaste a SP1 o es Vista con SP1 preinstalado?

  8. #8
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Viene con SP1 preinstalado
    ...
    un nuevo error...

    Firma con problemas:
    Nombre del evento de problema: BlueScreen
    Versión del sistema operativo: 6.0.6001.2.1.0.256.1
    Id. de configuración regional: 10250

    Información adicional del problema:
    BCCode: 50
    BCP1: FFFFF80007BA4A18
    BCP2: 0000000000000000
    BCP3: FFFFF800024CC13C
    BCP4: 0000000000000002
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 256_1

    Archivos que ayudan a describir el problema:
    C:\Windows\Minidump\Mini040509-02.dmp
    C:\Users\Juan\AppData\Local\Temp\WER-28017-0.sysdata.xml
    C:\Users\Juan\AppData\Local\Temp\WERB1D1.tmp.versi on.txt

    Lea nuestra declaración de privacidad:
    http://go.microsoft.com/fwlink/?link...3&clcid=0x0c0a

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


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

    Symbol search path is: SRV*rutalocal*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0xfffff800`0220f000 PsLoadedModuleList = 0xfffff800`023d4db0
    Debug session time: Sun Apr 5 18:38:32.324 2009 (GMT-5)
    System Uptime: 0 days 0:06:52.527
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    ................
    Loading User Symbols
    Loading unloaded module list
    .....
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffff80007ba4a18, 0, fffff800024cc13c, 2}


    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt!CmpRemoveKeyHash+4c )

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff80007ba4a18, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff800024cc13c, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002438080
    fffff80007ba4a18

    FAULTING_IP:
    nt!CmpRemoveKeyHash+4c
    fffff800`024cc13c 488b02 mov rax,qword ptr [rdx]

    MM_INTERNAL_CODE: 2

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    TRAP_FRAME: fffffa6001bdbac0 -- (.trap 0xfffffa6001bdbac0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80007ba4a10 rbx=0000000000000000 rcx=00000000000013b6
    rdx=fffff80007ba4a18 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800024cc13c rsp=fffffa6001bdbc58 rbp=0000000000000001
    r8=0000000000000000 r9=0000000023432e92 r10=fffff88007b23010
    r11=00000000000007ff r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    nt!CmpRemoveKeyHash+0x4c:
    fffff800`024cc13c 488b02 mov rax,qword ptr [rdx] ds:5cc0:fffff800`07ba4a18=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002272524 to fffff80002264350

    STACK_TEXT:
    fffffa60`01bdb9c8 fffff800`02272524 : 00000000`00000050 fffff800`07ba4a18 00000000`00000000 fffffa60`01bdbac0 : nt!KeBugCheckEx
    fffffa60`01bdb9d0 fffff800`02262ed9 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`07b23008 : nt!MmAccessFault+0x534
    fffffa60`01bdbac0 fffff800`024cc13c : fffff800`024cc1b3 fffff880`07b23008 00000000`00000001 00000000`23432e00 : nt!KiPageFault+0x119
    fffffa60`01bdbc58 fffff800`024cc1b3 : fffff880`07b23008 00000000`00000001 00000000`23432e00 00000000`00000202 : nt!CmpRemoveKeyHash+0x4c
    fffffa60`01bdbc60 fffff800`024d25ba : 00000000`00000000 00000000`23432e92 00000000`00000000 fffff800`024d5e28 : nt!CmpCleanUpKcbCacheWithLock+0x53
    fffffa60`01bdbc90 fffff800`024d5ef5 : 00000000`00000000 fffff880`00033120 fffff880`07ab7b60 fffffa80`039b2040 : nt!CmpDereferenceKeyControlBlock+0x18a
    fffffa60`01bdbcc0 fffff800`0227105a : fffff800`024d5e28 fffff800`023a18f8 fffffa80`039b2040 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xcd
    fffffa60`01bdbcf0 fffff800`02486ff3 : fffff800`0240c680 00000000`00000000 fffffa80`039b2040 00000000`00000080 : nt!ExpWorkerThread+0x11a
    fffffa60`01bdbd50 fffff800`0229e546 : fffffa60`019d2180 fffffa80`039b2040 fffffa60`019dbd40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
    fffffa60`01bdbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!CmpRemoveKeyHash+4c
    fffff800`024cc13c 488b02 mov rax,qword ptr [rdx]

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!CmpRemoveKeyHash+4c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

    FAILURE_BUCKET_ID: X64_0x50_nt!CmpRemoveKeyHash+4c

    BUCKET_ID: X64_0x50_nt!CmpRemoveKeyHash+4c

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

  9. #9
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Otra pantalla mas.... u.u
    Firma con problemas:
    Nombre del evento de problema: BlueScreen
    Versión del sistema operativo: 6.0.6001.2.1.0.256.1
    Id. de configuración regional: 10250

    Información adicional del problema:
    BCCode: a
    BCP1: 0000000000000008
    BCP2: 000000000000000C
    BCP3: 0000000000000000
    BCP4: FFFFF800022AC788
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 256_1

    Archivos que ayudan a describir el problema:
    C:\Windows\Minidump\Mini040509-03.dmp
    C:\Users\Juan\AppData\Local\Temp\WER-35287-0.sysdata.xml
    C:\Users\Juan\AppData\Local\Temp\WERF45C.tmp.versi on.txt

    Lea nuestra declaración de privacidad:
    http://go.microsoft.com/fwlink/?link...3&clcid=0x0c0a


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


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

    Symbol search path is: SRV*rutalocal*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0xfffff800`0224c000 PsLoadedModuleList = 0xfffff800`02411db0
    Debug session time: Sun Apr 5 19:14:26.214 2009 (GMT-5)
    System Uptime: 0 days 0:35:17.421
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    ................
    Loading User Symbols
    Loading unloaded module list
    ....
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {8, c, 0, fffff800022ac788}

    Probably caused by : ntkrnlmp.exe ( nt!ExpReleaseResourceForThreadLite+598 )

    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: 0000000000000008, memory referenced
    Arg2: 000000000000000c, IRQL
    Arg3: 0000000000000000, 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: fffff800022ac788, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002475080
    0000000000000008

    CURRENT_IRQL: c

    FAULTING_IP:
    nt!ExpReleaseResourceForThreadLite+598
    fffff800`022ac788 48391b cmp qword ptr [rbx],rbx

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: svchost.exe

    TRAP_FRAME: fffffa6004771890 -- (.trap 0xfffffa6004771890)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80002477440 rbx=0000000000000000 rcx=fffffa60005ec7f0
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800022ac788 rsp=fffffa6004771a20 rbp=0000000000000001
    r8=0000000000000000 r9=fffffa800668c101 r10=10013b5a4a390002
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nt!ExpReleaseResourceForThreadLite+0x598:
    fffff800`022ac788 48391b cmp qword ptr [rbx],rbx ds:19d1:00000000`00000000=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff800022a10ee to fffff800022a1350

    STACK_TEXT:
    fffffa60`04771748 fffff800`022a10ee : 00000000`0000000a 00000000`00000008 00000000`0000000c 00000000`00000000 : nt!KeBugCheckEx
    fffffa60`04771750 fffff800`0229ffcb : 00000000`00000000 fffff880`0f414010 00000000`00000000 00000000`00000008 : nt!KiBugCheckDispatch+0x6e
    fffffa60`04771890 fffff800`022ac788 : fffffa60`04771bc0 fffffa60`05cdbd38 fffffa60`04771bc0 fffffa60`05cdbd38 : nt!KiPageFault+0x20b
    fffffa60`04771a20 fffffa60`01216af7 : fffffa80`04d8e010 00000000`00000000 fffffa80`06657100 00000000`00000011 : nt!ExpReleaseResourceForThreadLite+0x598
    fffffa60`04771aa0 fffffa60`01218c04 : fffffa80`04d8e010 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCleanupIrpContext+0x2c8
    fffffa60`04771af0 fffffa60`012dd7cd : 00000000`00000000 fffffa80`05838c10 fffffa60`05cdbcb0 fffffa60`6d4e6f49 : Ntfs!NtfsExtendedCompleteRequest+0xd4
    fffffa60`04771b30 fffffa60`0122210d : fffffa80`04d8e010 fffffa80`05838c10 fffffa60`05cdbcb0 fffffa80`07df3b01 : Ntfs!NtfsCommonCreate+0x21c6
    fffffa60`04771d30 fffff800`0229b637 : fffffa60`05cdbc20 00000000`7ef50000 00000000`7ef52000 00000000`0d41ff88 : Ntfs!NtfsCommonCreateCallout+0x1d
    fffffa60`04771d60 fffff800`0229b5ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
    fffffa60`05cdbb40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!ExpReleaseResourceForThreadLite+598
    fffff800`022ac788 48391b cmp qword ptr [rbx],rbx

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!ExpReleaseResourceForThreadLite+598

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

    FAILURE_BUCKET_ID: X64_0xA_nt!ExpReleaseResourceForThreadLite+598

    BUCKET_ID: X64_0xA_nt!ExpReleaseResourceForThreadLite+598

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



    No se que mas pueda hacer... ya formatie 3 veces, use drivers de la misma web de mi placa (lo mismo con el video). pase el memtest a mi ram y no salio nada... alguna otra sugerencia?

  10. #10
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Otra pantalla azul...

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


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

    Symbol search path is: SRV*rutalocal*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0xfffff800`02258000 PsLoadedModuleList = 0xfffff800`0241ddb0
    Debug session time: Sun Apr 5 20:07:01.710 2009 (GMT-5)
    System Uptime: 0 days 0:51:49.529
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    ................
    Loading User Symbols
    Loading unloaded module list
    ....
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffffa000462dc20, 0, fffff800022cdd40, 5}


    Could not read faulting driver name
    Probably caused by : volsnap.sys ( volsnap!VspWriteVolumePhase25+5e6 )

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffa000462dc20, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff800022cdd40, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000005, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002481080
    fffffa000462dc20

    FAULTING_IP:
    nt!IoGetIoPriorityHint+0
    fffff800`022cdd40 8b4110 mov eax,dword ptr [rcx+10h]

    MM_INTERNAL_CODE: 5

    CUSTOMER_CRASH_COUNT: 4

    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    TRAP_FRAME: fffffa60025bea80 -- (.trap 0xfffffa60025bea80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8004071c10 rbx=0000000000000000 rcx=fffffa000462dc10
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800022cdd40 rsp=fffffa60025bec18 rbp=fffffa80041cadd0
    r8=0000000000000000 r9=0000000000000000 r10=00000000000007ff
    r11=fffffa60025bec18 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    nt!IoGetIoPriorityHint:
    fffff800`022cdd40 8b4110 mov eax,dword ptr [rcx+10h] ds:6f56:fffffa00`0462dc20=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff800022bb4e2 to fffff800022ad350

    STACK_TEXT:
    fffffa60`025be988 fffff800`022bb4e2 : 00000000`00000050 fffffa00`0462dc20 00000000`00000000 fffffa60`025bea80 : nt!KeBugCheckEx
    fffffa60`025be990 fffff800`022abed9 : 00000000`00000000 fffff800`022e51e2 00000000`00000000 fffffa80`059014b0 : nt!MmAccessFault+0x4f2
    fffffa60`025bea80 fffff800`022cdd40 : fffffa60`013bdd96 fffffa80`05901404 fffffa80`059014b0 00000000`00000008 : nt!KiPageFault+0x119
    fffffa60`025bec18 fffffa60`013bdd96 : fffffa80`05901404 fffffa80`059014b0 00000000`00000008 fffffa80`039f0520 : nt!IoGetIoPriorityHint
    fffffa60`025bec20 fffffa60`013c53fc : fffffa80`00040000 fffffa80`058ec540 fffffa80`05470010 fffffa80`039f0578 : volsnap!VspWriteVolumePhase25+0x5e6
    fffffa60`025bece0 fffffa60`013a84bd : fffffa80`039f0578 fffffa80`04dfaa60 fffffa80`04dfa9f0 fffffa80`04dfaa00 : volsnap!VspWriteVolumePhase22+0x2c
    fffffa60`025bed10 fffff800`024cfff3 : fffffa80`04aa6040 00000000`00000080 fffffa80`04aa4980 00000000`00000001 : volsnap!VspWorkerThread+0xad
    fffffa60`025bed50 fffff800`022e7546 : fffffa60`01963180 fffffa80`04aa6040 fffffa60`0196cd40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
    fffffa60`025bed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    volsnap!VspWriteVolumePhase25+5e6
    fffffa60`013bdd96 498bcc mov rcx,r12

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: volsnap!VspWriteVolumePhase25+5e6

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: volsnap

    IMAGE_NAME: volsnap.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 479198db

    FAILURE_BUCKET_ID: X64_0x50_volsnap!VspWriteVolumePhase25+5e6

    BUCKET_ID: X64_0x50_volsnap!VspWriteVolumePhase25+5e6

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

  11. #11
    Senior Member
    Fecha de ingreso
    29 jul, 03
    Ubicación
    japon
    Mensajes
    82

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    setea tus memorias manualmente desde bios tanto steps como voltaje segun caracteristicas de tus memorias. Creo es problema de voltaje que hace inestable el SO. Puedes probar aumenando un poco el voltaje CPU y NB para testear
    Core 2 Duo E6400 [email protected], Asus P5Q-E, DR2-800 3GB, ATI Radeon 4870, SSD G.Skill Falcon 64GB, PSU kurouto 450, LG ScarletII 32" FullHD

  12. #12
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Cita Iniciado por picapiedra Ver mensaje
    setea tus memorias manualmente desde bios tanto steps como voltaje segun caracteristicas de tus memorias. Creo es problema de voltaje que hace inestable el SO. Puedes probar aumenando un poco el voltaje CPU y NB para testear
    Ahorita estoy testeando ram por ram, le puse 1ro una de las ram de 2gb y funciono por mas de 30min sin ningun problema... ahorita estoy usando la otra memoria de 2gb y esta bien hasta el momento... podria ser uno de los slot de la placa??? si sigue bien voy a probar usar el otro slot de la placa.

    Nunca he seteado las memorias desde el bios, eso lo dejare para luego, alguna recomendacion decomo hacerlo :p?

  13. #13
    Senior Member
    Fecha de ingreso
    29 jul, 03
    Ubicación
    japon
    Mensajes
    82

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    busca el modelo de tu ram en la web del fabricante, ahi aparece las secs algo como ejemplo en tu caso puede ser 4-4-4-12. 2.2volt o 2.1volt por ahi

    En la bios en avanzados por ahi, cambiar de auto a manual y colocas los datos.

    Leyendo bien dices que ntes te pasó, que ram tenias y que tan frecuente era el error?.
    Core 2 Duo E6400 [email protected], Asus P5Q-E, DR2-800 3GB, ATI Radeon 4870, SSD G.Skill Falcon 64GB, PSU kurouto 450, LG ScarletII 32" FullHD

  14. #14
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Cita Iniciado por picapiedra Ver mensaje
    busca el modelo de tu ram en la web del fabricante, ahi aparece las secs algo como ejemplo en tu caso puede ser 4-4-4-12. 2.2volt o 2.1volt por ahi

    En la bios en avanzados por ahi, cambiar de auto a manual y colocas los datos.

    Leyendo bien dices que ntes te pasó, que ram tenias y que tan frecuente era el error?.
    Para mi ram es 5-5-5-(15-18) en el bios esta 15
    El model de ram es 2x2GB OCZ Reaper de 1066mhz
    El voltaje con el programa Everest marca lo siguiente 2.21v (para ambas ram)
    2.1v para cada una

    En el bios marca lo siguiente
    DRAM 1.8v (auto)
    DRAM Termination 0.9v auto
    Channel A Reference 0.9v auto
    Channel B Reference 0.9 auto

    Es lo mismo cuando uso una o uso 2 ram...
    Haber si notas algo raro ahi (el voltaje deberia ser en el bios 2.1?

  15. #15
    Senior Member
    Fecha de ingreso
    29 jul, 03
    Ubicación
    japon
    Mensajes
    82

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    dram entre 2.1 y 2.3 volt
    steps EPP 5-5-5-15
    (CAS-TRCD-TRP-TRAS)

    coloca y tesea
    Core 2 Duo E6400 [email protected], Asus P5Q-E, DR2-800 3GB, ATI Radeon 4870, SSD G.Skill Falcon 64GB, PSU kurouto 450, LG ScarletII 32" FullHD

  16. #16
    Senior Member
    Fecha de ingreso
    29 oct, 04
    Ubicación
    Viraco Arequipa
    Mensajes
    240

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Uhm es error de Memoria
    DUMP :D

    ... unica cosa, es quitar tu ram y probar otra..por que al parecer no quiere o esta forzada a detectarla..

    Corrijanme si esta mal !
    Yo le voy a AMD + Gentoo Linux + Steam = Happyness!

  17. #17
    Member Avatar de Dulce[K]^^!
    Fecha de ingreso
    27 feb, 09
    Mensajes
    45

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Cita Iniciado por edu4rdo Ver mensaje
    Uhm es error de Memoria
    DUMP :D

    ... unica cosa, es quitar tu ram y probar otra..por que al parecer no quiere o esta forzada a detectarla..

    Corrijanme si esta mal !
    :arrowu: agrre, puede ser memoria, hace unos meses tuve los mismos problemas, las pantallas azules seguidas, tb testie las ram para ver si me arrojaba errores pero no detectaba nada, pero igual decidi cambiarlas y a partir de ahi no me trajo ningun incoveniento, prueba poniendo otras memorias, o inclusive otras marcas...

    Saludos...

  18. #18
    Senior Member
    Fecha de ingreso
    29 jul, 03
    Ubicación
    japon
    Mensajes
    82

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Cita Iniciado por edu4rdo Ver mensaje
    Uhm es error de Memoria
    DUMP :D

    ... unica cosa, es quitar tu ram y probar otra..por que al parecer no quiere o esta forzada a detectarla..

    Corrijanme si esta mal !
    No entendi con esa parte de "al parecer no quiere o esta forzada a detectarla.."

    Sigo pensando que lo mas facil es colocar los datos manualmente, sino sabes busca temas referidos a overclock
    Core 2 Duo E6400 [email protected], Asus P5Q-E, DR2-800 3GB, ATI Radeon 4870, SSD G.Skill Falcon 64GB, PSU kurouto 450, LG ScarletII 32" FullHD

  19. #19
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Voy a probar cambiando el voltaje manualmente a 2.1v

    Dulce te refieres a que mi placa no soporta las ram o que las ram andan defectuosas o que?

  20. #20
    Senior Member
    Fecha de ingreso
    05 mar, 09
    Ubicación
    Lima
    Mensajes
    344

    Predeterminado Re: Error en VIsta - Pantalla AZUl!!!

    Probe poner manualmente los voltajes a como deberia haber estado
    estaba 3 5 5 5 15 y 1.8v
    segun la descripcion de la ram deberian trabajar a 3 5 5 5 18 y 2.1 - 2.2v (estan a 2.1v ahora) mi pc va encendida casi 3 horas y no me ha salido ningun pantallaso azul :) aun no kiero cantar victoria xD voy a exigirla mas y les estare informando.

Página 1 de 2 12 ÚltimoÚltimo

Temas similares

  1. pantalla azul :S
    Por alex_20 en el foro Ayuda Técnica
    Respuestas: 5
    Último mensaje: 08/10/2008, 15:19
  2. error pantalla azul
    Por tumeodar en el foro Ayuda Técnica
    Respuestas: 3
    Último mensaje: 03/06/2008, 22:45
  3. pantalla azul
    Por p1kachu en el foro Ayuda Técnica
    Respuestas: 5
    Último mensaje: 04/01/2008, 22:04
  4. PANTALLA AZUL EN WIN XP PRO??????????
    Por EL HABITANTE en el foro Ayuda Técnica
    Respuestas: 4
    Último mensaje: 15/03/2005, 00:53

Permisos de publicación

  • No puedes crear nuevos temas
  • No puedes responder temas
  • No puedes subir archivos adjuntos
  • No puedes editar tus mensajes
  •