Windows 7 BSOD "MEMORY_MANAGEMENT" Error

[Adam Jarvis]

Hi guys/girls!
I started to get this BSOD error this evening, and it appears to happen every 30, maybe 40 mins when I'm doing something on the PC. I've looked at a few other threads to see if any fixes would help there but I still have them pop up & restart my PC. I will say that almost all of the components are new (Graphics Card, RAM, CPU etc) so I'm really confused on what's happened.

I've added the CPU-Z & Other files required, if there's anything else I need to do, just ask & I hope to speak soon & hope the problem is fixed!

Thanks, Adam.

 

[Trouble]

Five out of the six indicating "Memory Management" as the issue.
DUMP:

BugCheck 1A, {41790, fffffa80019d8320, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
Followup: MachineOwner
[COLOR=#ff0000][U][B]MEMORY_MANAGEMENT (1a)[/B][/U][/COLOR]
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80019d8320
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002f35150 to fffff80002ec5c40
STACK_TEXT:  
fffff880`0500f828 fffff800`02f35150 : 00000000`0000001a 00000000`00041790 fffffa80`019d8320 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0500f830 fffff800`02ef9569 : fffff880`00000000 00000000`01c52fff fffffa80`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`0500f9f0 fffff800`031dd221 : fffffa80`03f09910 00000000`00000000 fffffa80`041aa090 fffffa80`041aa090 : nt!MiRemoveMappedView+0xd9
fffff880`0500fb10 fffff800`031dd623 : 0000007f`00000000 00000000`01b80000 fffffa80`00000001 00000000`0020b401 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0500fbd0 fffff800`02ec4ed3 : 00000000`00000000 00000000`01c1b450 fffffa80`0624bb30 00000000`01c1b444 : nt!NtUnmapViewOfSection+0x5f
fffff880`0500fc20 00000000`779815ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020a858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779815ba
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36024
fffff800`02f35150 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36024
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Followup: MachineOwner

My bets on Norton as being the problem so my first suggestions is to remove / uninstall it and follow that up by running the vendor specific proprietary removal tool from here https://www-secure.symantec.com/nor...10133834EN&product=home&version=1&pvid=f-home and then replace it with Microsoft Security Essential from here Link Removed due to 404 Error
Additionally you need to address the following old drivers by updating or uninstalling or renaming the file extension to .OLD
ManyCam_x64.sys 3/13/2008 ManyCam Virtual Webcam Download ManyCam free virtual webcam and webcam graphics software!
hamachi.sys 2/19/2009 LogMeIn Hamachi Virtual Network interface driver Link Removed due to 404 Error
Rt64win7.sys 2/26/2009 Realtek NIC Realtek
bcmwl664.sys 7/7/2009 Broadcom 802.11g Network Adapter Broadcom.com - Ethernet NIC Driver Downloads
After addressing the above let us know how you are progressing and attach any new dump files if problem persists
Regards
Randy

 

[Adam Jarvis]

Hi Randy, thanks for the reply!
I've done almost, if not everything that you have said to do & all was going well until it crashed a few minutes ago.. I'm confused on what's doing it as it happens at random moments.

Added the .DMP file within attachments.

Hope you can get back to me!
Thanks,
Adam

 

[Trouble]

Another

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, [COLOR=#ff0000][U][B]A PTE or the working set list is corrupt[/B][/U][/COLOR].
Arg2: 000000007ef7e001
Arg3: 0000000000000051
Arg4: fffff70001080000
BUGCHECK_STR:  0x1a_41284

Check memory for errors;

Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for 20 minutes or so.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+

Check hard drive for errors;

Launch an elevated command prompt (StartOrb->All Programs->Accessories->Command Prompt, right click it and choose Run As Administrator) and type
chkdsk C: /R
hit enter and answer Yes “Y” when prompted and reboot.
Let it run all five stages. When complete check the log file in Event Viewer for results (Click the StartOrb and type event viewer and hit enter, expand Windows Logs and highlight / select Application, click Action on the menu bar and select Find and type chkdsk and hit enter.

Check system files for errors;

Launch an elevated command prompt (StartOrb->All Programs->Accessories->Command Prompt, right click it and choose Run As Administrator) and type
sfc /scannow
and hit enter
See what information that provides in respect to the integrity of your system files.

Check you system for infections;

Grab this program Microsoft Standalone System Sweeper Beta | Microsoft Connect (get the correct version for your architecture) and a blank CD.
Double click the program and it will help you create a bootable CD. Boot your system from the CD (may require adjusting the BIOS to select the CD\DVD and first boot device or using and Fkey to evoke a boot menu that will allow you to select from a boot menu you CD\DVD as a one-time first boot device. Select Full scan (defaults to Quick) and see what it finds.

As a last resort you may find it necessary to run "Driver Verifier" I am not a big fan of this and would only consider it as a absolute last resort as it can result (although rarely) in some serious unintended consequences and require off-line registry editing in order to boot back into Windows normally. If you choose to consider this option Link Removed - Invalid URL has written an article regarding its' uses here Driver Verifier - jcgriff2.com
I will leave that decision to you.
Regards
Randy

 

[Adam Jarvis]

After using Memtest on both of my RAM sticks, Errors occurred on one of my sticks, removing it has stopped the Blue Screens completely, all I need to do now is buy another! Thanks a lot!

Adam

 

[Trouble]

Thanks Adam. Appreciate the info and you updating your thread with what you have found. Remember when purchasing memory it is always a good idea whenever possible to purchase matched sets or at least identical product identification numbers if purchasing separately.
Keep us posted as to how the new memory works out for you and we hope to continue to see you around the forum.
Regards
Randy

 

[Adam Jarvis]

Thanks Adam. Appreciate the info and you updating your thread with what you have found. Remember when purchasing memory it is always a good idea whenever possible to purchase matched sets or at least identical product identification numbers if purchasing separately.
Keep us posted as to how the new memory works out for you and we hope to continue to see you around the forum.
Regards
Randy

And I'd like to thank you for helping as much as possible, if anything happens which I'm unsure about, I'll definitely come back here as the service is great! I'll refer the website when I can as well!

Thanks, Adam!