Share via

Blue screen while gaming. Memory Management error.

Anonymous
2020-07-28T16:00:29+00:00

Hi,

While gaming or at random instances my laptop randomly shows a blue screen and the error is memory management.

While looking up ways to fix the issue I have done the following (with output):

  1. Ran windows memory diagnostics - The Windows Memory Diagnostic tested the computer's memory and detected no errors.
  2. SFC /scannow -

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.

  1. CBS Logs: Logs

2020-07-28 21:05:06, Info                  CSI    0000020e Hashes for file member [l:9]'Flash.ocx' do not match.

 Expected: {l:32 ml:33 b:0eeb61b1afd134e3e5e24d31186eaed84d54386279e3bec415a84ab244e7cfa7}.

 Actual: {l:32 b:a78d434e84d9ca42c82d0b275cf24f3c8c6add258203900ef748bf35af347932}.

2020-07-28 21:05:06, Info                  CSI    0000020f [SR] Cannot repair member file [l:9]'Flash.ocx' of Adobe-Flash-For-Windows, version 10.0.18362.901, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2020-07-28 21:05:06, Info                  CSI    00000210 Hashes for file member [l:9]'Flash.ocx' do not match.

 Expected: {l:32 ml:33 b:a587ade3f983b57175b267938b54e4bdb681f25a927f5d8c2465c962c8fb4cb0}.

 Actual: {l:32 b:a78d434e84d9ca42c82d0b275cf24f3c8c6add258203900ef748bf35af347932}.

2020-07-28 21:05:06, Info                  CSI    00000211 [SR] Cannot repair member file [l:9]'Flash.ocx' of Adobe-Flash-For-Windows, version 10.0.18362.901, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2020-07-28 21:05:06, Info                  CSI    00000212 Hashes for file member [l:9]'Flash.ocx' do not match.

 Expected: {l:32 ml:33 b:a587ade3f983b57175b267938b54e4bdb681f25a927f5d8c2465c962c8fb4cb0}.

 Actual: {l:32 b:a78d434e84d9ca42c82d0b275cf24f3c8c6add258203900ef748bf35af347932}.

2020-07-28 21:05:06, Info                  CSI    00000213 [SR] Cannot repair member file [l:9]'Flash.ocx' of Adobe-Flash-For-Windows, version 10.0.18362.901, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2020-07-28 21:05:06, Info                  CSI    00000214 [SR] This component was referenced by [l:74]'Package_2_for_KB4561600~31bf3856ad364e35~amd64~~10.0.1.1.4561600-2_neutral'

2020-07-28 21:05:07, Info                  CSI    00000215 Hashes for file member [l:9]'Flash.ocx' do not match.

 Expected: {l:32 ml:33 b:a587ade3f983b57175b267938b54e4bdb681f25a927f5d8c2465c962c8fb4cb0}.

 Actual: {l:32 b:a78d434e84d9ca42c82d0b275cf24f3c8c6add258203900ef748bf35af347932}.

2020-07-28 21:05:07, Info                  CSI    00000216 [SR] Could not reproject corrupted file ??\C:\Windows\SysWOW64\Macromed\Flash\Flash.ocx; source file in store is also corrupted

2020-07-28 21:05:07, Info                  CSI    00000217 Hashes for file member [l:9]'Flash.ocx' do not match.

 Expected: {l:32 ml:33 b:0eeb61b1afd134e3e5e24d31186eaed84d54386279e3bec415a84ab244e7cfa7}.

 Actual: {l:32 b:a78d434e84d9ca42c82d0b275cf24f3c8c6add258203900ef748bf35af347932}.

2020-07-28 21:05:07, Info                  CSI    00000218 [SR] Cannot repair member file [l:9]'Flash.ocx' of Adobe-Flash-For-Windows, version 10.0.18362.901, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2020-07-28 21:05:07, Info                  CSI    00000219 [SR] This component was referenced by [l:74]'Package_1_for_KB4561600~31bf3856ad364e35~amd64~~10.0.1.1.4561600-1_neutral'

2020-07-28 21:05:07, Info                  CSI    0000021a Hashes for file member [l:9]'Flash.ocx' do not match.

 Expected: {l:32 ml:33 b:0eeb61b1afd134e3e5e24d31186eaed84d54386279e3bec415a84ab244e7cfa7}.

 Actual: {l:32 b:a78d434e84d9ca42c82d0b275cf24f3c8c6add258203900ef748bf35af347932}.

2020-07-28 21:05:07, Info                  CSI    0000021b [SR] Could not reproject corrupted file ??\C:\Windows\System32\Macromed\Flash\Flash.ocx; source file in store is also corrupted

2020-07-28 21:05:07, Info                  CSI    0000021c [SR] Repair complete

2020-07-28 21:05:07, Info                  CSI    0000021d [SR] Committing transaction

2020-07-28 21:05:07, Info                  CSI    0000021e Creating NT transaction (seq 1)

2020-07-28 21:05:07, Info                  CSI    0000021f Created NT transaction (seq 1) result 0x00000000, handle @0x948

2020-07-28 21:05:07, Info                  CSI    00000220@2020/7/28:15:35:07.299 Beginning NT transaction commit...

2020-07-28 21:05:07, Info                  CSI    00000221@2020/7/28:15:35:07.304 CSI perf trace:

CSIPERF:TXCOMMIT;4220

2020-07-28 21:05:07, Info                  CSI    00000222 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

2020-07-28 21:05:17, Info                  CBS    Maint: idle processing paused

Looks like something with Adobe flash. I looked up what to do as mentioned in this article - https://www.wintips.org/fix-dism-source-files-could-not-be-found-windows-10-8/ 

DISM /Online /Cleanup-Image /RestoreHealth - Source files do not exist error.

I had done all the steps mentioned in the above article but it all ends up with source file do not exist error. 

DISM LOGS - DISM LOGS

Please Help.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2020-07-29T12:06:32+00:00

    Hi,

    Thank you for writing to Microsoft Community Forums.

    I understand that you receive Blue Screen error while playing games. I’ll certainly assist you with the issue.

    However, please let us know:

    As per the description, if the SFC scan fails, it is possible that the system files are corrupted and we will need to perform a repair installation on the computer. However, before proceeding with a repair installation, please share the dump files so that we can analyze them and get to the root cause of the issue. To share the files Navigate to C:\Windows\Minidump, upload the files to OneDrive and share the OneDrive link.

    Ideally, the best way to troubleshoot Blue Screen error is to boot the computer into Safe Mode, which will help in determining whether the issue is caused by a third party service/driver. However, as you have mentioned that you are receiving the Blue screen error while playing games, we cannot boot the computer into Safe Mode, since most of the games will not run in Safe Mode.

    Let us try other alternate solutions and check if that helps in resolving the issue.

    I would suggest you to perform a clean boot on the computer, and then try playing the games and check if you receive Blue Screen error.

    Performing a clean boot will start the computer with minimal set of drivers and programs, to determine whether a background program is causing the issue. Some of the Startup programs will not load after performing a clean boot on the computer. However, that functionality will return when you reset the computer to start normally after finishing the troubleshooting.

    To perform a clean boot on the computer refer to the article How to perform a clean boot in Windows.

    If performing a clean boot fixes the issue then, please refer to the section How to determine what is causing the problem after you do a clean bootto check which program is causing the issue.

    Note: Please refer the section Reset the computer to start normally after clean boot troubleshootingto boot the computer in to normal mode after troubleshooting.

    You may also want to refer the steps in the article Troubleshoot blue screen errors.

    Update Display driver:

    You may try updating the display driver and check if that makes a difference.

    Please refer the steps mentioned below to update display drivers:

    1. Press Windows logo key + X, and select Device Manager.
    2. Expand Display adapters.
    3. Right click on the display driver and select Update Drivers.
    4. Restart the computer if prompted.

    Article for reference: Update drivers in Windows 10.

    Adjust for best Performance:

    1. In the search box on the taskbar, type performance, then select Adjust the appearance and performance of Windows in the list of results.
    2. On the Visual Effects tab, select Adjust for best performance > Apply.
    3. Restart your PC and see if that speeds up your PC.

    We await your response.

    Regards,

    Nikhar Khare

    Microsoft Community - Moderator

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-08-06T13:50:06+00:00

    Hi Nikhar,

    Thanks for the swift response. 

    Please find the minidumps link below. It was taken after the last crash that had happened around 18:30 on August 6th.

    https://1drv.ms/u/s!ApjrJYnz0SpKgxR8WhGABe5fgE4i?e=PLy7SG

    The memory management Blue screen also happens randomly while using the computer. It happens more often while gaming.

    To answer your other queries,

    • Does the issue occur only while playing games? No. It can occur at random. More often while gaming.
    • What is the make and model of the computer? HP Omen - 17 an051na
    • Which build version of Windows 10 is installed on the computer? Windows 10 HOME, Version: 1909, OS Build: 18363.997

    I had updated drivers, also reinstalled them. I have also adjusted for best performance.

    Please help.

    Was this answer helpful?

    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more