Answer the question
In order to leave comments, you need to log in
Chrome: BSOD after update - what is the reason?
Situation
After the last update (21.0.1180.75) on a laptop (Win7 32, Celeron T3000, Radeon HD 4330 video card), after a few seconds of using Chrome (20-30 seconds, it's enough to click on two or three links), the system crashes into a BSOD.
It is Chrome that causes the blue screen, on different pages and under different users.
All other browsers and any other software work without failures indefinitely.
I went through two antiviruses: clean.
Did a few stress tests of the system: everything is OK, no failures.
There is no software on the laptop that falls into the list of programs published by Google that can cause Chrome to crash.
On a stationary machine (Win 7 64, Celeron G530, two active video cards) with the same version of Chrome, the situation is not observed.
According to Google help, deleted Chrome user profiles. Didn't help, crashes into BSOD.
According to information from the abyss of the Internet, I set Chrome to run in compatibility mode with Win 2003 SP1. It helped, the crashes in the BSOD stopped, but still it is somehow unnatural.
Question: who faced the situation, what is the cause of the phenomenon, and is it possible to stop Chrome from falling without switching to compatibility mode?
Answer the question
In order to leave comments, you need to log in
I came across something similar, at that time disabling hardware acceleration in the flash plugin settings helped.
Also, you can study chrome://flags to disable any hardware rendering acceleration.
You can manage plugins (to try to identify the causes of the crash) in chrome://plugins
chrome://flags
and I'm chrome://plugins
leaning towards fst , I blame flash.
chrome://flags
and I'm chrome://plugins
leaning towards fst , I blame flash.
try to update the bios of the laptop and the versions of the drivers for the hardware, if there is a fresh one. maybe it makes sense to turn off the chrome flash and try to work with the system
Issue closed, thanks everyone.
It helped to disable the built-in flash plugins of Chrome.
Some kind of conflict with the iron in these plugins apparently.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question