BSOD when connecting screen via HDMI RRS feed


All replies

  • What is your computer make and model? If not a branded computer what is your motherboard make and model?

    Please download and run Driver View and upload a copy of the report it produces to your Sky Drive.


    Type System Information in the Search Box above the start Button and press the ENTER key. Select File, Export and give the file a name noting where it is located. Please upload to your Sky Drive, share and post a link here.

    Run the Windows 7 Memory diagnostic Tool

    Hope this helps, Gerry

    Monday, October 1, 2012 9:05 PM
  • Looks like it was due to the graphics driver. It appears that you have a really recent one installed, but is it the driver that was supplied with your system by the manufacturer?

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {8, 80050033, 406f8, fffff8800f21fa3f}

    Unable to load image 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+1a3a3f )

    Followup: MachineOwner

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

    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
            .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)
    kb will then show the corrected stack.
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000406f8
    Arg4: fffff8800f21fa3f

    Debugging Details:

    BUGCHECK_STR:  0x7f_8



    PROCESS_NAME:  System


    LAST_CONTROL_TRANSFER:  from fffff8000309c769 to fffff8000309d1c0

    fffff800`04534d28 fffff800`0309c769 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`04534d30 fffff800`0309ac32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`04534e70 fffff880`0f21fa3f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0ed78000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1a3a3f


    fffff880`0f21fa3f ??              ???


    SYMBOL_NAME:  nvlddmkm+1a3a3f

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nvlddmkm

    IMAGE_NAME:  nvlddmkm.sys


    FAILURE_BUCKET_ID:  X64_0x7f_8_nvlddmkm+1a3a3f

    BUCKET_ID:  X64_0x7f_8_nvlddmkm+1a3a3f

    Followup: MachineOwner

    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f07c000 fffff880`0fd64000   nvlddmkm T (no symbols)          
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Thu Aug 30 09:50:16 2012 (503F8BB8)
        CheckSum:         00CCA304
        ImageSize:        00CE8000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    • Marked as answer by Juke Chou Monday, October 8, 2012 3:44 PM
    • Unmarked as answer by jbkkd Tuesday, October 9, 2012 9:30 PM
    Tuesday, October 2, 2012 2:52 PM
  • Also, the vsdatant.sys, a component of Checkpoint VPN, may be the issue.

    The error you are experiencing is similar to what was reported in the following thread:


    What seemed to work in the above thread is to install the following hotfixes for the Operating System:



    There is a link at the top of each article to request each hotfix.

    Also, contact Checkpoint for a updated "patched" version of Checkpoint VPN which may address what appears to be a known issue.  

    • Marked as answer by Juke Chou Monday, October 8, 2012 3:44 PM
    Tuesday, October 2, 2012 9:48 PM
  • Yes, I have installed my graphics card driver recently.

    I've done so because the one that came with the computer supplied by Dell started giving me the BSODs. That's why I installed a new version from the Nvidia site, to no avail. 

    Tuesday, October 9, 2012 9:32 PM