locked
BSoD kernel 41 RRS feed

  • Question

  • hi i have built a new computer , i have the latest drivers on the computer (except the video card i have downgraded it one update down for less BSoD's )

    a added the mini dump so you please can tell me why i get all of those BSoD's

    <<< System Summary >>>
      > Mainboard : MSI P67A-GD80 (MS-7672)
      > Chipset : Intel Sandy Bridge
      > Processor : Intel Core i7 2600K @ 3400MHz
      > Physical Memory : 16384MB (4 x 4096 DDR3-SDRAM )
      > Video Card : ATI Radeon HD 4850 X2
      > Hard Disk : OCZ-VERTEX2 3.5 ATA Device (115GB)
      > Hard Disk : Seagate ST31500341AS ATA Device (1500GB)
      > Hard Disk : Seagate ST3500320AS ATA Device (500GB)
      > Hard Disk : Western Digital WD2001FASS-00U0B0 ATA Device (2000GB)
      > DVD-Rom Drive : HGLQFG B8XYFO1I
      > DVD-Rom Drive : HL-DT-ST DVDRAM GH22NS40
      > Monitor Type : MT276 - 27 inches
      > Network Card : Realtek Semiconductor RTL8168/8111 PCIe Gigabit Ethernet Adapter
      > Network Card : Realtek Semiconductor RTL8168/8111 PCIe Gigabit Ethernet Adapter
      > Operating System : Windows 7 Ultimate Professional Media Center 6.01.7600 (64-bit)
      > DirectX : Version 11.00
      > Windows Performance Index : 7.2 on 7.9
    The EventViewer log:

    - System
    - Provider
    [ Name] Microsoft-Windows-Kernel-Power
    [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
    EventID 41
    Version 2
    Level 1
    Task 63
    Opcode 0
    Keywords 0x8000000000000002
    - TimeCreated
    [ SystemTime] 2011-07-14T15:50:14.649607300Z
    EventRecordID 14246
    Correlation
    - Execution
    [ ProcessID] 4
    [ ThreadID] 8
    Channel System
    Computer Alexy-PC
    - Security
    [ UserID] S-1-5-18
    - EventData
    BugcheckCode 268435582
    BugcheckParameter1 0xffffffffc0000094
    BugcheckParameter2 0xfffff88005934a81
    BugcheckParameter3 0xfffff880110eaef8
    BugcheckParameter4 0xfffff880110ea760
    SleepInProgress false
    PowerButtonTimestamp 0

     

    the link to the minidump https://skydrive.live.com/?cid=4338d0547b0b81fe&sc=documents&uc=1&nl=1&id=4338D0547B0B81FE%21128#

    Friday, July 15, 2011 6:53 AM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: ffffffffc0000094, The exception code that was not handled
    Arg2: fffff88005934a81, The address that the exception occurred at
    Arg3: fffff880110eaef8, Exception Record Address
    Arg4: fffff880110ea760, Context Record Address
    Debugging Details:
    ------------------
    OVERLAPPED_MODULE: Address regions for 'WUDFRd' and 'usbaapl64.sy' overlap
    EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Division enti re par z ro.
    FAULTING_IP: 
    atikmdag+e2a81
    fffff880`05934a81 41f7f0          div     eax,r8d
    EXCEPTION_RECORD:  fffff880110eaef8 -- (.exr 0xfffff880110eaef8)
    ExceptionAddress: fffff88005934a81 (atikmdag+0x00000000000e2a81)
       ExceptionCode: c0000094 (Integer divide-by-zero)
      ExceptionFlags: 00000000
    NumberParameters: 0
    CONTEXT:  fffff880110ea760 -- (.cxr 0xfffff880110ea760)
    rax=0000000000614658 rbx=fffff880110eb180 rcx=0000000000614658
    rdx=0000000000000000 rsi=fffffa800f98d400 rdi=fffff88005852000
    rip=fffff88005934a81 rsp=fffff880110eb130 rbp=0000000000000026
     r8=0000000000000000  r9=0000000000007075 r10=fffff880110eb180
    r11=fffff88005de5320 r12=0000000000000000 r13=fffffa800f7c6a84
    r14=0000000000000001 r15=0000000000000001
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    atikmdag+0xe2a81:
    fffff880`05934a81 41f7f0          div     eax,r8d
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x7E
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Division enti re par z ro.
    LAST_CONTROL_TRANSFER:  from fffffa800fdd3474 to fffff88005934a81
    STACK_TEXT:  
    fffff880`110eb130 fffffa80`0fdd3474 : 00000000`00000000 fffff880`05cd60b8 fffff880`deadbeef fffff880`110eb210 : atikmdag+0xe2a81
    fffff880`110eb138 00000000`00000000 : fffff880`05cd60b8 fffff880`deadbeef fffff880`110eb210 fffff880`05933bdd : 0xfffffa80`0fdd3474
    FOLLOWUP_IP: 
    atikmdag+e2a81
    fffff880`05934a81 41f7f0          div     eax,r8d
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  atikmdag+e2a81
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: atikmdag
    IMAGE_NAME:  atikmdag.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dae3c99
    STACK_COMMAND:  .cxr 0xfffff880110ea760 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+e2a81
    BUCKET_ID:  X64_0x7E_atikmdag+e2a81
    Followup: MachineOwner
    ---------
    2: kd> lmvm atikmdag
    start             end                 module name
    fffff880`05852000 fffff880`06186000   atikmdag   (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Wed Apr 20 02:53:29 2011 (4DAE3C99)
        CheckSum:         008E91DD
        ImageSize:        00934000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    ___________________________________________________________________________________________________________________________________
    The BSOD was caused by atimdag.sys driver. The latest update was the 20 April 2011. Check if there is a new update. If yes, download and install it. If no, rollback the install of the new driver and report that to ATI Technical Support.

    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

    • Marked as answer by plumon Friday, July 15, 2011 7:54 AM
    Friday, July 15, 2011 7:20 AM