Windows 10: 0x00000119 BSOD only in Fallout 4.

Discus and support 0x00000119 BSOD only in Fallout 4. in Windows 10 BSOD Crashes and Debugging to solve the problem; 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... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by BobLeSaget, Sep 10, 2016.

  1. 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 few seconds the game will restore itself back to normal, if i do not it will freeze the system, and upon rebooting i will see the 0x00000119 bsod in the event log. The peculiar thing is this issue seems to also be tied to my save file itself somehow, starting a new game this problem is completely absent but rises in frequency the longer i play after a certain point which seems to be 16+ hours on the save file. I have no idea if this is because of the game or possibly the game is somehow taxing certain parts of the computer more than others. I have not had this issue at all with any other games, or casual usage. The actual load in the game seems irrelevant as well as i have had the fps spike in both demanding outdoors locations and small interiors with very little actual load. I have played other fairly intensive games such as Deus Ex Mankind Divided and they have not had anything similar to the issues i am getting in Fallout. I am currently using the newest Nvidia drivers 372.70.

    I have tried various things to see if i could find out the cause of the problem or to resolve it, but nothing has really worked.
    First i tried Furmark/CPU Burner at about 30m of each, with neither of them causing any problems. The temperatures were about the lower 50's max on the CPU and 70-80 for the GPU.
    I also tried doing a clean uninstall and reinstall of the older 368.39 Nvidia drivers using DDU and safemode, but the only difference that made was with the old driver instead of lagging into a possible BSOD, it would just BSOD (same 0x00000119 BSOD).
    Running SFC/Scannow, the intel processor diagnostic, as well as HD health utilities found no problems.
    I moved the entire Fallout 4 installation to another hard drive but that did not fix it either.
    The computer itself is relatively new, only about a month old.
    I am a bit scared if this is just a problem with the game software; although admittedly i am unsure how it can crash the entire pc the way it does, or if it's just this specific game/situation highlighting a possible hardware problem that just nothing else is for now.

    I ran DPC Latency Checker and it seems during the fps spikes the latency will spike from 1500 μs to 100,000.
    The computer is running at stock settings on the cpu and gpu.
    The power supply is a 500w FSP 1U unit.

    :)
     
    BobLeSaget, Sep 10, 2016
    #1

  2. Fallout 4 BSOD Windows 10

    Hi,

    Check with others playing Fallout4 to see if this is a known issue.

    Set it to factory specs until it is running right.

    It may not help however post the minidump so we can analyze it.

    (Heat related does not always mean excessive heat as a component can be too sensitive to even the normal levels of heat.) Check the processor, heat sink, and the compound between them.

    Check the fans and even add extra to see if that helps.

    Video card along with memory can be in play here.

    Rob - SpiritX
     
    SpiritX MS MVP, Sep 10, 2016
    #2
  3. Fallout 4 BSOD Windows 10

    Hi,

    Be sure to contact the game's Support and Forums about any known issues as the game could be causing the issue.

    Troubleshoot blue screen errors

    http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors



    We can analyze the minidumps if you make them available from the OneDrive or other file sharing sites (such as MediaFire).
    If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there.

    Adding files to your OneDrive

    http://windows.microsoft.com/en-us/windows-8/getting-started-onedrive-tutorial

    Upload photos and files

    http://windows.microsoft.com/en-us/onedrive/add-photos-files

    One-Drive - Share files and folders and change permissions

    Share OneDrive files and folders

    Zip or upload the contents of C:\Windows\minidump
    Use OneDrive to upload collected files

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65



    ====================================================



    1.
    Suspect hardware - maybe video or memory however that is not a sure bet.

    Remove ALL power then reseat the cards memory and cables (on both ends when possible) - actually remove and replace - do not just snug. Clean out the dust bunnies and clear the vents. Ensure the fans are working. Try adding a small fan blowing into the intake
    to reduce the effects of heat. (Heat related does not always mean excessive heat as a component can be too sensitive to even the normal levels of heat.) Check the processor, heat sink, and the compound between them.

    2. Check the memory very thoroughly. Keep in mind that memory tests do not detect all errors such as the tiny speed differences between memory modules that appear to be identical. So it may be necessary to swap the modules in and out in different
    combinations and patterns. (See memory test methods below).

    3. Check with your video card/device maker's support and forums - update drivers.

    4. In needed run Driver Verifier to see if it can indicate a CAUSE (see Driver Verifier methods below).

    5. As needed use ALL the other methods in the troubleshooter below.

    =======================================================

    Have you added any hardware lately? Main likely culprits are hardware, major drivers, memory, and antivirus/antispyware/security products could be at fault.

    BCCode: 101 0x00000101

    BCCode: 101 0x00000101 <-- read this link

    A clock interrupt was not received on a secondary processor within the allocated time interval.



    BCCode: 101 0x00000101 <-- read this link

    Bug Check 0x101 CLOCK_WATCHDOG_TIMEOUT
    ==================================================

    This utility makes it easy to see which versions are loaded :

    Run DriverView - set VIEW to Hide Microsoft drivers - update those without

    Dump in their names (and update BIOS and chipset).

    DriverView - Free - utility displays the list of all device drivers currently loaded

    on your system. For each driver in the list, additional useful information is

    displayed: load address of the driver, description, version, product name,

    company that created the driver, and more.

    DriverView: Loaded Windows Drivers List



    For Drivers check System Maker as fallbacks and Device Maker's which are the

    most current. Control Panel - Device Manager - Display Adapter - write down

    the make and complete model of your video adapter - double click - Driver's

    tab - write down the version info. Now click UPdate Driver (this may not do

    anything as MS is far behind certifying drivers) - then Right Click - Uninstall -

    REBOOT this will refresh the driver stack.

    Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard

    if 3rd party with their own software and drivers and any other major device drivers

    you have.

    Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and

    then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their

    latest versions. (Look for BIOS, Chipset, and software updates at System Maker's

    site while there.)

    Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -

    REBOOT after each installation.

    Always check in Device Manager - Drivers tab to be sure the version you are

    installing actually shows up. This is because some drivers rollback before the

    latest is installed (sound drivers particularly do this) so install a driver - reboot

    - check to be sure it is installed and repeat as needed.

    Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER -

    heck manually by model.

    Manually look at manufacturer's sites for drivers - and Device Maker's sites.

    How to Find and Download Drivers


    ====================================================

    Memory tests do not catch all errors such as mismatched memory (possible even

    for sticks that appear to be identical) and when faster memory is placed in system

    behind slower memory. So it is best to also swap sticks in and out to check for

    those even if all memory tests fail to show a problem.

    To test RAM check here - let it run 4+ hours or so. <-- best method

    www.memtest.org

    MemTestX86 - Test RAM With

    MemTest86+ - Test RAM

    For the Windows Memory Diagnostic Tool.

    Type in Cortana's search box -> Windows Memory Diagnostics

    at top of list - click it. in Windows 8/8.1/10 the name is "Windows Memory

    Diagnostic".



    ================================================

    After doing ALL the updates you can, and if the issue continues, then run

    DriverVerifier. (Remember to use the Windows 8/8.1 methods posted at the

    top of the original reply above.)

    Driver Verifier can help find some BSOD issues :

    Using Driver Verifier to identify issues with Windows drivers for advanced users

    http://support.microsoft.com/kb/244617

    How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10

    are essemtially the same).

    Driver Verifier Manager & Device Manager in Windows

    Using Driver Verifier

    Using Driver Verifier

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver

    Issues

    http://www.youtube.com/watch?v=_VwIDD9xngM

    Driver Verifier

    http://www.techsupportforum.com/2110308-post3.html

    Using Driver Verifier

    http://www.faultwire.com/solutions/using_driver_verifier.php

    You can disable Driver Verifier

    http://support.microsoft.com/kb/244617

    WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

    Use BlueScreenView to see if there is a driver specified in the error message.

    Also check with MyEventViewer at the time of the BlueScreen.

    If DriverVerifier creates a minidump upload it and post the link here so we can

    analyze it.

    Hope this helps.

    --------------------------------------------------------------------------------------------

    Rob Brown -
    Microsoft MVP
    <- profile - Windows Experience : Bicycle - Mark Twain said it right.
     
    SpiritX MS MVP, Sep 10, 2016
    #3
  4. axe0 New Member

    0x00000119 BSOD only in Fallout 4.

    Hi BobLeSaget,

    Welcome to the 10forums *Smile

    I assume you haven't overclocked your CPU, GPU or RAM?

    Does this problem also occur on other games? If you've mentioned this, I'm sorry but I have missed that part *Sad
     
  5. CPU RAM and GPU are all on stock. I have not had this issue on any other game or benchmark utility as of yet.
     
    BobLeSaget, Sep 11, 2016
    #5
  6. axe0 New Member
    Alright, usually with game specific issues it's not a hardware problem but rather a game setting causing it, or game bug or driver bug.

    Just to ensure that there is no software conflict with the drivers, please use following instructions when clean installing the drivers
     
  7. One of the first things i tried was using DDU and reverting back to an older driver, but all the succeeded in doing was having the game cause a bsod instead of the lag/audio distortion into a BSOD. When i went back to the newest drivers 372.70 i got back the lag/audio distortion where i get time to alt-tab before BSOD. Another random thing that i forgot to list was, i had actually been playing the game a fair bit prior to 9/5 (when i first saw the issue) with the same settings but the problem had never shown before.
     
    BobLeSaget, Sep 11, 2016
    #7
  8. axe0 New Member

    0x00000119 BSOD only in Fallout 4.

    I'm aware of it yes, but I would ask you to follow my post completely in regards to the customized installation of the install setup.
     
  9. I see, well i'll try the driver install again but this time using the newest drivers.
     
    BobLeSaget, Sep 12, 2016
    #9
  10. axe0 New Member
    Keep me posted on how it goes *Smile
     
  11. Might be a bit before i can really test as i will be out of town for a week or so, and the problem itself is really random when it shows.
     
    BobLeSaget, Sep 13, 2016
    #11
  12. axe0 New Member
    No problem, take the time needed *Smile
     
  13. 0x00000119 BSOD only in Fallout 4.

    Well for a time i had the problem under control for a time i am unsure if it is due to new nvidia driver or bios update or what not, but it seems after windows forced its anniversary update on me the problem has returned. Maybe this is due to it also having messed with my gfx drivers, i am unsure. I ran the DPC latency monitor and it seems to confirm the problematic driver is dxgkrnl.sys

    ____________________________________________________________________________________________________ _____
    REPORTED ISRs
    ____________________________________________________________________________________________________ _____
    Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

    Highest ISR routine execution time (µs): 50110.397831
    Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

    Highest reported total ISR routine time (%): 0.233368
    Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

    Total time spent in ISRs (%) 0.266173

    ISR count (execution time <250 µs): 233316
    ISR count (execution time 250-500 µs): 0
    ISR count (execution time 500-999 µs): 4
    ISR count (execution time 1000-1999 µs): 12
    ISR count (execution time 2000-3999 µs): 5
    ISR count (execution time >=4000 µs): 0

    ____________________________________________________________________________________________________ _____
    REPORTED DPCs
    ____________________________________________________________________________________________________ _____
    DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

    Highest DPC routine execution time (µs): 25043.371575
    Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

    Highest reported total DPC routine time (%): 0.095817
    Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

    Total time spent in DPCs (%) 0.325179

    DPC count (execution time <250 µs): 836666
    DPC count (execution time 250-500 µs): 0
    DPC count (execution time 500-999 µs): 1
    DPC count (execution time 1000-1999 µs): 0
    DPC count (execution time 2000-3999 µs): 1
    DPC count (execution time >=4000 µs): 0


    Did a clean install of the 372.90 drivers with DDU again so we'll see how that goes. I suspect that the windows update screwed with my driver installation somehow as geforce experience showed that for w/e reason it downgraded my drivers from 372.90 to the 368.39 drivers.

    I managed to find http://answers.microsoft.com/en-us/w...8-48a67819472d
    The author seems to basically have the same issue i have with a nearly identical system setup. It makes me a bit wary if anything i can do will fix it or if this is just some severe issue with the gfx card+operating system.
     
    BobLeSaget, Sep 29, 2016
    #13
  14. axe0 New Member
    Keep me posted on the situation *Smile
     
  15. Something peculiar recently happened. I was browsing reddit on firefox and while i was scrolling part of the screen had a sudden horizontal distortion but it quickly went away after i switched tabs back and forth. I'm not sure if this is significant but it is a bit ominous.
     
    BobLeSaget, Sep 30, 2016
    #15
Thema:

0x00000119 BSOD only in Fallout 4.

Loading...
  1. 0x00000119 BSOD only in Fallout 4. - Similar Threads - 0x00000119 BSOD 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. 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...
  5. BSOD 5-10 mins in game Fallout 4

    in Windows 10 BSOD Crashes and Debugging
    BSOD 5-10 mins in game Fallout 4: Hi, I just recently built a new pc to replace my existing one. All programs I have ran seem fine, however when I go to play Fallout 4 it goes to blue screen with 5 to 10 minutes of gameplay or just idling in game. I have reinstalled the video card drivers. I have reinstalled...
  6. Multiple different and same BSOD randomly (Fallout 4)

    in Windows 10 BSOD Crashes and Debugging
    Multiple different and same BSOD randomly (Fallout 4): While playing fallout 4 and sometimes while not I will get random BSOD with various different messages. I have gotten CLOCK_WATCHDOG_TIMEOUT a couple of times, IRQL_GT_ZERO_AT_SERVICE once, WHEA_UNCORRECTABLE_ERROR multiple times, SYSTEM_SERVICE_EXCEPTION multiple times (this...
  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. Crashed playing Fallout 4

    in Windows 10 BSOD Crashes and Debugging
    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...
  10. BSOD, Error 0x00000119, Playing Unturned

    in Windows 10 BSOD Crashes and Debugging
    BSOD, Error 0x00000119, Playing Unturned: Hi Tenforums, After playing a bit of Unturned and watching Youtube, my PC made a BSOD. I have no idea what made happend and I would love some help. I have uploaded the dump file, like I was instructed, from this website. All tempetures were at right point, all under...
Tags:

Users found this page by searching for:

  1. interrupt secondary processor fallout 4