If disabling hardware acceleration in the browser fixes the crashes, you are most likely having an issue with your graphics drivers (reports so far have been exclusively on NVidia GPUs for that). Keep in mind that Pale Moon x64 will probably be one of the very few applications on your system (if not the only one) that talks to DirectX and your graphics drivers natively in 64-bit. Games and test suites usually run in 32-bit mode, and the 32-on-64 layer (WoW64) doesn't suffer from this particular problem.
Examining the minidump files (found in \minidump under the windows system folder) can help in determining if this was this actual kernel bug or a driver problem (e.g. graphics drivers). Sending me a PM with the file attached (they should be no larger than 250-300kB) or making it available to me on-line (e.g. ge.tt or dropbox or similar) will allow me to let you know if this is indeed this Windows kernel bug or if it was a more clear driver fault.
The solution is simple: switch to a 32-bit version of Pale Moon. The bug is specific to running a native 64-bit application. You will not lose all that much performance doing this (and if your system has trouble with the native 64-bit version, it may even be faster!) and will gain stability and also plugin compatibility. Even if disabling hardware acceleration fixes it for you, this would still be the better choice, since the 32-bit version with hardware acceleration will be faster and more efficient than a 64-bit version with it disabled.
Other possible solutions are:
- Check your system for malware! Viruses/worms/trojans, etc., can severely affect system run time operation and can cause these kinds of crashes, especially if it tries to interface with a 64-bit browser.
- Update your chipset drivers (for your motherboard) to the latest available version
- Update your video drivers
- Make sure you have the latest version of DirectX 9.0C installed
- Update your motherboard BIOS to the latest version
- Check with Microsoft to see if they have a kernel patch for you - MS support can be very helpful if it's a known issue but the hotfix may possibly not be publicly available
Also, if you get the option to report the crash to Microsoft, do so! The more bugcheck reports they get, the better they can pinpoint potential issues and supply fixes for them.