locked
Windows 7 keeps getting blue screens - The bugcheck was: 0x0000000a (0x8304ad78, 0x000000ff, 0x00000000, 0x8304ad78). RRS feed

  • Question

  • Hello all,

    My windows 7 PC keeps crashing with various BSOD's, the latest one was "

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x8304ad78, 0x000000ff, 0x00000000, 0x8304ad78). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072918-9625-01.

    "

    I have attached the DMP file below, I cant seem to figure out what is causing this issue.

    https://expirebox.com/download/ca3922ce8eed998aae47af900224bc45.html

    Thank you so much,

    John D

    Sunday, July 29, 2018 11:40 AM

All replies

  • Hello all,

    My windows 7 PC keeps crashing with various BSOD's, the latest one was "

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x8304ad78, 0x000000ff, 0x00000000, 0x8304ad78). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072918-9625-01.

    "

    I have attached the DMP files below, I cant seem to figure out what is causing this issue.

    Thank you so much,

    John D

    https://expirebox.com/download/74c457c04aae4d69a55db44da3aa051a.html

    • Merged by Joy-Qiao Monday, July 30, 2018 2:21 AM duplicate
    Sunday, July 29, 2018 12:22 PM
  • Here is the Bugcheck Analysis.

    The cause is shown as ntkrnlmp.exe.

    Can you tell what is ECDIS.exe? Is it a program in your computer. You could check it.

    *******************************************************************************
    *                                                                             *
    *                        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: 8304ad78, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000000, 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: 8304ad78, address which referenced memory

    Debugging Details:
    ------------------


    KEY_VALUES_STRING: 1


    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  7601.24168.x86fre.win7sp1_ldr.180608-0600

    SYSTEM_MANUFACTURER:  QEMU

    SYSTEM_PRODUCT_NAME:  Standard PC (i440FX + PIIX, 1996)

    SYSTEM_VERSION:  pc-i440fx-2.8

    BIOS_VENDOR:  SeaBIOS

    BIOS_VERSION:  1.10.2-1

    BIOS_DATE:  04/01/2014

    DUMP_TYPE:  2

    BUGCHECK_P1: ffffffff8304ad78

    BUGCHECK_P2: ff

    BUGCHECK_P3: 0

    BUGCHECK_P4: ffffffff8304ad78

    READ_ADDRESS: GetPointerFromAddress: unable to read from 83174830
    Unable to get MmSystemRangeStart
    GetUlongPtrFromAddress: unable to read from 831741f4
    GetUlongPtrFromAddress: unable to read from 831746cc
    Unable to get NonPagedPoolStart
    Unable to get PagedPoolStart
     8304ad78

    CURRENT_IRQL:  0

    FAULTING_IP:
    nt!KiTrap0E+0
    8304ad78 66c74424020000  mov     word ptr [esp+2],0

    IP_IN_PAGED_CODE:
    nt!KiTrap0E+0
    8304ad78 66c74424020000  mov     word ptr [esp+2],0

    CPU_COUNT: 2

    CPU_MHZ: bb7

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3c

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1'00000000 (cache) 1'00000000 (init)

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  ECDIS.exe

    ANALYSIS_SESSION_HOST:  DESKTOP-3OA0PAT

    ANALYSIS_SESSION_TIME:  07-29-2018 20:21:54.0858

    ANALYSIS_VERSION: 10.0.17134.12 amd64fre

    TRAP_FRAME:  80f9eb94 -- (.trap 0xffffffff80f9eb94)
    ErrCode = 00000000
    eax=00000000 ebx=00000000 ecx=1f60fde0 edx=77f06bb4 esi=13378714 edi=00000000
    eip=8304ad78 esp=80f9ec08 ebp=1f60fe44 iopl=0         nv up di pl nz ac pe cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=003b  gs=0000             efl=00010017
    nt!KiTrap0E:
    8304ad78 66c74424020000  mov     word ptr [esp+2],0       ss:0010:80f9ec0a=0000
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 8304ad78 to 8304b0d3

    FAILED_INSTRUCTION_ADDRESS:
    nt!KiTrap0E+0
    8304ad78 66c74424020000  mov     word ptr [esp+2],0

    STACK_TEXT: 
    80f9eb94 8304ad78 badb0d00 77f06bb4 1f60fd01 nt!KiTrap0E+0x35b
    1f60fe44 1f60fed4 00000000 00000000 005c5048 nt!KiTrap0E
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    005c514e 00000000 00000000 00000000 00000000 0x1f60fed4


    THREAD_SHA1_HASH_MOD_FUNC:  0170b88b7dca15c30e00441f580116429f62a8b9

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ada933a9a276772da07da6a496afa74cfee11069

    THREAD_SHA1_HASH_MOD:  6997106dce080e0f247cffc7d244723501c73d61

    FOLLOWUP_IP:
    nt!KiTrap0E+0
    8304ad78 66c74424020000  mov     word ptr [esp+2],0

    FAULT_INSTR_CODE:  2444c766

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!KiTrap0E+0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  5b1a9f18

    IMAGE_VERSION:  6.1.7601.24168

    STACK_COMMAND:  .thread ; .cxr ; kb

    FAILURE_BUCKET_ID:  0xA_CODE_AV_PAGED_IP_nt!KiTrap0E+0

    BUCKET_ID:  0xA_CODE_AV_PAGED_IP_nt!KiTrap0E+0

    PRIMARY_PROBLEM_CLASS:  0xA_CODE_AV_PAGED_IP_nt!KiTrap0E+0

    TARGET_TIME:  2018-07-28T14:54:31.000Z

    OSBUILD:  7601

    OSSERVICEPACK:  1000

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  1

    OSPLATFORM_TYPE:  x86

    OSNAME:  Windows 7

    OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

    OS_LOCALE: 

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2018-06-08 18:22:00

    BUILDDATESTAMP_STR:  180608-0600

    BUILDLAB_STR:  win7sp1_ldr

    BUILDOSVER_STR:  6.1.7601.24168.x86fre.win7sp1_ldr.180608-0600

    ANALYSIS_SESSION_ELAPSED_TIME:  5b8

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0xa_code_av_paged_ip_nt!kitrap0e+0

    FAILURE_ID_HASH:  {74c28ec0-2ec3-3afd-0954-1ea826e2f260}

    Followup:     MachineOwner
    ---------

    1: kd> .trap 0xffffffff80f9eb94
    ErrCode = 00000000
    eax=00000000 ebx=00000000 ecx=1f60fde0 edx=77f06bb4 esi=13378714 edi=00000000
    eip=8304ad78 esp=80f9ec08 ebp=1f60fe44 iopl=0         nv up di pl nz ac pe cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=003b  gs=0000             efl=00010017
    nt!KiTrap0E:
    8304ad78 66c74424020000  mov     word ptr [esp+2],0       ss:0010:80f9ec0a=0000

    Sunday, July 29, 2018 5:37 PM
  • Hi John, 

    Please check if the issue occur in Clean Boot environment and Safe mode environment to narrow down the issue. 

    As ntkrnlmp.exe is a Windows build-in component which was called kernal image, it rarely cause BSOD in system. If it is the criminal, the issue should occur again in safe mode and clean boot environment. 

    As most BSOD issue is caused by third party software or driver, so please uninstall third party software " ECDIS.exe" to check again.

    By the way, as your BIOS driver have not update since 2014, please go to manufacturer website and download the latest BIOS driver. 

    Bests,


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 30, 2018 2:18 AM