BSOD: Memory Management Error, No Dump?

Alakeram

Prominent
Feb 28, 2017
19
0
520
Okay so I've read probably about 60 or so different threads relating this issue, and NONE have helped, first a little intro to the issue.

Day 1: got parts, build my computer (only thing old on my computer right now is a Samsung SSD 256gb, 1tb western digital HD(I think?? I can't remember right now) and a GTX970TI which is only around 4 months old) just put in a MSI Z170A Carbon Pro Motherboard, with a I7 6700K CPU, 32gb of DDR4 ram (Corsair Vengeance 4 pack of 8gb) and a new Modular Power Supply HX750i. Booted up the computer everything ran smooth, did some benchmarking to test it, no issues. did some stress testing no issues. left the computer on for 12 hours no issues.

Day 2: Started computer up, played about 10 hours or so of some games, watched some videos the usual no issues. shut off my computer for the day (cause I got liquid cooling hooked up and don't wanna risk anything unless I'm home to save it, aka went to work)

Day 3: Came home from work, booted up computer friends yelled at me to play some games with them as SOON as I started the game up it crashed instantly.... with BSOD Memory Management...

looked around on here and a bunch of other sites with similar issues, tried all that was recommended and nothing worked, so I think my issue is way different.... so here I am asking for help (also newly registered but I always lurk these forums so much good info here)

I've ran windows memory test no issues (didn't bother with memtest84 or whatever its called) seeing as I highly doubt its my memory (some people will tell me I still got faulty memory, I've seen faulty memory and this is not the case)

the ONLY thing I can think of that was done differently was I had to upgrade to windows pro (upgrading my system invalidated my windows 10 copy so I had to buy a windows 10 pro copy cause I couldn't remember/find my windows 7 code)

and maybe my motherboard??? cause I've noticed (compared to my other computer which is way more older) it boots really slow, which has been like that since I built this computer... (counted the load time to be 2 mins 10 seconds to get to desktop) and people will probably tell me its my hd but my OS is on a SSD so that's not the issue

(old computer booted up in 15 seconds to desktop)

so please help me! i'm losing my damn mind!
and thanks for any and all help!

(forgot to mention when I BSOD it doesn't give me a memory dump file.... and I have it enabled... so no idea what the BSOD code is... or whats crashing it....)

Update: also forgot to mention that I had a different error yesterday messing with settings saying something like memory_readonly something like that... I searched that up yesterday and found pretty much nothing on it... it only happened once though.
 
Solution
Do you have latest BIOS? And/or sata/chipset drivers from MSI Web site? Can just run MSI Live Update 6 to confirm drivers, I wouldn't use it to update BIOS though (don't need win 10 crashing half way through that process).

How come you are sure its not your ram without running memtest86? I would run it and get a 2nd opinion.

Common causes of memory management error are drivers, ram or possibly hdd. Shame you get no dumps as its one of the few BSOD where the parameters are set values in 1 field.. can tell us more. If PC is freezing its hard for it to create a dump though.

Alakeram

Prominent
Feb 28, 2017
19
0
520
I don't like bumping threads... but I'm kinda desperate... also not sure if I posted this under the right area... seeing as I have no idea whats causing this lol..
 

Colif

Win 11 Master
Moderator
Do you have latest BIOS? And/or sata/chipset drivers from MSI Web site? Can just run MSI Live Update 6 to confirm drivers, I wouldn't use it to update BIOS though (don't need win 10 crashing half way through that process).

How come you are sure its not your ram without running memtest86? I would run it and get a 2nd opinion.

Common causes of memory management error are drivers, ram or possibly hdd. Shame you get no dumps as its one of the few BSOD where the parameters are set values in 1 field.. can tell us more. If PC is freezing its hard for it to create a dump though.
 
Solution

Alakeram

Prominent
Feb 28, 2017
19
0
520


Lol as soon as I saw this my computer crashed with a isql not equal or greater bsod.... not sure if it's related but my graphics card fan ain't running... it's also a msi brand
 

Colif

Win 11 Master
Moderator
irq errors are driver errors normally or can be ram as well. or motherboard/CPU but that is rare. My guess is its all caused by a driver

did you change your page file size as you should be getting some dump files?

If you are getting dumps, 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 :)

970ti fans may not run until its at a certain temp, I know my 980 fan won't run unless GPU is at 40C
 

Alakeram

Prominent
Feb 28, 2017
19
0
520
Okay so I finally got some DUMPs on the memory management, not sure how to post it....

Crash List

Created by using BlueScreenView
Dump File
Crash Time
Bug Check String
Bug Check Code
Parameter 1
Parameter 2
Parameter 3
Parameter 4
Caused By Driver
Caused By Address
File Description
Product Name
Company
File Version
Processor
Crash Address
Stack Address 1
Stack Address 2
Stack Address 3
Computer Name
Full Path
Processors Count
Major Version
Minor Version
Dump File Size
Dump File Time
022817-40921-01.dmp
2/28/2017 5:13:20 PM
MEMORY_MANAGEMENT
0x0000001a
00000000`00041201
ffff8600`99d12ec8
00000000`000002ad
ffffa480`6dbe9490
ntoskrnl.exe
ntoskrnl.exe+14a6f0
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
10.0.14393.693 (rs1_release.161220-1747)
x64
ntoskrnl.exe+14a6f0
 
 
 
 
C:\WINDOWS\Minidump\022817-40921-01.dmp
8
15
14393
399,052
2/28/2017 5:19:32 PM
022817-43687-01.dmp
2/28/2017 5:04:34 PM
MEMORY_MANAGEMENT
0x0000001a
00000000`00041792
fffff23f`fcad6240
00000000`00000004
00000000`00000000
ntoskrnl.exe
ntoskrnl.exe+14a6f0
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
10.0.14393.693 (rs1_release.161220-1747)
x64
ntoskrnl.exe+14a6f0
 
 
 
 
C:\WINDOWS\Minidump\022817-43687-01.dmp
8
15
14393
494,212
2/28/2017 5:07:26 PM
022817-45531-01.dmp
2/28/2017 5:51:32 PM
IRQL_NOT_LESS_OR_EQUAL
0x0000000a
ffffcf8c`f73f0000
00000000`00000002
00000000`00000001
fffff801`893ea940
ntoskrnl.exe
ntoskrnl.exe+14a6f0
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
10.0.14393.693 (rs1_release.161220-1747)
x64
ntoskrnl.exe+14a6f0
 
 
 
 
C:\WINDOWS\Minidump\022817-45531-01.dmp
8
15
14393
546,060
2/28/2017 5:53:59 PM
022817-46125-01.dmp
2/28/2017 8:07:14 PM
MEMORY_MANAGEMENT
0x0000001a
00000000`00041201
ffffa501`30984ec0
00000000`00000057
ffff8009`5e260eb0
ntoskrnl.exe
ntoskrnl.exe+14a6f0
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
10.0.14393.693 (rs1_release.161220-1747)
x64
ntoskrnl.exe+14a6f0
 
 
 
 
C:\WINDOWS\Minidump\022817-46125-01.dmp
8
15
14393
525,772
2/28/2017 8:09:58 PM
022817-46859-01.dmp
2/28/2017 6:56:42 PM
MEMORY_MANAGEMENT
0x0000001a
00000000`00041201
ffffe000`007f9fc8
00000000`0000008d
ffff830b`a1569f70
ntoskrnl.exe
ntoskrnl.exe+14a6f0
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
10.0.14393.693 (rs1_release.161220-1747)
x64
ntoskrnl.exe+14a6f0
 
 
 
 
C:\WINDOWS\Minidump\022817-46859-01.dmp
8
15
14393
530,116
2/28/2017 6:59:33 PM

that was the best way I could paste it... lol, but seems to be related to windows?
 

Alakeram

Prominent
Feb 28, 2017
19
0
520
well.... colif you were right... I just didn't wanna admit that BRAND NEW memory would piss that hard.... ALL 4 STICK!!!!!!!!!! are screwed... sending back for new ones now...

ran tests on all at one time, and then again individually... and all of them came back with 68887+ errors........... wow.

note to self: test memory before using it from now on...
 

Colif

Win 11 Master
Moderator
ntoskrnl = new technology operating system kernel - brains of windows. It does a lot of things though, both memory management & driver requests so it doesn't offer a great clue

Memory management Parameter 1 - 0x41792 - A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE.

think its a driver cauing it, its just causing the PC to crash on the windows side of transaction and blaming ntoskrnl

Read the instructions and run driver verifer - its built into windows and is designed to test drivers. It will crash so I suggest you run bluescreenview afterwards and see if it mentions a driver name