You could try to check if there is a newer display driver on the manufacturer's website or as optional in Windows Update. But I don't think this will change much, as I explain below.
In Windows 8, Microsoft has decided that its new and wonderful DPI algorithm,
which attempts to get things sized correctly based on both the resolution, size, and pixel density of a given display,
does a better scaling job than any user could possibly do.
Therefore Microsoft now decides for you on the best scaling for each and every one of your monitors depending on that monitor's properties.
The slider now only means : larger or smaller than the Microsoft-calculated scaling,
and it applies to all the monitors.
Another Microsoft brain-storming has resulted in the Windows 8 slider being replaced
in Windows 8.1 by a list of preset percentages, which works just like the slider.
The change was probably meant to underline the fact that the new automatic DPI algorithm
in Windows 8.1 is even more wonderful than that of Windows 8.
Setting the "Let me choose one scaling level for all my displays" will force the same
identical scaling on all monitors, no matter their size or properties,
which is exactly the opposite of what you wish.
This is of course another half-assed design decision by Microsoft,
based on the "Microsoft knows best" conception, manifestly untrue,
which there is no way to undo except by down-grading to a previous version of Windows.
One can only hope that some future update will correct this, but I think this
is quite unlikely to happen.
For more information, see the Extreme Windows Blog article Windows 8.1 DPI Scaling Enhancements.
EDIT: This has now been corrected in Windows 10, where individual
scaling is now possible.
Chrome has been lacking support for DirectWrite to render fonts on Windows. The issue you are describing is what happens not only on high DPI settings but also on normal (100%) settings.
There is a long and old thread on the Chromium issues website: https://code.google.com/p/chromium/issues/detail?id=25541
The developers said they already enable it on Chrome Canary builds but there is no timetable on when the regular version of Chrome will support it.
You can enable DirectWrite launching the latest Chrome Canary build with the following parameters:
# To enable DirectWrite:
--enable-direct-write --no-sandbox
# To enable DirectWrite and sub-pixel font scaling:
--enable-direct-write --no-sandbox --enable-experimental-web-platform-features
The above parameters were listed by one of the developers in the same thread. The post link is https://code.google.com/p/chromium/issues/detail?id=25541#c61
Be warned the by disabling the sandbox feature you are compromising one of Chrome's security features.
Opera, which uses Webkit, has the same problem as Chrome.
Best Answer
More info