This occasional bugcheck code 0x124 problem has been haunting my 64-bit Windows 7 since Firefox 3.6, going through all Firefox versions, till the latest one (10.0).
I followed all the steps described in this excellent guide to troubleshooting
- Ensured that none of the hardware components are overclocked
- Ensured that the machine is adequately cooled.
- Updated all hardware-related drivers.
- Updated the motherboard BIOS according to the manufacturer's instructions.
- Applied all Windows 7 updates.
- Stress-tested all hardware components.
- Cleaned and carefully removed any dust from the inside of the machine.
Yet, the system will continue to occasionally bugcheck with BSOD code 0x124 only when attempting to resize or scroll the Firefox browser window.
This problem never occurs in any other circumstances and never occurs even with Firefox itself when run in Ubuntu 8 or 10. It always happens only with Firefox.
The actual BSOD dump is meaningless because it always leads to
Which leads me to suspect that there might be a bug in Firefox that triggers a bug in ntoskrnl.exe?
Do you know of any such other report that may shed some light on this mystery?
Update: This problem is so weird that I started to suspect perhaps malware? This is despite the fact that I scanned my system with Malwarebytes and found no malware whatsoever. I decided to give Microsoft's Security Essentials a try. And look what it discovered after a 1/2 night run:
This is mind boggling... I thought that Malwarebytes is good enough but apparently not. On the other hand, so many Java exploits... Could they really be responsible for the BSODs?
I will be tracking this and report back if I have new findings.
Update 2 weeks later: After the above cleanup, the problem went away. But then I disabled Microsoft's Security Essentials because it slowed down my computer too much... Sure enough, the problem returned today and so I ran Microsoft's Security Essentials full scan again. This is what it found this time:
Update the next day, after I got another such crash: This time MSE was on all the time, so I was intrigued by the possibility that this isn't caused by malware after all? I performed a full scan by both MBM and MSE and didn't find any malware. Back to □ 1.