BSOD playing GTAIV and Fallout 4, error 0x0000007f


  1. Posts : 5
    Windows 10 Pro x64
       #1

    BSOD playing GTAIV and Fallout 4, error 0x0000007f


    Hello, I'm a new user here so please correct me if my posts are not ok.

    I was hoping to find some help on my little brothers new build. I'm posting here on his behalf.
    He's been experiencing some sudden crashes to desktop while playing games, and now recently a bluescreen.

    These are the specs:
    Motherboard: MSI 970 Gaming
    CPU: AMD FX8320
    Memory: 4x 4gb Corsair Vengeance 2133mhz (CMY8GX3M2B2133C9R)
    Graphics Cards: 2x MSI GTX 970 Gaming
    PSU: EVGA G2 Supernova 750w (please let me know if you believe this psu might not be able to power this build)

    I asked him to fire up a memtest to run overnight before this post and I will check with him tomorrow about the results.

    I also asked him to give me the BSOD dumpfile, which I am posting below:
    Code:
    ==================================================
    Dump File         : 112015-13093-01.dmp
    Crash Time        : 20/11/2015 00:01:59
    Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
    Bug Check Code    : 0x0000007f
    Parameter 1       : 00000000`00000008
    Parameter 2       : ffffd000`a85a5b30
    Parameter 3       : ffffd000`b85b2c50
    Parameter 4       : fffff803`74dcb4c0
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+14f4d0
    File Description  : 
    Product Name      : 
    Company           : 
    File Version      : 
    Processor         : x64
    Crash Address     : ntoskrnl.exe+14f4d0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : D:\Downloads\112015-13093-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 10240
    Dump File Size    : 371,128
    Dump File Time    : 20/11/2015 01:33:57
    ==================================================
    That's all the info I have for now, please reply if you need something else or if you can already spot something that might be the cause! Thank you.
    Last edited by Buttpirate; 20 Nov 2015 at 21:16.
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    Additional information is required.

    1. Download the DM Log Collector application to your desktop by clicking the link below

    DM Log Collector.exe

    2. Run it by double-clicking the icon on your desktop, and follow the prompts.
    3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

      My Computer


  3. Posts : 5
    Windows 10 Pro x64
    Thread Starter
       #3

    Thank you for your reply. I will ask my brother to run this application as soon as possible.

    In the meantime, he sent me these results from running memtest last night.

    Last edited by Buttpirate; 20 Nov 2015 at 17:07.
      My Computer


  4. Posts : 5
    Windows 10 Pro x64
    Thread Starter
       #4

    Okay, we've run the DM Log Collector. The zip file is attached to this post.

    Note that only two sticks of RAM were installed when we ran the DM Log Collector (slot 2 & 3), as we had been doing some more memtesting earlier with fewer memory modules installed to try and pinpoint a faulty module, without success though as there were no errors.

    Edit:

    We put all sticks back in and ran the memory with the XMP settings in memtest with test 6 only and immediately got a lot of errors on every single pass, but when we set the memory settings back to the bios default (auto) at 1333mhz and run the same test, we get no errors at all.

    Manually setting the RAM frequency to 1866mhz while leaving the timings at auto also passes memtest just fine.
    Last edited by Buttpirate; 20 Nov 2015 at 21:11.
      My Computer


  5. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #5

    Code:
    fffd000`a85b1578  00060080`00000000
    ffffd000`a85b1580  00000000`9318ea90
    ffffd000`a85b1588  fffff801`842769b0Unable to load image \SystemRoot\System32\drivers\e22w10x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for e22w10x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w10x64.sys
     e22w10x64+0x69b0
    ffffd000`a85b1590  ffffe000`79525790
    ffffd000`a85b1598  fffff803`74c20ba2 hal!HalBuildScatterGatherListV2+0x18682
    ffffd000`a85b15a0  00000000`00000101
    The problem appears to be the Killer network driver. You need to do some homework and determine if this driver is compatible on the Windows 10 installation.

    Have a look here for the latest Windows 10 compatible driver :
    Killer Networking - Driver Downloads
      My Computer


  6. Posts : 5
    Windows 10 Pro x64
    Thread Starter
       #6

    My brother reformatted his computer with Windows 10 recently so I think it should be fine but I've asked him to doublecheck his network driver just in case.

    Moreover, we did some tweaking in the bios where we set the DRAM-frequency to 1866mhz and increased the FSB-frequency from 200 to 215, effectively making the memory run at 2005mhz, aswell as upping the DRAM-voltage from 1.65 to 1.67.

    After running a quick memtest to check for those nasty instant errors at test 6 that we got earlier we were happy to see there were no errors. Now my brother has been playing GTAIV on the rig for well over an hour, making it his longest session so far. The system seem to be stable, or at least working better than it was before.

    It still bugs me that the memory wouldn't run in 2133mhz like it is supposed to, but I guess the CPU memory controller gets overloaded or something? After checking, the specifications does say the CPU only supports memory modules up to 1866mhz.

    I've asked him to initiate another memtest before he goes to sleep that will run overnight with all tests. I will post again tomorrow to verify if it passed without any errors.
      My Computer


  7. Posts : 5
    Windows 10 Pro x64
    Thread Starter
       #7

    The overnight memtest passed without a single error. I'm now pretty certain that the issue was with the RAM running faster than the memory controller could handle, so I'll go ahead and mark this thread as solved for now.

    I will be back if the crashes and bluescreens return, though hopefully they won't. :)
      My Computer


  8. Posts : 1
    Windows 10
       #8

    Hi i just wanted to say i got the same RAM, PSU (650 WATT), a gtx 970. and i got the exact same issue. Ive tried pretty much everything you have and the only thing that has worked for me is putting ram down to 1866 if i want to have my overclock at 4.6ghz. i guess our rams are just shitty or what? lol
      My Computer


 

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

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