Running Firefox causes a physical memory dump.

Every time I try to run the latest version of Firefox on Windows 7 I get a BSOD that shows a physical memory dump with messages like "bad_pool_header" or "system_service_exception." This happens even if I run Firefox in safe mode with all plugins disabled. I don't remember when I last updated Firefox, but I was not having this problem until today. I put my computer to sleep at night, and when I woke up this morning my internet connection was not available, so I had to reset my cable modem. After I regained my connection I found that Firefox was not working. Internet Explorer works fine. (Note that in System Details the listed version of Firefox is not the one I was running - I am currently on a different computer, but I was running the latest version of Firefox when I was having issues.)

addendum: the problem mentioned above is not solved by the latest update, and the problem not only occurs when using the scrollbar but on various occasions and exclusively when using Firefox. With the use of other applications (including Windows Internet explorer) the memoryproblem does not occur (upto now that is)

Similar Messages

IPOD causes "Blue Screen of Death" with physical memory dump

Plugged in the IPOD into USB port on computer. It shows "found USB device" and then 5-10 seconds later I get the blue screen of death and a notification that there is a driver error and a physical memory dump as occurred.
Spent two hours with Apple people and Dell people this morning and nothing. I have updated drivers, flashed my bios, uninstalled and then reinstalled the latest version of Itunes.
Any help would be greatly appreciated.

what numerical and text codes are you getting with it? (ie 0x[zeros/letters/numbers] CAPSANDUNDERSCORES)
if the blue screen mentions a specific file, let us know what that is called too. (exact spelling, please.)
here's a reference on the sorts of things i'm asking about:
Troubleshooting Windows Stop Messages
if you're just seeing a flash of a blue screen, we can use this technique to make hidden blue screens appear for us:
1) Open your system control panel (Start->Control Panels->System).
2) Select the "Advanced" tab.
3) Click the "Startup and Recover" section's "Settings" button
4) Verify that under "System Failure" the "Automatically restart" checkbox is not checked.

HP Pavilion dv6 Vista Recovery - Physical memory dump w/ error code 0x000000F4 (and others)

Hello Everyone,
This is my first time posting in the forums so I hope that I have chosen the appropriate area and will do my best to be brief but informative.
Computer: HP Pavilion dv6000
Operating System: Windows Vista.
For the past 6-8 months it has been unable to perform Windows Update citing that the most likely reason was a virus. I have tried numerous trouble shooting options when it was recommended that I perform a chkdsk. After initiating a chkdsk in Command Prompt, my computer restarted and had a black screen with no cursor. After watching this for 2 hours and realizing that none of the usual chkdsk progress or text was coming up I made the decision to force shut down.
When I rebooted, I was told to enter system recovery which I did and completed a system recovery from the hard drive. After the system recovery finished and the laptop restarted, I experience a Blue Screen of Death due to a physical memory dump. The error codes are STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8006671040, 0xFFFFFA8006671278, 0xFFFFF80001D01DA0).
I am not able to boot in safe mode. In the start up repair, I am able to enter command prompt from which I started chkdsk again. Both chkdsk f/ and chkdsk r/ passed with no errors. Additionally, the computer passed both UEFI Hard Drive and Memory tests. I have system recovery CDs for the computer but they fail at 78% completion.
Please let me know if you have any questions or require anymore information. I would appreciate any and all advice!
Thank you!
This question was solved.
View Solution.

Hello @GraydonS,
Welcome to the HP Forums, I hope you enjoy your experience!
I have read your post on how there is an error message being displayed on your notebook, being a Blue Screen of Death (BSOD), and I would be happy to assist you in this matter!
Since you are having recovery issues with your system, I recommend following this document on Troubleshooting System Recovery Problems (Windows Vista). This should help you to successfully recover your Operating System.
If the issue persists, please call our technical support at 1-800-474-6836. If you live outside the US/Canada Region please click the link below to get the support number for your region.
http://www.hp.com/cgi-bin/hpsupport/index.pl
I hope this helps!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

Physical memory dump error on my A60-155

I have got a Satellite A60 and recently when just turning on the computer after a week period of not using it, it gave a 'physical memory dump' and then asked if I want to start in safe mode or last known working settings or start windows normally. None of these options worked, all the computer did was dumping its memory. So I tried the recovery disc, it loaded all the required things but yet again it did a memory dump on load up.
So I formatted the laptop and tried a newer copy of windows XP on it (Both home and Professional) doing this did work (By that I mean it installed) and windows loaded as it should, I loaded the sound drivers and all the rest of the needed drivers, restarting the computer every time I installed a new device but when it came to the 'ATI Radeon Mobility 7000 IGP' driver as soon as it restarted it dumped the memory.
As soon as the ATI driver is installed the system will not load, but the new windows I have installed does let me start on last worked settings (This removes the graphics driver) So I went onto this Toshiba website and got the driver from here seeing as ATI doesn't provide the drivers for its merchandise, and yet again it resulted in the system not loading. I need to have the graphics working because without it I cant watch films or use my CAD software I need it working.
PLEASE HELP!!

Hello
Please try to use these settings shown on this page http://www.barrett.net/xpmemorydump.html .
By the way the graphic card should be installed at the beginning. After OS installation first that should be installed is the chipset driver and than graphic card driver. After that you can continue with all other drivers.
Bye

Physical Memory Dump in Windows 7

I bought my computer a little over a year ago, an HP Pavillion 6313w, at Wal-Mart. Up until the past week, I started receiving an error when completing a full scan using the Mcafee program that came with Verizon Internet Security Suite about dumping physical memory. A blue screen comes on, it completes the memory dump, and then restarts my computer. It'll ask how I want to start Windows and I'll check normally. It restarts and everything's fine again. No files are lost or anything. I just notice this whenever I complete a full anti-virus scan. I contacted Verizon via Live Chat and was told that my system is corrupt and would need to contact my system vendor. My computer is now out of warranty as of this past March. Is there any way to fix this problem without going through too much trouble or too much expense? One thing I have not done is back up my files and it shows one important message at the bottom. I'm not sure if this is related to a hardware problem. I did recently have some Windows updates completed. I complete a system restore back to about a month ago, but this did not resolve the issue. Any help would be much appreciated.

Sorry for not having gotten back to you sooner. I did recently follow the directions that you outlined for me and the issue has not come back after I did a full scan on McAfee. Hopefully that is what was needed to correct the problem. Thank you again for all of your help.

Recurring Physical Memory Dump and Blue Screen on Windows 7

I recently built a PC and have been getting pretty frequent blue screens whenever I use it. Today I got about 5 within an hour and have finally tried to fix it. I got Windows Debugger and have analyzed the .dmp files and the most common one that I have gotten
is this one:
* Bugcheck Analysis
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800d062028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre
STACK_TEXT:
fffff880`031dfb58 fffff800`0320ea3b : 00000000`00000124 00000000`00000000 fffffa80`0d062028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`031dfb60 fffff800`02da3463 : 00000000`00000001 fffffa80`0cc9f9a0 00000000`00000000 fffffa80`0cc9f9f0 : hal!HalBugCheckSystem+0x1e3
fffff880`031dfba0 fffff800`0320e700 : 00000000`00000728 fffffa80`0cc9f9a0 fffff880`031dff30 fffff880`031dff00 : nt!WheaReportHwError+0x263
fffff880`031dfc00 fffff800`0320e052 : fffffa80`0cc9f9a0 fffff880`031dff30 fffffa80`0cc9f9a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031dfd50 fffff800`0320df0d : 00000000`00000008 00000000`00000001 fffff880`031dffb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031dfd90 fffff800`03201e88 : 00000000`00000000 fffff880`031d7180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031dfdc0 fffff800`02c8b4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031dfdf0 fffff800`02c8b313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dff30 fffff880`053889c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`031ffb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_cache
FAILURE_ID_HASH: {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
Followup: MachineOwner
It looks like it's happening because of a system update I may have done? I'm not sure what to make of this or how to fix it.
Any help would be greatly appreciated.
Thanks

Mike
Virtual all of these are hardware related so I would start there. This type of crash is called a BCC124 and 99 times out of 100 it is hardware related.
Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see
if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though
it is"possible" that it is driver related (rare).
Stop 0x124 - what it means and what to try
Synopsis:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
ways.
2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games,
utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine
is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Should you find yourself in the situation of having performed all of the steps
above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
More advanced reading can be found here from a MS MVP IT PRO
http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
Wanikiya and Dyami--Team Zigzag

Physical Memory failure (DUMP)

I use SIS 648FX Chipset Based 648F NEO Series
using Pentium 4 HT 2.8 GHz processor
i already use Kingston 512 MB DDR 400 MHz PC3200 DIMM 3-3-3 for 3 months already. Yesterday I bought 1 more of Kingston 512 MB DDR 400 MHz PC3200 DIMM 3-3-3 to upgrade the RAM Memory
It doesn't work, computer doesn't even start. Before that my computer has 256 MB 266 Mhz memory module. It's strange, but if i reset CMOS settings with help of changing jumper position, the system starts.
If I use only one dimm than the computer can start.
I try both of the dimm. Both can start.
But when I use 2 dimm of Kingston 512 MB DDR 400 MHz PC3200 DIMM 3-3-3, the computer doesn't start.
IRQL_NOT_LESS_OR_EQUAL
Technical Information
***STOP: 0x00000A (0x3B08518D, 0x00000002, 0x00000001, 0x804F7444)
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrators or technical support group for further assistance.
MSI EXPERT pls help me ASAP

I had that experience.
First I tried boot with 1 DDR and Enable 'DRAM Timing by SPD' in CMOS setting.
And then I boot with both DDR. It solved my problem.
Then I tried to tweak DRAM Timing again.
You also increase RAM voltage little each time.
Cheer!!!

Blue Screen re: Physicial Memory Dump on HP Pavilion DV6-3210-US

Hello. I am running Windows 7 and recently have been getting this bright blue screen with a ton a words on it but I can only pick out CRASH DUMP and PHYSICAL MEMORY DUMP from this before it just disappears. In a couple of cases it tried to run a service repair and didn't let me choose to run in anything but safe mode. It has also let me choose what mode to run.
I took it to a computer repair company and they put a new hard drive on my computer, tuned it up and sent me on my way. I've had it back 2 days and I just got the error again. I have a 30 day guarantee on my repair and probably should take it back but they didn't fix it the first time. I don't think they knew what this was and went for what they knew they could do easily.
What do I do?

Hello SandykUtah.
The two most common causes of blue screen errors are problems with either the hard drive or the memory. Your notebook has diagnostics for both of these pieces of hardware. I suggest running them both in addition to the advice suggested above by maxpower757.
This document covers running the hard drive test. Simply repeat the process and select "memory test" to run the RAM test.
Make sure to post the results. I hope you have a great day!
Please click the white star under my name to give me Kudos as a way to say "Thanks!"
Click the "Accept as Solution" button if I resolve your issue.

GT60 0NC - Memory Dumps - BSOD - Replacing RAM

I just bought my GT60 a month ago and this past weekend my laptop started crashing. BSOD tells me that it was a physical memory dump.
I ran the Windows Memory Diagnostic test from bootup and the RAM failed 10% into the first pass.
I was going to RMA the laptop but I didn't feel it was worth sending it back for faulty RAM. In fact I've never heard of the RAM that my laptop came with. So I went ahead and ordered some GSkill ram from Newegg.
My problem is I have only found 1 stick of the 3 sticks of RAM for my GT60. The first stick I found it the first one you see when you pull off the back plate.
but I can't find the other 2 sticks.
Anyone know where they are?

Quote
Sometimes my computer doesn't even start after a few times of fail or it only shows 4GB RAM where there are 2x4GB.
PSU is more than adequate for your system and configuration. For some reason, if the 124 BSOD continues to be a problem, the CPU V. is being set too low. Always possible the CPU has an extremely high VID. With not all the RAM showing, I suspect a CPU socket pin problem of some or one being bent or damaged. A close inspection of the socket with a bright light and magnifier is recommended.
Quote
I used MSI live update 5 to update BIOS and everything.
In the future, to be much more safe, use the forum's USB flash procedure;
>> Forum USB Flash Method <<

Why Firefox 5 eating up 1074424KB of my 2027520KB physical memory, with 9 tabs has loaded pages and 6 problem loading page as i stoped them?

Firefox was minimized i was doing something else but while switching to another application the screen got frozen, when it become normal i checked Task Manager and got Firefox is using 10744424KB (almost 53% of physical memory). As stated in question 9 tabs finished loading and another 6tabs showing problem loading page as I stopped them clicking on offline mode and when they stopped loading I switched to online mode.

Yes, Safari Web Content can use a lot of RAM. However, I don't think that would be the cause of crashing; lots of memory use rarely causes crashes. Poorly written software that runs in kernel space (AV software fits this), can cause this.
Safari Web Content is "caching" a lot of stuff. More than I'd like it to. If you have 47 tabs open, and close them down to 1, SWC will still often be taking up a lot of RAM. If you quit and restart Safari it will give the memory back, though in general if the system is under memory pressure I think SWC will also release some more RAM. In general I never notice this to be an issue.
I think with OS X Mavericks things may improve as well, based on details on the Safari tab, as well as with "Compressed Memory" which would help as your system approaches using all its RAM:
http://www.apple.com/osx/preview/advanced-technologies.html

Premiere Elements 4.0 - dump of physical memory

Hey Everyone,
I was in the process of burning some videos(AVI format) and when i went to the green "SHARE" tab and would select DISK(to burn DVD), it would freeze up, then immediately go to a blue screen and come up with a error message of 'BEGINNING DUMP OF PHYSICAL MEMORY'. Windows recovery indicated a problem with the PX Engine and an update was available. I went to the website and downloaded the update, rebooted the PC, and tried again but still got the memory dump message.
i have burned many pictures on DVD creating slideshows and such but this is my first time burning actual video onto a DVD. I figured the process for burning video is the same as burning pics. i created a picture slide show afterwards and it burned it just fine - no errors.
Am i doing something wrong?

A BSOD is a major problem, and is very often a sign of hardware issues. The main causes are:
Heat buildup - in the CPU, or the HDD's
RAM - bad, or going bad
PSU - going bad, or improperly connected
MoBo - going bad
This ARTICLE will link to tools that will help you track those elements, and possibly show the bad element, or potentially bad element.
I would also change Reboot on Error, to OFF, so that you can write down the report on the BSOD. There might be something in that load of "abstract code" that will be helpful, but maybe not. Also, when one reboots after a BSOD, Windows will usually yield an error message to the effect of "Windows has recovered from a serious problem... " and will often help you trace the issue. Also, this ARTICLE will give you tips for finding clues as to what was happening, just before the BSOD.
If nothing else works, see this ARTICLE.
Before doing anything else, I would solve the BSOD issue.
Good luck,
Hunt

Beginning Dump of Physical Memory When Connecting iPhone

Hi everyone. I just moved to a new laptop and installed iTunes 7.5. When I initially connect my iPhone to the new laptop it pops up in the task manager that a new digital camera is found and begins the install process. About 15 seconds later the computer blue screens and throws up the "Beginning Dump of Physical Memory" error. This happens every time.
I've not tried to plug in my iPod yet so I don't know if that will do it as well but I really want my iPhone working on the new computer. It worked great on my old laptop.
Anyone have any ideas?

If you have a logitech device on your machine, then this might be the cause. If so, do a search on this site to look for the fix.

Window Crashed, "dumping physical memory"

Harlo, i know the title is misleading. Before anything, here are my specs
PSU: Cooler Master 520W modular
MB: MSI Neo 2 FR
RAM: 2Gb x 2 800mhz Kingston
CPU: Intel E7300
GPU: Sapphire 4830 512DDR3
HDD: WD 320gb
I bought this system back in Feb. All the while OK except for some minor tweak i guess it's fault from the hardware installation. After that the system run smoothly with no problem.
Until recently, one month ago, my system will restart itself without any warning, then after restart would say "Windows faced critical error...." This always happen after i shut down and on back my PC. after several same restart it gets back to normal and i can play the last remnant without trouble
And more recently, sometime it just hand during start up with this big blue screen that has lots of text and last few lines that said "dumping physical memory". At first i thought maybe window drivers or something, i reinstall windows but still get the same problem. updated my driver for GPU to ATI CCC 9.6 still like that.
i ran out of idea where to check? could it be hardware again? suggestions welcome.

Do memory check with >>Memtest86<<
Also what is the BSOD error code received?

Each time that I go into edit with Photoshop Elements 8 it causes a physical dump and shuts down

Each time that I go into my Photoshop Elements 8 it causes a physical dump and shuts down. I have only used this program a few times although I have had it a few years. The first couple of times it worked fine; but now, it shuts me down each time. I have already tried unistall and reinstall. Help!

Well, can you try opening just the Photoshop Elements 8 (from the Start menu) and see if it opens Editor from Welcome Screen or not?
It it still crashes, please try couple of probable solutions as mentioned below:
Solution 1:
Close Elements.
Launch the Photoshop Elements Welcome Screen and hold down ctrl + alt + shift as you click Editor.
Continue to hold the keys until you see a message box asking if you want to delete Photoshop Elements settings file; click Yes. Elements will open with default preferences.
Solution 2: In case any network printer is attached try to launch without network or printer uninstall or make different printer as default.
Solution 3: Try launching with anti-virus off or removing PSE from conflicting list.
Solution 4:
On the drive on which you have installed PSE,on my machine it is on C:
Go to C:\Program Files\Adobe\Photoshop Elements 10\Locales\<locale>\Plug-Ins\Import-Exportand you will find twain plug-in. Remove that plug-in from that location and copy it somewhere else.
Now launch PSE and check if it works.

Am running Firefox 7.0.1 now. Normal memory usage is 157mb but when running Facebook (not running apps nor games), it goes up to 553mb Why?

Am running Firefox 7.0.1 now. Normal memory usage is 157mb but when running Facebook (not running apps nor games), it goes up to 553mb Why?

I encountered the same type of problem. Firefox running terribly slowly and slowing down my entire machine (Core i5 with 256GB SSD). Searching the forums, I found a couple of things about troubleshooting performance issues, one of which was to use '''hardware acceleration''', that is on by default. It was turned on on my PC, '''so I tried deactivating it, and it worked!'''
So doing the exact opposite as Mozilla support said solved the problem. It is really a pain now to work with Firefox. I'm using it because I have no choice, but I'd recommend IE and Chrome over Firefox... Whatever, the market will decide once Firefox has become to crappy...

Running Firefox causes a physical memory dump.

Similar Messages

Maybe you are looking for