Crashed playing Fallout 4


  1. Posts : 64
    Windows 10 Pro 64-bit
       #1

    Crashed playing Fallout 4


    Hello, new Skylake PC, crashed playing Fallout 4. PC restarted. Here is the minidump analysis:
    rash 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 10240 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 10240.16590.amd64fre.th1_st1.151104-1714
    Machine Name:
    Kernel base = 0xfffff802`0ac16000 PsLoadedModuleList = 0xfffff802`0af3b070
    Debug session time: Fri Nov 13 14:19:49.045 2015 (UTC - 5:00)
    System Uptime: 0 days 1:08:44.678
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************


    INVALID_MDL_RANGE (12e)
    A driver has called the IoBuildPartialMdl() function and passed it an MDL
    to map part of a source MDL, but the virtual address range specified is
    outside the range in the source MDL. This is a driver bug. The source
    and target MDLs, as well as the address range length to be mapped are the
    arguments to the IoBuildPartialMdl() function, i.e.;
    IoBuildPartialMdl(
    IN PMDL SourceMdl,
    IN OUT PMDL TargetMdl,
    IN PVOID VirtualAddress,
    IN ULONG Length
    )
    Arguments:
    Arg1: ffffe00145c1f220
    Arg2: ffffd000fffd3030
    Arg3: 0000000000001001
    Arg4: 00000000000001ff


    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: 0x12E


    PROCESS_NAME: System


    CURRENT_IRQL: 2


    LAST_CONTROL_TRANSFER: from fffff8020adbf278 to fffff8020ad654d0


    STACK_TEXT:
    ffffd000`fffd2f88 fffff802`0adbf278 : 00000000`0000012e ffffe001`45c1f220 ffffd000`fffd3030 00000000`00001001 : nt!KeBugCheckEx
    ffffd000`fffd2f90 fffff801`8b22fd03 : 00000000`00001200 ffffe001`584a2128 00000000`00000000 ffffe001`4cf3010a : nt! ?? ::FNODOBFM::`string'+0x4b178
    ffffd000`fffd2fd0 fffff802`0ac6299d : ffffe001`45db1010 ffffe001`471e9040 ffffe001`45db11bb ffffe001`45db1010 : NTFS!NtfsMasterIrpAsyncCompletionRoutine+0x2f3
    ffffd000`fffd3140 fffff801`8bb52f59 : ffffe001`45c27010 00000000`003bb901 ffffe001`46ba6010 00000000`00000000 : nt!IopfCompleteRequest+0x20d
    ffffd000`fffd3200 fffff802`0ac6299d : ffffe001`561f74cb 00000000`00000009 00000000`00000000 ffffe001`4d9e8848 : CLASSPNP!TransferPktComplete+0x4a9
    ffffd000`fffd3400 fffff801`8ada2ec3 : ffffd000`fffcd000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x20d
    ffffd000`fffd34c0 fffff801`8ada2902 : 00000000`00000000 ffffe001`46bfe1b0 ffffd000`fffd3690 00000000`003bb94f : storport!RaidCompleteRequestEx+0x53
    ffffd000`fffd3590 fffff801`8adc4d6f : fffff802`0af30400 ffffd000`fa1d1010 ffffe001`46bcc1a0 00000000`00000000 : storport!RaidUnitCompleteRequest+0x482
    ffffd000`fffd3720 fffff802`0ac66e65 : ffffd000`fffaaf00 00000000`003bb94f 00000000`00000000 ffffd000`fffd3a30 : storport!RaidpAdapterRedirectDpcRoutine+0xaf
    ffffd000`fffd37c0 fffff802`0ac66540 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x275
    ffffd000`fffd3910 fffff802`0ad6822a : ffffd000`fffa8180 ffffd000`fffa8180 ffffd000`fffb4cc0 ffffe001`5828a080 : nt!KiRetireDpcList+0xe0
    ffffd000`fffd3b60 00000000`00000000 : ffffd000`fffd4000 ffffd000`fffcd000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a




    STACK_COMMAND: kb


    FOLLOWUP_IP:
    CLASSPNP!TransferPktComplete+4a9
    fffff801`8bb52f59 4183ff02 cmp r15d,2


    SYMBOL_STACK_INDEX: 4


    SYMBOL_NAME: CLASSPNP!TransferPktComplete+4a9


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: CLASSPNP


    IMAGE_NAME: CLASSPNP.SYS


    DEBUG_FLR_IMAGE_TIMESTAMP: 559f383f


    FAILURE_BUCKET_ID: X64_0x12E_CLASSPNP!TransferPktComplete+4a9


    BUCKET_ID: X64_0x12E_CLASSPNP!TransferPktComplete+4a9


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

    Can anyone decipher this for me please?
      My Computer


  2. Posts : 64
    Windows 10 Pro 64-bit
    Thread Starter
       #2

    Second restart, just while on desktop:

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage | OSR)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 10240 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 10240.16590.amd64fre.th1_st1.151104-1714
    Machine Name:
    Kernel base = 0xfffff800`c548b000 PsLoadedModuleList = 0xfffff800`c57b0070
    Debug session time: Fri Nov 13 16:25:06.183 2015 (UTC - 5:00)
    System Uptime: 0 days 1:37:01.816
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_SCHEDULER_INTERNAL_ERROR (119)
    The video scheduler has detected that fatal violation has occurred. This resulted
    in a condition that video scheduler can no longer progress. Any other values after
    parameter 1 must be individually examined according to the subtype.
    Arguments:
    Arg1: 000000000000000d, The subtype of the bugcheck:
    Arg2: 000000000000000d
    Arg3: ffffe001699021a0
    Arg4: 0000000008262000

    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: 0x119

    PROCESS_NAME: System

    CURRENT_IRQL: 5

    LAST_CONTROL_TRANSFER: from fffff80032253c3d to fffff800c55da4d0

    STACK_TEXT:
    fffff800`c75e6858 fffff800`32253c3d : 00000000`00000119 00000000`0000000d 00000000`0000000d ffffe001`699021a0 : nt!KeBugCheckEx
    fffff800`c75e6860 fffff800`34f6bc2f : ffffe001`6bf5d010 ffffe001`6bf56000 00000000`00000000 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xcd
    fffff800`c75e68a0 fffff800`34f642ae : ffffe001`6bf5d010 ffffe001`6bf5d010 fffff800`c75e6a19 fffff800`c75e6aa0 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x7963
    fffff800`c75e68e0 fffff800`322796c4 : ffffe001`6a306040 00000000`00000000 fffff800`341c3584 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0x7e
    fffff800`c75e6910 fffff800`342173bf : ffffe001`6a306040 fffff800`c75e6a19 fffff800`c75e6aa0 ffffe001`69efb000 : dxgkrnl!DxgNotifyInterruptCB+0x74
    fffff800`c75e6940 ffffe001`6a306040 : fffff800`c75e6a19 fffff800`c75e6aa0 ffffe001`69efb000 fffff800`3421734f : nvlddmkm+0xe73bf
    fffff800`c75e6948 fffff800`c75e6a19 : fffff800`c75e6aa0 ffffe001`69efb000 fffff800`3421734f ffffe001`69efb000 : 0xffffe001`6a306040
    fffff800`c75e6950 fffff800`c75e6aa0 : ffffe001`69efb000 fffff800`3421734f ffffe001`69efb000 00000000`00000000 : 0xfffff800`c75e6a19
    fffff800`c75e6958 ffffe001`69efb000 : fffff800`3421734f ffffe001`69efb000 00000000`00000000 00000000`00000000 : 0xfffff800`c75e6aa0
    fffff800`c75e6960 fffff800`3421734f : ffffe001`69efb000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`69efb000
    fffff800`c75e6968 ffffe001`69efb000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xe734f
    fffff800`c75e6970 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe001`6a306040 : 0xffffe001`69efb000


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    dxgmms2!VidSchDdiNotifyInterruptWorker+7963
    fffff800`34f6bc2f cc int 3

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: dxgmms2!VidSchDdiNotifyInterruptWorker+7963

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: dxgmms2

    IMAGE_NAME: dxgmms2.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 55fa55af

    FAILURE_BUCKET_ID: X64_0x119_dxgmms2!VidSchDdiNotifyInterruptWorker+7963

    BUCKET_ID: X64_0x119_dxgmms2!VidSchDdiNotifyInterruptWorker+7963

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


    Is this a DX12 thing?
      My Computer


  3. Posts : 64
    Windows 10 Pro 64-bit
    Thread Starter
       #3

    Hello, can anyone help me with this please?
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #4
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:41.
Find Us




Windows 10 Forums