BSOD Memory_Management 0x0000001A

uglistix · 06 Sep 2013

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 · 11 Sep 2013

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 · 11 Sep 2013

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.

Code:

**************************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: BAD_POOL_HEADER (19)
 
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`

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

uglistix · 15 Sep 2013

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 · 21 Sep 2013

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 · 21 Sep 2013

Code:

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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

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

RAM - Test with Memtest86+

Tip

Pay close attention to Part 3 of the tutorial "If you have errors"
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.