BSOD ao usar um cabo HDMI

Question

Eu tenho um Dell XPS 15 (L502x) executando o Windows 7 x64 Home Premium e tenho um problema BSOD ao conectar uma tela externa.

Eu tentei conectar duas telas - uma com HDMI > DVI e HDMI > HDMI, e o segundo com o mesmo HDMI > Cabo HDMI.

Com ambas as telas eu recebo um BSOD após um tempo de uso (BSOD aleatório, pode ocorrer mesmo quando não estiver interagindo com o computador).

Aqui está uma pequena análise de dois despejos relevantes, um que afirma que o problema é com a placa gráfica nvidia, e o segundo diz que o problema é com a placa interna.

Alguma idéia de por que isso aconteceria?

Primeiro:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff8800f22fa3f

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x7f_8

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  9

LAST_CONTROL_TRANSFER:  from fffff8000308a769 to fffff8000308b1c0

STACK_TEXT:  
fffff800'00ba4d28 fffff800'0308a769 : 00000000'0000007f 00000000'00000008 00000000'80050033 00000000'000406f8 : nt!KeBugCheckEx
fffff800'00ba4d30 fffff800'03088c32 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nt!KiBugCheckDispatch+0x69
fffff800'00ba4e70 fffff880'0f22fa3f : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880'0d12df70 00000000'00000000 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nvlddmkm+0x1a3a3f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1a3a3f
fffff880'0f22fa3f ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+1a3a3f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  503f8bb8

FAILURE_BUCKET_ID:  X64_0x7f_8_nvlddmkm+1a3a3f

BUCKET_ID:  X64_0x7f_8_nvlddmkm+1a3a3f

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

Segundo:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff8800591c802

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x7f_8

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  b

LAST_CONTROL_TRANSFER:  from fffff800030cd769 to fffff800030ce1c0

STACK_TEXT:  
fffff800'00ba4d28 fffff800'030cd769 : 00000000'0000007f 00000000'00000008 00000000'80050033 00000000'000406f8 : nt!KeBugCheckEx
fffff800'00ba4d30 fffff800'030cbc32 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nt!KiBugCheckDispatch+0x69
fffff800'00ba4e70 fffff880'0591c802 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880'0c780fe0 00000000'00000000 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : igdkmd64+0x2e8802


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igdkmd64+2e8802
fffff880'0591c802 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  igdkmd64+2e8802

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d41a3e1

FAILURE_BUCKET_ID:  X64_0x7f_8_igdkmd64+2e8802

BUCKET_ID:  X64_0x7f_8_igdkmd64+2e8802

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

Terceiro:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff8800f23b837

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  9

LAST_CONTROL_TRANSFER:  from fffff8000329c769 to fffff8000329d1c0

STACK_TEXT:  
fffff800'0493dd28 fffff800'0329c769 : 00000000'0000007f 00000000'00000008 00000000'80050033 00000000'000406f8 : nt!KeBugCheckEx
fffff800'0493dd30 fffff800'0329ac32 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nt!KiBugCheckDispatch+0x69
fffff800'0493de70 fffff880'0f23b837 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880'0e1bbff0 00000000'00000000 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nvlddmkm+0x19d837


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+19d837
fffff880'0f23b837 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+19d837

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  503f8bb8

FAILURE_BUCKET_ID:  X64_0x7f_8_nvlddmkm+19d837

BUCKET_ID:  X64_0x7f_8_nvlddmkm+19d837

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

    

Answer 1

Você está usando dois monitores conectando um à placa nvidia e o outro à porta de vídeo integrada mobo? Eu acho que os dois podem ser conflitantes em termos de hardware ou software, é difícil de determinar. Você pode querer apenas comprar uma placa de vídeo autônoma que suporte dois monitores nativamente, em vez de tentar que seu chip de vídeo integrado funcione com sua placa nvidia.

    

Answer 2

Nos comentários, você diz que ambos os monitores podem ser exibidos usando a placa gráfica NVIDIA do seu laptop.

Quais adaptadores de exibição aparecem no Gerenciador de dispositivos usando o Gerenciamento do computador? Veja meu exemplo abaixo.

Se os dois monitores puderem ser acionados pelo adaptador NVIDIA, desabilitarei o adaptador Intel se ele estiver ativo no seu sistema.