BSOD - ntoskrnl.exe - Memory Management

You're welcome, and I am glad that has provided more stability. Thank you for posting back.

Let us know in a few days how the system is responding. :)

Well it seems more stable now. It wont randomly crash while I'm actively using it. However, If I leave my computer up for the night to finish a download or something, Ill be greeted with a BSOD when I get back. The thing is, none of them match up. They all report different stop messages. Anyways, I've gotten about 5 more BSOD's since last week. I'll post an updated report.

Device Concerns:

Code:

Broadcom 20702 Bluetooth 4.0 Adapter	USB\VID_0A5C&PID_21E1\C01885ECD5AB	This device is disabled.

Were you aware of the above? If so, please explain your troubleshooting steps.

Software Concerns:

Security Software:

Security Software: ??? Make sure to install security software. I recommend either of these:

• Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.
  
  
• Good and Free system security combination.

After installing your security software, update it, and then run full scans today with each program. Report back the results of the scans.

Software Conflicts/Performance:

You also have a number of unnecessary programs on your system that may be lowering performance or causing conflicts. Troubleshoot Application Conflicts by Performing a Clean Startup

Analysis:

Your crashes primarily indicate hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• 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).
  
     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. WARNING: The steps that follow can void your warranty!!!
  
  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.

Memtest86+ Errors:

Have you tried narrowing down which of your modules caused the errors? Since your blue screen crashes occur regularly, we can test the memory through running Windows. Test the memory slots and modules as follows.

1. Shut down and turn off your computer.
2. Unplug all power sources to the tower (unplug the power from the outlet/surge protector or PSU).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing.
5. Remove all but one memory module making sure you are grounded while doing so.
6. Replace the casing and put the remaining memory modules in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).

Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.


Test by doing your normal routine in Windows for twice as long as it takes to get a crash or until you get a crash, whichever comes first. You can also test by doing the tasks that generally cause crashes.

writhziden said:

Device Concerns:

Code:

Broadcom 20702 Bluetooth 4.0 Adapter	USB\VID_0A5C&PID_21E1\C01885ECD5AB	This device is disabled.

Were you aware of the above? If so, please explain your troubleshooting steps.

Software Concerns:Security Software:

Security Software: ??? Make sure to install security software. I recommend either of these:[list][*]Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.

Well as for the Bluetooth adapter, I keep that off to save battery. Also, there is no security software at the moment because I am just trying to narrow down the problem, and Norton has a history with me of messing things up. So i thought I'd leave it off for a while until this gets sorted out. I'm pretty good with not getting viruses from doing stupid things so I'm good with it. But I have NIS 2012 back on now, so no worries.

I'll do those other things with the RAM and HDD, but it is quite possible that my harddrive is failing. Better get that fixed soon. I'll report back when I get more info and do some of those steps.

It turns out it doesn't seem to be hard drive failure. I had a spare hard drive laying around, and I did a clean install on it. Ran it on my laptop and after about five minutes of messing around, boom. Another BSOD about memory management. So it looks like i've narrowed it down to RAM. I guess i'll have to call in to HP and see if they can replace it for me.