Bsod - (non_paged_area/memory_management)

[Cryoquake]

I recently made a thread in regards to my Bluescreens and I will now upload more of the Minidumps. They generally occur when I am on Chrome and watching a Youtube video. I just received one then in regards to MEMORY_MANAGEMENT and no reason was shown.

I apologize with the dumps as I'm not sure which errors are which but they're all uploaded. Much help is appreciated guys, this is happening daily.

 

[zigzag3143]

Driver verified and related to Lycosa.sys Tarantula Keyboard Driver from Razer USA Ltd. I would re-install newest driver available

 

[Cryoquake]

I uninstalled the Lycosa driver a few days ago as it's not needed anymore and the errors are still going. Is there anything that may have occurred with the last BSOD?

 

[zigzag3143]

I uninstalled the Lycosa driver a few days ago as it's not needed anymore and the errors are still going. Is there anything that may have occurred with the last BSOD?

Apologies you did in fact remove it in the latest DMP.

Most recent outwardly blames an OS file but that isnt likely.

I would run a System file check and re-enable driver verifier.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[Cryoquake]

Thank you for your response, I ran SFC and Driver Verifier and the BSODs stopped on that end. I had another MEMORY_MANAGEMENT error. I've run out of ideas besides it's hardware issues or Skype. I'm tilting towards Skype now as the computer is very new and was running fine before I started to install software. Attached is the latest BSOD dump.

Thank you!

 

[writhziden]

You say the system is new. Is it still under warranty?

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The memory steps that follow can void your warranty!!!

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 210855
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.