Bsod when downloading large files Bugcheck 124 memory_corruption.sys

Page 1 of 3 123 LastLast

  1. Posts : 15
    Windows 10 Pro x64
       #1

    Bsod when downloading large files Bugcheck 124 memory_corruption.sys


    Hey guys, first post and new to the forum.

    Built a new pc in the last 7 days and have been having constant bsod issues.

    Initially It was happening randomly even after all manufacturer drivers up to date and windows updates complete. Mostly happened during downloading large files and I was also unable to open any games. Also occuring randomly under general use or even idle overnight.

    After a few clean wipes and fresh windows installs and even creating a second usb win10 install media (just in case) the bsods have been reduced greatly but are still occuring. I can now open most games and play them no worries.

    The only thing I have done different is the new usb install media + I also let windows update after the manufacturer drivers were installed instead of before. I also have not installed ICUE (corsair cooler control software) this time either.

    One thing to note was that I was able to download large game files + install all third party software I usually use and the pc ran for 6+ hours no issues (after manufacturer drivers installed) but before I let win10 auto update for the first time on this last fresh install, I also played some of my usual games for 20-30 mins each to test. BSOD (Bugcheck code: 0x9C)(intelppm.sys )occured only when trying to play subnautica below zero, which is an incomplete game in its early stages and very buggy any way.

    After I felt comfortable that the issue wasnt manufacturer drivers or maybe third party software I let the updates occur and then left my pc on overnight downloading some more large game files. I woke up and discovered that 2 hours after the updates occured, BSOD (Bugcheck code: 0x124 - memory_corruption.sys) happened again.

    I have stress tested the cpu with OCCT for 4+ hours with no errors, memtest86 on each stick for 8 passes each with no errors, run chkdsk on both drives plus also checked both drives with third party software (seagate tool and hdtunepro).

    I have attached the V2 log collector file I just ran.

    Any help appreciated.
      My Computer


  2. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    Hi n00byn00b ,

    Welcome to the TF BSOD forum.

    The bugchecks were 9C and 124.
    There was a misbehaving driver.

    Some testing may be repeated so that there are new results posted into the thread.

    Perform the following steps:

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) bcdedit /enum {badmemory}

    9) 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

    10) Make sure that there is no over clocking while troubleshooting.

    11) Open file explorer > this PC > C: > in the right upper corner search for: C:\widows\memory.dmp > zip > post a share link into the thread using one drive, drop box, or google drive

    Code:
    Crash dump found at C:\Windows\MEMORY.DMP
    Creation date: 08/23/2019 02:48:06
    Size on disk: 1153 MB


    12) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    14) Connect the computer to the Internet using Ethernet or cat5e.
    Turn off wireless with a mechanical off if available.

    15) Uninstall both of these drivers:
    netwtw06.sys
    netwtw08.sys

    16) Continue using the computer with only Ethernet access

    17) For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

    If there are BSOD after steps 1 - 17 then advance to these steps

    18) To ensure that there are no improper bios settings please reset the bios.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computer’s CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    19) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    Download Speccy | Find your computer specs, free!
    Download Speccy | Find your computer specs, free!
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer

    20) Download and install IPDT:
    Download Intel(R) Processor Diagnostic Tool

    21) Post an image of IPDT results into the thread (test time is approximately 15 minutes)

    22) Run Prime95 - Stress Test Your CPU
    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
    Prime95 - Stress Test Your CPU
    a) Record the maximum temperature and post the maximum temperature into the thread
    b) Record test duration and post the uninterrupted test duration into the thread
    c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
    d) Use the Microsoft snipping tool to post images into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10

    23) Run Memtest86 version 8.2 (or newer version if available) for four passes.
    Repeat the test so that eight passes are performed.
    MemTest86 - Official Site of the x86 Memory Testing Tool
    Use a camera or smart phone camera to take pictures and post images into the thread.
    In case there are any problems uploading images use share links (one drive, drop box, or google drive)
    Memtest86 has a feature to produce a text report.
    Please post this in addition to the images.

    24) Run HD Tune (free version) (all drives)
    https://www.hdtune.com/
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    25) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    http://www.seagate.com/support/downl...ls-win-master/
    http://knowledge.seagate.com/article...S/FAQ/202435en

    26) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
    FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
    FurMark - GPU Stress Test
    Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
    a) Record the maximum temperature and post the maximum temperature into the thread.
    b) Record the test duration and post the uninterrupted test duration into the thread.
    c) Aim for testing 1 hour.
    d) Use the Microsoft snipping tool to post images into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10

    27) All of these tests should be done with the bios reset and no over clocking.

    28) For each of the above tests please record maximum temperatures.

    29) And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10


    Code:
    netwtw06	___ Intel(R) Wireless Adapter Driver for Windows 10 - 64 Bit	c:\windows\system32\drivers\netwtw06.sys	Kernel Driver	No	Manual	Stopped	OK	Normal	No	No
    Code:
    netwtw08	___ Intel(R) Wireless Adapter Driver for Windows 10 - 64 Bit	c:\windows\system32\drivers\netwtw08.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes
    Code:
    Name	[00000001] Intel(R) Wireless-AC 9462
    Adapter Type	Ethernet 802.3
    Product Type	Intel(R) Wireless-AC 9462
    Installed	Yes
    PNP Device ID	PCI\VEN_8086&DEV_A370&SUBSYS_02A48086&REV_10\3&11583659&0&A3
    Last Reset	23/08/2019 10:55 AM
    Index	1
    Service Name	Netwtw08
    IP Address	192.168.0.213, fe80::34ab:d9f3:e41a:132b, 2001:8003:6415:f400:a59a:cb09:d873:2415, 2001:8003:6415:f400:34ab:d9f3:e41a:132b
    IP Subnet	255.255.255.0, 64, 128, 64
    Default IP Gateway	192.168.0.1, fe80::a691:b1ff:fea9:ea8a
    DHCP Enabled	Yes
    DHCP Server	192.168.0.1
    DHCP Lease Expires	8/03/1933 6:53 AM
    DHCP Lease Obtained	8/03/1933 5:53 AM
    MAC Address	‪04:EA:56:B8:F2:18‬
    Memory Address	0xFE1FC000-0xFE1FFFFF
    IRQ Channel	IRQ 4294967289
    IRQ Channel	IRQ 4294967288
    Driver	C:\WINDOWS\SYSTEM32\DRIVERS\NETWTW08.SYS (21.30.1.1, 8.81 MB (9,237,496 bytes), 27/06/2019 9:46 PM)
    Code:
    Netwtw06     ___ Intel(R) Wireless  ___ Intel(R) Wireless  Kernel        Manual     Stopped    OK         FALSE       FALSE        2,945,024         4,546,560   0          8/06/2018 1:44:55 AM   C:\Windows\system32\drivers\Netwtw06.sys         8,192      
    Netwtw08     ___ Intel(R) Wireless  ___ Intel(R) Wireless  Kernel        Manual     Running    OK         TRUE        FALSE        2,961,408         4,886,528   0          24/06/2019 8:16:39 PM  C:\Windows\system32\drivers\Netwtw08.sys         8,192
    Code:
    Netwtw08.sys Mon Jun 24 03:16:39 2019 (5D10A307)
    Code:
    Event[1373]:
      Log Name: System
      Source: volmgr
      Date: 2019-08-23T10:49:50.107
      Event ID: 49
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-21JNGSL
      Description: 
    Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
    Last edited by zbook; 23 Aug 2019 at 00:13.
      My Computer


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

    Thanks for the quick and comprehensive reply. Here are steps 1 through 9. Will work through the rest and report as completed.

    Microsoft Windows [Version 10.0.18362.295]
    (c) 2019 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 but was unable to fix some of them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

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

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1


    Error: 87

    The online/cleanup-image/scanhealth option is unknown.
    For more information, refer to the help by running DISM.exe /?.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

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

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.295

    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.

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

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.295

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

    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.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    C:\Windows\system32>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    182528 file records processed.
    File verification completed.
    3113 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    183 reparse records processed.
    256766 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    183 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    37120 data files processed.
    CHKDSK is verifying Usn Journal...
    37056728 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    487722791 KB total disk space.
    68815500 KB in 125014 files.
    92576 KB in 37121 indexes.
    0 KB in bad sectors.
    301535 KB in use by the system.
    65536 KB occupied by the log file.
    418513180 KB available on disk.

    4096 bytes in each allocation unit.
    121930697 total allocation units on disk.
    104628295 allocation units available on disk.

    C:\Windows\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-21JNGSL\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.

    C:\Windows\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\Windows\system32>

    - - - Updated - - -

    Here are start up and recovery and virtual memory screenshots/snips

    I am currently zipping the memory.dmp file, it is 15gb so will take a little while.

    I will now switch to ethernet, delete drivers as instructed and continue normal operation of PC untill BSOD does or does not reoccur.
      My Computer


  4. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    The memory dumps can disappear if not immediately uploaded.

    The size displayed was 1.1 GB.

    The maximum size is 1.5 GB.
    Please do not upload 15 GB.

    The problem was the setting for startup and recovery system failure.

    Change complete memory dump to automatic memory dump.
    Reboot to maintain settings.



    Open administrative command prompt and copy and paste:

    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt

    Find the new text file on the desktop > post a share link into the thread.

    Search for
    C:\Windows\Logs\CBS\CBS.log > post a share link into the thread
      My Computer


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

    Sorry, I forgot I changed that earlier because I was using a program called whocrashedit to analyse the dump files, and it recommended switching to complete dump, or I misinterpereted it's instructions.

    So I should switch back to automatic memory dump, and reboot.

    Just to clarify, is this for future bsod memory dump file analysis? Or did the intial steps I took in command prompt (1-9) generate this file you would like to see? and if so , should I repeat them once switched back to automatic dump.

    Sorry if I am misinterpreting your instructions, this is all new territory to me and I don't really understand what I am doing here, just mimicing the instructions you give and uploading back to here.
      My Computer


  6. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    The changes to the startup and recovery are for any future BSOD.
    Automatic memory dumps will not include the user mode dump files and will include kernal dumps.
    Rebooting is necessary to maintain the automatic setting.
    It can be easy to miss BSOD if automatically restart is checked.
    The administrative prompt command already unchecked automatically restart.
    So any future BSOD should display a blue screen with bugcheck and : (
    Sometimes a driver can be seen in the form *.sys

    For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive


    Scannow had displayed corruption that was fixed by running the DISM commands.
      My Computer


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

    Ok understood.

    Here is the share link for sfcdetails and CBS files.

    BSOD win10 forum share - Google Drive
      My Computer


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

    There were known hash mismatch problems for Microsoft defender producing corruption when running scannow.
    This was confirmed in the logs.

    Code:
    2019-08-23 15:12:58, Info                  CSI    0000015e [SR] Repairing corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpComputerStatus.cdxml from store
    2019-08-23 15:12:58, Info                  CSI    00000160 [SR] Repairing corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreat.cdxml from store
    2019-08-23 15:12:58, Info                  CSI    00000162 [SR] Repairing corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatCatalog.cdxml from store
    2019-08-23 15:12:58, Info                  CSI    00000164 [SR] Repairing corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatDetection.cdxml from store
    2019-08-23 15:12:58, Info                  CSI    00000166 [SR] Repairing corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpPreference.cdxml from store
    2019-08-23 15:12:58, Info                  CSI    00000168 [SR] Repairing corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpScan.cdxml from store
    2019-08-23 15:12:58, Info                  CSI    0000016a [SR] Repairing corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpWDOScan.cdxml from store
    2019-08-23 15:12:58, Info                  CSI    0000016c [SR] Repairing corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpSignature.cdxml from store
    2019-08-23 15:12:58, Info                  CSI    0000016e [SR] Repairing corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\Defender.psd1 from store
      My Computer


  9. Posts : 15
    Windows 10 Pro x64
    Thread Starter
       #9

    Do you believe this to be the cause of the bsods and was it fixed with those commands?
      My Computer


  10. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #10

    Most of the time bugchecks 124 are caused by malfunctioning hardware.
    In the debugging there was a misbehaving driver.
    With the driver uninstalled there will be an evaluation period (the longer the better)(ideally a week).
    Then a second evaluation period after reinstalling a new driver.
    If there are no BSOD or unexpected shutdowns / restarts then the troubleshooting will be completed.

    If bugcheck 9C or 124 reappears with the driver removed then proceed with steps 17 onward.
      My Computer


 

  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 17:45.
Find Us




Windows 10 Forums