Dump files to read for me

Page 1 of 2 12 LastLast

  1. Posts : 12
    Windows 7 Ultimate x64
       #1

    Dump files to read for me


    Hi guys,im getting alot of BSOD everyday and i want someone to read the dump files.i have attached in rar the latest dmp files.

    I would really appreciate if someone helps me. Cheers
      My Computer


  2. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #2

    Dump Files is (.zip) Format...
      My Computer


  3. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #3

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000000, 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: fffff80002c83cdc, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS:  0000000000000000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeWaitForSingleObject+17c
    fffff800`02c83cdc 4c8938          mov     qword ptr [rax],r15
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  ekrn.exe
    
    TRAP_FRAME:  fffff8800b154600 -- (.trap 0xfffff8800b154600)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a0002e6ac8
    rdx=0000000000000028 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002c83cdc rsp=fffff8800b154790 rbp=0000000000000000
     r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
    r11=fffff880031d5180 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    nt!KeWaitForSingleObject+0x17c:
    fffff800`02c83cdc 4c8938          mov     qword ptr [rax],r15 ds:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c79ca9 to fffff80002c7a740
    
    STACK_TEXT:  
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KeWaitForSingleObject+17c
    fffff800`02c83cdc 4c8938          mov     qword ptr [rax],r15
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KeWaitForSingleObject+17c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!KeWaitForSingleObject+17c
    
    BUCKET_ID:  X64_0xA_nt!KeWaitForSingleObject+17c
    
    Followup: MachineOwner
    ---------
    Possible Cause - ntkrnlmp.exe - System process for Windows

    Please scan with your AV and Run a System File Checker Scan

    See SFC /SCANNOW Command - System File Checker For More Information

    Please Upload any other BSOD's you receive for a BSOD cannot give a Certain answer as to what is the problem and you may experience more BSOD's

    The More we analyse the Better chance we get to finding the solution to your Problem

    Many Thanks,
    Josh
      My Computer


  4. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #4

    Hey Josh thanks for helping.

    I did a sfc scan and it showed ok.However after i did a full scan with ESET Smart Security i received another blue screen.I think its called the error Cache manager something.
    Is there a chance i have a faulty ram?Its brand new ram

    You can find the dump file attached.

    I am waiting for your reply.

    Thnx
      My Computer


  5. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Josh,

    I did download the utility Blue screen viewer and i see that most of the BSOD are from the [IMG]file:///C:/Users/Jenkenis/AppData/Local/Temp/moz-screenshot.png[/IMG]ntoskrnl.exe.

    What is ntoskrnl.exe? See the picture attached

    Please note that all the BSOD started when i upgraded my Asus Maximus Extreme(updated latest firmware) with the following components:

    SSD drive
    USB3/SATA3 Pci express card
    8gb(2gb each of ram) (OCZ 1600MHZ)
      My Computer


  6. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #6

    It is a Kernal file and is part of Windows OS - You said you added more Ram please remove the RAM and See if it stops the BSOD I will Debug the Recent Files
      My Computer


  7. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #7

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CACHE_MANAGER (34)
        See the comment for FAT_FILE_SYSTEM (0x23)
    Arguments:
    Arg1: 0000000000050830
    Arg2: fffff8800337e808
    Arg3: fffff8800337e070
    Arg4: fffff80002f7edcf
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff8800337e808 -- (.exr 0xfffff8800337e808)
    ExceptionAddress: fffff80002f7edcf (nt!MiSectionDelete+0x000000000000003f)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff8800337e070 -- (.cxr 0xfffff8800337e070)
    rax=fffff8a00ec72110 rbx=6d536d4d00010311 rcx=fffff8a00f5f32a0
    rdx=00000000746c6644 rsi=0000000000000000 rdi=fffff8a00f5f32a0
    rip=fffff80002f7edcf rsp=fffff8800337ea40 rbp=0000000000000002
     r8=fffffa8010e70750  r9=fffff8800337e8c8 r10=fffffa8007c0b7c0
    r11=fffff8800337eab0 r12=fffff80002ec7800 r13=0000000000000000
    r14=00000000ffffffff r15=0000000000000001
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nt!MiSectionDelete+0x3f:
    fffff800`02f7edcf 0fba633814      bt      dword ptr [rbx+38h],14h ds:002b:6d536d4d`00010349=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    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_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS:  ffffffffffffffff 
    
    FOLLOWUP_IP: 
    nt!MiSectionDelete+3f
    fffff800`02f7edcf 0fba633814      bt      dword ptr [rbx+38h],14h
    
    FAULTING_IP: 
    nt!MiSectionDelete+3f
    fffff800`02f7edcf 0fba633814      bt      dword ptr [rbx+38h],14h
    
    BUGCHECK_STR:  0x34
    
    LAST_CONTROL_TRANSFER:  from fffff80002c928b4 to fffff80002f7edcf
    
    STACK_TEXT:  
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!MiSectionDelete+3f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    STACK_COMMAND:  .cxr 0xfffff8800337e070 ; kb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x34_nt!MiSectionDelete+3f
    
    BUCKET_ID:  X64_0x34_nt!MiSectionDelete+3f
    
    Followup: MachineOwner
    ---------
    This one did turn out to be Memory Corruption please Remove the recent Stick(s) of RAM
      My Computer


  8. Posts : 2,298
    Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
       #8

    For Reference of others who wish to Debug - Dump Files in (.zip) Format
      My Computer


  9. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Hi Josh,

    So basically should i test the new rams one by one without overclocking them?With default setting from the bios,my rams are read from 1600MHz to 1066MHz...
      My Computer


  10. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #10

    Hi Josh,

    New BSOD.Find attached.

    Error on dxgkrnl.sys and atikmpag.sys.

    After these BSOD,im using the PC with single ram of 2gb now.Lets see the results.
      My Computer


 
Page 1 of 2 12 LastLast

  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 23:48.
Find Us