Again bluescreens (see 106.0.5) with 107.0.1 and my Gemini Lake CPU notebook, old codebase ?
I got again blue screens (see also Release Notes of 106.0.5) with 107.0.1 and my Gemini Lake CPU notebook, was an old codebase taken ? I get NO bluescreens (crash) with with 107.0, the only AddOn I loaded is uBlock Origin, nothing else. This is VERY annoying, saw this also with Firefox ESR, with ESR, there was no code fix for Gemini Lake CPUs.
Alla svar (3)
Perform a hard reset.
Run a hardware diagnostic test. Disconnect external devices. Boot into safe mode with networking. Run the blue screen troubleshooter using SupportAssist. Repair the missing or corrupted Windows system files. Update the BIOS and drivers. Restore the computer using Windows System Restore.
Greetings,
Tech Guy
techguy150 schrieb
Perform a hard reset. Run a hardware diagnostic test. Disconnect external devices. Boot into safe mode with networking. Run the blue screen troubleshooter using SupportAssist. Repair the missing or corrupted Windows system files. Update the BIOS and drivers. Restore the computer using Windows System Restore. Greetings, Tech Guy
This is NOT very helpful, because ALL other software, even the former Firefox versions before 106.0 and the version 106.0.5 and 107.0 is working smoothless. The versions 106.0.1 to 106.0.4 and the 107.0.1 generates bluescreens, you do not have to surf to a special site, just a few visits of different websites is enough. It is definitely NOT related with the hardware. I guess such an answer like your answer is a copy+paste version of a call center. Working with Windows privately and @work for more than 24 years, I know what I'm doing.
Hi Peter, 107.0.1 should have been built on 107.0, and not an earlier version. However, a fix sometimes needs to be backed out due to causing other issues, so there could have been a change that wasn't documented in the release notes.
You may want to file a bug on https://bugzilla.mozilla.org/
(Although we often troubleshoot crashes here in Support, I suspect the Mozilla Crash Reporter isn't collecting/submitting the usual data, so you need someone who can interpret whatever data is available in Windows' logs.)