Problema BSoD / Ecrã Azul - como diagnosticar e resolver?
- Autor do tópico Madcaddie
- Data Início
RostabalPT
Power Member
Tenho este PC à exatamente 1 semana. Atualizei logo para o Windows 10 mas parece-me que sempre que tenho certas aplicações abertas por um determinado tempo tenho o BSoD.
A aplicação que mais noto isso é no qBittorrent.
Eu quando fiz a atualização para o 10 só fiz o "Repor este PC". Será que ocorreu algo durante o upgrade e com uma instalação de raiz isto vai ao sítio?
EDIT: Ontem o pc entrou numa boot loop e nem sei como resolvi aquilo mas fiz um clean install. Pensava que tinha resolvido à uns minutos teve outro ecrã azul com o erro: page in nonpaged area. Começo a pensar que é um driver qualquer que está a causar isto pois ontem à noite estive a atualizar os drivers através do Gestor de Dispositivos.
A aplicação que mais noto isso é no qBittorrent.
Eu quando fiz a atualização para o 10 só fiz o "Repor este PC". Será que ocorreu algo durante o upgrade e com uma instalação de raiz isto vai ao sítio?
EDIT: Ontem o pc entrou numa boot loop e nem sei como resolvi aquilo mas fiz um clean install. Pensava que tinha resolvido à uns minutos teve outro ecrã azul com o erro: page in nonpaged area. Começo a pensar que é um driver qualquer que está a causar isto pois ontem à noite estive a atualizar os drivers através do Gestor de Dispositivos.
Última edição:
regster
Power Member
Tenho aqui um PC que o último BSOD foi este:
==================================================
Dump File : 103115-17238-01.dmp
Crash Time : 31-10-2015 17:08:13
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`0063af20
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74200
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.19018 (win7sp1_gdr.150928-1507)
Processor : x64
Crash Address : ntoskrnl.exe+74200
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\103115-17238-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 318.208
Dump File Time : 31-10-2015 17:09:29
==================================================
Cumps.
==================================================
Dump File : 103115-17238-01.dmp
Crash Time : 31-10-2015 17:08:13
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`0063af20
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74200
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.19018 (win7sp1_gdr.150928-1507)
Processor : x64
Crash Address : ntoskrnl.exe+74200
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\103115-17238-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 318.208
Dump File Time : 31-10-2015 17:09:29
==================================================
Cumps.
Olá 
Hoje estava a criar um disco de reparação e de repente o PC desliga-se sozinho e quando liga aparece o ecrã azul com a seguinte mensagem: OCORREU UM PROBLEMA NO PC E É NECESSÁRIO REINICIA-LO. O PC SERÁ REINICIADO AUTOMATICAMENTE. ERRO MEMORY_MANAGEMENT
Depois da mensagem o PC tenta reiniciar mas aparece sempre a mesma mensagem e o PC está sempre a tentar reiniciar sem efeito.
Se alguém me puder ajudar agradecia! Eu necessito do PC para trabalhar.
Hoje estava a criar um disco de reparação e de repente o PC desliga-se sozinho e quando liga aparece o ecrã azul com a seguinte mensagem: OCORREU UM PROBLEMA NO PC E É NECESSÁRIO REINICIA-LO. O PC SERÁ REINICIADO AUTOMATICAMENTE. ERRO MEMORY_MANAGEMENT
Depois da mensagem o PC tenta reiniciar mas aparece sempre a mesma mensagem e o PC está sempre a tentar reiniciar sem efeito.
Se alguém me puder ajudar agradecia! Eu necessito do PC para trabalhar.
Viva,
Nos últimos dias tenho tido um bsod no meu computador sempre que o inicio pela primeira vez durante o dia. O erro indicado é este: PAGE_FAULT_IN_NONPAGED_AREA. Algumas sugestões? Estou a utilizar o windows 8.1 64bit...Devo fazer a atualização para o 10 na esperança que isto vá ao sítio?
Nos últimos dias tenho tido um bsod no meu computador sempre que o inicio pela primeira vez durante o dia. O erro indicado é este: PAGE_FAULT_IN_NONPAGED_AREA. Algumas sugestões? Estou a utilizar o windows 8.1 64bit...Devo fazer a atualização para o 10 na esperança que isto vá ao sítio?
paulosousa11
Membro
Malta alguém me pode ajudar? Desde há uns dias para cá tenho tido BSOD fiz o tutorial que está na primeira página (tinha 3 'files' na pasta minidump)
As possíveis causas que apareceram foi isto:
win32kfull.sys
hardware ( nt!MiOutPageSingleKernelStack+2b4 )
dxgmms1.sys
Fiz atualização para windows 10 na esperança de isto resolver mas continua igual.
O que devo fazer? Estava a pensar em fazer uma 'instalação limpa 'do windows 10...
agradecia ajuda.
As possíveis causas que apareceram foi isto:
win32kfull.sys
hardware ( nt!MiOutPageSingleKernelStack+2b4 )
dxgmms1.sys
Fiz atualização para windows 10 na esperança de isto resolver mas continua igual.
O que devo fazer? Estava a pensar em fazer uma 'instalação limpa 'do windows 10...
agradecia ajuda.
lacerdamachado
Membro
Boa tarde,
Hoje mais uma vez voltou-me a aparecer um blue screen quando simplesmente a ver um video online. o pc desligou se e quando ligue mostrou me uma janela com o seguntes promenores:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: FFFFF880063C4638
BCP2: 0000000000000002
BCP3: 0000000000000008
BCP4: FFFFF880063C4638
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\031416-10140-01.dmp
C:\Users\Manuel\AppData\Local\Temp\WER-62806-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Reinstalei o windows e as drivers a pouco tempo pois li na internet que podia ser um erro da intalação das drivers.
Espero que me possam ajudar com alguma solução ou dica.
Obrigado
Hoje mais uma vez voltou-me a aparecer um blue screen quando simplesmente a ver um video online. o pc desligou se e quando ligue mostrou me uma janela com o seguntes promenores:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: FFFFF880063C4638
BCP2: 0000000000000002
BCP3: 0000000000000008
BCP4: FFFFF880063C4638
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\031416-10140-01.dmp
C:\Users\Manuel\AppData\Local\Temp\WER-62806-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Reinstalei o windows e as drivers a pouco tempo pois li na internet que podia ser um erro da intalação das drivers.
Espero que me possam ajudar com alguma solução ou dica.
Obrigado
vieirinha6712
Power Member
Sacka o Hardware monitor e mete aqui print
lacerdamachado
Membro
![btn_viewall.gif" style="border:none;" alt="lacerdamachado&](http://<div style="width:480px;text-align:right;"><embed width="480" height="360" src="http://pic2.pbsrc.com/flash/rss_slideshow.swf" flashvars="rssFeed=http%3A%2F%2Ffeed1108.photobucket.com%2Falbums%2Fh406%2Flacerdamachado%2Ffeed.rss" type="application/x-shockwave-flash" wmode="transparent" /><a href="javascript:void(0);" target="_blank"><img src="http://pic.photobucket.com/share/icons/embed/btn_geturs.gif" style="border:none;" /></a><a href="http://s1108.photobucket.com/user/lacerdamachado/library/" target="_blank"><img src="http://pic.photobucket.com/share/icons/embed/btn_viewall.gif" style="border:none;" alt="lacerdamachado's album on Photobucket" /></a></div>){kind=icon}
vieirinha6712
Power Member
As temperaturas tão boas passe lhe com um memtest86 e deixa o correr umas boas horas eu normalmente quando é pra testar as memorias deixo sempre uma noite inteira a testar.
Paradox000
Power Member
Boas noites,
Há cerca de uns 4 dias para cá que tenho tido uma BSOD no meu PC.
O erro é identificado como KMODE_EXCEPTION_EXCEPTION_NOT_HANDLED
A última "coisa" que instalei foi o programa das Finanças para entregar o IRS e fora isso só mesmo atualizações do Windows.
Até hoje à tarde, ainda tinha o controlador gráfico Catalyst da AMD/ATI e pensei que fosse por isso e instalei as Crimson e até agora não voltou a acontecer nada.
Visto que só uso o PC para jogos (Xenoverse e BF3) e internet tou a achar muito estranho que seja disto, de qq forma aqui vai uma análise com o Windbg. NOTA: Tenho o Windows 10
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\042316-25671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Non-directory path: 'C:\Program Files\Windows Kits\8.0\Debuggers\x64\SymbolCheck.dll'
Symbol search path is: http://msdl.microsoft.com/download/symbols;C:\Program Files\Windows Kits\8.0\Debuggers\x64\SymbolCheck.dll
Executable search path is:
Windows 8 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.212.amd64fre.th2_release_sec.160328-1908
Machine Name:
Kernel base = 0xfffff803`f2014000 PsLoadedModuleList = 0xfffff803`f22f2cd0
Debug session time: Sat Apr 23 16:20:41.393 2016 (UTC + 1:00)
System Uptime: 0 days 0:06:01.068
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff801e9f754ef, 0, 20}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
Followup: MachineOwner
---------
*** Memory manager detected 23582 instance(s) of page corruption, target is likely to have memory corruption.
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801e9f754ef, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000020, Parameter 1 of the exception
Debugging Details:
------------------
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000020
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - A instru o no 0x%p fez refer ncia mem ria no 0x%p. A mem ria n o p de ser %s.
FAULTING_IP:
NTFS!NtfsFindPrefixHashEntry+1df
fffff801`e9f754ef 44394710 cmp dword ptr [rdi+10h],r8d
EXCEPTION_PARAMETER2: 0000000000000020
BUGCHECK_STR: 0x1E_c0000005_R
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: services.exe
CURRENT_IRQL: 0
BAD_PAGES_DETECTED: 5c1e
TRAP_FRAME: ffffd00026ee49c0 -- (.trap 0xffffd00026ee49c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc001f2303000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801e9f754ef rsp=ffffd00026ee4b50 rbp=0000000000000000
r8=000000000578384b r9=000000009e69822f r10=ffffc001f876c5e4
r11=ffffd00026ee4c58 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
NTFS!NtfsFindPrefixHashEntry+0x1df:
fffff801`e9f754ef 44394710 cmp dword ptr [rdi+10h],r8d ds:00000000`00000010=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff803f216a496 to fffff803f2156760
STACK_TEXT:
ffffd000`26ee40f8 fffff803`f216a496 : 00000000`0000001e ffffffff`c0000005 fffff801`e9f754ef 00000000`00000000 : nt!KeBugCheckEx
ffffd000`26ee4100 fffff803`f21613c2 : ffffe001`73778c58 00000000`00000003 ffffd000`00000018 ffffe001`72b1f080 : nt! ?? ::FNODOBFM::`string'+0x5396
ffffd000`26ee47e0 fffff803`f215faa1 : ffffc001`ee5ca9a8 fffff803`00000012 fffff801`e9f005d0 ffffd000`000000a0 : nt!KiExceptionDispatch+0xc2
ffffd000`26ee49c0 fffff801`e9f754ef : ffffe001`701b7180 ffffe001`00000003 ffffc001`ee5ca9a8 ffffe001`701b84f0 : nt!KiPageFault+0x221
ffffd000`26ee4b50 fffff801`e9f761fb : ffffe001`73778c58 ffffe001`701b84f0 ffffc001`eafb3150 fffff801`e9ebd801 : NTFS!NtfsFindPrefixHashEntry+0x1df
ffffd000`26ee4c60 fffff801`e9f770c5 : ffffe001`73778c58 ffffe001`7451d610 ffffe001`73778c58 ffffd000`26ee4e98 : NTFS!NtfsFindStartingNode+0x2cb
ffffd000`26ee4d20 fffff801`e9f75efd : ffffe001`73778c58 ffffe001`7451d610 ffffd000`234b7160 ffffe001`73138001 : NTFS!NtfsCommonCreate+0x425
ffffd000`26ee4f50 fffff803`f2159327 : ffffd000`234b70f0 ffffe001`731e7b60 ffffe001`72f4c6c0 00000000`00000000 : NTFS!NtfsCommonCreateCallout+0x1d
ffffd000`26ee4f80 fffff803`f21592ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
ffffd000`234b6f30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 23582 instance(s) of page corruption, target is likely to have memory corruption.
Há cerca de uns 4 dias para cá que tenho tido uma BSOD no meu PC.
O erro é identificado como KMODE_EXCEPTION_EXCEPTION_NOT_HANDLED
A última "coisa" que instalei foi o programa das Finanças para entregar o IRS e fora isso só mesmo atualizações do Windows.
Até hoje à tarde, ainda tinha o controlador gráfico Catalyst da AMD/ATI e pensei que fosse por isso e instalei as Crimson e até agora não voltou a acontecer nada.
Visto que só uso o PC para jogos (Xenoverse e BF3) e internet tou a achar muito estranho que seja disto, de qq forma aqui vai uma análise com o Windbg. NOTA: Tenho o Windows 10
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\042316-25671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Non-directory path: 'C:\Program Files\Windows Kits\8.0\Debuggers\x64\SymbolCheck.dll'
Symbol search path is: http://msdl.microsoft.com/download/symbols;C:\Program Files\Windows Kits\8.0\Debuggers\x64\SymbolCheck.dll
Executable search path is:
Windows 8 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.212.amd64fre.th2_release_sec.160328-1908
Machine Name:
Kernel base = 0xfffff803`f2014000 PsLoadedModuleList = 0xfffff803`f22f2cd0
Debug session time: Sat Apr 23 16:20:41.393 2016 (UTC + 1:00)
System Uptime: 0 days 0:06:01.068
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff801e9f754ef, 0, 20}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
Followup: MachineOwner
---------
*** Memory manager detected 23582 instance(s) of page corruption, target is likely to have memory corruption.
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801e9f754ef, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000020, Parameter 1 of the exception
Debugging Details:
------------------
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000020
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - A instru o no 0x%p fez refer ncia mem ria no 0x%p. A mem ria n o p de ser %s.
FAULTING_IP:
NTFS!NtfsFindPrefixHashEntry+1df
fffff801`e9f754ef 44394710 cmp dword ptr [rdi+10h],r8d
EXCEPTION_PARAMETER2: 0000000000000020
BUGCHECK_STR: 0x1E_c0000005_R
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: services.exe
CURRENT_IRQL: 0
BAD_PAGES_DETECTED: 5c1e
TRAP_FRAME: ffffd00026ee49c0 -- (.trap 0xffffd00026ee49c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc001f2303000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801e9f754ef rsp=ffffd00026ee4b50 rbp=0000000000000000
r8=000000000578384b r9=000000009e69822f r10=ffffc001f876c5e4
r11=ffffd00026ee4c58 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
NTFS!NtfsFindPrefixHashEntry+0x1df:
fffff801`e9f754ef 44394710 cmp dword ptr [rdi+10h],r8d ds:00000000`00000010=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff803f216a496 to fffff803f2156760
STACK_TEXT:
ffffd000`26ee40f8 fffff803`f216a496 : 00000000`0000001e ffffffff`c0000005 fffff801`e9f754ef 00000000`00000000 : nt!KeBugCheckEx
ffffd000`26ee4100 fffff803`f21613c2 : ffffe001`73778c58 00000000`00000003 ffffd000`00000018 ffffe001`72b1f080 : nt! ?? ::FNODOBFM::`string'+0x5396
ffffd000`26ee47e0 fffff803`f215faa1 : ffffc001`ee5ca9a8 fffff803`00000012 fffff801`e9f005d0 ffffd000`000000a0 : nt!KiExceptionDispatch+0xc2
ffffd000`26ee49c0 fffff801`e9f754ef : ffffe001`701b7180 ffffe001`00000003 ffffc001`ee5ca9a8 ffffe001`701b84f0 : nt!KiPageFault+0x221
ffffd000`26ee4b50 fffff801`e9f761fb : ffffe001`73778c58 ffffe001`701b84f0 ffffc001`eafb3150 fffff801`e9ebd801 : NTFS!NtfsFindPrefixHashEntry+0x1df
ffffd000`26ee4c60 fffff801`e9f770c5 : ffffe001`73778c58 ffffe001`7451d610 ffffe001`73778c58 ffffd000`26ee4e98 : NTFS!NtfsFindStartingNode+0x2cb
ffffd000`26ee4d20 fffff801`e9f75efd : ffffe001`73778c58 ffffe001`7451d610 ffffd000`234b7160 ffffe001`73138001 : NTFS!NtfsCommonCreate+0x425
ffffd000`26ee4f50 fffff803`f2159327 : ffffd000`234b70f0 ffffe001`731e7b60 ffffe001`72f4c6c0 00000000`00000000 : NTFS!NtfsCommonCreateCallout+0x1d
ffffd000`26ee4f80 fffff803`f21592ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
ffffd000`234b6f30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 23582 instance(s) of page corruption, target is likely to have memory corruption.
Paradox000
Power Member
Boas,
o meu problema ainda continua. E desta feita o erro é agora MEMORY_MANAGEMENT.
Já correi o diagnóstico à memória e não apareceu qualquer erro...
será sinal de algum módulo memória RAM a "ir à vida"? Tenho dois de 4GB cada...
o meu problema ainda continua. E desta feita o erro é agora MEMORY_MANAGEMENT.
Já correi o diagnóstico à memória e não apareceu qualquer erro...
será sinal de algum módulo memória RAM a "ir à vida"? Tenho dois de 4GB cada...
Paradox000
Power Member
Levei o meu PC para um colega meu de trabalho dar uma olhada e ele testou uma a uma com o Memtest86 e não houve problemas.
Ele depois correu o FixWin 10 limpou alguns ficheiros de sistema corrompidos e ... até agora não posso me queixar ..
Aliás o único "contra" que posso dizer até agora é a velocidade de arranque após um reinício... demora mais que o normal...
Boas Pessoal será que alguem me possa ajudar?
ha uns dias atrás estava a jogar e deu.me um BlueScreen depois disso nunca mais iniciou o windows, já formatei o pc umas poucas vezes , ja tentei diferentes drives e sempre q a drive fica instalada , faço reboot e da BS dps do logo do windows.
Experimentei com outra gráfica e o pc inicia normal e com a grafica onboard tambem,
mas penso que a minha 560 n esteja danificada, penso que é 1 problema de drivers segundo a minha longa pesquisa no google...
NOTA: Nunca fiz OC em nada
ficam aki os specs do meu PC:
asus p8z68 v gen3
Nvidia gtx 560 dcii top/2di/1gd5
G Skill RipjawsX F3-12800CL9-4GBXL (2x4gb) 1600
i5 2500k 3.3ghz
LC power 6600 v2.2
desde já agradeço a ajuda.
este foi o erro q deu nos dmp file
Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\062516-5116-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23455.amd64fre.win7sp1_ldr.160516-0600
Machine Name:
Kernel base = 0xfffff800`01c50000 PsLoadedModuleList = 0xfffff800`01e92730
Debug session time: Sat Jun 25 05:59:25.936 2016 (UTC + 1:00)
System Uptime: 0 days 0:00:11.592
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 116, {fffffa8009330010, fffff8800336b5c4, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+14a5c4 )
Followup: MachineOwner
ha uns dias atrás estava a jogar e deu.me um BlueScreen depois disso nunca mais iniciou o windows, já formatei o pc umas poucas vezes , ja tentei diferentes drives e sempre q a drive fica instalada , faço reboot e da BS dps do logo do windows.
Experimentei com outra gráfica e o pc inicia normal e com a grafica onboard tambem,
mas penso que a minha 560 n esteja danificada, penso que é 1 problema de drivers segundo a minha longa pesquisa no google...
NOTA: Nunca fiz OC em nada
ficam aki os specs do meu PC:
asus p8z68 v gen3
Nvidia gtx 560 dcii top/2di/1gd5
G Skill RipjawsX F3-12800CL9-4GBXL (2x4gb) 1600
i5 2500k 3.3ghz
LC power 6600 v2.2
desde já agradeço a ajuda.
este foi o erro q deu nos dmp file
Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\062516-5116-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23455.amd64fre.win7sp1_ldr.160516-0600
Machine Name:
Kernel base = 0xfffff800`01c50000 PsLoadedModuleList = 0xfffff800`01e92730
Debug session time: Sat Jun 25 05:59:25.936 2016 (UTC + 1:00)
System Uptime: 0 days 0:00:11.592
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 116, {fffffa8009330010, fffff8800336b5c4, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+14a5c4 )
Followup: MachineOwner
Última edição:
Genius R80
Membro
Boa noite.
Tenho um problema com a minha máquina e tenho esperança que me possam ajudar. Ontem o meu computador levou com o BSoD que provocou reinícios em loop... Como não sabia que mais lhe fazer, acabei por formatar o computador, visto não ter nada de essencial. O problema é que após instalar de novo o Windows, continuo com o mesmo problema. Isto acontece sempre que tento instalar a Drive da Placa Gráfica, tanto pelo Windows Update como manualmente ou Nvidia Experience. A situação é frustrante, não faço ideia do que se passa, tenho medo que a gráfica esteja danificada.
Bem, o BSoD que me aparece refere o seguinte:
driver_irql_not_less_or_equal (dxgmms2.sys)
Deixo aqui o relatório gerado pelo WinDBG:
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081616-23765-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.545.amd64fre.th2_release.160802-1857
Machine Name:
Kernel base = 0xfffff801`3f078000 PsLoadedModuleList = 0xfffff801`3f355cf0
Debug session time: Tue Aug 16 23:19:50.515 2016 (UTC + 1:00)
System Uptime: 0 days 0:30:55.182
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 D1, {298, 2, 0, fffff800c100817e}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchSignalSyncObjectsFromGpu+16e )
Followup: MachineOwner
---------
0: 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: 0000000000000298, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800c100817e, address which referenced memory
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.10586.545 (th2_release.160802-1857)
SYSTEM_MANUFACTURER: System manufacturer
SYSTEM_PRODUCT_NAME: System Product Name
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 0501
BIOS_DATE: 05/09/2011
BASEBOARD_MANUFACTURER: ASUSTeK Computer INC.
BASEBOARD_PRODUCT: P8Z68-V
BASEBOARD_VERSION: Rev 1.xx
DUMP_TYPE: 2
BUGCHECK_P1: 298
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff800c100817e
READ_ADDRESS: fffff8013f3f5520: Unable to get MiVisibleState
0000000000000298
CURRENT_IRQL: 2
FAULTING_IP:
dxgmms2!VidSchSignalSyncObjectsFromGpu+16e
fffff800`c100817e 483900 cmp qword ptr [rax],rax
CPU_COUNT: 4
CPU_MHZ: d48
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 2a
CPU_STEPPING: 7
CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 29'00000000 (cache) 29'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
ANALYSIS_SESSION_HOST: DESKTOP-6ELTV30
ANALYSIS_SESSION_TIME: 08-17-2016 00:08:39.0595
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
TRAP_FRAME: ffffd00101ef0590 -- (.trap 0xffffd00101ef0590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000298 rbx=0000000000000000 rcx=ffffd00101ef0770
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800c100817e rsp=ffffd00101ef0720 rbp=ffffd00101ef07b9
r8=ffffd00101ef0770 r9=0000000000000000 r10=ffffc001fcc8f010
r11=ffffe001c64bb7b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
dxgmms2!VidSchSignalSyncObjectsFromGpu+0x16e:
fffff800`c100817e 483900 cmp qword ptr [rax],rax ds:00000000`00000298=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8013f1c54e9 to fffff8013f1ba940
STACK_TEXT:
ffffd001`01ef0448 fffff801`3f1c54e9 : 00000000`0000000a 00000000`00000298 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd001`01ef0450 fffff801`3f1c3cc7 : ffffe001`c6962840 fffff801`00000000 00000000`00000000 ffffe001`c6c96e38 : nt!KiBugCheckDispatch+0x69
ffffd001`01ef0590 fffff800`c100817e : 00000000`00000000 ffffe001`c64bb7b0 00000000`00000001 ffffc001`fcc8f010 : nt!KiPageFault+0x247
ffffd001`01ef0720 fffff800`c104683d : ffffe001`00000000 ffffe001`c8ee80b0 00000000`00000001 00000000`00000000 : dxgmms2!VidSchSignalSyncObjectsFromGpu+0x16e
ffffd001`01ef0810 fffff800`c104c453 : 00000000`00000068 ffffd001`01ef08f1 ffffc002`001228b0 00000000`00000068 : dxgmms2!VIDMM_GLOBAL::EndPreparation+0xdd
ffffd001`01ef0860 fffff800`c1065693 : ffffe001`c737bbd8 ffffd001`00000000 00000000`00000001 ffffe001`00000000 : dxgmms2!VIDMM_GLOBAL:
rocessSystemCommand+0x7a7
ffffd001`01ef0950 fffff801`3f0bea45 : 00000000`00000000 ffffe001`c7371840 fffff800`c1064960 ffffc001`fc0a3700 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xd23
ffffd001`01ef0c10 fffff801`3f1bfae6 : fffff801`3f394180 ffffe001`c7371840 fffff801`3f0bea04 00000000`00000246 : nt!PspSystemThreadStartup+0x41
ffffd001`01ef0c60 00000000`00000000 : ffffd001`01ef1000 ffffd001`01eeb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 9d06157b91a330aa28d6d546262eb64b58625e71
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 773011b588cb491216492e46518153d99ff1c9e9
THREAD_SHA1_HASH_MOD: 095cd051b92649ba772290b1d0e90a081d4df072
FOLLOWUP_IP:
dxgmms2!VidSchSignalSyncObjectsFromGpu+16e
fffff800`c100817e 483900 cmp qword ptr [rax],rax
FAULT_INSTR_CODE: f003948
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms2!VidSchSignalSyncObjectsFromGpu+16e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 57a1b55f
IMAGE_VERSION: 10.0.10586.545
BUCKET_ID_FUNC_OFFSET: 16e
FAILURE_BUCKET_ID: AV_dxgmms2!VidSchSignalSyncObjectsFromGpu
BUCKET_ID: AV_dxgmms2!VidSchSignalSyncObjectsFromGpu
PRIMARY_PROBLEM_CLASS: AV_dxgmms2!VidSchSignalSyncObjectsFromGpu
TARGET_TIME: 2016-08-16T22:19:50.000Z
OSBUILD: 10586
OSSERVICEPACK: 545
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-08-03 10:15:01
BUILDDATESTAMP_STR: 160802-1857
BUILDLAB_STR: th2_release
BUILDOSVER_STR: 10.0.10586.545
ANALYSIS_SESSION_ELAPSED_TIME: 81c5
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_dxgmms2!vidschsignalsyncobjectsfromgpu
FAILURE_ID_HASH: {14bccf82-5452-187f-feaf-22020beca8a4}
Followup: MachineOwner
---------
Entretanto, o Windows Update oferece-me a seguinte informação:
"Ocorreram problemas ao instalar algumas atualizações, mas voltaremos a tentar mais tarde. Caso continue a ver esta mensagem e pretenda procurar informações na Web ou contactar o suporte, isto pode ajudar:
nVidia - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3, Graphics Adapter WDDM2.0 - NVIDIA GeForce GTX 570 - Erro 0x80246002
NVIDIA Corporation - Graphics Adapter WDDM2.0 - NVIDIA High Definition Audio - Erro 0x80246002
NVIDIA driver update for NVIDIA GeForce GTX 570 - Erro 0x80246002"
Agradeço desde já a ajuda
Tenho um problema com a minha máquina e tenho esperança que me possam ajudar. Ontem o meu computador levou com o BSoD que provocou reinícios em loop... Como não sabia que mais lhe fazer, acabei por formatar o computador, visto não ter nada de essencial. O problema é que após instalar de novo o Windows, continuo com o mesmo problema. Isto acontece sempre que tento instalar a Drive da Placa Gráfica, tanto pelo Windows Update como manualmente ou Nvidia Experience. A situação é frustrante, não faço ideia do que se passa, tenho medo que a gráfica esteja danificada.
Bem, o BSoD que me aparece refere o seguinte:
driver_irql_not_less_or_equal (dxgmms2.sys)
Deixo aqui o relatório gerado pelo WinDBG:
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081616-23765-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.545.amd64fre.th2_release.160802-1857
Machine Name:
Kernel base = 0xfffff801`3f078000 PsLoadedModuleList = 0xfffff801`3f355cf0
Debug session time: Tue Aug 16 23:19:50.515 2016 (UTC + 1:00)
System Uptime: 0 days 0:30:55.182
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 D1, {298, 2, 0, fffff800c100817e}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchSignalSyncObjectsFromGpu+16e )
Followup: MachineOwner
---------
0: 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: 0000000000000298, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800c100817e, address which referenced memory
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.10586.545 (th2_release.160802-1857)
SYSTEM_MANUFACTURER: System manufacturer
SYSTEM_PRODUCT_NAME: System Product Name
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 0501
BIOS_DATE: 05/09/2011
BASEBOARD_MANUFACTURER: ASUSTeK Computer INC.
BASEBOARD_PRODUCT: P8Z68-V
BASEBOARD_VERSION: Rev 1.xx
DUMP_TYPE: 2
BUGCHECK_P1: 298
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff800c100817e
READ_ADDRESS: fffff8013f3f5520: Unable to get MiVisibleState
0000000000000298
CURRENT_IRQL: 2
FAULTING_IP:
dxgmms2!VidSchSignalSyncObjectsFromGpu+16e
fffff800`c100817e 483900 cmp qword ptr [rax],rax
CPU_COUNT: 4
CPU_MHZ: d48
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 2a
CPU_STEPPING: 7
CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 29'00000000 (cache) 29'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
ANALYSIS_SESSION_HOST: DESKTOP-6ELTV30
ANALYSIS_SESSION_TIME: 08-17-2016 00:08:39.0595
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
TRAP_FRAME: ffffd00101ef0590 -- (.trap 0xffffd00101ef0590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000298 rbx=0000000000000000 rcx=ffffd00101ef0770
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800c100817e rsp=ffffd00101ef0720 rbp=ffffd00101ef07b9
r8=ffffd00101ef0770 r9=0000000000000000 r10=ffffc001fcc8f010
r11=ffffe001c64bb7b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
dxgmms2!VidSchSignalSyncObjectsFromGpu+0x16e:
fffff800`c100817e 483900 cmp qword ptr [rax],rax ds:00000000`00000298=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8013f1c54e9 to fffff8013f1ba940
STACK_TEXT:
ffffd001`01ef0448 fffff801`3f1c54e9 : 00000000`0000000a 00000000`00000298 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd001`01ef0450 fffff801`3f1c3cc7 : ffffe001`c6962840 fffff801`00000000 00000000`00000000 ffffe001`c6c96e38 : nt!KiBugCheckDispatch+0x69
ffffd001`01ef0590 fffff800`c100817e : 00000000`00000000 ffffe001`c64bb7b0 00000000`00000001 ffffc001`fcc8f010 : nt!KiPageFault+0x247
ffffd001`01ef0720 fffff800`c104683d : ffffe001`00000000 ffffe001`c8ee80b0 00000000`00000001 00000000`00000000 : dxgmms2!VidSchSignalSyncObjectsFromGpu+0x16e
ffffd001`01ef0810 fffff800`c104c453 : 00000000`00000068 ffffd001`01ef08f1 ffffc002`001228b0 00000000`00000068 : dxgmms2!VIDMM_GLOBAL::EndPreparation+0xdd
ffffd001`01ef0860 fffff800`c1065693 : ffffe001`c737bbd8 ffffd001`00000000 00000000`00000001 ffffe001`00000000 : dxgmms2!VIDMM_GLOBAL:
rocessSystemCommand+0x7a7ffffd001`01ef0950 fffff801`3f0bea45 : 00000000`00000000 ffffe001`c7371840 fffff800`c1064960 ffffc001`fc0a3700 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xd23
ffffd001`01ef0c10 fffff801`3f1bfae6 : fffff801`3f394180 ffffe001`c7371840 fffff801`3f0bea04 00000000`00000246 : nt!PspSystemThreadStartup+0x41
ffffd001`01ef0c60 00000000`00000000 : ffffd001`01ef1000 ffffd001`01eeb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 9d06157b91a330aa28d6d546262eb64b58625e71
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 773011b588cb491216492e46518153d99ff1c9e9
THREAD_SHA1_HASH_MOD: 095cd051b92649ba772290b1d0e90a081d4df072
FOLLOWUP_IP:
dxgmms2!VidSchSignalSyncObjectsFromGpu+16e
fffff800`c100817e 483900 cmp qword ptr [rax],rax
FAULT_INSTR_CODE: f003948
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms2!VidSchSignalSyncObjectsFromGpu+16e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 57a1b55f
IMAGE_VERSION: 10.0.10586.545
BUCKET_ID_FUNC_OFFSET: 16e
FAILURE_BUCKET_ID: AV_dxgmms2!VidSchSignalSyncObjectsFromGpu
BUCKET_ID: AV_dxgmms2!VidSchSignalSyncObjectsFromGpu
PRIMARY_PROBLEM_CLASS: AV_dxgmms2!VidSchSignalSyncObjectsFromGpu
TARGET_TIME: 2016-08-16T22:19:50.000Z
OSBUILD: 10586
OSSERVICEPACK: 545
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-08-03 10:15:01
BUILDDATESTAMP_STR: 160802-1857
BUILDLAB_STR: th2_release
BUILDOSVER_STR: 10.0.10586.545
ANALYSIS_SESSION_ELAPSED_TIME: 81c5
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_dxgmms2!vidschsignalsyncobjectsfromgpu
FAILURE_ID_HASH: {14bccf82-5452-187f-feaf-22020beca8a4}
Followup: MachineOwner
---------
Entretanto, o Windows Update oferece-me a seguinte informação:
"Ocorreram problemas ao instalar algumas atualizações, mas voltaremos a tentar mais tarde. Caso continue a ver esta mensagem e pretenda procurar informações na Web ou contactar o suporte, isto pode ajudar:
nVidia - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3, Graphics Adapter WDDM2.0 - NVIDIA GeForce GTX 570 - Erro 0x80246002
NVIDIA Corporation - Graphics Adapter WDDM2.0 - NVIDIA High Definition Audio - Erro 0x80246002
NVIDIA driver update for NVIDIA GeForce GTX 570 - Erro 0x80246002"
Agradeço desde já a ajuda
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?