Chrome is causing BSoD errors on Windows 10 [7 Tested Fixes]

• If it occurs while you’re working in Chrome, a BSoD might be caused by some browser settings.
• Sometimes, G oogle Chrome causes a BSoD MEMORY_MANAGEMENT error.
• No matter the error, you shouldn’t have any trouble fixing it if you use a BSoD troubleshooting tool.
• Logging into Safe mode with Networking on Windows 10 will help you test if the issue is Chrome or your system.

• Easy migration: use the Opera assistant to transfer exiting data, such as bookmarks, passwords, etc.
• Optimize resource usage: your RAM memory is used more efficiently than Chrome does
• Enhanced privacy: free and unlimited VPN integrated
• No ads: built-in Ad Blocker speeds up loading of pages and protects against data-mining
• Download Opera

We can agree that a Blue Screen of Death is something no one wants to see on their Windows PC. They appear rarely but when they do, then they certainly point towards a major issue.

A hefty number of users reported BSoDs caused by Chrome, while they were roaming the internet or watching YouTube videos. Apparently, the system just crashed on them.

Now, we’re afraid that this matter is hardly caused by Chrome on its own. The browser is probably only a trigger. Nonetheless, we have a hefty number of steps for you to try and, hopefully, address the BSoDs for good.

How to fix BSoD caused by Chrome on Windows 10

1. Disable Hardware Acceleration
2. Try a BSoD troubleshooter
3. Run SFC and DISM
4. Disable Fast Boot and start PC in a clean boot regime
5. Boot into Safe mode
6. Update Windows and BIOS
7. Run Driver Verifier and reinstall failing drivers
8. Reinstall Windows 10

1. Disable Hardware Acceleration

1. Open Chrome.
2. Click on the 3-dot menu and open Settings.
3. In the Search bar, type hardware.
4. Toggle off the “Use hardware acceleration when available” setting.
5. Restart your browser.

2. Try a BSoD troubleshooter

A dedicated blue screen fixer will look into all possible bugs that might have led to this issue, so it might be your best shot to get rid of it and to prevent such events in the future.

3. Run SFC and DISM

1. In the Windows Search bar, type cmd. Right-click click on Command Prompt and run it as admin.
2. In the command-line, type sfc/scannow and press Enter.
3. After its done, type the following command and press Enter after each:
   • DISM /online /Cleanup-Image / ScanHealth
   • DISM /Online /Cleanup-Image /RestoreHealth
4. When the procedure ends, restart your PC.

This issue probably goes beyond Chrome. We’re possibly looking at the Windows system corruption of some kind and the best way to resolve it is with SFC and DISM combined.

Those two are the built-in system utilities run through the elevated command prompt. Once you get them running, they’ll scan for system errors and fix them by replacing corrupted or incomplete files.

4. Disable Fast Boot and start PC in a clean boot regime

1. In the Windows Search bar, type Power and open Power & sleep settings.
2. Click on the Additional power settings.
3. Click on the Choose what the power buttons do from the left pane.
4. Choose Change settings that are currently unavailable.
5. Disable Fast Startup and confirm changes.
6. Now, in the Windows Search bar, type msconfig and open System Configuration.
7. Under the Services tab, check the Hide all Microsoft services box.
8. Click Disable all to disable all active third-party services.
9. select the Startup tab and go to Task Manager.
10. Prevent all programs from starting with the system and confirm changes.
11. Restart your PC.

A clean boot should eliminate the possible negative impact of third-party applications on your system stability.

5. Boot into Safe mode

1. During the startup, when the Windows logo appears, press and hold the Power button until the PC shuts down.
2. Power on the PC and repeat the procedure 3 times. The fourth time you start the PC, the Advanced recovery menu should appear.
3. Choose Troubleshoot.
4. Select Advanced Options and then Startup settings.
5. Click Restart.
6. Choose Safe mode with Networking from the list.
7. Run Chrome and look for improvements.

Run a System Scan to discover potential errors

If the problem disappears, we strongly suggest following instructions from the next step on this list. If it’s still present, move to the next step.

6. Update Windows and BIOS

Now we’re reaching the most probable reason for the BSoD. And those are drivers. The simplest way to address this is to allow Windows Update to install all missing drivers.

In addition, we’ll need you to check on the BIOS/UEFI version you’re running and apply updates if necessary. You can find out everything you need to know about BIOS flashing in our extensive guide.

For the driver update, we suggest opening Device Manager and checking for driver updates. They should be administered automatically. If that doesn’t help, move to next step.

7. Run Driver Verifier and reinstall failing drivers

1. Make sure to create a Restore Point.
2. Right-click on the Start and open Command Prompt (Admin) from the Power User menu.
3. In the command line, type verifier and press Enter.
4. The windows will pop-up.
5. Choose “Create custom settings (for code developers)” and click Next.
6. Select I/O verification, Force pending I/O requests, and IRP logging from the list and click Next.
7. On the next screen, click “Select driver names from a list”.
8. Check all non-Microsoft drivers and click Finish.
9. Reboot your PC and let the Driver Verifier work in the background for no more than 48 hours. 24 hours should do. You might experience slight performance drops as the tool will be a burden on drivers for the testing purpose.
10. After 24 hours or so, open Driver Verifier again and choose to Delete existing settings and click Finish. Restart your PC.

Driver Verifier, the built-in tool which detects illegal actions made by corrupt drivers. That way you’ll find out what exact driver is causing BSoD and you can install a proper iteration timely.

8. Reinstall Windows 10

Finally, if none of the previous steps worked for you, we suggest reinstalling Windows 10 cleanly. Of course, this time we suggest relying on OEM-provided drivers instead of their generic versions provided by Windows Update. If you’re not sure how to install Windows 10, we’ve got a full guide on that.

With that said, we can wrap it up. If you have any questions or suggestions, make sure to tell us in the comments section below.

Google Chrome , BSOD and Windows 10

Replies (4) 

Please read this wiki to find out how to find and upload your event viewer logs

All instructions are in our Wiki article below.
Should you have any questions please ask us.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The SFC scan was the first thing I tried but it was unsuccessful. It just caused more problems. «Windows could not perform the operation» it said. Getting rid of the extension in Chrome that I don’t use did the trick. I’m tempted to run the SFC scan again, but based on its performance history I’m thinking no. Do you think it is worth A try?

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

IF SFC fails the chances are that the OS is wounded and often the fastest way to fix it is to refresh the OS or do a repair install from the win 10 ISO

Of course you can try SFC and if you have a problem we can help you with it

Читайте также:  Что такое olp лицензии windows

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

IF SFC fails the chances are that the OS is wounded and often the fastest way to fix it is to refresh the OS or do a repair install from the win 10 ISO

Of course you can try SFC and if you have a problem we can help you with it

I tried running the SFC/scannow and got the same result as before. «. could not perform the requested operation.

Immediately after running, the BSOD has now returned «critical-process-died». Computer before scan=fine.

Computer after scan=broke. I’ve already spent several hours with MS techs to fix this. I’ve had enough; its going to the computer shop. Thanks for your help but its a bad sign when the MS tools are broken to start to fix a new broken OS.

Bsod при работе с любым браузером

Синий экран появляется как только открываю любой браузер.. скрины ошибок во вложении.

Пытался лечить, но пишет тоже ошибку.

Ответы (15) 

* Попробуйте выбрать меньший номер страницы.

* Введите только числа.

* Попробуйте выбрать меньший номер страницы.

* Введите только числа.

Был ли этот ответ полезным?

К сожалению, это не помогло.

Отлично! Благодарим за отзыв.

Насколько Вы удовлетворены этим ответом?

Благодарим за отзыв, он поможет улучшить наш сайт.

Насколько Вы удовлетворены этим ответом?

Благодарим за отзыв.

Был ли этот ответ полезным?

К сожалению, это не помогло.

Отлично! Благодарим за отзыв.

Насколько Вы удовлетворены этим ответом?

Благодарим за отзыв, он поможет улучшить наш сайт.

Насколько Вы удовлетворены этим ответом?

Благодарим за отзыв.

Вот что получилось.

Дамп: 061520-28515-01.dmp (15.06.2020 16:23:01)
Код: 0x133 — DPC_WATCHDOG_VIOLATION
Процесс: Registry, вероятно вызвано: NETIO.SYS
FAILURE_BUCKET_ID: 0x133_DPC_NETIO!NetioAllocateMdl

Дамп: 061520-27578-01.dmp (15.06.2020 19:01:58)
Код: 0x1E — KMODE_EXCEPTION_NOT_HANDLED
Процесс: System, вероятно вызвано: fwpkclnt.sys
Сторонние модули в стеке: Netwtw08.sys
Сторонние модули в Raw-стеке: igdkmd64.sys, klflt.sys, ipeaklwf.sys, klwtp.sys, Netwtw08.sys
FAILURE_BUCKET_ID: 0x1E_c0000005_R_fwpkclnt!FwppInjectComplete

Дамп: 061120-28765-01.dmp (11.06.2020 12:03:40)
Код: 0x1E — KMODE_EXCEPTION_NOT_HANDLED
Процесс: System, вероятно вызвано: NETIO.SYS
Сторонние модули в стеке: klim6.sys
Сторонние модули в Raw-стеке: klflt.sys, acsock64.sys, ipeaklwf.sys, rt640x64.sys, klim6.sys, kneps.sys
FAILURE_BUCKET_ID: 0x1E_c0000005_NETIO!NetioAllocateMdl

Дамп: 061120-28171-01.dmp (11.06.2020 17:00:23)
Код: 0x1E — KMODE_EXCEPTION_NOT_HANDLED
Процесс: avp.exe, вероятно вызвано: fwpkclnt.sys
Сторонние модули в стеке: rt640x64.sys
FAILURE_BUCKET_ID: 0x1E_c0000005_R_fwpkclnt!FwppInjectComplete

Дамп: 061120-27718-01.dmp (11.06.2020 07:55:49)
Код: 0xD1 — DRIVER_IRQL_NOT_LESS_OR_EQUAL
Процесс: chrome.exe, вероятно вызвано: fwpkclnt.sys
Сторонние модули в стеке: Netwtw06.sys
FAILURE_BUCKET_ID: AV_fwpkclnt!FwppInjectComplete

Похоже проблема не в браузера, а в сети.
Попробуйте перезапустить сетевое соединение, для этого выполните следующее в командную строку с правами администратора введите:
netsh winsock reset и нажмите Enter.
netsh int ip reset и нажмите Enter.
ipconfig /release и нажмите Enter.
ipconfig /renew и нажмите Enter.
ipconfig /flushdns и нажмите Enter.