Sign in with
Sign up | Sign in
Your question
Solved

Hardware Acceleration Turned off yields better results?

Tags:
  • Chrome
  • Hardware
  • Apps
Last response: in Apps General Discussion
Share
August 10, 2014 10:35:37 AM

So I've used Chrome for quite a while and after switching over to the Chrome 37 I found that it kept BSODing my computer. So I looked it up and all and some people found that hardware acceleration was going against their drivers. So i turned it off and so far it hasn't crashed but I noticed something odd as well; Chrome is running much much faster! Why is that? Wasn't the point of Hardware Acceleration to speed it up?

More about : hardware acceleration turned yields results

August 10, 2014 12:55:19 PM

Marco Lalvay said:
So I've used Chrome for quite a while and after switching over to the Chrome 37 I found that it kept BSODing my computer. So I looked it up and all and some people found that hardware acceleration was going against their drivers. So i turned it off and so far it hasn't crashed but I noticed something odd as well; Chrome is running much much faster! Why is that? Wasn't the point of Hardware Acceleration to speed it up?


Probably a placebo effect, but if there was a driver conflict that resulted in BSoDs there's a good chance that there were other performance affecting consequences as well
m
0
l
August 10, 2014 12:59:02 PM

It definitely wasn't a placebo, it was much much faster at loading videos and pictures. But i could agree with driver mess ups, any ideas how to find out what the driver conflicts might have been?
m
0
l
Related resources
August 10, 2014 1:00:40 PM

Marco Lalvay said:
It definitely wasn't a placebo, it was much much faster at loading videos and pictures. But i could agree with driver mess ups, any ideas how to find out what the driver conflicts might have been?


The BSoD will usually provide some indication of which kernel module caused the crash. If it's a case of memory corruption though the crash may occur in a module other than the one that contains the bug though. The best approach is to simply perform a blanket driver update from all appropriate vendors.
m
0
l
August 10, 2014 1:11:49 PM

After a quick look through it seems to be ATI Radeon Kernel Mode Driver somehow conflicting with Chrome. So I guess all that's left to do is boot in safe mode and uninstall and re install all my graphics drivers yes?
m
0
l

Best solution

August 10, 2014 1:38:24 PM

Marco Lalvay said:
After a quick look through it seems to be ATI Radeon Kernel Mode Driver somehow conflicting with Chrome. So I guess all that's left to do is boot in safe mode and uninstall and re install all my graphics drivers yes?


Yeah. reboot and run Display Driver Uninstaller and then install the latest stable 14.4 release or 14.7 beta release
Share
August 10, 2014 2:54:55 PM

Well that's all done and done. Ill let ya know if my computer crashes with hardware acceleration on or not by sometime tomorrow. :3
m
0
l
August 10, 2014 3:03:54 PM

okay, sounds good
m
0
l
August 11, 2014 3:24:43 PM

So far so good! thanks for the help yo :3
m
0
l
August 11, 2014 3:46:53 PM

glad to hear it!
m
0
l
October 12, 2014 10:45:56 PM

Marco Lalvay said:
..............some people found that hardware acceleration was going against their drivers. So i turned it off and so far it hasn't crashed but I noticed something odd as well; Chrome is running much much faster! Why is that? Wasn't the point of Hardware Acceleration to speed it up?


This is in response to your observation of Chrome running much faster after turning off hardware acceleration and why that is. I'm not an expert, but in trying to find out why Chrome is constantly crashing my laptop (high CPU usage when Chrome is in use, making the laptop sluggish to the extreme) found that the GPU process Chrome uses to render graphics seems to be my issue. Some have reported that by disabling hardware acceleration, Chrome runs smoother, faster so there must be a connection between the two. Here is a link I found that confirmed my issue and discusses this briefly, although I admit a lot of this info is over my head: https://code.google.com/p/chromium/issues/detail?id=385.... This is one of several pieces of information I read on this particular issue; I hope it gets fixed in a future update of Chrome.
m
0
l
!