BSOD - memory_management, please help

Please run the tool in posting instruction as administrator. Otherwise, just simply upload all the content in minidump folder to us because I can't see any minidump files in the one you uploaded
upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

If you are using any program such as CCleaner, they may clean out your minidump folder, please double check that

Hi and Welcome to SF!

Because it is new PC, it's always good to eliminate hardware cause:
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes. (Exception code c000005)

Please enable driver Verifier:
Driver Verifier - Enable and Disable

BUGCHECK SUMMARY:

Code:

BugCheck 1A, {41790, fffffa8000c812d0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )

Followup: MachineOwner
---------
PROCESS_NAME:  MsMpEng.exe
BugCheck 3B, {c0000005, fffff960000e808f, fffff88003dcafd0, 0}

Probably caused by : win32k.sys ( win32k!xxxDestroyThreadInfo+6e7 )

Followup: MachineOwner
---------

Window Defender was the process running at the time of crash, try to disable it to see if it resolve the problem:
What is msmpeng.exe and how to remove it

Run system file check:

Open an elevated command prompt and enter sfc /scannow.

Let us know if you need help

Tuan

This crash happened because the system decremented the number of pte's in a page table, but the number was already 0 so there was an underflow to ffff, causing the bugcheck.

Driver verifier should be enabled doing DMA validation, as well as some memory manager changes so that the memory manager checks that a page is still zero before going to use a page from the zeroed list, to catch this:

Code:

Key:   HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Value: PageValidationFrequency
Type:  REG_DWORD
Data:  1

Key:   HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Value: PageValidationAction
Type:  REG_DWORD
Data:  1

Key:   HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Value: VerifyMode
Type:  REG_DWORD
Data:  2

Open a command prompt, and type "verifier /flags 0x80 /all", and then reboot.

If you start getting bugchecks after that, post them here - I am pretty certain this is going to be a hardware problem, but a PAGE_NOT_ZERO bugcheck would tell us for certain one way or the other if we can capture it.

Gnomicide said:

Running that memory test right now. Looks like it takes a while to do a few passes.

Is this something I need to keep my eye on or does it save a log somewhere that I can post later?

Don't worry about the SFC log.

Be sure to enable verifier: Driver Verifier - Enable and Disable

Have you enabled Driver Verifier? It will cause BSOD's when it stresses faulty drivers. Be sure to upload any BSOD's.