BSOD Memory_Management 0x0000001A

[uglistix]

Hi all,

I've been experiencing numerous BSOD on a new build Zotac ID90 running Windows 7. The BSOD message is always "MEMORY_MANAGEMENT" leading me to suspect that this may be an indication of faulty RAM. I'm about to run a series of memtest86+ tests but wondered if anyone can spot anything else in the various files from the SF Diagnostic tool (attached).

I might just be imagining this, but it does feel like it occurs most often when I am either heavily using Photoshop or whilst resuming from hibernation.

Any help would be appreciated.

Thanks!

John

System: Zotac ID90 Bare Bones
Memory: Crucial 16Gb Kit: CT2KIT102464BF160B
HDD: OCZ Vertex 4 256GB SSD

 

[koolkat77]

Most of your bugchecks show 1A Memory Management.
Please first start with testing RAM.
------------------------
Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to Part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
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.
Arg2: fffffa8000a46580
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f31d40 to fffff80002ec0b80

STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35084
fffff800`02f31d40 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51db806a

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

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

 

[uglistix]

Thanks for the quick response. I'll get the machine running some tests overnight and report back with my findings.

 

[uglistix]

I'm 9 hours into testing and it has successfully completed 2 passes. I see that the guide says I need at least 7 passes - do these need to be completed in one go? Or can they be done in batches? I'm just wondering whether I can stop the testing and use the PC today and then resume testing this evening... and do the same tomorrow, etc until I have 7 passes?

 

[Britton30]

All 7 passes need to be done in one session. The reason is because each successive pass uses a different set of data it reads and writes to the RAM. Many times errors, if any, don't show until the 6th or 7th pass.

Beside RAM other memory could be at fault, the CPU cache or graphics memory. Does the Zotac use only the Intel on chip graphics? If so, check your BIOS to see if you can allocate more RAM to the IGPU, Integrated Graphics Processing Unit.

I have 16GB 2133 RAM and memtest takes a bit over 8 hours to run 7 passes. You could contact Corsair about the issues as well, you have to create an account to do it though. http://corsair.force.com/ I don't know your location, this is the US.
If you are still in the return time for the RAM you can ask for a replacement too.

 

[uglistix]

It took 24 hours, but I have now completed 8 passes with no errors...

Zotac do use the onboard graphics and in the bios there are a few options for setting the memory usage. Currently "DVMT 5" memory usage is preallocated 256M and is allowed to go up to 256M. So it looks a little bit constrained.

Shall I set this to pre-allocate the maximum of 1024M and allow it to use "Max"?

 

[uglistix]

I changed the memory usage of the onboard graphics to prellocate 1024M and to use "Max" as per my previous post. However the csystem has already crashed again with the same BSOD - so I'm guessing that hasn't solved the problem.

Any ideas on the next steps?

Thanks,
John

 

[koolkat77]

Upload the new reports

 

[uglistix]

Latest reports from the SF Diagnostic tool attached.

 

[koolkat77]

Reduce the start-up items, Antivirus software is basically whats required.

• Remove Startup Programs in Windows 7
• Clean Startup in Windows 7

------------------------
Follow these-

Get rid of intel rapid storage.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

------------------------
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow - read here

Run Disk Check on your Hard Drive for file system errors and bad sectors on it - read here
------------------------
Upload a screenshot using:

• CrystalDiskInfo:tip: For how to upload a screenshot or file, read here

Test your Hard Drive(s) by running:

• Hard Drive Diagnostic Procedure

------------------------
Test your Hardware for Stability and Heat Problems with Prime95:

• Stress Test With Prime95

------------------------
How to Stress Test a Video Card with Furmark:

• Video Card - Stress Test with Furmark

------------------------
Test your CPU Stability with IntelBurnTest:

• CPU - Stress Test Using IntelBurnTest

Monitor hardware temperature with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:

• Piriform - Speccy
• CPUID - HWMonitor

 

[uglistix]

Looks like I have some homework for the weekend! Thanks - I'll work through these steps over the weekend and report back when done.

 

[uglistix]

Ok - so I worked through the list.

1. I removed a few non-essential items from the startup programs.

2. I wasn't able to verify that I had "Intel Rapid Storage". I was a bit loathe to remove the "items under disc drives" because this included my main drive - the SSD! So I haven't completed this step...

3. Checked with OCZ and I have the latest firmware according to their SSD Util tool. My bios version was already up to date. I ran Intel's Inf checking tool and it suggested only two drivers needed updating - the Graphics HD 4000, Centrino Wireless-N 135. Both of these are now up to date. I also noticed the Realtek ethernet drivers were out of date - so I updated these.

4. I ran the System File Checker. It did not find any "Integrity Violations"

5. I ran the Disk Checker (both boxes ticked). As I only have one drive it scheduled the job for the next reboot. After rebooting it ran the checks and did not find any issues.

6. I ran the GPU stress testing until the temperatures stopped rising (note that Furmarker wasn't able to display the temps - I had to install another app to monitor this!). Temperatures stopped rising at 71C after abour 15 minutes.

I then had to take a break from testing the PC as my wife needed it back (she uses it for her photography business). Whilst she was using it she got a new BSOD message - something about "Bad Pool Header". I'm not sure if this is related to the original Memory Management BSOD or if this is something new that I've somehow introduced with all the dirver updates?!

I've attached the latest output from the SF Diagnostic tool.

Thanks!

 

[koolkat77]

Please update the drivers below.

SiLib.sys Wed Feb 7 05:13:54 2007 ~ USBXpress Development Kit
Driver Reference Table - SiLib.sys

DSI_SiUSBXp_3_1.sys Wed Feb 7 05:15:34 2007 ~ Garmin ANT wireless USB stick
Driver Reference Table - DSI_SiUSBXp_3_1.sys
------------------------
To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

------------------------
Reduce the start-up items, Antivirus software is basically whats required.

• Remove Startup Programs in Windows 7
• Clean Startup in Windows 7

[FONT="Lucida Console"]**************************Wed Sep 11 01:49:07.612 2013 (UTC + 6:00)**************************
Loading Dump File [C:\Users\Usra\091013-5397-01.dmp]
 
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
 
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
 
System Uptime: 3 days 22:50:31.472
 
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
 
Probably caused by : ntoskrnl.exe ( nt+75b80 )
 
BugCheck 19, {21, fffff8a0000f5000, 2530, 2520}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000019]BAD_POOL_HEADER (19)[/url]
 
Arguments: 
Arg1: 0000000000000021, the data following the pool block being freed is corrupt.  Typically this means the consumer (call stack ) has overrun the block.
Arg2: fffff8a0000f5000, The pool pointer being freed.
Arg3: 0000000000002530, The number of bytes allocated for the pool block.
Arg4: 0000000000002520, The corrupted value found following the pool block.
BUGCHECK_STR:  0x19_21
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`[/FONT]

If the bsods continue enable driver verifier.
------------------------
Enable Driver Verifier to see if it catches any misbehaving driver:

• :tip: Driver Verifier - Enable and Disable
• :info: Using Driver Verifier to identify issues with Drivers

 

[uglistix]

Thanks. Both of the drivers highlighted are installed as part of Garmin's ANT+ USB stick. I went to Garmin's website and they didn't have any updated drivers. ANT's website seemed to be for developers and I couldn't find any USB drivers that weren't part of a full blown SDK. Whilst I was searching for the drivers I started the Garmin software so that I could try the "Check for Updates" option and within a few seconds of starting it I got the memory management BSOD. This happened twice! So I decided to completely remove all ANT and Garmin software and drivers as I don't really need it on this computer anyway.

I removed another 4 or 5 items from the start up - including Sandboxie, Onenote, Power ISO.

There were another 30 or so "important" updates from Windows which I have now installed.


I'll keep an eye on the system and post back with an update in a few days.

Thanks!

 

[uglistix]

The system had been working fine for the last few days - but then today I got 2 of the memory management BSOD within a few minutes of each other. Each time it was about 30 seconds after I had started to transfer some photos of a memory card (memory card plugged in via the USB 3.0 port). I was eventually able to transfer the files successfully using a USB 2.0 port.

Once again I've attached the SF Disagnostic files.

 

[koolkat77]

[FONT="Lucida Console"]Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sat Sep 21 20:01:55.441 2013 (UTC + 6:00)
System Uptime: 0 days 0:05:45.300
BugCheck 1A, {41790, fffffa8000c5ff10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sat Sep 21 19:54:58.555 2013 (UTC + 6:00)
System Uptime: 5 days 18:01:48.427
BugCheck 1A, {41790, fffffa80007ebf10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

------------------------
Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to Part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.