Constant BSOD and reboot when starting fallout 4 saved game

Page 1 of 2 12 LastLast

  1. Poko
    Posts : 48
    Microsoft Windows 10 Pro 64 bits 15063 Multiprocessor Free
       New #1

    Constant BSOD and reboot when starting fallout 4 saved game


    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 and nothing
    • I used memtest , no error was found

    My computer started beeping (Award BIOS legacy) 3 longs beeps and 1 short , so i removed one ram card and everything was fixed no more random BSOD and i could play games like nothing ever happened
    That worked for 1 and half day , once again im having random BSOD when watching videos or trying to start a game
    This little ****er (ntkrnlmp.exe) has been causing a LOT of BSOD from SYSTEM_SERVICE_EXCEPTION PAGE_FAULT_IN_NONPAGED_AREA IRQL_NOT_LESS_OR_EQUAL KMODE_EXCEPTION_NOT_HANDLED BAD_POOL_HEADER

    Im uploading my whocrashed report too, whocrashed says i need to update atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

    No idea how to update that...

    Honestly i dont know what else i can do about this , if anyone could lend me a hand i would really apreciate it because my sanity is suffering a lot of damage with this random BSOD
    Last edited by Poko; 11 Jun 2017 at 14:03.
      My Computer
    Quote Quote

  3. zbook
    Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       New #2

    Code:
    atikmdag.sys
ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
http://support.amd.com/us/Pages/AMDSupportHub.aspx 
Get from OEM for laptops
    Code:
    fltmgr.sys
Microsoft Filesystem Filter Manager
Windows Update
    Code:
    dxgkrnl.sys
DirectX Graphics Kernel
Windows Update
    Code:
    Ntfs.sys
NT File System Driver
Windows Update

    Code:
    WdFilter.sys
Windows 8 CP - Microsoft antimalware file system filter driver
Windows Update
    Code:
    tcpip.sys
Microsoft TCP/IP Driver (networking related)
Windows Update
    Code:
    dxgmms1.sys
DirectX Graphics MMS
Windows Update
    Code:
    rdyboost.sys
ReadyBoost Driver
Windows Update

    The preliminary debugging with Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64 found the above *.sys drivers related to the BSOD. There were some minidump that could not be read.

    The logs are in a foreign language and were not able to be searched or interpreted.

    Open device manger, expand display adapters, right click on each row , then left click on properties, left click on uninstall device for any ATI or AMD drivers. On the manufacturers web site find the latest driver for your computer and install.

    Open administrative command prompt and type or copy and paste these commands:

    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) chkdsk /scan

    To post the results of the above three commands: Right click on the top bar of the administrative command prompt box, hover over edit, left click on select all. Then right click the top bar again, hover over edit, left click copy then paste into the forum.

    In the memory test that you ran which version of the software and how many runs did you make? Run memtest86+ for 8 or more runs (run overnight).
    If bsod are frequent then place your computer in clean boot to reduce the frequency of bsod:

    How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

    https://support.microsoft.com/en-us/...oot-in-windows

    This is a link for AMD drivers: AMD Support and Radeon Software Driver Download


    If you are able to resend any logs in English we may be able to use search and provide more information on the debugging.
    Last edited by zbook; 09 Jun 2017 at 15:58.
      My Computer
    Quote Quote

  4. Poko
    Posts : 48
    Microsoft Windows 10 Pro 64 bits 15063 Multiprocessor Free
    Thread Starter
       New #3

    Thank you for your reply , ill see what i can do about the lenguage (spanish), meanwhile ill start with the drivers and the commands
      My Computer
    Quote Quote

  6. Poko
    Posts : 48
    Microsoft Windows 10 Pro 64 bits 15063 Multiprocessor Free
    Thread Starter
       New #4

    This is the cmd report but sadly no error found so the adventure continues
    sfc /scannow dism /online /cleanup-image /restorehealth chkdsk /scan
    Attachment 138776

    Also i ran memtest 7 times but just for precautions im gonna run it again
      My Computer
    Quote Quote

  7. zbook
    Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       New #5

    Please run memtest86+ version 5.01 for 8 or more runs (there were multiple dumps indicating memory corruption). Sometimes it takes runs in the teens to find corruption. (plan to run it overnight in clean boot.)

    Memtest86+ - Advanced Memory Diagnostic Tool
      My Computer
    Quote Quote

  8. Poko
    Posts : 48
    Microsoft Windows 10 Pro 64 bits 15063 Multiprocessor Free
    Thread Starter
       New #6

    Thank you for your reply zbook , i ran memtest86+ 8 times but no error was found also ntkrnlmp.exe has caoused a new BSOD called APC INDEX MISMATCH
      My Computer
    Quote Quote

  9. Poko
    Posts : 48
    Microsoft Windows 10 Pro 64 bits 15063 Multiprocessor Free
    Thread Starter
       New #7

    I ran memtest86+ again, but no error was found , thank you for your reply anyways
      My Computer
    Quote Quote

  10. zbook
    Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       New #8

    Open administrative command prompt and type or copy and paste this command:
    shutdown /r /o /f /t 00
    That will open the windows recovery or advanced troubleshooting menu.
    Navigate to startup options
    It will restart then select #6 safe mode with command prompt.
    Type or copy and paste: shutdown /r
    It will reboot to the desktop.

    The above navigation with the windows advanced troubleshooting menu is critical when using windows driver verifier as it is the method to turn off the application.
    Using windows driver verifier will stimulate all non-Microsoft drivers and produce BSOD.
    The BSOD will continue unless windows driver verifier is turned off, or until all misbehaving drivers are fixed.
    When bsods happen the screen can be set to automatically restart . This could be the current setting.
    Turning off automatically restart is necessary so that you can view the bsod screen.
    This link will explain how to turn off automatic restart:
    BSOD Finding and fixing them - Microsoft Community
    On the bsod screen it will often display stop code driver verifier detected violation. This does not provide the misbehaving driver and that can be found by debugging the minidump files created by using windows driver verifier.
    In addition to displaying a stop code at times the windows driver verifier produced bsod screen may display the misbehaving driver: *.sys
    If you see the misbehaving driver record it for later use.

    Download and install bluescreenview in addition to whocrashed to aide in the processing of the minidump files. Most often the analysis is the same but sometimes there is additional information. After each bsod you will use safe mode with command prompt and enter the command: verifier /reset
    When back on the desktop you will run each whocrashed and bluescreenview. They will perform an immediate analysis of the minidump and provide the misbehaving driver and device or application. You will then uninstall the driver or application and repetitively use widows driver verifier until you no longer have bsod.
    Once you no longer have bsod you will then find the most up to date drivers and install them. The process is repeated until you no longer have any bsod and then you will run windows driver verifier for 36 hours of typical use. If there are no longer any bsod you will then turn off windows driver verifier.
    An alternative method is to install a new driver immediately after it has been uninstalled. You will pick the method that you prefer, either wait until all misbehaving drivers have been removed or install new drivers immediatley after the misbehaving drivers or applications have been uninstalled


    In the left lower corner search when you type verifier it will open a pop up to set windows driver verifier.
    Use this guide to for the settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    At times software produces bsod and you may need to uninstall software.
    On one of my computers I cannot find a good driver for Cyberlink. An alternative is to use VLC player or know that using Cyberlink may produce a bsod.
    Sometimes antivirus software produces bsod. So while using windows driver verifier make sure that you are only using windows defender.

    You can start using windows driver verifier when you have the time to manage and troubleshoot the bsod.

    Update your zip file with the new bsod.
      My Computer
    Quote Quote

  12. zbook
    Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       New #9

    ...
      My Computer
    Quote Quote

  13. Poko
    Posts : 48
    Microsoft Windows 10 Pro 64 bits 15063 Multiprocessor Free
    Thread Starter
       New #10

    Thank you for your comment , for some reason my computer just started to reboot non stop , it was BSOD after BSOD non stop so i couldnt use a lot it these days
    I managed to translate the dumpfiles using another dumpfile reader

    Attachment 139347
    Attachment 139345
    Attachment 139346

    I discovered that if i let my pc turned on for a while without doing anything there isnt any BSOD , tonight i will run driver verifier and ill upload the files
      My Computer
    Quote Quote

 

  Related Discussions
BSOD when starting game first time
in BSOD Crashes and Debugging

This is a little weird, I usually get BSOD when I start my PC when it hasn't been on for hours, but when I blue screen and boot Windows back up it doesn't seem to BSOD. I'm not sure if this is just a coincidence, but can someone please advise?
Hello, I have had many BSODs regarding ntoskrnl.exe, FLTMGR.SYS, WdFilter.sys since I have updated to Windows 10 from Windows 7. I have checked drivers, memtest, and bios drivers. All is fine. Memtest for a whole night. Specs: i7 4970k gtx 1080...
BSOD when starting game (WoW)
in BSOD Crashes and Debugging

Hi all, I am new here, and hopefully can ask the braintrust for some help. I recently returned to the game after a long pause (WoW). Now my system crashes almost instantly (within the first 20 seconds) of logging in and beginning play. I am at...
BSOD 5-10 mins in game Fallout 4
in BSOD Crashes and Debugging

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...
Bsod when starting a game
in BSOD Crashes and Debugging

Hey guys, When im using my PC for normal use (internet,word,music, etc..) I have no problem. But the moment I start up a game I get a bsod. Does anyone know what the problem is and how to solve it? Thanks in advance!
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 05:05.
Find Us




Windows 10 Forums