Kernal Power Event ID 41 BSOD playing games, installed new hardware


  1. Posts : 4
    Windows 7 Home Premium 64bit
       #1

    Kernal Power Event ID 41 BSOD playing games, installed new hardware


    Ladies and gentlemen, I've come with hopes that one of you can help me before money needs to be involved. I own an HP Pavilion p7-1017cb home desktop, with the following specs:

    Processor: Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz
    Motherboard: Pegatron Corp. 2AC2
    HDD: 1TB SATA generic hard disk drive
    PSU: 250 Watt generic
    Optical Drive: SuperMulti DVD Burner
    Memory: Samsung 4GB DDR3 (1 piece)
    OS: Windows 7 Home Premium 64bit
    Security: Windows Security Essentials

    Just tonight, I installed these components:
    PSU: EVGA 600 Watt Bronze
    GPU: Galaxy nVidia GTX 650 Ti GC

    I followed the installation instructions and the computer booted without a hitch. I did not overclock the GPU other than what the factory did. About 10 minutes into playing STALKER: Clear Sky, the computer screen turned off, followed by an awful sound from the speakers, before rebooting. Then I see this error description upon logging on:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 116
    BCP1: FFFFFA8009587010
    BCP2: FFFFF8800F9DC074
    BCP3: FFFFFFFFC000009A
    BCP4: 0000000000000004
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\103113-13010-01.dmp
    C:\Users\Tony\AppData\Local\Temp\WER-55317-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    I checked to see if I installed the parts wrong and thought I might have when I didn't use the provided power cable in the GPU box. So I did and I unfortunately got the same error. Thankfully, the BSOD only occurs when playing games, not normal PC stuff like browsing the web and Office applications. And now you know how I came here and hope one of you guys can find the origin of this error, if it's not faulty hardware.

    Here's the link to my computer's MEMORY.DMP
    https://www.dropbox.com/s/73r3tg4e923t3g4/MEMORY.DMP
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi Satsu Ryu.

    A stop ox116 is a display/graphics reacted issue.

    Install the NVIDIA DRIVERS 314.22WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know the Wattage of the PSU. It is a very vital information here, as it is a more or less two years old branded desktop.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    Let us know the results.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8009587010, fffff8800f9dc074, ffffffffc000009a, 4}
    
    *** 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+994074 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8009587010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f9dc074, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000004, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+994074
    fffff880`0f9dc074 803dae0aefff00  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0f8ccb29)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`06715a48 fffff880`0fcdc140 : 00000000`00000116 fffffa80`09587010 fffff880`0f9dc074 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`06715a50 fffff880`0fcaf867 : fffff880`0f9dc074 fffffa80`07a09000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`06715a90 fffff880`0fcdbf4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`09587010 fffff880`0fdac35a : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`06715b40 fffff880`0fdab03d : fffffa80`0a66fd50 00000000`00000080 00000000`00000000 fffffa80`0797b410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`06715bc0 fffff800`031132ea : 00000000`0245fb7b fffffa80`076338b0 fffffa80`039559e0 fffffa80`076338b0 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`06715c00 fffff800`02e678e6 : fffff880`02fd5180 fffffa80`076338b0 fffff880`02fdffc0 00390042`00000001 : nt!PspSystemThreadStartup+0x5a
    fffff880`06715c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+994074
    fffff880`0f9dc074 803dae0aefff00  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0f8ccb29)],0
    
    SYMBOL_NAME:  nvlddmkm+994074
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52676afe
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f048000 fffff880`0fc7f000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Oct 23 11:51:50 2013 (52676AFE)
        CheckSum:         00C0CF0F
        ImageSize:        00C37000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 4
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Hi Arc, thanks for the reply!

    I've done as you said and have completely uninstalled the nVidia drivers, booted to safe mode, removed anything else with Driver Sweeper, rebooted normally, and then installed the 314.22WHQL drivers.

    Using the settings recommended in the FurMark link, my GPU didn't generate any artifacts when the temperature plateaued at 90C. Once the application's temperature alarm went off, I stopped.

    I have not done any overclocking to the GPU. However, the Galaxy GTX 650 Ti GC is factory overclocked out of the box.

    The wattage of the current PSU is 600. It is a EVGA Bronze 600 Watt PSU. I used the Power Supply Calculator and I may be missing some items, but I marked as much as I know about the PC. The only thing I wasn't sure of was the fan size in the case. But other than that, the Power Supply Calculator recommended a 257w.

    And here is what Speccy looks like after three hours of browsing the web and watching Hulu.com


    EDIT:
    An hour ago I decided to try my luck at playing some games again. I kept alt-tabbing between windows and noticed the GPU started to become too hot (90C) after around 10 minutes of play. So I popped the case's side panel open and saw that a wire was leaning into the GPU fan, that was causing the formerly mysterious sound. I've also decided to keep the side panel off, as I think the default case may not be conducive for good airflow. Been playing for maybe 45 minutes so far and temps are good (55C) and no BSOD. Will remain vigilant for any further changes.
    Last edited by Satsu Ryu; 01 Nov 2013 at 16:33.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    I would like to support you that the default case is responsible for lack of ventilation. Plan for a larger case, and one additional cooler.
      My Computer


  5. Posts : 4
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    Will do. Also, everything has been running fine and well on the NVIDIA DRIVERS 314.22WHQL but is there any reason to not update to the current 331.65WHQL?
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Yes, there are reasons. None of the driver versions after 314.22 are stable.
      My Computer


  7. Posts : 4
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    Alright, thanks for the heads up then and of course the advice from your other replies.

    EDIT: I'm going to mark this thread solved. I haven't had any strange problems since then. If something else comes up, I'll make another thread for it. Thanks again Arc!
    Last edited by Satsu Ryu; 07 Nov 2013 at 10:35.
      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 07:17.
Find Us