Windows BSOD always late at night RRS feed

  • Question

  • Hi,

    On the 26th and 28th of this month at around 3:40 to 4:10am (computer being on most of the day) I've had a random BSOD and then the computer would restart... windows would not send an error report upon restart so I have no idea what could be the cause.

    Log files:




    Wednesday, September 28, 2011 10:50 PM


  • *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *




    An attempt was made to access a pageable (or completely invalid) address at an

    interrupt request level (IRQL) that is too high.  This is usually

    caused by drivers using improper addresses.

    If kernel debugger is available get stack backtrace.


    Arg1: 0000000000000000, memory referenced

    Arg2: 000000000000000b, IRQL

    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation

    Arg4: fffff88004cbb76d, address which referenced memory


    Debugging Details:




    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0d100







    fffff880`04cbb76d 0000            add     byte ptr [rax],al








    PROCESS_NAME:  System


    TRAP_FRAME:  fffff80000b9c630 -- (.trap 0xfffff80000b9c630)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800a561fc0

    rdx=fffffd7ff663a920 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff88004cbb76d rsp=fffff80000b9c7c8 rbp=fffff80000b9c8e0

     r8=0000000000000020  r9=fffff80000b9c8e0 r10=000000f800870000

    r11=fffffa800a561fc0 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0         nv up ei ng nz na pe cy


    fffff880`04cbb76d 0000            add     byte ptr [rax],al ds:ecc0:00000000`00000000=??

    Resetting default scope




    fffff880`04cbb76d 0000            add     byte ptr [rax],al


    LAST_CONTROL_TRANSFER:  from fffff80002cda1e9 to fffff80002cdac40



    fffff800`00b9c4e8 fffff800`02cda1e9 : 00000000`0000000a 00000000`00000000 00000000`0000000b 00000000`00000001 : nt!KeBugCheckEx

    fffff800`00b9c4f0 fffff800`02cd8e60 : fffffa80`0a36ca00 00000000`0000001b 00000012`08000000 fffffa80`0a561fb0 : nt!KiBugCheckDispatch+0x69

    fffff800`00b9c630 fffff880`04cbb76d : fffff880`04c5eb93 00000000`00000005 fffffa80`099f7050 fffffa80`0a543e20 : nt!KiPageFault+0x260

    fffff800`00b9c7c8 fffff880`04c5eb93 : 00000000`00000005 fffffa80`099f7050 fffffa80`0a543e20 fffff880`04cf71a0 : atikmdag+0xb876d

    fffff800`00b9c7d0 00000000`00000005 : fffffa80`099f7050 fffffa80`0a543e20 fffff880`04cf71a0 00000000`00000002 : atikmdag+0x5bb93

    fffff800`00b9c7d8 fffffa80`099f7050 : fffffa80`0a543e20 fffff880`04cf71a0 00000000`00000002 fffff880`04cefaf6 : 0x5

    fffff800`00b9c7e0 fffffa80`0a543e20 : fffff880`04cf71a0 00000000`00000002 fffff880`04cefaf6 00000000`00000000 : 0xfffffa80`099f7050

    fffff800`00b9c7e8 fffff880`04cf71a0 : 00000000`00000002 fffff880`04cefaf6 00000000`00000000 00000000`00000000 : 0xfffffa80`0a543e20

    fffff800`00b9c7f0 00000000`00000002 : fffff880`04cefaf6 00000000`00000000 00000000`00000000 00000003`00000030 : atikmdag+0xf41a0

    fffff800`00b9c7f8 fffff880`04cefaf6 : 00000000`00000000 00000000`00000000 00000003`00000030 fffff880`0000000a : 0x2

    fffff800`00b9c800 00000000`00000000 : 00000000`00000000 00000003`00000030 fffff880`0000000a 00000007`00000048 : atikmdag+0xecaf6







    fffff880`04cbb76d 0000            add     byte ptr [rax],al




    SYMBOL_NAME:  atikmdag+b876d


    FOLLOWUP_NAME:  MachineOwner


    MODULE_NAME: hardware


    IMAGE_NAME:  hardware






    BUCKET_ID:  X64_IP_MISALIGNED_atikmdag.sys


    Followup: MachineOwner




    Bug Check Code 0xD1: http://msdn.microsoft.com/en-us/library/ff560244.aspx

    Your BSOD was caused by atikmdag.sys driver. More about it: http://www.exe-dll.com/driver/atikmdag.sys.htm

    Please update it and if this does not help, contact ATI or your manufacturer Technical Support as it seems that you have hardware problems.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer 

    • Proposed as answer by Juke Chou Friday, September 30, 2011 10:38 AM
    • Marked as answer by Juke Chou Friday, October 7, 2011 3:25 AM
    Thursday, September 29, 2011 7:31 AM