Windows 10: Crashed playing Fallout 4

Discus and support Crashed playing Fallout 4 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello, new Skylake PC, crashed playing Fallout 4. PC restarted. Here is the minidump analysis: rash Dump Analysis provided by OSR Open Systems... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by brouhahaha, Nov 12, 2015.

  1. BROUHAHAHA
    brouhahaha Win User

    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 OSR Online - The Home Page for Windows Driver Developers 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?

    :)
     
    brouhahaha, Nov 12, 2015
    #1
  2. GAGESERBEN
    GageSerben Win User

    I cant play fallout 3 on windows 10.... Please help!!!

    I just got Fallout 3 but I cant play it on my windows 10 device please help. How do I fix this? All it does is crash... I got the Fallout on disk, it runs but it wont play.
     
    GageSerben, Nov 12, 2015
    #2
  3. AUSTIN98
    Austin98 Win User
    Games crash and strange things happen to the desktop in Windows 10.

    I was playing Fallout 4 and left for about 10 minutes. I came back to see that my computer had gone to sleep which it normally does not do when running a game so I new either the game crashed or windows 10 freaked out for some reason. I woke the computer
    back up to see that the desktop icons, which had originally been sorted with games on the right and other applications on the left, had been randomly scattered across the screen and the volume icon in the bottom right has been partially grayed out and my network
    icon does not open like it normally did. Occasionally I will also have Fallout 4 get minimized and an error saying "Your system is low on memory - Cause of issue Fallout 4" however Fallout 4 was still running and I opened task manager to see that it was only
    using 3 GBs of Memory when my system has 16 GBs of memory installed. I use Fallout 4 only because I play the game a lot and that's where I notice these issues the most, but I have experienced these with other games as well, so Fallout 4 itself is not the issue.
    Screenshot of issue after crash below.


    Crashed playing Fallout 4 [​IMG]
     
    Austin98, Nov 12, 2015
    #3
  4. BROUHAHAHA
    brouhahaha Win User

    Crashed playing Fallout 4

    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 OSR Online - The Home Page for Windows Driver Developers 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?
     
    brouhahaha, Nov 12, 2015
    #4
  5. BROUHAHAHA
    brouhahaha Win User
    Hello, can anyone help me with this please?
     
    brouhahaha, Nov 13, 2015
    #5
  6. AXE0
    axe0 New Member
    axe0, Apr 5, 2018
    #6
Thema:

Crashed playing Fallout 4

Loading...

  1. Crashed playing Fallout 4 - Similar Threads - Crashed playing Fallout

  2. OneDrive Problems with Fallout 4

    in Windows 10 Software and Apps
    OneDrive Problems with Fallout 4: I recently downloaded Fallout 4 from steam and every time I try and save, whether its a quick save or manual save, it brings up this message and I have to open the recycle bin and restore the save. Is there any fix to this or am I doomed to this every single time I save?...

  3. OneDrive Problems with Fallout 4

    in Windows 10 Gaming
    OneDrive Problems with Fallout 4: I recently downloaded Fallout 4 from steam and every time I try and save, whether its a quick save or manual save, it brings up this message and I have to open the recycle bin and restore the save. Is there any fix to this or am I doomed to this every single time I save?...

  4. fallout 4 gamepass for pc

    in Microsoft Windows 10 Store
    fallout 4 gamepass for pc: Hi i've recently gotten a computer i have gamepass ultimate and i downloaded fallout 4 from game pass and when ever i attempt to start the game it goes to the top left corner of my screen and i cant interact with it or close the tab ive unistalled and reinstalled multiple...

  5. Problem playing Fallout 4 on Windows 10

    in Windows 10 Ask Insider
    Problem playing Fallout 4 on Windows 10: Hi, I have a problem. When I play Fallout 4 (I play with the settings on ultra) everything is perfect, but there are times when I pause the game and go away for a while. When I return, the screen is idle (up to here everything is normal), but when it turns on it shows all...

  6. BSOD on videos or playing fallout 4

    in Windows 10 BSOD Crashes and Debugging
    BSOD on videos or playing fallout 4: Hello , i'v been having constants BSOD everytime im watching videos on youtube or when im trying to start a game, I switched from win 7 to win 10 , so i though it was some old driver. I updated every single driver yet nothing I checked if there as a problem with the disk...

  7. BSOD started when playing Fallout 4

    in Windows 10 BSOD Crashes and Debugging
    BSOD started when playing Fallout 4: Attachment 48342 The first BSOD was while playing fallout 4. After it happened a 2nd time i ran driver verifier /standard /all. This sent the machine into a boot loop. I disabled driver verifier. My PC seems to run fine under normal conditions, but this is worrying. The...

  8. Regular BSoDs while playing Fallout 4.

    in Windows 10 BSOD Crashes and Debugging
    Regular BSoDs while playing Fallout 4.: Hi there, I'm experiencing random bsods while playing Fallout 4, I tried searching on Fallout 4 forums etc but couldn't find anything relevant to my problems. I tried checking what could be the cause with WhoCrashed but it hasn't really given me any useful information...

  9. BSOD Crash when in Modern 2016 games such as Fallout 4, and more

    in Windows 10 BSOD Crashes and Debugging
    BSOD Crash when in Modern 2016 games such as Fallout 4, and more: I've gotten BSOD when playing games and they happen on Modern games 15 minutes into playing sometimes sooner. I thought it was the drivers and updated as much as possible but still it does it. I've run whocrash and it comes up with something to this effect below - Fri...

  10. 0x00000119 BSOD only in Fallout 4.

    in Windows 10 BSOD Crashes and Debugging
    0x00000119 BSOD only in Fallout 4.: Hello, i have recently been getting the most inexplicable error when playing Fallout 4. For whatever reason sometimes when i am playing it my game will have a suddenly huge spike in fps, dropping from 60 to 5-10, and the audio will distort terribly. If i alt tab and wait a...