Memory Management BSOD, Windows 10, only occurs when playing a game for a while.

[warpapa]

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. I'm pretty positive it isn't a thermal issue:

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

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

So from what I've gathered, it is very likely a driver issue?

Here's what I get in whocrashed:

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. [/code]



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. [/code]



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 have an automatic windows memory dump too from one of the crashes.

https://1drv.ms/u/s!Ao0fe1t2z7I-pAK9XE5Jfjayumir

I don't know if there's anything else I can give. If so, please just tell me!

Thank you for any help. 🙁

EDIT 12:30 PM 8/3:

Just got another BSOD.
This time, it read 'System Thread Exception Not Handled,' and this is the whocrashed log for it:
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.

 

[Colif]

Memory management can be drivers or ram, who crashed is just blaming the kernel as that is what crashed, but normally not what caused the problem. I can't read dumps myself but a few around here can.

What are specs of PC?

You can download and run memtest86 to create a USB that you can boot PC using and check ram sticks, 1 stick at a time. The only error count you want is 0, Any higher and you need to remove/replace stick.

run tests while you wait for an answer

 

[warpapa]

Memory management can be drivers or ram, who crashed is just blaming the kernel as that is what crashed, but normally not what caused the problem. I can't read dumps myself but a few around here can.

What are specs of PC?

You can download and run memtest86 to create a USB that you can boot PC using and check ram sticks, 1 stick at a time. The only error count you want is 0, Any higher and you need to remove/replace stick.

run tests while you wait for an answer

MOBO: MSI B350 Gaming Pro
GPU: EVGA GTX 1060 6GB
CPU: Ryzen 5 1600
RAM: CORSAIR Vengeance LPX 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 2400 (PC4 19200) Desktop Memory Model CMK16GX4M2A2400C16R

If you need any other specs I will post!

Are all flashdrives bootable? I have an old unopened USB stick from like... 2010. I guess I can try it at least and figure that out!

 

[Colif]

i think you can make all bootable. the program itself will format the drive for you

 

[gardenman]

I downloaded 801mb memory dump and ran it through the debugger and got the following information: https://pastebin.com/Qt5J3BVk

There seems to be either some corruption in the dump file, or the debugger just didn't read it correctly. I deleted the vast majority of errors listed in the text but left a few to show how bad it was.

Maybe johnbl or someone else will show up and provide more information, I can only give you the basics from the debugger.

I can't help you with this, wait for Colif or someone else to reply. Good luck.

 

[warpapa]

I downloaded 801mb memory dump and ran it through the debugger and got the following information: https://pastebin.com/Qt5J3BVk

There seems to be either some corruption in the dump file, or the debugger just didn't read it correctly. I deleted the vast majority of errors listed in the text but left a few to show how bad it was.

Maybe johnbl or someone else will show up and provide more information, I can only give you the basics from the debugger.

I can't help you with this, wait for Colif or someone else to reply. Good luck.

Thanks for trying, Gardenman.

General update: I've gotten two more errors; seems that I'm getting a whole slew of them today.

IRQL Not Less or Equal just popped up, and earlier I got a 'System Service Exception' with a fltmgr.sys.

Part of me is just tempted to do another clean install of Windows and see if that'd help. I'm not sure how to avoid automatically downloading all drivers, though... and if that'd stop from downloading necessary wifi drivers if I did stop that.

Here's the latest whocrashed for the most recent BSOD, anyway.

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.

A friend suggested I change my memory dumps to small memory dumps or something like that and I did so. I'll just link all four of the recent crashes here, just incase someone does come around. Gonna run memtest tonight once I'm getting ready for bed.

https://1drv.ms/f/s!Ao0fe1t2z7I-pAndd88aklPAJ4Xa

 

[gardenman]

Hi, I ran the dump file(s) through the debugger and got the following information: https://pastebin.com/LPrFqMfu

Spoiler

File: 080317-20375-01.dmp (Thu Aug 3 15:59:56 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)] {ffff9a8376f2cb00, ff, 0, fffff80184afe53e}
Probably caused by: memory_corruption (Process: svchost.exe)

File: 080317-20609-01.dmp (Thu Aug 3 12:26:36 2017)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)] {ffffffffc0000005, fffff8020a870440, ffffd000c8fe1128, ffffd000c8fe0960}
Probably caused by: memory_corruption (Process: NVDisplay.Cont)

File: 080217-14734-01.dmp (Wed Aug 2 15:19:20 2017)
BugCheck: [MEMORY_MANAGEMENT (1A)] {41793, ffffc580c496f770, 1f, 1e}
Probably caused by: memory_corruption (Process: chrome.exe)

File: 080217-15171-01.dmp (Wed Aug 2 23:00:16 2017)
BugCheck: [MEMORY_MANAGEMENT (1A)] {41289, 7ffab39b2000, 1578, 7dfab39b2205}
Probably caused by: memory_corruption (Process: chrome.exe)

I can't help you with this. Wait for Colif or someone else to reply. Good luck.

 

[Colif]

at least this one isn't full of error messages... i looked at other and half the thing is errors

Update your Intel WiFi adapter drivers if you can, I have seen Netwbw02.sys cause errors already this week.
Update Razer drivers
update Realtek LAN drivers

there is one more BIOS since your version - this might help with memory management as its description is

- Improved memory compatibility.
- Updated AGESA Code 1.0.0.6
- Support PCI Lan wake up function.

https://www.msi.com/Motherboard/support/B350M-GAMING-PRO.html

 

[warpapa]

Tentatively seems the BIOS update has fixed all my problems... I'll monitor it for the next day or two; thank you, though, Colif and Gardenman! 😀