BSOD Possibly because of SLI / OpenGL


  1. Posts : 5
    7 Ultimate x64
       #1

    BSOD Kernel Power: Possibly SLI / OpenGL related


    System Specs:
    Cpu: i7 970
    Motherboard: Rampage III Extreme
    Ram: OCZ Flex Extreme 12 GB Tripple Channel kit @ 2133
    Video: 2x Nvidia HD superclocked 570s in SLI
    Hard Drive(s): 3x Ocz vertex 2 in raid 0, (superfetch, prefetch, indexing, defragmentation disabled)
    Western Digital Caviar Black 2tb (storage drive)
    OS: windows 7 ultimate sp1 retail

    Basically, this "kernal power" event only happens when sli is enabled, and odd enough it happens to a friend with a very similar system build, same nvidia setup, also an Asus ROG motherboard, but anyways back on topic.

    When SLI is enabled, this error starts showing up. I replaced the 850 watt psu that I had, knowing that was not the likely cause. A 1200 watt psu is nearly overkill. With the 7 year warranty though, I couldn't resist! I noticed as well this does not happen at all when running any direct3d game, but it happens frequently with opengl games.

    I had to disable all of my overclocks to come to this conclusion, but typically I run my processor @ 4.2ghz, and both video cards are then overclocked. I did finally get a minidump to happen, and am attaching the requested files.

    Thanks in advance!
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    Stop overclocking the cards, a hardware error may be causing this.
    Disable SLI and test each card individually with OCCT
    NVIDIA/AMD Video Card - Test with OCCT

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for real bugcheck).
    Arguments:
    Arg1: fffffa800a3e44e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f8599c8, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000000, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+1759c8
    fffff880`0f8599c8 ??              ???
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x117
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`065f0630 fffff880`080d35f7 : fffffa80`0a3e44e0 fffff880`0811fec4 fffffa80`0a3e44e0 fffff880`080a1843 : watchdog!WdDbgReportRecreate+0xa3
    fffff880`065f0b50 fffff880`080d42bc : fffff8a0`0c641230 fffff8a0`0c641230 00000000`00000080 fffffa80`0a3e44e0 : dxgkrnl!TdrUpdateDbgReport+0xcb
    fffff880`065f0ba0 fffff880`080a86b3 : 00000000`00000001 fffffa80`0fd1e000 00000000`00000000 fffff880`00000067 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
    fffff880`065f0bd0 fffff880`080d4e0f : fffffa80`0fd1a658 ffffffff`fffe7960 fffffa80`0a3e44e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0xef
    fffff880`065f0c80 fffff880`081a3ec1 : fffffa80`0a42e510 00000000`00000080 00000000`00000000 fffffa80`0fd1a010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`065f0d00 fffff800`0391afee : 00000000`fffffc32 fffffa80`0fd4c060 fffffa80`09ce09e0 fffffa80`0fd4c060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`065f0d40 fffff800`036715e6 : fffff800`037f5e80 fffffa80`0fd4c060 fffff800`03803cc0 fffff880`01852384 : nt!PspSystemThreadStartup+0x5a
    fffff880`065f0d80 00000000`00000000 : fffff880`065f1000 fffff880`065eb000 fffff880`065f0110 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+1759c8
    fffff880`0f8599c8 ??              ???
    
    SYMBOL_NAME:  nvlddmkm+1759c8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b
    
    FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 5
    7 Ultimate x64
    Thread Starter
       #3

    The cards currently are not overlcocked, and running a default values. This has been happening for a while now.

    Edit: I'm going to redo the system, if the problem persists, i'll post a reply. As a reference, this is also happening on another computer I built, same nvidia setup, no overclocks, and also an Asus Rog system. Could it be a voltage issue with the motherboard itself?
      My Computer


  4. Posts : 5
    7 Ultimate x64
    Thread Starter
       #4

    After a fresh install of windows, latest drivers etc, I ran OCCT, here's the results of the memory tests, they did throw errors, is this within normal ranges? SLI was disabled as a reference.

    Edit, did the GPU occt test, and it failed within minutes.. added those results as well.
      My Computer


  5. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #5

    There is a hardware fault with one of your GPU. Run the Test with only one graphics card plugged in to identify the defective one.
      My Computer


  6. Posts : 5
    7 Ultimate x64
    Thread Starter
       #6

    Luckily I can disable the pci-e port :)

    Tested both cards separately, looks like main card is throwing errors. At least the secondary card is ok! I'll have to RMA the main card. Until then, thanks Once I get both cards back in if the problem persists, I'll post back.
    Last edited by nate302; 24 Nov 2011 at 13:32.
      My Computer


  7. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #7

    nate302 said:
    Luckily I can disable the pci-e port :)

    Tested both cards separately, looks like main card is throwing errors. At least the secondary card is ok! I'll have to RMA the main card. Until then, thanks Once I get both cards back in if the problem persists, I'll post back.
    Keep us updated with more dumps if BSODs occur again :)
      My Computer


  8. Posts : 5
    7 Ultimate x64
    Thread Starter
       #8

    Will do Not looking forward to dismantling the water loop though
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:45.
Find Us