Dumping physical memory

[slavkaf]

Hello there.
I am very new here.
Yesterday I was on computer for a while, then left it open for like 2-3 hours. When I got back to it, the screen was blue with a text saying about dumping physical memory. I didn't know what to do so I hit a power button. After that I turned it back on the laptop started fixing the problem automatically. When it was over, I restored the computer. I just don't know why it happend as my computer is very new, I just bought it over a months ago. I don't download too much on it. hardly anything. don't use to play games on it.
my computer is HP d6 6116nr, it is Windows7 64bit. everything original came with the laptop.
I would appreciate any help.
Thank you.

 

[zigzag3143]

Hello there.
I am very new here.
Yesterday I was on computer for a while, then left it open for like 2-3 hours. When I got back to it, the screen was blue with a text saying about dumping physical memory. I didn't know what to do so I hit a power button. After that I turned it back on the laptop started fixing the problem automatically. When it was over, I restored the computer. I just don't know why it happend as my computer is very new, I just bought it over a months ago. I don't download too much on it. hardly anything. don't use to play games on it.
my computer is HP d6 6116nr, it is Windows7 64bit. everything original came with the laptop.
I would appreciate any help.
Thank you.

These crashes were caused by memory corruption (probablyR elated to btmcom.sys Bluetooth Serial Port Driver from Motorola, Inc.)
Please run these two tests to verify your memory and find which driver is causing the problem.
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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool", "Force Pending I/O Requests" and "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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[slavkaf]

thank you for your very fast response. I appreiate it very much.
first of all, I doubt I will be able to do those tests myself, they sound too complicated for me and I don't want to mess up something and make it worse than it is. But I saw you mentioned Bluetooth. I noticed that Bluetooth didn't work right on the computer. I mean it is active only when the laptop in on before it falls asleep. If I want to use Bluetooth after my laptop after it's been inactive for a while, I need to restart it to activate Bluetooth again. it is pain in the neck, but I don't use it that often. So maybe it is Bluetooth after all.
Thank you for your help

 

[zigzag3143]

thank you for your very fast response. I appreiate it very much.
first of all, I doubt I will be able to do those tests myself, they sound too complicated for me and I don't want to mess up something and make it worse than it is. But I saw you mentioned Bluetooth. I noticed that Bluetooth didn't work right on the computer. I mean it is active only when the laptop in on before it falls asleep. If I want to use Bluetooth after my laptop after it's been inactive for a while, I need to restart it to activate Bluetooth again. it is pain in the neck, but I don't use it that often. So maybe it is Bluetooth after all.
Thank you for your help

I said probably bluetooth

If at all unsure dont.

If it is under warranty return it.