1.    03 Aug 2017 #1
    Join Date : Aug 2017
    Posts : 4
    Windows

    BSOD while gaming; Memory Management, System Thread Exc., IRQL Not...


    I've looked far and wide through these forums searching for the cause, but I'm at my technological wits end to go further alone. I've recently rebuilt my PC; new CPU, new ram, new gpu, new mobo... it should all be fine, I think, but I'm getting these errors only when I'm playing video games.

    SYSTEM SPECS:
    MOBO: MSI B350 GAMING PRO
    GPU: EVGA GTX 1060 6GB
    RAM: Corsair Vengeance LPX 16GB (8x2GB) 2400
    CPU: Ryzen 5 1600

    I've checked and monitored the temps, and they seem to be fine.

    I ran windows memory diagnostic
    , and that came back clean.

    I've run memtest86 for about 3 passes per stick, and it seemed okay... going to do a more comprehensive test of this tonight, once I go to bed.

    These are the whocrashed results.

    On Thu 8/3/2017 3:59:56 PM your computer crashed
    crash dump file: C:\Windows\Minidump\080317-20375-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)
    Bugcheck code: 0xA (0xFFFF9A8376F2CB00, 0xFF, 0x0, 0xFFFFF80184AFE53E)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 8/3/2017 12:26:36 PM your computer crashed
    crash dump file: C:\Windows\Minidump\080317-20609-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1F1440)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8020A870440, 0xFFFFD000C8FE1128, 0xFFFFD000C8FE0960)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 8/2/2017 11:00:16 PM your computer crashed
    crash dump file: C:\Windows\Minidump\080217-15171-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
    Bugcheck code: 0x1A (0x41289, 0x7FFAB39B2000, 0x1578, 0x7DFAB39B2205)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 8/2/2017 11:00:16 PM your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x1A (0x41289, 0x7FFAB39B2000, 0x1578, 0x7DFAB39B2205)
    Error: MEMORY_MANAGEMENT
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 8/2/2017 3:19:20 PM your computer crashed
    crash dump file: C:\Windows\Minidump\080217-14734-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
    Bugcheck code: 0x1A (0x41793, 0xFFFFC580C496F770, 0x1F, 0x1E)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    I honestly don't know what else to do. Maybe a more comprehensive eight-hour memtest will yield some results, but if somebody could help me with the dumps just to make sure it isn't drivers/there aren't any explicit obvious signs that point to a fault... that would be very helpful.

    Thank you for reading.
    Last edited by warpapa; 03 Aug 2017 at 16:00.
      My ComputerSystem Spec
  2.    03 Aug 2017 #2
    Join Date : Apr 2017
    Posts : 8,654
    windows 10 professional version 1607 build 14393.969 64 bit

    Hi warpapa ,

    The bsod mini dump files when debugged indicate memory problems.

    1) Run memtest86+ version 5.01 for at least 8 runs.

    This may take many hours so plan to run it overnight.
    Memtest86+ - Advanced Memory Diagnostic Tool
    When Memtest86+ has completed 8 or more runs use a camera or a smart phone camera to make an image of the results to post into the thread.
    Memory problems. - Microsoft Community

    MemTest86+ - Test RAM Windows 10 BSOD Tutorials

    It may take 1 - 2 hours /GB RAM for the testing to complete 8 passes.
    Anything less that 8 passes is an incomplete test and is wasting time.
    If there is 1 error that is a failed test and testing can be aborted.
    There is 16 GB of RAM on 2 DIMM
    If testing both RAM at one time displays 1 error then stop testing both and test 1 RAM at a time in the same DIMM.
    This will differentiate the good from the malfunctioning RAM.
    If both RAM pass in the same DIMM then check the next DIMM with the RAM that passed.
    This will then check the DIMM/MB

    Again the time does not differentiate good from bad testing.
    It is the number of passes.
    Anything less that 8 passes has too high an incidence of false negatives.
    That is it indicates RAM is ok because the testing was inadequate.
    The more passes that are made the less the problems with false negatives.
    Please use a camera to make a picture and post the image or images into the thread.



    2) open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) dism /online /cleanup-image /restorehealth

    5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread





    Code:
    BugCheck 1A, {41793, ffffc580c496f770, 1f, 1e}Probably caused by : memory_corruption
    Code:
    BugCheck A, {ffff9a8376f2cb00, ff, 0, fffff80184afe53e}Probably caused by : memory_corruption
    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff8020a870440, ffffd000c8fe1128, ffffd000c8fe0960}Probably caused by : memory_corruption
    Code:
    8/2/2017 5:49 AM    Application Error    Faulting application name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Faulting module name: KERNELBASE.dll, version: 10.0.14393.0, time stamp: 0x57899809
    Exception code: 0xc06d007e
    Fault offset: 0x0000000000017788
    Faulting process id: 0x31a0
    Faulting application start time: 0x01d30b53287577a7
    Faulting application path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Faulting module path: C:\Windows\System32\KERNELBASE.dll
    Report Id: 5b6aa6be-f499-48ec-b77b-70161672ebfe
    Faulting package full name: 
    Faulting package-relative application ID:8/3/2017 5:09 PM    Application Error    Faulting application name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Faulting module name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Exception code: 0xc0000409
    Fault offset: 0x000000000022af80
    Faulting process id: 0xa0c
    Faulting application start time: 0x01d30c797a4ee1cf
    Faulting application path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Faulting module path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Report Id: 65d89c6b-1ef5-4bfa-b3a5-91d6703b97b3
    Faulting package full name: 
    Faulting package-relative application ID:8/2/2017 7:35 PM    Application Error    Faulting application name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Faulting module name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Exception code: 0xc0000409
    Fault offset: 0x000000000022af80
    Faulting process id: 0xa94
    Faulting application start time: 0x01d30bc46c44aa8b
    Faulting application path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Faulting module path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Report Id: 1b422920-0151-4717-a033-7c1e0fdc4247
    Faulting package full name: 
    Faulting package-relative application ID:8/3/2017 7:00 PM    Application Error    Faulting application name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Faulting module name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Exception code: 0xc0000409
    Fault offset: 0x000000000022af80
    Faulting process id: 0xab4
    Faulting application start time: 0x01d30c8a7d81ec6f
    Faulting application path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Faulting module path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Report Id: 0615eece-06ad-4a5e-8b42-2f118592b4d2
    Faulting package full name: 
    Faulting package-relative application ID:8/3/2017 6:06 AM    Application Error    Faulting application name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Faulting module name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Exception code: 0xc0000409
    Fault offset: 0x000000000022af80
    Faulting process id: 0xad0
    Faulting application start time: 0x01d30c0c0f7a3815
    Faulting application path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Faulting module path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Report Id: 075e0725-4d31-4185-9a00-9add81299ce8
    Faulting package full name: 
    Faulting package-relative application ID:8/3/2017 3:02 AM    Application Error    Faulting application name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Faulting module name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Exception code: 0xc0000409
    Fault offset: 0x000000000022af80
    Faulting process id: 0xb20
    Faulting application start time: 0x01d30c04cb1e6331
    Faulting application path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Faulting module path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Report Id: cb2c0cf6-b42d-4cce-bae0-767ba1d809d4
    Faulting package full name: 
    Faulting package-relative application ID:8/3/2017 4:49 PM    Application Error    Faulting application name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Faulting module name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58eb9957
    Exception code: 0xc0000409
    Fault offset: 0x000000000022af80
    Faulting process id: 0xb68
    Faulting application start time: 0x01d30c7572423b9c
    Faulting application path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Faulting module path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe
    Report Id: 8bc8fe8d-77f8-4226-afe0-1697b8002d9e
    Faulting package full name: 
    Faulting package-relative application ID:
      My ComputerSystem Spec
  3.    04 Aug 2017 #3
    Join Date : Aug 2017
    Posts : 4
    Windows
    Thread Starter

    Quote Originally Posted by zbook View Post
    Hi warpapa ,
    The bsod mini dump files when debugged indicate memory problems.
    1) Run memtest86+ version 5.01 for at least 8 runs.
    Please use a camera to make a picture and post the image or images into the thread.
    2) open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) dism /online /cleanup-image /restorehealth5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
    Woowee! That all took some time, but here we go.

    Step 1. Memtest 86 Results - took pictures and saved the html results. Pictures first (of both screens after it completed) and then the HTML results. I'll post an imgur link and also upload the direct files.
    Attachment 147060Attachment 147062Attachment 147061

    Imgur: The most awesome images on the Internet

    Steps 2-5. Command Prompt runs finished - hopefully I pasted them in right.

    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.


    C:\Windows\system32>sfc /scannow


    Beginning system scan. This process will take some time.


    Beginning verification phase of system scan.
    Verification 100% complete.


    Windows Resource Protection found corrupt files and successfully repaired
    them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.


    C:\Windows\system32>dism /online /cleanup-image /restorehealth


    Deployment Image Servicing and Management tool
    Version: 10.0.14393.0


    Image Version: 10.0.14393.0


    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.


    C:\Windows\system32>
      My ComputerSystem Spec
  4.    04 Aug 2017 #4
    Join Date : Nov 2015
    Posts : 2,863
    64bit Win 10 Pro ver 1709 Build 16299.64

    Hello warpapa

    I noticed that there is a more recent BIOS for your system that might have some improved memory compatibility. This would be worth trying.
      My ComputersSystem Spec
  5.    04 Aug 2017 #5
    Join Date : Aug 2017
    Posts : 4
    Windows
    Thread Starter

    Quote Originally Posted by philc43 View Post
    Hello warpapa

    I noticed that there is a more recent BIOS for your system that might have some improved memory compatibility. This would be worth trying.
    Do you think at this point I can just overwrite the memtest86 USB? I'm not really sure how to update bios... I heard I just need to download the file for the update to my USB, and run m-flash?

    Also, thanks for all the help so far.
      My ComputerSystem Spec
  6.    04 Aug 2017 #6
    Join Date : Nov 2015
    Posts : 2,863
    64bit Win 10 Pro ver 1709 Build 16299.64

    The memtest86 USB will be very useful for future testing so it would be worth keeping it but if you do not have another USB drive then you will just have to reuse it and create it again later.

    The BIOS update process is well documented on the MSI website, there is both a video and pdf file:
    https://msi.com/Motherboard/support/...AMING-PRO.html
      My ComputersSystem Spec
  7.    04 Aug 2017 #7
    Join Date : Aug 2017
    Posts : 4
    Windows
    Thread Starter

    Tentatively seems the BIOS update has fixed all my problems... I'll monitor it for the next day or two; thank you, Philc!
      My ComputerSystem Spec
  8.    04 Aug 2017 #8
    Join Date : Nov 2015
    Posts : 2,863
    64bit Win 10 Pro ver 1709 Build 16299.64

    You are welcome, I hope it continue to work for you!
      My ComputersSystem Spec
  9.    04 Aug 2017 #9
    Join Date : Apr 2017
    Posts : 8,654
    windows 10 professional version 1607 build 14393.969 64 bit

    1) Open administrative command prompt and type or copy and paste:
    chkdsk /scan

    When this has completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread



    2) turn off windows fast startup:
    Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

    3) ordinarily we have all OP use memtest86+ for testing memory as the software testing differs by each vendor.
    What can we do to make the link to click on easier for the next OP?
    Should there be more links so that they are easier to find?
    Should a comment be made to only use one web site?
    Should a comment be made not to use the other web sites?
    Please indicate how you made the choice?

    4) please post a follow up zip after a few more days of monitoring:
    BSOD - Posting Instructions - Windows 10 Forums

    Code:
    Windows failed fast startup with error status 0xC00000D4.
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
BSOD's while gaming, citing Memory management issues.
Hi guys, I recently bought a new PC, its maybe 6 months old at this point and around 3 months ago I started having BSOD's. These only occur when I am gaming, never had one before when browsing etc. The stop code is generally memory...
BSOD Crashes and Debugging
IRQL and Memory Management
Hello all, Actionman here. Averagely tech savvy, and normally handle issues on my own, but as of this week having many BSODs I can't seem to nail down. Unfortunately I'm currently not capable of connecting to the Internet in any consistent way...
BSOD Crashes and Debugging
Solved IRQL , Pool Curroption , Memory management HELP!
Hi, So for the past two weeks i have been recieving lots of BSOD's. Most of them are IRQL not less than Equal , then memory management. I have tried doing the driver verification only to have it consitantly loop (which is what it supposed to...
BSOD Crashes and Debugging
Solved BSOD - Memory Management & others while gaming/browsing
Quite an array of different codes been popping up since I upgraded to windows 10 in the last couple of months irql_not_less_or_equal memory management was another one I have attached several dumps, as I am a bit at my wits end as to...
BSOD Crashes and Debugging
Memory Management, system secuiry service etc.
hello, i've been having random bsod issues. and i can not seem to figure out the trigger of these bsod's. i get memory management when im browsing, playing a game or when i dont even use the laptop. The system security bsod i have no clue on. My...
BSOD Crashes and Debugging
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 04:20.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums