BSOD occuring frequently


  1. Posts : 2
    Windows 7
       #1

    BSOD occuring frequently


    Hi there, I am receiving the following error code: Event ID 41, Kernel-Power. This has occurred a few times and I am wondering how kit can be fixed? Attached are the minidumps. Thanks for your help in advance!
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    steffiec said:
    Hi there, I am receiving the following error code: Event ID 41, Kernel-Power. This has occurred a few times and I am wondering how kit can be fixed? Attached are the minidumps. Thanks for your help in advance!


    Hi and welceome

    Its your video driver

    I would
    download a fresh copy and install it
    run a system file check
    type cmd in search>right clicka nd run as admin>sfc /scannow

    If you are over clocking stop

    Let us know the results

    Ken

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\010210-17737-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`03011000 PsLoadedModuleList = 0xfffff800`0324ee50
    Debug session time: Sat Jan  2 00:13:22.430 2010 (GMT-5)
    System Uptime: 0 days 0:22:53.396
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    ..............
    Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8004c0e2f0, fffff88004e8bb90, ffffffffc000009a, 4}
    
    Unable to load image \SystemRoot\system32\DRIVERS\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+5e8b90 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8004c0e2f0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004e8bb90, 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+5e8b90
    fffff880`04e8bb90 4053            push    rbx
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`0670db48 fffff880`074a6ef8 : 00000000`00000116 fffffa80`04c0e2f0 fffff880`04e8bb90 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`0670db50 00000000`00000116 : fffffa80`04c0e2f0 fffff880`04e8bb90 ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5cef8
    fffff880`0670db58 fffffa80`04c0e2f0 : fffff880`04e8bb90 ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
    fffff880`0670db60 fffff880`04e8bb90 : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`04c0e2f0 : 0xfffffa80`04c0e2f0
    fffff880`0670db68 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`04c0e2f0 fffff880`0747a867 : nvlddmkm+0x5e8b90
    fffff880`0670db70 00000000`00000004 : 00000000`00000001 fffffa80`04c0e2f0 fffff880`0747a867 fffff880`04e8bb90 : 0xffffffff`c000009a
    fffff880`0670db78 00000000`00000001 : fffffa80`04c0e2f0 fffff880`0747a867 fffff880`04e8bb90 fffffa80`06bce000 : 0x4
    fffff880`0670db80 fffffa80`04c0e2f0 : fffff880`0747a867 fffff880`04e8bb90 fffffa80`06bce000 00000000`00000000 : 0x1
    fffff880`0670db88 fffff880`0747a867 : fffff880`04e8bb90 fffffa80`06bce000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`04c0e2f0
    fffff880`0670db90 fffff880`04e8bb90 : fffffa80`06bce000 00000000`00000000 ffffffff`c000009a fffffa80`06bc9010 : dxgkrnl+0x30867
    fffff880`0670db98 fffffa80`06bce000 : 00000000`00000000 ffffffff`c000009a fffffa80`06bc9010 fffffa80`065cc010 : nvlddmkm+0x5e8b90
    fffff880`0670dba0 00000000`00000000 : ffffffff`c000009a fffffa80`06bc9010 fffffa80`065cc010 fffffa80`065cc6d0 : 0xfffffa80`06bce000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+5e8b90
    fffff880`04e8bb90 4053            push    rbx
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nvlddmkm+5e8b90
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a6e492b
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 2
    Windows 7
    Thread Starter
       #3

    Hi There, thanks for your help. I downloaded and installed the new driver and ran a scan...this is the result below. If I understand correctly, overclocking is running a component at a higher speed than what the part was manufacturered for, correct? (I did some reading on wikipedia) but how do I know if I'm doing this? and how do I make sure I don't do it? I am not running anything abnormal on my system...just photo editing software...with my media player running in the background (music) and then that's when I've had the BSOD occur.
    .
    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:\Windows\system32>sfc/scannow
    Beginning system scan. This process will take some time.
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection did not find any integrity violations.
    C:\Windows\system32>
      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 04:54.
Find Us