memory management bsod, windows 10

[MagnaTriDelts]

Reformatted my PC recently and got this blue screen of death error. The following is what shows up in the event viewer.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-07-16T08:41:01.554724000Z" />
<EventRecordID>1631</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>DESKTOP-8U1EUG6</Computer>
<Security />
</System>
- <EventData>
<Data Name="param1">0x0000001a (0x0000000000041792, 0xfffff6bffaf28940, 0x0004000000000000, 0x0000000000000000)</Data>
<Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
<Data Name="param3">aa6fc185-d302-4569-9b29-02965370664f</Data>
</EventData>
</Event>

Any advice would be appreciated.

 

[Colif]

can you do these 2 things:
1. Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

2. Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[MagnaTriDelts]

Thank you for the response.

1. Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 7/16/2017 1:39:24 AM 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 (0x41792, 0xFFFFF6BFFAF28940, 0x4000000000000, 0x0)
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.

2. As for this option, I did everything as stated in the link you provided but I do not have the file minidump show up in C/windows/minidump.

 

[MagnaTriDelts]

Most recent bsod.

1.On Mon 7/17/2017 5:37:22 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\071717-13390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xF7 (0x48C0CF8D70E52, 0x8C0CF8D70E52, 0xFFFF73F30728F1AD, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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.

2. Minidump link. https://drive.google.com/open?id=0By-Y6JC9XU4uNWtiV0FRSVZ4ZGc

 

[gardenman]

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

File: 071717-13390-01.dmp (Mon Jul 17 20:37:22.121 2017)
BugCheck: [DRIVER_OVERRAN_STACK_BUFFER (F7)] {48c0cf8d70e52, 8c0cf8d70e52, ffff73f30728f1ad, 0}
Probably caused by: ntkrnlmp.exe (Process: svchost.exe)

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

 

[johnbl]

I would check for bios and driver updates from the motherboard vendor
you will want to run memtest86 and confirm that the system is not having memory errors.

the problem was caused because of one single bit being wrong.