Windows 8 and 8.1 Forums


Various BSODs in Past Two Days

  1. #21


    bangalore
    Posts : 634
    Windows 8.1 professional x64 + WMC


    update your ati driver to the latest stable version of the driver.

    http://support.amd.com/us/Pages/AMDSupportHub.aspx

    after the update upload the drivers.txt file

    Code:
    Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2*** 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, fffff8800b90b611, fffff8800a22f0a8, fffff8800a22e8e0}
    
    
    Probably caused by : hardware ( atikmdag+10b611 )
    
    
    Followup: MachineOwner
    ---------
    
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8800b90b611, The address that the exception occurred at
    Arg3: fffff8800a22f0a8, Exception Record Address
    Arg4: fffff8800a22e8e0, 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.
    
    
    FAULTING_IP: 
    atikmdag+10b611
    fffff880`0b90b611 89442418        mov     dword ptr [rsp+18h],eax
    
    
    EXCEPTION_RECORD:  fffff8800a22f0a8 -- (.exr 0xfffff8800a22f0a8)
    ExceptionAddress: fffff8800b90b611 (atikmdag+0x000000000010b611)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000190
    Attempt to read from address 0000000000000190
    
    
    CONTEXT:  fffff8800a22e8e0 -- (.cxr 0xfffff8800a22e8e0)
    rax=0000000000000000 rbx=0000000f04e60000 rcx=fffffa800f96551f
    rdx=fffff8800a22f3e0 rsi=fffffa800f965520 rdi=fffff8800a22f540
    rip=fffff8800b90b611 rsp=fffff8800a22f2e8 rbp=fffff8800a22f450
     r8=0000000000004000  r9=0000000000000000 r10=0000000000004000
    r11=fffff8800b9d36a0 r12=fffffa8014e532c0 r13=0000000000000001
    r14=00000000ffffffff r15=fffff8800b800000
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    atikmdag+0x10b611:
    fffff880`0b90b611 89442418        mov     dword ptr [rsp+18h],eax ss:fffff880`0a22f300=ffffffff
    Resetting default scope
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    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:  0000000000000190
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8002c762168
    GetUlongFromAddress: unable to read from fffff8002c7621f8
     0000000000000190 Nonpaged pool
    
    
    FOLLOWUP_IP: 
    atikmdag+10b611
    fffff880`0b90b611 89442418        mov     dword ptr [rsp+18h],eax
    
    
    BUGCHECK_STR:  AV
    
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    
    MISALIGNED_IP: 
    atikmdag+10b611
    fffff880`0b90b611 89442418        mov     dword ptr [rsp+18h],eax
    
    
    LAST_CONTROL_TRANSFER:  from fffff8800b811541 to fffff8800b90b611
    
    
    STACK_TEXT:  
    fffff880`0a22f2e8 fffff880`0b811541 : fffffa80`0f965520 fffff880`0a22f540 00000000`ffffffff fffff880`0b800000 : atikmdag+0x10b611
    fffff880`0a22f2f0 fffffa80`0f965520 : fffff880`0a22f540 00000000`ffffffff fffff880`0b800000 fffff880`00000001 : atikmdag+0x11541
    fffff880`0a22f2f8 fffff880`0a22f540 : 00000000`ffffffff fffff880`0b800000 fffff880`00000001 00000000`00004000 : 0xfffffa80`0f965520
    fffff880`0a22f300 00000000`ffffffff : fffff880`0b800000 fffff880`00000001 00000000`00004000 00000000`00004000 : 0xfffff880`0a22f540
    fffff880`0a22f308 fffff880`0b800000 : fffff880`00000001 00000000`00004000 00000000`00004000 fffffa80`0db94000 : 0xffffffff
    fffff880`0a22f310 fffff880`00000001 : 00000000`00004000 00000000`00004000 fffffa80`0db94000 00000000`00000000 : atikmdag
    fffff880`0a22f318 00000000`00004000 : 00000000`00004000 fffffa80`0db94000 00000000`00000000 00000000`00004000 : 0xfffff880`00000001
    fffff880`0a22f320 00000000`00004000 : fffffa80`0db94000 00000000`00000000 00000000`00004000 00000000`00000000 : 0x4000
    fffff880`0a22f328 fffffa80`0db94000 : 00000000`00000000 00000000`00004000 00000000`00000000 fffff880`05a22853 : 0x4000
    fffff880`0a22f330 00000000`00000000 : 00000000`00004000 00000000`00000000 fffff880`05a22853 fffff880`0a22f400 : 0xfffffa80`0db94000
    
    
    
    
    SYMBOL_STACK_INDEX:  0
    
    
    SYMBOL_NAME:  atikmdag+10b611
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: hardware
    
    
    IMAGE_NAME:  hardware
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    
    STACK_COMMAND:  .cxr 0xfffff8800a22e8e0 ; kb
    
    
    FAILURE_BUCKET_ID:  IP_MISALIGNED_atikmdag.sys
    
    
    BUCKET_ID:  IP_MISALIGNED_atikmdag.sys
    
    
    Followup: MachineOwner
    ---------
    
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8800b90b611, The address that the exception occurred at
    Arg3: fffff8800a22f0a8, Exception Record Address
    Arg4: fffff8800a22e8e0, 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.
    
    
    FAULTING_IP: 
    atikmdag+10b611
    fffff880`0b90b611 89442418        mov     dword ptr [rsp+18h],eax
    
    
    EXCEPTION_RECORD:  fffff8800a22f0a8 -- (.exr 0xfffff8800a22f0a8)
    ExceptionAddress: fffff8800b90b611 (atikmdag+0x000000000010b611)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000190
    Attempt to read from address 0000000000000190
    
    
    CONTEXT:  fffff8800a22e8e0 -- (.cxr 0xfffff8800a22e8e0)
    rax=0000000000000000 rbx=0000000f04e60000 rcx=fffffa800f96551f
    rdx=fffff8800a22f3e0 rsi=fffffa800f965520 rdi=fffff8800a22f540
    rip=fffff8800b90b611 rsp=fffff8800a22f2e8 rbp=fffff8800a22f450
     r8=0000000000004000  r9=0000000000000000 r10=0000000000004000
    r11=fffff8800b9d36a0 r12=fffffa8014e532c0 r13=0000000000000001
    r14=00000000ffffffff r15=fffff8800b800000
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    atikmdag+0x10b611:
    fffff880`0b90b611 89442418        mov     dword ptr [rsp+18h],eax ss:fffff880`0a22f300=ffffffff
    Resetting default scope
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    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:  0000000000000190
    
    
    READ_ADDRESS:  0000000000000190 Nonpaged pool
    
    
    FOLLOWUP_IP: 
    atikmdag+10b611
    fffff880`0b90b611 89442418        mov     dword ptr [rsp+18h],eax
    
    
    BUGCHECK_STR:  AV
    
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    
    MISALIGNED_IP: 
    atikmdag+10b611
    fffff880`0b90b611 89442418        mov     dword ptr [rsp+18h],eax
    
    
    LAST_CONTROL_TRANSFER:  from fffff8800b811541 to fffff8800b90b611
    
    
    STACK_TEXT:  
    fffff880`0a22f2e8 fffff880`0b811541 : fffffa80`0f965520 fffff880`0a22f540 00000000`ffffffff fffff880`0b800000 : atikmdag+0x10b611
    fffff880`0a22f2f0 fffffa80`0f965520 : fffff880`0a22f540 00000000`ffffffff fffff880`0b800000 fffff880`00000001 : atikmdag+0x11541
    fffff880`0a22f2f8 fffff880`0a22f540 : 00000000`ffffffff fffff880`0b800000 fffff880`00000001 00000000`00004000 : 0xfffffa80`0f965520
    fffff880`0a22f300 00000000`ffffffff : fffff880`0b800000 fffff880`00000001 00000000`00004000 00000000`00004000 : 0xfffff880`0a22f540
    fffff880`0a22f308 fffff880`0b800000 : fffff880`00000001 00000000`00004000 00000000`00004000 fffffa80`0db94000 : 0xffffffff
    fffff880`0a22f310 fffff880`00000001 : 00000000`00004000 00000000`00004000 fffffa80`0db94000 00000000`00000000 : atikmdag
    fffff880`0a22f318 00000000`00004000 : 00000000`00004000 fffffa80`0db94000 00000000`00000000 00000000`00004000 : 0xfffff880`00000001
    fffff880`0a22f320 00000000`00004000 : fffffa80`0db94000 00000000`00000000 00000000`00004000 00000000`00000000 : 0x4000
    fffff880`0a22f328 fffffa80`0db94000 : 00000000`00000000 00000000`00004000 00000000`00000000 fffff880`05a22853 : 0x4000
    fffff880`0a22f330 00000000`00000000 : 00000000`00004000 00000000`00000000 fffff880`05a22853 fffff880`0a22f400 : 0xfffffa80`0db94000
    
    
    
    
    SYMBOL_STACK_INDEX:  0
    
    
    SYMBOL_NAME:  atikmdag+10b611
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: hardware
    
    
    IMAGE_NAME:  hardware
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    
    STACK_COMMAND:  .cxr 0xfffff8800a22e8e0 ; kb
    
    
    FAILURE_BUCKET_ID:  IP_MISALIGNED_atikmdag.sys
    
    
    BUCKET_ID:  IP_MISALIGNED_atikmdag.sys
    
    
    Followup: MachineOwner
    ---------

      My System SpecsSystem Spec

  2. #22


    I now have the most recent stable version of the ATI drivers. However, I cannot create the drivers.txt file with the SF Diagnostic Tool. I'm running as admin and I tried both Grab All and just Driver List, but it results in an empty text file. I even tried re-downloading the tool.
      My System SpecsSystem Spec

  3. #23


    The SF Tool is still not correctly dumping everything (I attached what it could get). But I got another BSOD just now related to the AMD Control Panel:

    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck F7, {fffff8800ec7d787, 7f69fadd3eb3, ffff80960522c14c, 0}
    
    
    Probably caused by : ntkrnlmp.exe ( nt!_report_gsfailure+25 )
    
    
    Followup: MachineOwner
    ---------
    
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_OVERRAN_STACK_BUFFER (f7)
    A driver has overrun a stack-based buffer.  This overrun could potentially
    allow a malicious user to gain control of this machine.
    DESCRIPTION
    A driver overran a stack-based buffer (or local variable) in a way that would
    have overwritten the function's return address and jumped back to an arbitrary
    address when the function returned.  This is the classic "buffer overrun"
    hacking attack and the system has been brought down to prevent a malicious user
    from gaining complete control of it.
    Do a kb to get a stack backtrace -- the last routine on the stack before the
    buffer overrun handlers and bugcheck call is the one that overran its local
    variable(s).
    Arguments:
    Arg1: fffff8800ec7d787, Actual security check cookie from the stack
    Arg2: 00007f69fadd3eb3, Expected security check cookie
    Arg3: ffff80960522c14c, Complement of the expected security check cookie
    Arg4: 0000000000000000, zero
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
    
    
    SECURITY_COOKIE:  Expected 00007f69fadd3eb3 found fffff8800ec7d787
    
    
    BUGCHECK_STR:  0xF7
    
    
    PROCESS_NAME:  CCC.exe
    
    
    CURRENT_IRQL:  0
    
    
    LAST_CONTROL_TRANSFER:  from fffff803c456613d to fffff803c4489340
    
    
    STACK_TEXT:  
    fffff880`0ec7d730 fffff803`c456613d : 00000000`000000f7 fffff880`0ec7d787 00007f69`fadd3eb3 ffff8096`0522c14c : nt!KeBugCheckEx
    fffff880`0ec7d738 fffff803`c484fa36 : fffff803`c4851b4d 00000000`000004c3 fffff880`0ec7d808 00000000`00000000 : nt!_report_gsfailure+0x25
    fffff880`0ec7d778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopSynchronousServiceTail+0x216
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nt!_report_gsfailure+25
    fffff803`c456613d cc              int     3
    
    
    SYMBOL_STACK_INDEX:  1
    
    
    SYMBOL_NAME:  nt!_report_gsfailure+25
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50ab0e64
    
    
    BUCKET_ID_FUNC_OFFSET:  25
    
    
    FAILURE_BUCKET_ID:  0xF7_MISSING_GSFRAME_nt!_report_gsfailure
    
    
    BUCKET_ID:  0xF7_MISSING_GSFRAME_nt!_report_gsfailure
    
    
    Followup: MachineOwner
    ---------
      My System SpecsSystem Spec

  4. #24


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Sorry to butt in here, but please try a couple of the free scans here: Free Online AntiMalware Resources
    We generally can't fix BSOD's caused by infections - so it's best to rule them out at this point.
      My System SpecsSystem Spec

  5. #25


    Thanks usasma! I actually was running a Windows Defender full system scan when I received another BSOD. I'm running it again now and I'll try out some of the anti-malware in your link if this does not work.

    This one mentions memory corruption, but I did run a few passes of memtest86+ a few months ago with no errors:
    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 3B, {c000001d, fffff803d1b57a6f, fffff8802e4ef6f0, 0}
    
    
    Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+3e0 )
    
    
    Followup: MachineOwner
    ---------
    
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c000001d, Exception code that caused the bugcheck
    Arg2: fffff803d1b57a6f, Address of the instruction which caused the bugcheck
    Arg3: fffff8802e4ef6f0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    
    Debugging Details:
    ------------------
    
    
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
    
    
    FAULTING_IP: 
    nt!MmUnmapViewInSystemCache+3e0
    fffff803`d1b57a6f 0f84e1000000    je      nt!MmUnmapViewInSystemCache+0x4c7 (fffff803`d1b57b56)
    
    
    CONTEXT:  fffff8802e4ef6f0 -- (.cxr 0xfffff8802e4ef6f0)
    rax=0000058000000000 rbx=fffff6fcc00330b0 rcx=0000000fffffffff
    rdx=0000000000000000 rsi=0000000000000016 rdi=fffff8802e4f0250
    rip=fffff803d1b57a6f rsp=fffff8802e4f00f0 rbp=fffff98006616000
     r8=0000000000000000  r9=fffffa801c030f20 r10=0000000000000002
    r11=000000000001f75a r12=fffff8a0135314a8 r13=0000000000011947
    r14=fffff6fcc0033200 r15=fffffa800a8296d0
    iopl=0         nv up ei ng nz ac po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297
    nt!MmUnmapViewInSystemCache+0x3e0:
    fffff803`d1b57a6f 0f84e1000000    je      nt!MmUnmapViewInSystemCache+0x4c7 (fffff803`d1b57b56) [br=0]
    Resetting default scope
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x3B
    
    
    PROCESS_NAME:  MsMpEng.exe
    
    
    CURRENT_IRQL:  0
    
    
    LAST_CONTROL_TRANSFER:  from fffff803d1ee7cf8 to fffff803d1b57a6f
    
    
    STACK_TEXT:  
    fffff880`2e4f00f0 fffff803`d1ee7cf8 : 00000003`00000000 fffff880`00e5d830 00000000`00000000 fffffa80`0d9adcf0 : nt!MmUnmapViewInSystemCache+0x3e0
    fffff880`2e4f03f0 fffff803`d1b572d7 : 00000000`00780000 00000000`00000000 fffffa80`1e720a58 00000000`00800000 : nt!CcUnmapVacb+0x58
    fffff880`2e4f0430 fffff803`d1b42052 : 00000000`00780001 00000000`00000000 fffffa80`1ed35be0 00000000`00000000 : nt!CcUnmapVacbArray+0x1f7
    fffff880`2e4f04a0 fffff803`d1b5a600 : fffffa80`00000000 00000000`00800000 fffff880`2e4f0590 fffff880`2e4f0578 : nt!CcGetVirtualAddress+0x332
    fffff880`2e4f0540 fffff803`d1b5a3f2 : fffffa80`0d9adcf0 000000b1`a12baf09 fffff880`2e4f0690 fffff880`000065a7 : nt!CcMapAndCopyInToCache+0x170
    fffff880`2e4f0630 fffff880`016fd020 : 00000000`008065a7 fffffa80`0e3a7940 fffffa80`1b826168 fffffa80`2e8271d0 : nt!CcCopyWriteEx+0x1b2
    fffff880`2e4f06d0 fffff880`014e6415 : 00000000`00000000 00000000`000002b0 000000b1`00000585 00000000`00000000 : Ntfs!NtfsCopyWriteA+0x290
    fffff880`2e4f0930 fffff880`014e6b53 : fffff880`2e4f0a20 00000000`00000000 fffffa80`2e827100 fffffa80`1b826010 : fltmgr!FltpPerformFastIoCall+0x155
    fffff880`2e4f0990 fffff880`0150eabd : 00000000`00004001 fffffa80`2e8271d0 fffff880`2e4f0000 00000000`00000000 : fltmgr!FltpPassThroughFastIo+0xc3
    fffff880`2e4f09f0 fffff803`d1ee8441 : fffffa80`2e8271d0 fffffa80`2e8271d0 000000b1`9f27c448 fffffa80`0df9f2c0 : fltmgr!FltpFastIoWrite+0x19d
    fffff880`2e4f0aa0 fffff803`d1b01353 : ffffffff`ffffff01 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x5d0
    fffff880`2e4f0bd0 000007fd`6ab02c6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000b1`9504e9d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fd`6ab02c6a
    
    
    
    
    FOLLOWUP_IP: 
    nt!MmUnmapViewInSystemCache+3e0
    fffff803`d1b57a6f 0f84e1000000    je      nt!MmUnmapViewInSystemCache+0x4c7 (fffff803`d1b57b56)
    
    
    SYMBOL_STACK_INDEX:  0
    
    
    SYMBOL_NAME:  nt!MmUnmapViewInSystemCache+3e0
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50ab0e64
    
    
    STACK_COMMAND:  .cxr 0xfffff8802e4ef6f0 ; kb
    
    
    IMAGE_NAME:  memory_corruption
    
    
    BUCKET_ID_FUNC_OFFSET:  3e0
    
    
    FAILURE_BUCKET_ID:  0x3B_nt!MmUnmapViewInSystemCache
    
    
    BUCKET_ID:  0x3B_nt!MmUnmapViewInSystemCache
    
    
    Followup: MachineOwner
    ---------
      My System SpecsSystem Spec

  6. #26


    I got 3 more BSODs since my last post. I got another memory corruption one when scanning with Windows Defender and the most recent one was while playing a game (see below). I scanned with ESET and nothing was found and I scanned with Spybot S&D... nothing was found. Attached is what the SF tool gives me. Anyone have any other suggestions to try?

    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 19, {d, fffff8a071686bf0, 37c39c06d26b06e6, 37c39c06d26b06ee}
    
    
    Probably caused by : Pool_Corruption ( nt!ExFreePool+60 )
    
    
    Followup: Pool_corruption
    ---------
    
    
    5: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 000000000000000d, 
    Arg2: fffff8a071686bf0
    Arg3: 37c39c06d26b06e6
    Arg4: 37c39c06d26b06ee
    
    
    Debugging Details:
    ------------------
    
    
    
    
    BUGCHECK_STR:  0x19_d
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    PROCESS_NAME:  farcry3_d3d11.
    
    
    CURRENT_IRQL:  1
    
    
    LOCK_ADDRESS:  fffff8017d4eb8a0 -- (!locks fffff8017d4eb8a0)
    
    
    Resource @ nt!PnpRegistryDeviceResource (0xfffff8017d4eb8a0)    Exclusively owned
        Contention Count = 97
         Threads: fffffa801bdbdb00-01<*> 
    1 total locks, 1 locks currently held
    
    
    PNP_TRIAGE: 
    	Lock address  : 0xfffff8017d4eb8a0
    	Thread Count  : 1
    	Thread address: 0xfffffa801bdbdb00
    	Thread wait   : 0x917b9
    
    
    LAST_CONTROL_TRANSFER:  from fffff8017d4851e4 to fffff8017d290340
    
    
    STACK_TEXT:  
    fffff880`2de5c308 fffff801`7d4851e4 : 00000000`00000019 00000000`0000000d fffff8a0`71686bf0 37c39c06`d26b06e6 : nt!KeBugCheckEx
    fffff880`2de5c310 fffff801`7d483b48 : fffff880`00000000 fffff8a0`543438f0 fffff8a0`75ce18b0 00000000`000000ab : nt!ExFreePool+0x60
    fffff880`2de5c3a0 fffff801`7d5c96f2 : fffff8a0`54343900 00000000`00000200 fffff8a0`00091580 00000000`52504e50 : nt!ExFreePoolWithTag+0xb39
    fffff880`2de5c480 fffff801`7d5c983a : 00000000`00000040 fffff880`2de5c5c1 00000000`00000004 00000000`00000001 : nt!CmOpenCommonClassRegKeyWorker+0x166
    fffff880`2de5c500 fffff801`7d5ca0ae : 00000000`00000002 00000000`00000000 fffff880`2de5c710 00000000`00010000 : nt!CmOpenCommonClassRegKey+0x102
    fffff880`2de5c610 fffff801`7d5cb19c : 00000000`00000001 fffff880`2de5ca58 00000000`00000000 fffff880`2de5c858 : nt!IopGetDeviceInterfaces+0xee
    fffff880`2de5c7e0 fffff801`7d5c765f : fffff880`2de5cc28 fffff801`7d65588c fffffa80`0d0402f0 fffffa80`162f3bb0 : nt!PiCMGetDeviceInterfaceList+0xf8
    fffff880`2de5c8e0 fffff801`7d5c77cd : d400de94`0f02fc6b 0000001f`00120089 00000002`00000001 00000000`77732300 : nt!PiCMHandleIoctl+0x157
    fffff880`2de5c920 fffff801`7d5c73f1 : fffff801`7d5c738c fffffa80`0d040e40 00000000`00000000 00000000`00000000 : nt!PiCMFastIoDeviceDispatch+0x55
    fffff880`2de5c970 fffff801`7d673fca : fffffa80`1bd28260 fffffa80`1bd28210 00000000`00000000 00000000`00000000 : nt!PiDaFastIoDispatch+0x65
    fffff880`2de5c9d0 fffff801`7d674d56 : 00000000`00000000 fffffa80`00000000 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x3d9
    fffff880`2de5cb60 fffff801`7d28f353 : fffffa80`1bdbdb00 00000000`00000000 00000000`001f0000 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
    fffff880`2de5cbd0 00000000`77732ad2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`044deb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77732ad2
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nt!ExFreePool+60
    fffff801`7d4851e4 cc              int     3
    
    
    SYMBOL_STACK_INDEX:  1
    
    
    SYMBOL_NAME:  nt!ExFreePool+60
    
    
    FOLLOWUP_NAME:  Pool_corruption
    
    
    IMAGE_NAME:  Pool_Corruption
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    
    MODULE_NAME: Pool_Corruption
    
    
    BUCKET_ID_FUNC_OFFSET:  60
    
    
    FAILURE_BUCKET_ID:  0x19_d_nt!ExFreePool
    
    
    BUCKET_ID:  0x19_d_nt!ExFreePool
    
    
    Followup: Pool_corruption
    ---------
      My System SpecsSystem Spec

  7. #27


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Memory corruption refers to something wrong with the virtual address' that the program was using.
    As such this can be:
    - an error caused by the program in it's own memory space
    - an error caused by another program in the original program's memory space
    - an error in the RAM that's storing that memory space
    - an error in the virtual memory that's storing that memory space (the pagefile on your hard drive)
    - an error caused by other memory structures (such as the CPU cache, the memory controllers, or even video memory) when operating on data from a particular memory space
    - a blip in the ether (in other words, a random problem) - but you wouldn't be here if it was just that (as it wouldn't be repeating).

    Most often it's a 3rd party (non-Microsoft) program that's causing the problem.
    Next most often is a hardware problem
    And lastly is that it may be a Windows problem.

    Please make sure that you have all available Windows Updates. Run the utility several times to ensure that you have them all - it's very important to keep up with them in a newly released OS.

    See these 2 lines from the stack text:
    Code:
    fffff880`2de5cbd0 00000000`77732ad2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`044deb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77732ad2
    The 0x77732ad2 is either a bad address or a user level function's address (because this is a minidump it doesn't contain references to user level functions and their memory address')
    The System Service thing above it tends to confirm (but it is by no means a certain thing) that it's most likely a user level function (IMO) - so we presume that it's a 3rd party driver that's causing this.

    You have 7 memory dumps uploaded - and they show 5 different BSOD error codes and blame 4 different causes. This (the random errors/blames) is usually a symptom of low-level driver problems (to include compatibility issues) or hardware problems.

    So, I suspect that it's a low-level driver issue.
    A quick look at the dump file output shows 3 known drivers that cause these sort of problems. Please note that a lot of the references point to Win7 systems. As Win8 is new we rely on the behavior of these programs in Win7 to predict problems in Win8. We're way, way deep into the SWAG curve here (Scientific Wild-A**ed Guess):

    Un-install this one:
    RTCore64.sys Tue Sep 6 08:24:50 2011 (4E661112)
    RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
    http://www.carrona.org/drivers/driver.php?id=RTCore64.sys

    Instructions below on how to get rid of this one:
    AODDriver2.sys Thu Apr 5 05:23:37 2012 (4F7D6499)
    AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.
    Just keep an eye on this one:
    xusb22.sys Wed Jul 25 22:26:57 2012 (5010AAF1)
    A wireless USB XBox controller. This isn't a known troublemaker - but the 2009 version of xusb21.sys was a problem. In short, keep an eye on this one - but it's not necessary to do anything with it.
    xusb22.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Dec 24 20:07:43.327 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122412-13369-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 2:34:56.056
    Probably caused by :Pool_Corruption ( nt!ExFreePool+60 )
    BugCheck 19, {d, fffff8a071686bf0, 37c39c06d26b06e6, 37c39c06d26b06ee}
    BugCheck Info: BAD_POOL_HEADER (19)
    Arguments: 
    Arg1: 000000000000000d, 
    Arg2: fffff8a071686bf0
    Arg3: 37c39c06d26b06e6
    Arg4: 37c39c06d26b06ee
    BUGCHECK_STR:  0x19_d
    PROCESS_NAME: farcry3_d3d11.
    FAILURE_BUCKET_ID: 0x19_d_nt!ExFreePool
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec 24 17:28:32.718 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122412-13119-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 1:51:08.448
    Probably caused by :hardware ( dxgmms1!VidSchiSendToExecutionQueue+ea )
    BugCheck 1000007E, {ffffffffc0000005, fffff88005a05e52, fffff8801c5697c8, fffff8801c569000}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88005a05e52, The address that the exception occurred at
    Arg3: fffff8801c5697c8, Exception Record Address
    Arg4: fffff8801c569000, Context Record Address
    PROCESS_NAME: System
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: IP_MISALIGNED_dxgmms1.sys
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec 23 23:30:02.454 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122312-15178-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 5:01:51.183
    Probably caused by :memory_corruption ( nt!MmUnmapViewInSystemCache+3e0 )
    BugCheck 3B, {c000001d, fffff803d1b57a6f, fffff8802e4ef6f0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c000001d, Exception code that caused the bugcheck
    Arg2: fffff803d1b57a6f, Address of the instruction which caused the bugcheck
    Arg3: fffff8802e4ef6f0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: MsMpEng.exe
    FAILURE_BUCKET_ID: 0x3B_nt!MmUnmapViewInSystemCache
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec 23 17:40:29.942 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122312-18564-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:4 days 8:48:44.672
    Probably caused by :ntkrnlmp.exe ( nt!_report_gsfailure+25 )
    BugCheck F7, {fffff8800ec7d787, 7f69fadd3eb3, ffff80960522c14c, 0}
    BugCheck Info: DRIVER_OVERRAN_STACK_BUFFER (f7)
    Arguments: 
    Arg1: fffff8800ec7d787, Actual security check cookie from the stack
    Arg2: 00007f69fadd3eb3, Expected security check cookie
    Arg3: ffff80960522c14c, Complement of the expected security check cookie
    Arg4: 0000000000000000, zero
    BUGCHECK_STR:  0xF7
    DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
    PROCESS_NAME: CCC.exe
    FAILURE_BUCKET_ID: 0xF7_MISSING_GSFRAME_nt!_report_gsfailure
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec 17 22:57:35.616 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121712-13306-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:1 days 3:46:53.345
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :hardware ( atikmdag+10b611 )
    BugCheck 1000007E, {ffffffffc0000005, fffff8800b90b611, fffff8800a22f0a8, fffff8800a22e8e0}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8800b90b611, The address that the exception occurred at
    Arg3: fffff8800a22f0a8, Exception Record Address
    Arg4: fffff8800a22e8e0, Context Record Address
    PROCESS_NAME: System
    BUGCHECK_STR:  AV
    FAILURE_BUCKET_ID: IP_MISALIGNED_atikmdag.sys
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Dec  1 03:43:30.575 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120112-14913-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:3 days 20:28:05.304
    Probably caused by :hardware ( nt!NtClose+32e )
    BugCheck 50, {ffffffff80000000, 1, fffff801ff6b772e, 2}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
    Arguments: 
    Arg1: ffffffff80000000, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff801ff6b772e, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: uTorrent.exe
    FAILURE_BUCKET_ID: IP_MISALIGNED
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Nov 27 04:14:47.465 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112712-13946-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 11:17:09.194
    Probably caused by :dxgkrnl.sys ( dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+59 )
    BugCheck 3B, {c0000005, fffff80275ed6322, fffff8801d295390, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80275ed6322, Address of the instruction which caused the bugcheck
    Arg3: fffff8801d295390, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: dwm.exe
    FAILURE_BUCKET_ID: 0x3B_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Mon Dec 24 20:07:43.327 2012 (UTC - 5:00)**************************
    RTCore64.sys                Tue Sep  6 08:24:50 2011 (4E661112)
    AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)
    vmci.sys                    Mon Apr 30 21:14:27 2012 (4F9F38F3)
    vsock.sys                   Mon Apr 30 21:15:24 2012 (4F9F392C)
    Rt630x64.sys                Tue Jun 12 09:37:53 2012 (4FD74631)
    amd_sata.sys                Tue Jun 12 10:24:37 2012 (4FD75125)
    amd_xata.sys                Tue Jun 12 10:24:45 2012 (4FD7512D)
    VMNET.SYS                   Sun Jul  8 03:58:34 2012 (4FF93DAA)
    vmnetadapter.sys            Sun Jul  8 03:58:35 2012 (4FF93DAB)
    vmnetbridge.sys             Sun Jul  8 03:59:19 2012 (4FF93DD7)
    hcmon.sys                   Wed Aug  1 20:10:29 2012 (5019C575)
    RTKVHD64.sys                Tue Aug  7 06:49:39 2012 (5020F2C3)
    vmnetuserif.sys             Wed Aug 15 16:31:54 2012 (502C073A)
    vmx86.sys                   Wed Aug 15 18:05:11 2012 (502C1D17)
    AtihdW86.sys                Tue Aug 21 22:26:37 2012 (5034435D)
    LEqdUsb.Sys                 Tue Sep 18 05:26:44 2012 (50583E54)
    LHidEqd.Sys                 Tue Sep 18 05:26:46 2012 (50583E56)
    LHidFilt.Sys                Tue Sep 18 05:26:53 2012 (50583E5D)
    LMouFilt.Sys                Tue Sep 18 05:26:58 2012 (50583E62)
    atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
    atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
    HWiNFO64A.SYS               Wed Nov 14 06:15:59 2012 (50A37D6F)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec 17 22:57:35.616 2012 (UTC - 5:00)**************************
    atikmpag.sys                Sun Dec  2 02:13:21 2012 (50BAFF91)
    atikmdag.sys                Sun Dec  2 03:21:53 2012 (50BB0FA1)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Dec  1 03:43:30.575 2012 (UTC - 5:00)**************************
    usbfilter.sys               Tue Jun 19 07:07:40 2012 (4FE05D7C)
    xusb22.sys                  Wed Jul 25 22:26:57 2012 (5010AAF1)
    atikmpag.sys                Thu Nov 15 11:57:47 2012 (50A51F0B)
    atikmdag.sys                Thu Nov 15 12:59:33 2012 (50A52D85)
    
    http://www.carrona.org/drivers/driver.php?id=RTCore64.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=vmci.sys
    http://www.carrona.org/drivers/driver.php?id=vsock.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
    http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
    http://www.carrona.org/drivers/driver.php?id=hcmon.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
    http://www.carrona.org/drivers/driver.php?id=vmx86.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW86.sys
    http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    xusb22.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
      My System SpecsSystem Spec

  8. #28


    I followed usasma's instructions and uninstalled MSI afterburner, uninstalled all AMD stuff and installed the latest stable video driver (driver only method), and I have not had a BSOD until about 5 minutes ago and its another memory corruption one:
    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck A, {4, 2, 1, fffff802582fb9c0}
    
    
    Probably caused by : memory_corruption ( nt!MiAddPageToFlushMdl+140 )
    
    
    Followup: MachineOwner
    ---------
    
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000004, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff802582fb9c0, address which referenced memory
    
    
    Debugging Details:
    ------------------
    
    
    
    
    WRITE_ADDRESS:  0000000000000004 
    
    
    CURRENT_IRQL:  2
    
    
    FAULTING_IP: 
    nt!MiAddPageToFlushMdl+140
    fffff802`582fb9c0 413bd0          cmp     edx,r8d
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  AV
    
    
    PROCESS_NAME:  System
    
    
    TRAP_FRAME:  fffff8802fd325d0 -- (.trap 0xfffff8802fd325d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000015 rbx=0000000000000000 rcx=0000000009a3a190
    rdx=0000000000000016 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff802582fb9c0 rsp=fffff8802fd32760 rbp=fffffa80202f1690
     r8=0000000000000020  r9=0000000000000020 r10=0000000000000000
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    nt!MiAddPageToFlushMdl+0x140:
    fffff802`582fb9c0 413bd0          cmp     edx,r8d
    Resetting default scope
    
    
    LAST_CONTROL_TRANSFER:  from fffff80258281669 to fffff80258282340
    
    
    STACK_TEXT:  
    fffff880`2fd32488 fffff802`58281669 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`2fd32490 fffff802`5827fee0 : 00000000`00000001 00000003`368b38c0 fffff880`2fd32600 fffff880`2fd325d0 : nt!KiBugCheckDispatch+0x69
    fffff880`2fd325d0 fffff802`582fb9c0 : 00000000`00000020 fffffa80`13a68bf0 00000000`00000000 00000000`00000004 : nt!KiPageFault+0x260
    fffff880`2fd32760 fffff802`582f88bb : 00000003`368b38c0 fffffa80`202f1690 fffff8a0`11d7b0b8 00000000`00000004 : nt!MiAddPageToFlushMdl+0x140
    fffff880`2fd327a0 fffff802`582fb3a9 : fffff880`2fd32c30 00000000`00000000 00000000`00000000 00000000`00000001 : nt!MiFlushSectionInternal+0x3bb
    fffff880`2fd329b0 fffff802`582f96fb : 00000000`01f50b9f 00000000`01f50b00 00000000`00000000 fffffa80`11b91df0 : nt!MmFlushSection+0x205
    fffff880`2fd32a70 fffff802`582fc275 : fffffa80`0fb894f8 00000000`00000000 00000000`00000001 00000000`00000000 : nt!CcFlushCachePriv+0x3fb
    fffff880`2fd32b70 fffff802`582f3e0f : 00000000`00000000 00000000`00000000 00000000`00020000 fffff802`582b6d5b : nt!CcWriteBehind+0x225
    fffff880`2fd32bf0 fffff802`582ba511 : fffff802`5848b0c0 fffffa80`25140a00 fffffa80`0d043800 fffff802`5848b0c0 : nt!CcWorkerThread+0x233
    fffff880`2fd32cc0 fffff802`58229551 : 00000000`00000000 00000000`00000080 fffff802`582ba3d0 fffffa80`25140a00 : nt!ExpWorkerThread+0x142
    fffff880`2fd32d50 fffff802`58267dd6 : fffff880`01acf180 fffffa80`25140a00 fffffa80`2bb22200 fffffa80`0d0ce940 : nt!PspSystemThreadStartup+0x59
    fffff880`2fd32da0 00000000`00000000 : fffff880`2fd33000 fffff880`2fd2d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nt!MiAddPageToFlushMdl+140
    fffff802`582fb9c0 413bd0          cmp     edx,r8d
    
    
    SYMBOL_STACK_INDEX:  3
    
    
    SYMBOL_NAME:  nt!MiAddPageToFlushMdl+140
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50ab0e64
    
    
    IMAGE_NAME:  memory_corruption
    
    
    BUCKET_ID_FUNC_OFFSET:  140
    
    
    FAILURE_BUCKET_ID:  AV_nt!MiAddPageToFlushMdl
    
    
    BUCKET_ID:  AV_nt!MiAddPageToFlushMdl
    
    
    Followup: MachineOwner
    ---------
    Is there anything else I should try?
      My System SpecsSystem Spec

  9. #29


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Please zip up and upload the memory dumps so we can have a look at them (sometimes, with a bit of massaging, we can convince them to give up more info). They are located in C:\Windows\Minidump.

    As for what to try, please run Driver Verifier according to these instructions: Driver Verifier Settings
    The reason for this is that several of the tests in Driver Verifier will specifically check IRQL errors (which you are having)
      My System SpecsSystem Spec

  10. #30


    Attached are dumps. I will set up driver verifier when I get home from work.
      My System SpecsSystem Spec

Page 3 of 6 FirstFirst 12345 ... LastLast
Various BSODs in Past Two Days
Related Threads
I've been getting seemingly random BSODs on my Win8.1 box for months now. There are several different errors that show up, and most of them seem to point to the drivers. I have no idea which driver could be causing the issue though, as I've reinstalled the majority of them. A few I can remember:...
2x WHEA_UNCORRECTABLE_ERROR BSODs in 3 days in BSOD Crashes and Debugging
I suffered my first BSOD 2 days ago while playing Elite Dangerous. It was a WHEA_UNCORRECTABLE_ERROR with references to GenuineIntel, WIN8_DRIVER_FAULT, and the process was Elite Dangerous. I put it down to faulty code in the game somewhere, but just tonight, while browsing on Firefox, I...
Four different BSODs in two days in BSOD Crashes and Debugging
Hi, In the past two days my Dell laptop (Win8 OS) has crashed four times with different BSOD error messages. What I have attempted is to run my anti-malware software and to go back to a restore point, but it hasn't work so I'm worried it is a problem with the RAM. The errors shown are...
Solved BSODs over the last couple of days in BSOD Crashes and Debugging
Over the last couple of days I've been having random BSOD after a few hours of use or so. I've been unable to find anything that causes it to occur, it appears to just happen randomly. Thanks for any help!
Ended up getting 4 Acer All in One 23" touchscreens at work this past week. Getting them set up for a tradeshow. They are the Acer Aspire 5600U's. They were $999 from NewEgg for Core i3-3110m, 8gb ram, 1TB hard drive, Intel HD400 graphics, DVD burner, 23" 1080p 10 point touchscreen, Windows...
4 of them for work, and 1 which is a Christmas present. Gotta buy some pc's before somebody declares the pc dead.
Hi everyone! I just installed Windows 8 yesterday and after the initial "wow" factor I installed my graphics drivers and rebooted. Upon restart, I got past the welcome screen and logged in (no password error) and after the screen quickly goes blank as if it's about to log in, then it returns to...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook