BSOD Kernel Power 41, Getting it on both games and browsers.

  1. Posts : 1
    Windows 7 x64

    BSOD Kernel Power 41, Getting it on both games and browsers.

    For some weeks now (ever since 20.09.2013 to 23.10.2013) i've been getting all these BSOD while browsing or playing games.
    i've updated all the drivers i can get to. including the Nvidia one.
    Computer is pretty new, so im not quite sure where the problem originates from.
    I followed the post rules and made a copy of the sf diagnostic.


      My Computer

  2. Posts : 15,026
    Windows 10 Home 64Bit

    Welcome to the Forum.

    Do not start the trial version of MalwareBytes

    • System File Checker
      • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.

    • Run Disk Check in Windows 7
      • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

    • Test and Diagnose RAM issues with MEMTEST86+
      • Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
        • Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. RAM - Test with Memtest86+

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {fffff300138725f0, 0, fffff8800f742d80, 7}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Could not read faulting driver name
    Probably caused by : nvlddmkm.sys ( nvlddmkm+318d80 )
    Followup: MachineOwner
    4: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arg1: fffff300138725f0, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff8800f742d80, If non-zero, the instruction address which referenced the bad memory
    Arg4: 0000000000000007, (reserved)
    Debugging Details:
    Could not read faulting driver name
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003308100
    GetUlongFromAddress: unable to read from fffff800033081c0
     fffff300138725f0 Nonpaged pool
    fffff880`0f742d80 488b5c2430      mov     rbx,qword ptr [rsp+30h]
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    TRAP_FRAME:  fffff88003770430 -- (.trap 0xfffff88003770430)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=fffffa800c751000
    rdx=0000000000137340 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800f742d80 rsp=fffff880037705c0 rbp=fffff88003770801
     r8=0000000000000020  r9=fffff880037705c0 r10=fffff8800f7f0be0
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    fffff880`0f742d80 488b5c2430      mov     rbx,qword ptr [rsp+30h] ss:0018:fffff880`037705f0=0000000000000000
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff8000314d53b to fffff800030d0bc0
    fffff880`037702c8 fffff800`0314d53b : 00000000`00000050 fffff300`138725f0 00000000`00000000 fffff880`03770430 : nt!KeBugCheckEx
    fffff880`037702d0 fffff800`030cecee : 00000000`00000000 fffff300`138725f0 fffffa80`10102d00 fffffa80`0cedaf98 : nt! ?? ::FNODOBFM::`string'+0x43781
    fffff880`03770430 fffff880`0f742d80 : fffffa80`00000001 fffffa80`0cedaf98 fffff880`03770801 fffffa80`10102000 : nt!KiPageFault+0x16e
    fffff880`037705c0 fffffa80`00000001 : fffffa80`0cedaf98 fffff880`03770801 fffffa80`10102000 fffffa80`10102000 : nvlddmkm+0x318d80
    fffff880`037705c8 fffffa80`0cedaf98 : fffff880`03770801 fffffa80`10102000 fffffa80`10102000 fffff880`0f744d98 : 0xfffffa80`00000001
    fffff880`037705d0 fffff880`03770801 : fffffa80`10102000 fffffa80`10102000 fffff880`0f744d98 00000000`00000000 : 0xfffffa80`0cedaf98
    fffff880`037705d8 fffffa80`10102000 : fffffa80`10102000 fffff880`0f744d98 00000000`00000000 fffff880`037706f0 : 0xfffff880`03770801
    fffff880`037705e0 fffffa80`10102000 : fffff880`0f744d98 00000000`00000000 fffff880`037706f0 fffffa80`10103a90 : 0xfffffa80`10102000
    fffff880`037705e8 fffff880`0f744d98 : 00000000`00000000 fffff880`037706f0 fffffa80`10103a90 fffff880`03770634 : 0xfffffa80`10102000
    fffff880`037705f0 00000000`00000000 : fffff880`037706f0 fffffa80`10103a90 fffff880`03770634 fffffa80`10103a90 : nvlddmkm+0x31ad98
    fffff880`0f742d80 488b5c2430      mov     rbx,qword ptr [rsp+30h]
    SYMBOL_NAME:  nvlddmkm+318d80
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+318d80
    BUCKET_ID:  X64_0x50_nvlddmkm+318d80
    Followup: MachineOwner
    4: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f42a000 fffff880`10055000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Fri Sep 27 11:45:06 2013 (52451B62)
        CheckSum:         00C0274A
        ImageSize:        00C2B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Follow this:
    Arc said:
    Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL 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
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

    Let us know the results.
      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 20:44.
Find Us