Windows 10: Unknown_Image minidump

Discus and support Unknown_Image minidump in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, My PC is crashing allot and i heard that you can verify the problem using minidump, so i wan't to ask what my problem is! Minidump thru... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Koen van den Bank, Aug 5, 2018.

  1. KOEN VAN DEN BANK
    Koen van den Bank Win User

    Unknown_Image minidump


    Hi,


    My PC is crashing allot and i heard that you can verify the problem using minidump, so i wan't to ask what my problem is!


    Minidump thru Osronline.


    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 17134 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0xfffff800`0c49e000 PsLoadedModuleList = 0xfffff800`0c8581f0
    Debug session time: Sun Aug 5 16:18:43.231 2018 (UTC - 4:00)
    System Uptime: 0 days 0:24:59.934
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
    An attempt was made to write to readonly memory. The guilty driver is on the
    stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: ffff9607a154d478, Virtual address for the attempted write.
    Arg2: 810000000b2ce121, PTE contents.
    Arg3: ffff8a0b77eeb5f0, (reserved)
    Arg4: 000000000000000b, (reserved)

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0xBE

    PROCESS_NAME: explorer.exe

    CURRENT_IRQL: 2

    BAD_PAGES_DETECTED: a13e

    TRAP_FRAME: ffff8a0b77eeb5f0 -- (.trap 0xffff8a0b77eeb5f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffff9607a1d49890 rbx=0000000000000000 rcx=0000000000000000
    rdx=ffff9607a1d49890 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000c9ff8e0 rsp=ffff8a0b77eeb780 rbp=ffff8a0b77eeb839
    r8=0000000000000000 r9=0000000000000001 r10=fffff8000c8714e0
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    nt!PiDmEnumObjectsWithCallback+0x168:
    fffff800`0c9ff8e0 f0ff4308 lock inc dword ptr [rbx+8] ds:00000000`00000008=????????
    Resetting default scope

    LOCK_ADDRESS: fffff8000c8724e0 -- (!locks fffff8000c8724e0)

    Resource @ nt!PiEngineLock (0xfffff8000c8724e0) Available

    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

    1 total locks

    PNP_TRIAGE:
    Lock address : 0xfffff8000c8724e0
    Thread Count : 0
    Thread address: 0x0000000000000000
    Thread wait : 0x0

    LAST_CONTROL_TRANSFER: from fffff8000c6885c7 to fffff8000c636430

    STACK_TEXT:
    ffff8a0b`77eeb338 fffff800`0c6885c7 : 00000000`000000be ffff9607`a154d478 81000000`0b2ce121 ffff8a0b`77eeb5f0 : nt!KeBugCheckEx
    ffff8a0b`77eeb340 fffff800`0c54b408 : 00000000`00000000 00000000`00000003 00000000`00000000 ffff8844`22110880 : nt!MiSystemFault+0x1416e7
    ffff8a0b`77eeb480 fffff800`0c643ada : ffffd103`00000000 00000000`00000000 fffff800`0c795140 ffffd103`b31b0b60 : nt!MmAccessFault+0x1f8
    ffff8a0b`77eeb5f0 fffff800`0c9ff8e0 : ffff9607`a1d5d230 ffff8a0b`77eeb839 fffff800`0c871480 00000000`00000000 : nt!KiPageFault+0x31a
    ffff8a0b`77eeb780 fffff800`0ca05034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`c0000001 : nt!PiDmEnumObjectsWithCallback+0x168
    ffff8a0b`77eeb8a0 fffff800`0ca0332d : 00000000`00000000 ffffd103`00000000 00000000`00000016 00000000`00000000 : nt!PiDqObjectManagerEnumerateAndRegisterQuery+0x348
    ffff8a0b`77eeb9e0 fffff800`0ca5310a : ffffd103`b31b0b60 00000000`00000000 00000000`00000000 ffff8a0b`77eebb20 : nt!PiDqQuerySerializeActionQueue+0xa1
    ffff8a0b`77eeba70 fffff800`0ca015ea : ffffd103`b6f803a0 fffff800`0c52d501 ffffd103`00000000 ffffd103`b6085e00 : nt!PiDqIrpQueryGetResult+0x14e
    ffff8a0b`77eebb10 fffff800`0ca00266 : ffffd103`b6f803a0 ffffd103`b0971e40 fffff800`0c799940 00000000`00002000 : nt!PiDqDispatch+0x1ca
    ffff8a0b`77eebb50 fffff800`0c5221a9 : ffffd103`b6f803a0 ffffd103`b7ca3860 00000000`00000000 00000000`20206f49 : nt!PiDaDispatch+0x46
    ffff8a0b`77eebb80 fffff800`0c9952eb : ffffd103`b6f803a0 00000000`00000000 ffffd103`b6f803a0 00000000`00000000 : nt!IofCallDriver+0x59
    ffff8a0b`77eebbc0 fffff800`0c9a122f : ffffd103`00000000 ffffd103`b7ca38b0 00000000`00000000 ffff8a0b`77eec001 : nt!IopSynchronousServiceTail+0x1ab
    ffff8a0b`77eebc70 fffff800`0c9a19d6 : ffff87ec`25a7908f 00000000`00000000 00000000`00000000 00000000`1aaacf88 : nt!IopXxxControlFile+0x66f
    ffff8a0b`77eebda0 fffff806`f18ae0f8 : 00000000`00000002 00000000`000002f8 00000000`00000088 00000000`82ac8004 : nt!NtDeviceIoControlFile+0x56
    ffff8a0b`77eebe10 00000000`00000002 : 00000000`000002f8 00000000`00000088 00000000`82ac8004 00000000`1aaacf88 : aswSnx+0x2e0f8
    ffff8a0b`77eebe18 00000000`000002f8 : 00000000`00000088 00000000`82ac8004 00000000`1aaacf88 fffff806`00470007 : 0x2
    ffff8a0b`77eebe20 00000000`00000088 : 00000000`82ac8004 00000000`1aaacf88 fffff806`00470007 00000000`00000000 : 0x2f8
    ffff8a0b`77eebe28 00000000`82ac8004 : 00000000`1aaacf88 fffff806`00470007 00000000`00000000 00000000`00000000 : 0x88
    ffff8a0b`77eebe30 00000000`1aaacf88 : fffff806`00470007 00000000`00000000 00000000`00000000 00000000`1f4fd7f0 : 0x82ac8004
    ffff8a0b`77eebe38 fffff806`00470007 : 00000000`00000000 00000000`00000000 00000000`1f4fd7f0 00000000`00001000 : 0x1aaacf88
    ffff8a0b`77eebe40 00000000`00000000 : 00000000`00000000 00000000`1f4fd7f0 00000000`00001000 00000000`00000000 : 0xfffff806`00470007


    STACK_COMMAND: kb

    SYMBOL_NAME: PAGE_NOT_ZERO

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    BUCKET_ID: PAGE_NOT_ZERO

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

    *** Memory manager detected 41278 instance(s) of page corruption, target is likely to have memory corruption.

    :)
     
    Koen van den Bank, Aug 5, 2018
    #1
  2. DIGITALERR0R
    digitalerr0r Win User

    MiniDumps

    Can someone please execute these minidumps and post back the information i can't get the symbols to work on vista. ( the minidumps are from windows xp service pack 2)

    Thanks
     
    digitalerr0r, Aug 5, 2018
    #2
  3. CALLEGRAFI
    callegrafi Win User
    W10 1703 - BSoD - Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Hello there!

    We are seeing quite a lot of bluescreens on our EliteBook 840 G3 that use W10 1703.

    The error is:

    Probably caused by :
    Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    I would be very happy if someone could point us to whats causing it! Unknown_Image minidump :)

    I have uploaded a minidump here: Delat

    Thanks in advance,

    Carl
     
    callegrafi, Aug 5, 2018
    #3
  4. OLORECKLESSOLO
    oloRECKLESSolo Win User

    Unknown_Image minidump

    BSoD - IRQL not less or equal - minidump

    • Acer V7-482PQ
    • a bunch (listed above)
    • Windows Build 17040.rs_prerelease.171110-1506
    • updated the
      minidump       link
    I'll check out the upgrade link. Thanks for the reply.
     
    oloRECKLESSolo, Aug 5, 2018
    #4
Thema:

Unknown_Image minidump

Loading...

  1. Unknown_Image minidump - Similar Threads - Unknown_Image minidump

  2. BSOD Watchdog violation,finally managed to get minidump file

    in Windows 10 Gaming
    BSOD Watchdog violation,finally managed to get minidump file: Hello,my pc is getting BSOD pretty often,never had a minidump file to analyze,finally today my pc managed to create a dmp filei do not understand what is causing my blue screen,please help me here are the results : For analysis of this file, run !analyze -v nt!KeBugCheckEx:...

  3. BSOD Watchdog violation,finally managed to get minidump file

    in Windows 10 Software and Apps
    BSOD Watchdog violation,finally managed to get minidump file: Hello,my pc is getting BSOD pretty often,never had a minidump file to analyze,finally today my pc managed to create a dmp filei do not understand what is causing my blue screen,please help me here are the results : For analysis of this file, run !analyze -v nt!KeBugCheckEx:...

  4. BSOD Watchdog violation,finally managed to get minidump file

    in Windows 10 BSOD Crashes and Debugging
    BSOD Watchdog violation,finally managed to get minidump file: Hello,my pc is getting BSOD pretty often,never had a minidump file to analyze,finally today my pc managed to create a dmp filei do not understand what is causing my blue screen,please help me here are the results : For analysis of this file, run !analyze -v nt!KeBugCheckEx:...

  5. Blue screen after running any game. Minidump says memory issues

    in Windows 10 Gaming
    Blue screen after running any game. Minidump says memory issues: This is a repost of the original posted months ago as I haven't gotten any responses. So this is a rather complicated question as I've been working on this on/off for months. I will try to simplify it but I have already tried multiple repair methods. I am aware that at this...

  6. Blue screen after running any game. Minidump says memory issues

    in Windows 10 Software and Apps
    Blue screen after running any game. Minidump says memory issues: This is a repost of the original posted months ago as I haven't gotten any responses. So this is a rather complicated question as I've been working on this on/off for months. I will try to simplify it but I have already tried multiple repair methods. I am aware that at this...

  7. Blue screen after running any game. Minidump says memory issues

    in Windows 10 BSOD Crashes and Debugging
    Blue screen after running any game. Minidump says memory issues: This is a repost of the original posted months ago as I haven't gotten any responses. So this is a rather complicated question as I've been working on this on/off for months. I will try to simplify it but I have already tried multiple repair methods. I am aware that at this...

  8. How to understand minidump files?

    in Windows 10 Gaming
    How to understand minidump files?: I am trying to trace the origins of the crash for computers that get the BSOD, and I have the minidump files that I read through BlueScreenView, but I can't interpret the messages and am struggling to find research on it. I can tell that people are able to figure out exactly...

  9. How to understand minidump files?

    in Windows 10 Software and Apps
    How to understand minidump files?: I am trying to trace the origins of the crash for computers that get the BSOD, and I have the minidump files that I read through BlueScreenView, but I can't interpret the messages and am struggling to find research on it. I can tell that people are able to figure out exactly...

  10. Multiple BSOD - "Probably Caused by:" memory_corruption / Unknown_Image / ntkrnlmp.exe -...

    in Windows 10 BSOD Crashes and Debugging
    Multiple BSOD - "Probably Caused by:" memory_corruption / Unknown_Image / ntkrnlmp.exe -...: Hello, I've recently started getting random BSOD on my Windows 10 machine. Only one has happened while light web browsing and the others have happened while the computer is idle and/or locked. The "Probably cause by" reason has been memory_corruption a couple times,...

Users found this page by searching for:

  1. unknown_image

    ,

  2. unknown_image crash

    ,

  3. pc unknown image

    ,
  4. driver probably at fault is unknown image,
  5. dump analysis returned module name and image name as unkonw,
  6. Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ),
  7. memoy dump probably caused by unknown_image,
  8. BSOD memory.dmp Unknown_Image ( ANALYSIS_INCONCLUSIVE ),
  9. Windows 10 unkown image,
  10. Unknown_Image ( ANALYSIS_INCONCLUSIVE),
  11. unknown_image bsod,
  12. Unknown_Image blue screen,
  13. minidump image unknown,
  14. image_name: unknown_image,
  15. unknown_image minidump