Memory_Management BSOD

Page 1 of 5 123 ... LastLast

  1. Posts : 373
    Windows 7 Ultimate x6
       #1

    Memory_Management BSOD


    My brand new laptop (Sager NP8130) with a freshly installed Windows and with all updated drivers just experienced a BSOD out of nowhere while surfing the Internet. It says "Memory_Management" in the message. Here are the necessary things for troubleshooting in this forum:

    -Windows 7 Ultimate x64
    -original OS installed
    -full retail version
    -age of system hardware is around 2 weeks
    -age of OS is 1 week

    I've uploaded the necessary files for your reference. I hope somebody can help me with this. Thank you very much.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    kevindd992002 said:
    My brand new laptop (Sager NP8130) with a freshly installed Windows and with all updated drivers just experienced a BSOD out of nowhere while surfing the Internet. It says "Memory_Management" in the message. Here are the necessary things for troubleshooting in this forum:

    -Windows 7 Ultimate x64
    -original OS installed
    -full retail version
    -age of system hardware is around 2 weeks
    -age of OS is 1 week

    I've uploaded the necessary files for your reference. I hope somebody can help me with this. Thank you very much.

    These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

    In this case Acrobat reader was the active app.

    If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!



    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    2-Driver verifier

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Driver Verifier - Enable and Disable


    Further Reading
    Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  3. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #3

    Ok, I will do those. Would it also be possible that my pagefile is set too low at 400MB?

    And btw, is it possible for you to post the minidump crash analysis here for me to know what it looks like?
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    kevindd992002 said:
    Ok, I will do those. Would it also be possible that my pagefile is set too low at 400MB?

    And btw, is it possible for you to post the minidump crash analysis here for me to know what it looks like?
    If your page file is set below your memory size it cant write a DMP file.
      My Computer


  5. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #5

    zigzag3143 said:
    kevindd992002 said:
    Ok, I will do those. Would it also be possible that my pagefile is set too low at 400MB?

    And btw, is it possible for you to post the minidump crash analysis here for me to know what it looks like?
    If your page file is set below your memory size it cant write a DMP file.
    Oh ok, but we do not need a dump file in this case? How big is a minidump file? I can see that I have a 301KB DMP file in the Minidump folder of Windows, is that the one?
      My Computer


  6. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #6

    BTW, just now I had this famous error: 'Nvidia Kernel Mode Driver 285.62 has stopped responding and recovered' and the screen went out for a few seconds and came back. I experienced this error before with my old laptop. Can this be one possible reason for the memory_management error?
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    kevindd992002 said:
    BTW, just now I had this famous error: 'Nvidia Kernel Mode Driver 285.62 has stopped responding and recovered' and the screen went out for a few seconds and came back. I experienced this error before with my old laptop. Can this be one possible reason for the memory_management error?
    Nope that is a different error




    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    If you are overclocking STOP

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
      My Computer


  8. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #8

    zigzag3143 said:
    kevindd992002 said:
    BTW, just now I had this famous error: 'Nvidia Kernel Mode Driver 285.62 has stopped responding and recovered' and the screen went out for a few seconds and came back. I experienced this error before with my old laptop. Can this be one possible reason for the memory_management error?
    Nope that is a different error




    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    If you are overclocking STOP

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Thanks. I already attached the minidump file.

    So if I understand it correctly, since my pagefile is just 400MB, it is better to just set my system to do a small memory dump (minidump) file in times of BSODs instead of setting it to do a kernel memory dump since the kernel memory dump needs a pagefile that is equal to the size of my RAM. Did I get it right?
      My Computer


  9. Posts : 28,845
    Win 8 Release candidate 8400
       #9

    kevindd992002 said:
    zigzag3143 said:
    kevindd992002 said:
    BTW, just now I had this famous error: 'Nvidia Kernel Mode Driver 285.62 has stopped responding and recovered' and the screen went out for a few seconds and came back. I experienced this error before with my old laptop. Can this be one possible reason for the memory_management error?
    Nope that is a different error




    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    If you are overclocking STOP

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:

    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Thanks. I already attached the minidump file.

    So if I understand it correctly, since my pagefile is just 400MB, it is better to just set my system to do a small memory dump (minidump) file in times of BSODs instead of setting it to do a kernel memory dump since the kernel memory dump needs a pagefile that is equal to the size of my RAM. Did I get it right?
    Correct! We also have to wait for a couple more crashes. You should be running memtest and then verifier in the mean time.
      My Computer


  10. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #10

    Surprisingly, I got errors in Memtest86+ with the two modules (2x4GB) installed in my RAM slots. Does this direct to the problem right away?
      My Computer


 
Page 1 of 5 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:42.
Find Us