BSOD at different times, cant pinpoint the cause (Kernal Power 41)

  1. Posts : 2
    64 bit windows 7

    BSOD at different times, cant pinpoint the cause (Kernal Power 41)

    Hi i have been getting a weird BSOD and there is no distinct line during the blue screen that i can give you as it seems to be a little different to many BSOD's

    Here is some of the information i can give you

    At the time of the particular Blue screen which was 10:18 PM i got the following errors in Event Viewer under System Tab, there where no errors at the time under Application tab

    Critical 6/23/2014 10:18:15 PM Kernel-Power 41 (63)
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Error 6/23/2014 10:18:19 PM BugCheck 1001 None

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8800f2dcdbb, 0xfffff880054aa228, 0xfffff880054a9a80). A dump was saved in:

    Error 6/23/2014 10:18:19 PM EventLog 6008 None
    The previous system shutdown at 10:17:16 PM on ‎6/‎23/‎2014 was unexpected.

    I also have a minidump file of it in my Minidump folder but i cannot attach it here because i apparently dont have permission to do so even though i went through the properties to allow full access

    EDIT: ive uploaded the minidump now
    Last edited by scocuzza; 24 Jun 2014 at 22:53.
      My Computer

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

    Welcome to the forum scocuzza,

    Please upload your MSINFO32 file.
    • Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter.
    • Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
    • Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\admin\Downloads\062314-9968-01\062314-9968-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`03265000 PsLoadedModuleList = 0xfffff800`034a8890
    Debug session time: Tue Jun 24 08:17:50.490 2014 (UTC + 6:00)
    System Uptime: 0 days 7:26:10.302
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000007E, {ffffffffc0000005, fffff8800f2dcdbb, fffff880054aa228, fffff880054a9a80}
    Probably caused by : atikmdag.sys ( atikmdag+c7dbb )
    Followup: MachineOwner
    2: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8800f2dcdbb, The address that the exception occurred at
    Arg3: fffff880054aa228, Exception Record Address
    Arg4: fffff880054a9a80, Context Record Address
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    fffff880`0f2dcdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    EXCEPTION_RECORD:  fffff880054aa228 -- (.exr 0xfffff880054aa228)
    ExceptionAddress: fffff8800f2dcdbb (atikmdag+0x00000000000c7dbb)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000000006a8
    Attempt to read from address 00000000000006a8
    CONTEXT:  fffff880054a9a80 -- (.cxr 0xfffff880054a9a80)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000078000 rdi=0000000000000002
    rip=fffff8800f2dcdbb rsp=fffff880054aa460 rbp=fffffa800897a960
     r8=0000000000000002  r9=000000f41a500000 r10=0000000000000000
    r11=fffff880054aa690 r12=fffffa8008981b40 r13=fffffa8007c52840
    r14=fffffa800acf4600 r15=fffff8800f215000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    fffff880`0f2dcdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
    Resetting default scope
    PROCESS_NAME:  System
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  00000000000006a8
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003512100
    GetUlongFromAddress: unable to read from fffff800035121c0
     00000000000006a8 Nonpaged pool
    fffff880`0f2dcdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    LAST_CONTROL_TRANSFER:  from fffff88000000001 to fffff8800f2dcdbb
    fffff880`054aa460 fffff880`00000001 : fffff880`00000000 fffffa80`08981b00 00000000`00000000 fffffa80`0acf4600 : atikmdag+0xc7dbb
    fffff880`054aa468 fffff880`00000000 : fffffa80`08981b00 00000000`00000000 fffffa80`0acf4600 fffff880`0f33df6f : 0xfffff880`00000001
    fffff880`054aa470 fffffa80`08981b00 : 00000000`00000000 fffffa80`0acf4600 fffff880`0f33df6f 00000000`00000000 : 0xfffff880`00000000
    fffff880`054aa478 00000000`00000000 : fffffa80`0acf4600 fffff880`0f33df6f 00000000`00000000 fffff880`04610181 : 0xfffffa80`08981b00
    SYMBOL_NAME:  atikmdag+c7dbb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: atikmdag
    IMAGE_NAME:  atikmdag.sys
    STACK_COMMAND:  .cxr 0xfffff880054a9a80 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+c7dbb
    BUCKET_ID:  X64_0x7E_atikmdag+c7dbb
    Followup: MachineOwner
    2: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f215000 fffff880`10125000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 18 08:13:16 2014 (53508A3C)
        CheckSum:         00EAEEE6
        ImageSize:        00F10000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Your BSODs were caused by the latest ATI Drivers, you may consider reverting to an older version of the driver to see if that helps.

    To perform a clean install of a driver, follow this tutorial:

    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

    Scan with Kaspersky TDSSKiller:

    ESET online scanner:

    Run Disk Check on your hard disk for file system errors and bad sectors on it:
      My Computer

  3. Posts : 2
    64 bit windows 7
    Thread Starter

    Hi thanks for your reply, after posting my BSOD problem here i updated my amd driver to a different version (the newest beta 14.6) and have yet to get the blue screen *fingers crossed* because i had a feeling it had something to do with that driver so hopefully i pinpointed the cause

    im having trouble uploading the msinfo files because i the text file i save ends up being 1.42 MB which is to large to upload so i uploaded a txt file of dxdiag if thats of any use
      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 11:13.
Find Us