Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD- memory_management


  • Please log in to reply
11 replies to this topic

#1 AlexandraMW

AlexandraMW

  • Members
  • 69 posts
  • OFFLINE
  •  
  • Local time:11:14 PM

Posted 24 January 2012 - 11:18 AM

While doing schoolwork on my laptop (It was issued by my school because of my online classes) it started going very, very slow and eventually it got a BSOD- it said it was Memory_Management.
What is this error and how do I fix it?
Other pertinent information:
HP 365 laptop
Running Windows 7
Physical memory has been very close to full for a few days; I have been unable to pinpoint the cause. Firefox seems to be taking most of the physical memory though. But I can't do without it as this is the browser I use for my schoolwork and IE doesn't work. I was using IE and Firefox concurrently when the BSOD occurred.
MBAM said it was clear of viruses about 1-2 hrs before the BSOD.

Edited by AlexandraMW, 24 January 2012 - 11:18 AM.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:14 AM

Posted 24 January 2012 - 12:06 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 AlexandraMW

AlexandraMW
  • Topic Starter

  • Members
  • 69 posts
  • OFFLINE
  •  
  • Local time:11:14 PM

Posted 24 January 2012 - 12:20 PM

Will do!
I can't find the actual download button! :(

Edited by AlexandraMW, 24 January 2012 - 12:23 PM.


#4 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:14 AM

Posted 24 January 2012 - 12:21 PM

I'm not sure I can be any more clear. Sorry.

#5 AlexandraMW

AlexandraMW
  • Topic Starter

  • Members
  • 69 posts
  • OFFLINE
  •  
  • Local time:11:14 PM

Posted 24 January 2012 - 12:24 PM

Okay. I'll try my best. But I can't figure out how to actually download what you sent me and I'm confused...

#6 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:14 AM

Posted 24 January 2012 - 12:29 PM

Try downloading from here:
http://download.cnet.com/BlueScreenView/3000-2094_4-10965136.html

Also, please don't edit a post after there has been a response. It makes the response look foolish and out of context. Thank you.

#7 AlexandraMW

AlexandraMW
  • Topic Starter

  • Members
  • 69 posts
  • OFFLINE
  •  
  • Local time:11:14 PM

Posted 24 January 2012 - 12:30 PM

I tried to edit before you made the response because I didn't want to sound mean. :(

#8 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:14 AM

Posted 24 January 2012 - 12:33 PM

Okay, no problem. Let's move on to solving your problem.

#9 AlexandraMW

AlexandraMW
  • Topic Starter

  • Members
  • 69 posts
  • OFFLINE
  •  
  • Local time:11:14 PM

Posted 24 January 2012 - 12:33 PM

Anywho, here you are! Thanks for being so patient with me.
==================================================
Dump File : 012412-30076-01.dmp
Crash Time : 1/24/2012 8:12:34 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00041284
Parameter 2 : 0x1cee7001
Parameter 3 : 0x0000a8eb
Parameter 4 : 0xc0802000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+deef4
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17713 (win7sp1_gdr.111025-1505)
Processor : 32-bit
Crash Address : ntoskrnl.exe+deef4
Stack Address 1 : ntoskrnl.exe+67ba8
Stack Address 2 : ntoskrnl.exe+67dfe
Stack Address 3 : ntoskrnl.exe+9fb24
Computer Name :
Full Path : C:\Windows\Minidump\012412-30076-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 148,225
==================================================

#10 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:14 AM

Posted 24 January 2012 - 12:45 PM

1) Did it only happen the one time? If so, I wouldn't worry about it.

2) Same question for the system "going slow" - only the one time or is it now constant?

3) What do you mean "Physical Memory has been close to full"? How are you determining that?

4) If you want to check the installed ram, here are instructions to do so:

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

#11 AlexandraMW

AlexandraMW
  • Topic Starter

  • Members
  • 69 posts
  • OFFLINE
  •  
  • Local time:11:14 PM

Posted 24 January 2012 - 12:47 PM

1. BSOD has only been one time so far, yes.
2. Going slow, also only the one time.
3. Using task manager, it consistently says my physical memory is around 50%. The laptop I used to use very rarely got that high.

#12 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:14 AM

Posted 24 January 2012 - 01:50 PM

Don't worry about anything then. Let's see if it happens again - if not, it might just have been an anomaly.

As for memory usage - don't worry about that either. Your concern with xp is cpu usage, and as long as there are no processes hogging the cycles you're fine. There's an old saying: unused ram is wasted ram.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users