0x00000119 BSOD only in Fallout 4.

Page 5 of 5 FirstFirst ... 345

  1. Posts : 88
    Windows 10
    Thread Starter
       #41

    Looks like whatever the new problems are seem to be persisting, my pc had two gfx driver crashes/black screens after waking from hibernate until it just black screened and forced me to reboot the pc. Then i had 4 or so BSOD's at the login menu before it finally let me log back in, all with the tag bad pool header. This is the same as back when i tried to reinstall the realtek drivers. I will attach another DM log, can you see if it says what the problem is? In the meantime i might try reinstalling older realtek sound drivers.

    I noticed that according to bluescreenview at least one of those blue screens was attributed to MSI command center so i'm going to uninstall the various MSI apps and see how that goes as well.

    Well this probably what i deserved for not immediately heeding the warning that was given two pages ago. I literally did not think MSI software that was not even for overclocking but for checking for updates could possibly cause BSODs like this "assuming it was the primary cause". It makes me wonder how they could even release such software publicly.

    I'm not sure if it's to blame for that strange issue i had waking from hibernate though, where once again i had my gfx drivers reboot a few times except this time it never fully recovered and i had to restart the pc.
    Last edited by BobLeSaget; 16 Oct 2016 at 17:36.
      My Computer


  2. Posts : 14,903
    Windows 10 Pro
       #42

    You're correct, it's a driver from the MSI programs.
    Code:
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    ffffcf80`6694f558 fffff801`5056bb3e : 00000000`00000019 00000000`00000022 ffffcf80`666d3000 00000000`00000000 : nt!KeBugCheckEx
    ffffcf80`6694f560 fffff801`504f8453 : ffffcf80`666d3000 ffffcf80`6694f680 ffffcf80`6694f688 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x126ae
    ffffcf80`6694f630 fffff806`3e471a04 : 00000000`00000000 ffffba8b`35a18bf0 ffffba8b`35be0a80 ffffcf80`666d3000 : nt!MmFreeContiguousMemory+0x13b
    ffffcf80`6694f6e0 00000000`00000000 : ffffba8b`35a18bf0 ffffba8b`35be0a80 ffffcf80`666d3000 00000000`00000801 : amifldrv64+0x1a04
    
    Bugcheck code 00000019
    Arguments 00000000`00000022 ffffcf80`666d3000 00000000`00000000 00000000`00000000
    Debug session time: Sun Oct 16 23:53:15.367 2016 (UTC + 2:00)
    System Uptime: 0 days 0:00:11.037
    2: kd> lmvm amifldrv64
    Browse full module list
    start             end                 module name
    fffff806`3e470000 fffff806`3e477000   amifldrv64 T (no symbols)           
        Loaded symbol image file: amifldrv64.sys
        Image path: \??\C:\Program Files (x86)\MSI\DPC Latency Tuner\amifldrv64.sys
        Image name: amifldrv64.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue Sep 13 08:30:53 2011 (4E6EF89D)
        CheckSum:         000105EF
        ImageSize:        00007000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      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 12:34.
Find Us




Windows 10 Forums