Problema BSoD / Ecrã Azul - como diagnosticar e resolver?

[Dat55]

Tem-me dado BSOD nos últimos dias como podem ver na screen, alguém me pode ajudar? Colo aqui o debug e a screen do bluescreenview. este é o único ficheiro que tenho.

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


Loading Dump File [C:\Windows\Minidump\113014-24984-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 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff803`bea0a000 PsLoadedModuleList = 0xfffff803`bece0370
Debug session time: Sun Nov 30 11:49:06.663 2014 (UTC + 0:00)
System Uptime: 0 days 0:05:46.398
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, {440, 2, 1, fffff803bea947e2}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

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

1: kd> !analyze –v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {440, 2, 1, fffff803bea947e2}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

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: 0000000000000440, 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: fffff803bea947e2, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff803bed6a138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000440

CURRENT_IRQL: 2

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff803`bea947e2 48890a mov qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: svchost.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME: ffffd00082018ef0 -- (.trap 0xffffd00082018ef0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8003902800 rbx=0000000000000000 rcx=ffffd00082019118
rdx=0000000000000440 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803bea947e2 rsp=ffffd00082019080 rbp=ffffd00082019100
r8=0000000000000000 r9=0000000000000001 r10=0020000000030907
r11=fffffa8003907000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KxWaitForLockOwnerShip+0x12:
fffff803`bea947e2 48890a mov qword ptr [rdx],rcx ds:00000000`00000440=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff803beb64ce9 to fffff803beb591a0

STACK_TEXT:
ffffd000`82018da8 fffff803`beb64ce9 : 00000000`0000000a 00000000`00000440 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd000`82018db0 fffff803`beb6353a : fffffa80`00902790 fffff803`becab05e ffffc000`d37cf000 ffffd000`82018ef0 : nt!KiBugCheckDispatch+0x69
ffffd000`82018ef0 fffff803`bea947e2 : ffffc000`d39447d0 ffffd000`820194b8 ffffd000`82019189 fffff803`bede203b : nt!KiPageFault+0x23a
ffffd000`82019080 fffff803`bea646ff : fffffa80`00902790 00000000`00000000 ffffc000`d39cbd08 ffffc000`d39cbd14 : nt!KxWaitForLockOwnerShip+0x12
ffffd000`820190b0 fffff803`bea63a83 : 00000000`000300d3 fffffa80`00902790 fffff680`708d6868 00000000`00000000 : nt!MiInsertPageInFreeOrZeroedList+0x7ef
ffffd000`820191f0 fffff803`bea6347b : ffffd000`82019248 00000000`00000000 ffffc000`d39448a0 fffff803`bede1770 : nt!MiPfnShareCountIsZero+0x83
ffffd000`82019220 fffff803`bea760e3 : 9a500000`2fecd867 00000000`00000005 fffff680`708d6878 fffff580`10804000 : nt!MiDeletePteRun+0x1ab
ffffd000`82019410 fffff803`bea5df66 : ffffe000`55f11080 fffff803`bed0a180 00000000`00000000 00000000`0000339e : nt!MiDeleteVirtualAddresses+0x463
ffffd000`820196a0 fffff803`bea59130 : ffffe000`55ec0870 00000000`00000010 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0xbc6
ffffd000`82019790 fffff803`beb649b3 : 00000000`00010002 ffffd000`82019a70 00000000`00000000 00000000`00000028 : nt!NtFreeVirtualMemory+0x820
ffffd000`820198f0 fffff803`beb5ce00 : fffff803`beebb50f 00000000`00000001 00000000`00000000 ffffe000`55f11080 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`82019a88 fffff803`beebb50f : 00000000`00000001 00000000`00000000 ffffe000`55f11080 00000000`00000000 : nt!KiServiceLinkage
ffffd000`82019a90 fffff803`bedec437 : 000000e1`1ac90000 00000000`00000000 ffffe000`548fc090 ffffe000`548fc090 : nt!RtlFreeUserStack+0x27
ffffd000`82019ac0 fffff803`bedb218b : ffffffff`00000000 ffffe000`55f11080 ffffe000`55f11001 00000000`00000000 : nt!PspExitThread+0x32f
ffffd000`82019bd0 fffff803`bedb2128 : ffffe000`55f11080 ffffe000`55f11080 00007ffa`369c114c 00007ff6`c9008000 : nt!PspTerminateThreadByPointer+0x47
ffffd000`82019c00 fffff803`beb649b3 : ffffe000`55f11080 ffffd000`82019cc0 00000000`00000010 00007ffa`369c114c : nt!NtTerminateThread+0x40
ffffd000`82019c40 00007ffa`38cb1baa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000e1`1ad0f818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`38cb1baa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KxWaitForLockOwnerShip+12
fffff803`bea947e2 48890a mov qword ptr [rdx],rcx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 53fe6f2e

IMAGE_VERSION: 6.3.9600.17328

BUCKET_ID_FUNC_OFFSET: 12

FAILURE_BUCKET_ID: AV_nt!KxWaitForLockOwnerShip

BUCKET_ID: AV_nt!KxWaitForLockOwnerShip

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!kxwaitforlockownership

FAILURE_ID_HASH: {724b07b1-4226-85fe-f372-16d33b9a3b93}

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

 

[Freamon]

Boa tarde, ultimamente tenho tido este BSOD no meu pc, alguém pode-me ajudar?

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+75b90 )

Followup: MachineOwner

 

[espacoina]

Boa tarde.
Tem aparecido ecrã azul, dá-me este erro, alguém sabe o que poderá ser?

Problem signature:
Problem Event Name:BlueScreen
OS Version:6.1.7601.2.1.0.256.1
Locale ID:2070
Additional information about the problem:
BCCode:d1
BCP1:00000000
BCP2:00000002
BCP3:00000000
BCP4:00000000
OS Version:6_1_7601
Service Pack:1_0
Product:256_1
Files that help describe the problem:
C:\Windows\Minidump\120714-82609-01.dmp
C:\Users\Bruno\AppData\Local\Temp\WER-92718-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

 

[Broka]

Preciso da vossa ajuda.

Apareceu-me ha dois dias no meu portátil este écran azul. Nunca tive problemas antes, tenho lá imensa informação de trabalho, etc. Nao queria perder essa informação.

Alguem me sabe resolver isto? Ou aconselham-me algum sítio p resolver? Tinha ido a um sítio mas queriam-me formatar o portátil e eu nao quero perder documentos, etc q tenho no portátil.

[/URL][/IMG]

 

[Andrew65]

@Broka És capaz de entrar em modo de segurança?

 

[peralta]

Isso é um problema com o controlador do disco rigido, mas pode estar ligado a outros problemas.

Mexeste na BIOS antes de acontecer isso??
Mudaste o controlador de AHCI para IDE ou vice-versa??

 

[Broka]

@Broka És capaz de entrar em modo de segurança?

Sim, em modo de segurança consegui entrar (cliquei no F8). Aproveitei e passei coisas para o disco rigido.

Mas o problema persiste.. Mas pelo menos ja tenho as coisas comigo.

 

[Broka]

Isso é um problema com o controlador do disco rigido, mas pode estar ligado a outros problemas.

Mexeste na BIOS antes de acontecer isso??
Mudaste o controlador de AHCI para IDE ou vice-versa??

Não mexi em nada (acho eu). :-S

 

[peralta]

Vai a Bios, e procurar pela controlador sata, algo como AHCI ou IDE, se tiver AHCI altera para IDE, se tiver IDE altera para AHCI.

Para aceder a bios clica no botão assist com o portátil desligado, e depois está lá a opção de ir a BIOS, acho que é F2. Basta só procurar o que disse e depois gravar as alterações.

Este problema também acontece por vezes com problemas com os drivers da placa rede wireless.

Faz o seguinte, faz o download do bluescreenview, entra em modo de segurança e depois tira um print screen dos resultados. Se tiver mais que um resultado tira print aos 2/3 primeiros dumps.

 

[pmcs1]

Viva,

Desde domingo passado que tenho tido, por vezes, um BSOD sempre que ligo o computador, fazendo com que ele reinicie. No entanto, não é constante porque há dias em que tenho apenas um BSOD, noutros dias tenho dois seguidos e noutros dias até nem tenho nada. Isso deixa-me um pouco preocupado porque o computador tem apenas 6 meses. O BSOD acontece sempre entre o iniciar do windows e a iniciação do ambiente de trabalho e nunca quando já estou com o PC ligado. Por vezes acontece logo após a ter iniciado o ambiente de trabalho.

Ontem, formatei o PC na espectativa que os BSOD's terminassem. Todavia hoje de manha tive um outra vez após ter ligado o computador.
Depois de alguma pequisa sobre este problema, instalei o BlueScreenViewer na tentativa de achar o que está a funcionar mal. Este foi o resultado:



Sera que alguém tem a solução para este problema?
Vou colocar as specs do pc caso precisem...

Motherboard Asus H97-Plus
INTEL CORE i5 4590 (3.3GHZ) SKT 1150
GSKILL KIT 8GB DDR3 1600MHZ RIPJAW (CL9 - 1.5V)
XFX PRO 550W CORE EDITION
Gráfica MSI GTX760 TwinFrozr OC 2GB DDR5
SEAGATE 1TB SATA III 64MB


Obrigado pela atenção. Saudações

 

[Miki Bakakiki]

Boas malta, tive um BSOD!!!

Gostava de fazer o debug, mas nao estou a entender bem a parte do path... alguem me pode ajudar?

 

[JPiece]

Boas Amigos
Tenho tido uns problemas de Blue-Screen e penso que o mesmo é da Gráfica.
Tenho uma ATI 4570 de 512 MB no meu Toshiba L500D-168 e o erro aparece-me constantemente.
Aqui esta ele:

Já desinstalei o Driver com a ajuda do Revo Uninstaller, limpei Cache etc com o CCleaner mas é na mesma.
Por vezes também me dá este: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Podem dar uma ajudinha, já fiz a formatação do Portátil e o problema mantém-se.
Obrigado

 

[fábio lima]

Caros, o meu Portátil está parvo.

BIOS atualizada, windows instalado, e nada...
Tenho um disco SSD na drive de DVD, onde tem windows 8. Ligo o portátil e dá erro de boot ( 0x00000f ). Ligo, pressiono o botão para escolher o boot, escolho o DVD (que é o mesmo que está definido na BIOS) e já arranca. Aqui está a parvoíce: não liga tendo DVD definido em primeiro arranque na BIOS, pressiono F12 para escolher BOOT, escolho o mesmo e já dá.

Além do disco SSD montado pela drive de DVD tenho outro interno original que foi formatado ao instalar o windows no SSD.
Já andei à procura pelo google fora e não encontro solução. Isto chateia-me porque nem sempre consigo ir ao boot escolher para arrancar. Há dias que fico 10 minutos até conseguir.

 

[kpirata]

Estes são os erros que aparecem do bluescreen!!!

012915-21824-01.dmp 29-01-2015 08:23:59 BAD_POOL_CALLER 0x000000c2 00000000`00000060 00000000`00000000 00000000`00000000 00000000`00000000 hal.dll hal.dll+42a0 x64 ntoskrnl.exe+731c0 C:\Windows\Minidump\012915-21824-01.dmp 8 15 7601 276.024 29-01-2015 08:24:57

012815-24991-01.dmp 28-01-2015 14:52:53 BUGCODE_USB_DRIVER 0x000000fe 00000000`00000005 fffffa80`083491a0 00000000`80863b34 fffffa80`08767c48 USBPORT.SYS USBPORT.SYS+2dff2 x64 ntoskrnl.exe+731c0 C:\Windows\Minidump\012815-24991-01.dmp 8 15 7601 327.760 28-01-2015 14:54:24

012715-22152-01.dmp 27-01-2015 20:01:23 BUGCODE_USB_DRIVER 0x000000fe 00000000`00000005 fffffa80`092a01a0 00000000`80863b34 fffffa80`09906c48 USBPORT.SYS USBPORT.SYS+2dfea x64 ntoskrnl.exe+7b580 C:\Windows\Minidump\012715-22152-01.dmp 8 15 7601 327.760 27-01-2015 20:02:52

Podem-me ajudar a resolver isto???? É grave???

 

[fábio lima]

Caros, o meu Portátil está parvo.

BIOS atualizada, windows instalado, e nada...
Tenho um disco SSD na drive de DVD, onde tem windows 8. Ligo o portátil e dá erro de boot ( 0x00000f ). Ligo, pressiono o botão para escolher o boot, escolho o DVD (que é o mesmo que está definido na BIOS) e já arranca. Aqui está a parvoíce: não liga tendo DVD definido em primeiro arranque na BIOS, pressiono F12 para escolher BOOT, escolho o mesmo e já dá.

Além do disco SSD montado pela drive de DVD tenho outro interno original que foi formatado ao instalar o windows no SSD.
Já andei à procura pelo google fora e não encontro solução. Isto chateia-me porque nem sempre consigo ir ao boot escolher para arrancar. Há dias que fico 10 minutos até conseguir.

Já que ninguém respondeu, e eu encontrei a solução: Instalei o windows 8.1 numa Pen, fiz arranque pela pen, repair: boot repair.

 

[MudkipzPT]

http://i.epvpimg.com/Ah0Eh.png

Se alguem me conseguir ajudar,agradecia muito mesmo!

 

[Blue Zee]

Atualiza os controladores da placa de rede e testa.

 

[MudkipzPT]

Atualiza os controladores da placa de rede e testa.

Depois de ter atualizado a driver da placa de rede até ficou bem mas parece que agora voltaram os blue screens e tive 2 quase seguidos com espaço de 5 minutos

http://epvpimg.com/mmDvb

&

 

[Blue Zee]

Considerando a variedade e multiplicidade de BSODs, acho que está na altura de formatar e instalar tudo de fresco.
Lamento, mas não vejo alternativa.

 

[MudkipzPT]

Considerando a variedade e multiplicidade de BSODs, acho que está na altura de formatar e instalar tudo de fresco.
Lamento, mas não vejo alternativa.

eu formatei com aquela opção que o windows 8 tem pra fazer isso,n sei se é a mesma coisa,mas n há mesmo mais nenhuma alternativa?