1. Este site usa cookies. Ao continuar a usar este site está a concordar com o nosso uso de cookies. Saber Mais.

[LER 1º POST] "BSoD/Ecrã Azul" - Como diagnosticar e resolver

Discussão em 'Windows 7 e anteriores' iniciada por Madcaddie, 2 de Novembro de 2008. (Respostas: 2327; Visualizações: 324708)

  1. lordbifana

    lordbifana Power Member

    o meu pc começou a dar um erro DPC_watchdog_violation ja actualizei as drivers todas e tudo o que encontrei no google mas persiste...algum conselho?
     
  2. Spartacuss

    Spartacuss Power Member

    Conseguiste resolver o teu problema?
     
  3. Blue Zee

    Blue Zee Power Member

    Desinstala os controladores Nvidia com o DDU.

    Reinicia e reinstala.
    A ver.
     
  4. rjckarddo

    rjckarddo Power Member

    Boas, ao fim de 6 anitos o meu asus ofereu-me o BSOD.

    Assinatura do problema:
    Nome do Evento de Problema: BlueScreen
    Versão do SO: 6.1.7601.2.1.0.256.48
    ID de Região: 2070

    Informações adicionais sobre o problema:
    BCCode: d1
    BCP1: 000000000000002C
    BCP2: 0000000000000002
    BCP3: 0000000000000001
    BCP4: FFFFF880058FB4CE
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Ficheiros que ajudam a descrever o problema:
    C:\Windows\Minidump\060517-10046-01.dmp
    C:\Users\Ricardo\AppData\Local\Temp\WER-24679-0.sysdata.xml

    Leia a nossa declaração de privacidade online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0816

    Se a declaração de privacidade online não estiver disponível, leia a declaração de privacidade offline:
    C:\Windows\system32\pt-PT\erofflps.txt


    Alguém me consegue dar alguma dica de possíveis causas? Desde já o meu agradecimento.
     
  5. Titantropo

    Titantropo Power Member

    Eu que estava tão contente de não ter BSOD's há uns dois anos... Será do disco novo? Tenho o sistema a arrancar automaticamente, mas isto não está a gravar em lado nenhum. Porquê?

    Já agora, "Imagem de Erro Mínima da Memória (256KB)" ou "Imagem de Erro da Memória Kernel"?

    Edit: já que tinha isto para não reiniciar, mesmo não gravando, tirei uma foto que diz drive_not_les_or_equal
    cmudaxp.sys

    Pelo que vi na net e aqui https://vip.asus.com/forum/view.asp...X&id=20080822024635828&page=1&SLanguage=en-us

    Pode ser drivers da placa de som. Antes de ir mexer em algum lado a estas horas, haverá alguma coisa que sustente essa informação? Algum caso anterior que já vos tenha passado pelas mãos...
     
    Última edição: 3 de Setembro de 2017
  6. ipel77

    ipel77 Power Member

    Já há algum tempo que tenho alguns BSOD no pc e não sei qual é a causa. Segui os passos do 1º post e tive este relatório:

    se !analyze -v to get detailed debugging information.

    BugCheck 3B, {c0000005, fffff800030c258d, fffff88002852040, 0}

    Probably caused by : win32k.sys ( win32k!RawInputThread+9b0 )

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

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

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff800030c258d, Address of the instruction which caused the bugcheck
    Arg3: fffff88002852040, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - A instru o no 0x%08lx fez refer ncia mem ria no 0x%08lx. A mem ria n o p de ser %s.

    FAULTING_IP:
    nt!KiDeliverApc+ed
    fffff800`030c258d 498b4a30 mov rcx,qword ptr [r10+30h]

    CONTEXT: fffff88002852040 -- (.cxr 0xfffff88002852040;r)
    rax=0000000000000000 rbx=fffffa80060fb8b0 rcx=0000000000000002
    rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80060fb900
    rip=fffff800030c258d rsp=fffff88002852a10 rbp=fffff88002852c20
    r8=fffbfa80060fb900 r9=000000000000000d r10=fffbfa80060fb8f0
    r11=fffffa80060fb8b0 r12=fffffa8006075b10 r13=0000000000000000
    r14=0000000000000002 r15=0000000000000001
    iopl=0 nv up ei ng nz na po cy
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
    nt!KiDeliverApc+0xed:
    fffff800`030c258d 498b4a30 mov rcx,qword ptr [r10+30h] ds:002b:fffbfa80`060fb920=????????????????
    Last set context:
    rax=0000000000000000 rbx=fffffa80060fb8b0 rcx=0000000000000002
    rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80060fb900
    rip=fffff800030c258d rsp=fffff88002852a10 rbp=fffff88002852c20
    r8=fffbfa80060fb900 r9=000000000000000d r10=fffbfa80060fb8f0
    r11=fffffa80060fb8b0 r12=fffffa8006075b10 r13=0000000000000000
    r14=0000000000000002 r15=0000000000000001
    iopl=0 nv up ei ng nz na po cy
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
    nt!KiDeliverApc+0xed:
    fffff800`030c258d 498b4a30 mov rcx,qword ptr [r10+30h] ds:002b:fffbfa80`060fb920=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: csrss.exe

    CURRENT_IRQL: 2

    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

    LAST_CONTROL_TRANSFER: from fffff8000307ff0d to fffff800030c258d

    STACK_TEXT:
    fffff880`02852a10 fffff800`0307ff0d : 00000000`00000004 00000000`00000000 00000000`00000000 00000000`00000004 : nt!KiDeliverApc+0xed
    fffff880`02852a90 fffff800`0314fc03 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiCheckForKernelApcDelivery+0x25
    fffff880`02852ac0 fffff960`000d73b0 : 00000000`00000000 fffff960`00308ed0 00000000`00000004 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x41084
    fffff880`02852af0 fffff960`00065378 : fffffa80`0000007b fffffa80`0000000f fffff880`00000001 ffffffff`80000454 : win32k!RawInputThread+0x9b0
    fffff880`02852bc0 fffff960`000e819a : fffffa80`00000002 fffff880`046dcf40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
    fffff880`02852bf0 fffff800`030cdc13 : fffffa80`060fb8b0 00000000`00000004 000007ff`fffd3000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
    fffff880`02852c20 000007fe`fd7e1f1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`019cfa88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd7e1f1a


    FOLLOWUP_IP:
    win32k!RawInputThread+9b0
    fffff960`000d73b0 448b1d39202300 mov r11d,dword ptr [win32k!gnRetryReadInput (fffff960`003093f0)]

    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: win32k!RawInputThread+9b0
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME: win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5960f368
    IMAGE_VERSION: 6.1.7601.23865
    STACK_COMMAND: .cxr 0xfffff88002852040 ; kb
    FAILURE_BUCKET_ID: X64_0x3B_win32k!RawInputThread+9b0
    BUCKET_ID: X64_0x3B_win32k!RawInputThread+9b0
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x3b_win32k!rawinputthread+9b0
    FAILURE_ID_HASH: {606088d1-53bb-c486-87da-0475c66e2179}
    Followup: MachineOwner


    Será que alguém me pode ajudar?
    O PC é este:

    i7 860 @4.0GHz
    Maximus III Formula
    GSkill Trident 2000MHz (2x2Gb)
    Sapphire HD5850
    Intel SSD 330 120Gb / Seagate 500GB
    Corsair HX-650
     
  7. Titantropo

    Titantropo Power Member

    Preciso mesmo de saber se devo escolher a "Imagem de Erro Mínima da Memória (256KB)" ou "Imagem de Erro da Memória Kernel", porque isto está a piorar. E já agora, um modo de analisar o disco que eu próprio consiga perceber, porque acho que o mal é do disco.

    Já agora, isto ajuda a saber o que causou o BSOD de hoje, já que os dumps não gravam?

    Nome do registo:System
    Origem: Microsoft-Windows-Kernel-Power
    Data: 25-09-2017 23:26:07
    ID do evento: 89
    Categoria de Tarefa:(86)
    Nível: Informações
    Palavras-chave:(32)
    Utilizador: SYSTEM
    Computador:
    Descrição:
    A zona térmica ACPI ACPI\ThermalZone\TZ00 foi enumerada.
    _PSV = 0K
    _TC1 = 0
    _TC2 = 0
    _TSP = 0ms
    _AC0 = 353K
    _AC1 = 328K
    _AC2 = 323K
    _AC3 = 318K
    _AC4 = 313K
    _AC5 = 0K
    _AC6 = 0K
    _AC7 = 0K
    _AC8 = 0K
    _AC9 = 0K
    _CRT = 378K
    _HOT = 0K
    _PSL - ver dados de evento.
    Evento Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>89</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>86</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000020</Keywords>
    <TimeCreated SystemTime="2017-09-25T22:26:07.075052700Z" />
    <EventRecordID>119749</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="72" />
    <Channel>System</Channel>
    <Computer></Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="ThermalZoneDeviceInstanceLength">21</Data>
    <Data Name="ThermalZoneDeviceInstance">ACPI\ThermalZone\TZ00</Data>
    <Data Name="AffinityCount">1</Data>
    <Data Name="_PSV">0</Data>
    <Data Name="_TC1">0</Data>
    <Data Name="_TC2">0</Data>
    <Data Name="_TSP">0</Data>
    <Data Name="_AC0">353</Data>
    <Data Name="_AC1">328</Data>
    <Data Name="_AC2">323</Data>
    <Data Name="_AC3">318</Data>
    <Data Name="_AC4">313</Data>
    <Data Name="_AC5">0</Data>
    <Data Name="_AC6">0</Data>
    <Data Name="_AC7">0</Data>
    <Data Name="_AC8">0</Data>
    <Data Name="_AC9">0</Data>
    <Data Name="_CRT">378</Data>
    <Data Name="_HOT">0</Data>
    <ComplexData Name="_PSL">0000000000000000</ComplexData>
    </EventData>
    </Event>
     
    Última edição: 26 de Setembro de 2017
  8. The "ATTEMPTED WRITE TO READONLY MEMORY" BSOD (Blue Screen of Death) error may appear when the computer abruptly shuts down during the initialization process for Windows Operating System. The Blue Screen of Death is really just the popularized name for what is technically called a STOP message or STOP error.

    To resolve the ATTEMPTED WRITE TO READONLY MEMORY BSOD error, check the system for over clocking. You can disable all Overclocking or use a lower setting based on the clock frequency specified by the manufacturer of the CPU, GPU, and other installed devices. You can also resolve this issue by employing the Last Known Good Configuration feature that allows you to start the computer by employing the latest settings and configurations that worked.

    To check if the error is caused by a faulty drive, run an automatic driver update or manually update the drivers to the latest available versions.

    To manually update a driver, follow these steps:

    1. Click Start
    2. Type in devmgmt.msc in the search box
    3. Click devmgmt from results list
    4. Right-click on the driver
    5. To update the driver, select Update Driver Software.
    6. To disable the driver, select Disable.
    7. To uninstall the driver, select Uninstall.
    To run an automatic driver update, follow these steps:

    1. Click Start
    2. Go to Devices and Printers
    3. Right-click on your computer
    4. Select Device Installation Settings
    5. Select Yes, do this automatically
    6. Click Save Changes