New PC randomly restarts with ‘Memory Management’ message on BSOD

Topic

New Reply

From the first day on, my newly assembled PC randomly crashed and restarted, with ‘Memory Management’ error message. I have followed all the advices I could find online, including checking the memory and updating the drivers, to no avail. Don’t know what to do anymore. Help please.
The event log:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 9/29/2013 7:32:56 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: PC2013
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:

41
2
1
63
0
0x8000000000000002

1365

System
PC2013

26
0x41790
0xfffffa800a71b7f0
0xffff
0x0
false
0

Thank you!

Reply | Quote

Replies

From the first day on, my newly assembled PC randomly crashed and restarted, with ‘Memory Management’ error message. I have followed all the advices I could find online, including checking the memory and updating the drivers, to no avail. Don’t know what to do anymore. Help please.

Welcome to the Forums!

By what means did you check the memory? A little more information about the rig could prove useful; motherboard specs, CPU, memory size and number of sticks, etc.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Welcome to the Forums!

By what means did you check the memory? A little more information about the rig could prove useful; motherboard specs, CPU, memory size and number of sticks, etc.

Hi Thanks for your reaction.
motherboard Asus z87-expert. bios version 1405 (up to date)
CPU Intel core i7 4770
memory corsair DDR3-1600 16G quad kit
OS windows 7 64bit
I scanned the memory with memotest86+ and CPU-Z but found no problem.

Reply | Quote

memory corsair DDR3-1600 16G quad kit

zy,

Hello… Try running just “two sticks” and see what “haps”. Also does the installed memory show up in BIOS?:cheers: Regards Fred

PS: If your only running with 2 …then try just one stick… Also make sure that there installed in the correct positions

Reply | Quote

How long did you run the memory tests? Multiple passes are often necessary.

You can also try removing the memory sticks in pairs. If the first pair runs without issue, replace them with the pair you removed. If you do produce an issue with either pair, then try one stick at a time to find out which stick is the problem.

And there is also the possibility that one of the memory slots might have an issue. Memory problems can sometimes be tedious to reduce to the actual culprit(s).

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

If I’m reading the error code correctly, it’s a bugcheck 0x26, which doesn’t tie in with your “‘Memory Management’ message on BSOD” description:

STOP 0x00000026: CDFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.

…

Cause
One possible cause of this bug check is disk corruption. Corruption in the file system or bad blocks (sectors) on the disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system’s ability to read and write to the disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Resolving the Problem

To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace).

To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

I think that with 16GB fitted, we can rule out the “nonpaged pool memory depletion problem”.

A collection of crash dumps and related data is needed to enable an analysis of the crashes, please carefully read and follow these instructions: http://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-death-bsod-posting-instructions-windows-8-7-vista.html and attach the required zip file to a reply back here – we’ll try to work out the likely cause.

Reply | Quote

If I’m reading the error code correctly, it’s a bugcheck 0x26, which doesn’t tie in with your “‘Memory Management’ message on BSOD” description:

I think that with 16GB fitted, we can rule out the “nonpaged pool memory depletion problem”.

A collection of crash dumps and related data is needed to enable an analysis of the crashes, please carefully read and follow these instructions: http://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-death-bsod-posting-instructions-windows-8-7-vista.html and attach the required zip file to a reply back here – we’ll try to work out the likely cause.

Thank you guys for your replies. With this post I attached the required files, as well as the minidump and system log from the latest crash.
Furthermore, below is a screen capture from my windows message after it restarted.

35019-message1

Reply | Quote

From what I can tell, it looks like ‘something’ is interfering with drivers/data loaded into memory, both crash dumps are the same type (MEMORY_MANAGEMENT 0x1a) and sub error:

Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.

2x Norton files are overlapped in the first crash “OVERLAPPED_MODULE: Address regions for ‘EX64’ and ‘ENG64.SYS’ overlap” and the crash seems to have been called by Norton. In the second crash, a fault had already been logged by Windows Error Reporting; WER recorded an error with a RADAR_PRE_LEAK in the Trusted Installer module 2 minutes before the crash.

I don’t see a known bad driver loaded that would be triggering this behaviour, but I do see some drivers I suspect may be involved, the Bluetooth hardware has a problem, there’s what I would call spyware installed, Norton Internet Security may be clashing with Windows’ own firewall as well. Lets try to deal with those issues and see if it helps.

iMesh music toolbar – uninstall it, section #4: http://support.imesh.com/index.php?/Knowledgebase/Article/View/28/0/uninstall–install

Uninstall all ASUS utility (ie: anything ASUS that’s not hardware drivers).

Uninstall Norton fully, after a reboot, use their tool to ensure it’s all gone and use MSE during testing: http://windows.microsoft.com/en-us/windows/security-essentials-download and check that Windows firewall is turned on.

Update the Atheros AR9462 Bluetooth driver: http://www.atheros.cz/atheros-bluetooth-drivers.php

I’m unsure whether the PC is using the correct SATA chipset(s) drivers, I’m seeing too many SATA/SAS drivers loaded; can you post a screenshot of the Disk Manager section so we can checkout the disk partitioning/Boot/System scheme?

WER also reported a problem with MemDiag at boot, both crashes happened within 5 minutes of boot.

Overall, I’m really not sure what could be causing this but malware would be high on my list of possibilities.

Reply | Quote

I’m unsure whether the PC is using the correct SATA chipset(s) drivers, I’m seeing too many SATA/SAS drivers loaded; can you post a screenshot of the Disk Manager section so we can checkout the disk partitioning/Boot/System scheme?
[/B].

Thanks Satrow. I will go try out your suggestions.

In the meantime I post the screenshot of the Disk Manager.
35037-diskManagement

Reply | Quote

Ok, the drive layout looks normal, I don’t think we should ‘mess’ with any extraneous HDD adapter drivers at this stage, I don’t see them as being relevant to the current problem.

I think a another 7+ full runs of MemTest86+, booted from a CD/USB drive is on the cards; if this is a recently bought PC (still under warranty), it may be better not to open the case and remove/swap sticks around and to continue testing them all together. Details here: http://carrona.org/memdiag.html Do this overnight or while you’re at work/college or whatever – it’s likely to take a few hours.

Reply | Quote

Hi zy_18, I experienced a similar problem with a customers new desktop. Ran MemTest86+ test for 5hrs which didn’t return a fault ?? Not unusual ! However the BSOD was pointing to a memory fault. So I returned it to the store under warranty with my notes, not once but 3 times. It was frustrating, but I had no doubt it was the memory chip or chips causing the BSOD.

The store tech finally accepted my diagnosis that is was a memory fault & swapped the DDR3 chips for a new set & problem solved. It could have also been a MOBO track or Mem socket fault, but in my case it was a chip problem.

Don’t mess with it. If it’s under warranty, don’t void your warranty by opening it or breaking the stores seals. take it back to the store.

gluk

Reply | Quote