Hi Leo,
Thank you! I appreciate the response a lot, but unfortunately there's really not much more detail i can give you.
I don't have 10.2.0.1 or 10.2.0.2 installed on my machine, and frankly, i don't want to, because 10.2.0.0 has been running great for about a week now (and the week before trying 10.2.0.2), and i don't want to have the whole system freeze up again over and over causing crazy amounts of rollbacks and corruption in files and settings of any application running at the time (hinting at stuff like registry change journal rollbacks, etc).
I do agree that it seems highly unlikely that Directory Opus is the cause of any of this.. But what can i say? I have rolled back every single driver to versions that are at least months old (when i was most definitely not experiencing a single problem), one by one. This includes Intel AHCI storage drivers, Realtek network drivers, Realtek audio drivers, nVidia graphics drivers, Logitech mouse drivers, Renesas USB 3.0 drivers. I uninstalled a lot of applications that could cause problems like freezing, such as: Diskeeper (defragger), Visual Studio 2010 and 2012 profiling drivers, Avast! anti-virus, cFos Broadband Connect (PPPoE dialing driver) and cFosSpeed (traffic shaper), Adobe Flash, Fraps.
None of those had an impact. Chrome still froze. The only thing i didn't do at the time was rollback Directory Opus, because like you, i didn't even imagine that it could be the cause of the freezes.
A simple way to reproduce the problem is to just hover over the small blank tab thingy in Chrome and click it until you've opened about 100 tabs. Then close the tabs one by one. This causes the freeze about 30% of the time. Make sure to have around 10-20 tabs of random stuff already open in Chrome--but there's no need to touch them. Sometimes just opening and closing Chrome over and over again causes the freeze. Sometimes i just boot my computer, Directory Opus and a few background apps auto-load, i dial up my PPPoE connection, open Chrome as my first order of business and wham! Freeze.
There's no single web page or image that causes this freezing. I browse about a gazillion different things daily. It's entirely random.
As for the Chrome extensions i have installed, they are: "avast! WebRep 7.0.1474" and "Google Docs 0.3", both of which i have tried disabling to no avail. In fact the first thing i did was curse at Avast and try a few other anti-virus before realising that it was not Avast at all.. I have an extension called "NJStar Chromate - Chinese WebSite Convertor 3.0.2 " that is always disabled--i only have it there to remember what its name is, should my Chinese wife (who needs it) needs it reinstalled on her Chrome. It might be worth noting that i ran Chrome with "--disable-gpu" or some such command line, verified that all hardware acceleration was disabled via "chrome://gpu-internals/", and it still froze. I've also disabled every single "plugin" (including Flash, etc) at "chrome://plugins/" (not quite sure how they differ from "extension"), and the freezes still happen.
I know i probably should be reporting this to "the Chrome team" (which i presume is "Google"), but there's two problems there. The first is that the forums are positively flooded with rubbish. My post would get lost. It doesn't look like Google even read most of it anyway, and for good reason given the garbage i've seen in there. The second is, and i'm not quite sure how to say this without offending anyone, but i very much doubt that Chrome is the actual program at fault here, since, you know, it's a multi-billion dollar company with tens of thousands of employees whose browser is used on almost every conceivable OS and computer anywhere in the world by hundreds of millions of people. For example, if applications started freezing on my computer after i installed a relatively unknown anti-virus software, i would not fire off reports to any of those application vendors--i would report it to the anti-virus vendor.
I've been waiting for 2 weeks to see if my computer or Chrome freezes again. I use them heavily every day, all day. But, it has not frozen as long as Directory Opus 10.2.0.0 is installed. All of my normal apps and latest drivers and normal hardware is installed and in use.
I could probably try to image my boot/system drive, and then install 10.2.0.1/2 again and try to freeze it all up, but it would be a lot of trouble, and i don't even know what i would be doing that for. It would only be proving something that i already know, and giving me no extra information. For example, i tried running a circular xperf session and waited for the freezing, whereupon i rushed to the console window on my second monitor to get it to dump the latest activity to an .etl, but after hard resetting a few minutes later, the .etl was 0 bytes when i booted up and found it..
I'm seriously out of ideas and frustrated about the whole thing. At the same time i've been sitting for 2 weeks (with a brief and annoying ~3 hour session in the middle with Directory Opus 10.2.0.2) very content with Chrome not freezing. I'd like to keep the status quo if possible, but i also really want the CPU usage fixes that came in 10.2.0.2.
This seems to be somewhat of a stalemate. I'll try the next beta of Directory Opus, but if it freezes again, i'm rolling back to 10.2.0.0. There's really not much more information i can give you regarding the freezes, unless you have something specific you want to ask me to provide. Perhaps some sort of "dxdiag" equivalent that will dump my entire system specs to you. I don't know what tool would be the best thing for that.
The bottom line is, and though it may seem like i'm either mistaken or lying: Directory Opus 10.2.0.0 runs brilliant (except a tad of a CPU hog) and not a single thing (including Chrome) crashes or freezes for weeks (and likely for months and years to come if this issue can't get sorted and i don't update Directory Opus)--but within hours of installing either *.1 or *.2 beta, Chrome freezes.
Given this, though it seems highly unlikely that Directory Opus is causing the freezes, it can also be said that it is highly unlikely that any underlying and perhaps very slight hardware or driver issues would not present themselves at all for weeks when using Directory Opus 10.2.0.0. I've found the trigger, for sure (ie: Directory Opus betas). But is the trigger the actual cause? I don't know. It seems likely, since the likelihood of presentation of issues would be high after weeks, if there were even slight hidden hardware/driver issues somewhere. Also given the fact that the betas are "betas". I don't know how many GPSoft customers actually use the betas. I'm sure you have information on that. But it's not everyone, right? The pool of non-beta users is somewhat small enough already (compared to say, Chrome users), without resorting to dividing that pool into those who read forums, dividing further into those who can diagnose issues, dividing further into those who have mighty big beasts of computers, dividing even further into those who fit all of the above criteria and run the betas. That would seem to be a very small sample of people.
I lost a week of my life to trying to figure out what was causing the freezes only to have them simply cease upon installing Directory Opus 10.2.0.0 instead of 10.2.0.1. I've lost well over an hour of my life writing this post. I'm really trying to not lose more precious time over something that it would appear i have barely any control over anyway.
Of course i could just be cheeky and ask: what did you change or break in the betas? 
That's proprietary information, i'm sure. Information i would very much like to have, but unfortunately i have no way of obtaining. All of my cards are on the table--i've told you everything--but i don't see many of GPSoft's cards. There of course are internal changing workings at play that i have no idea about.
Maybe i should just stick to normal releases and forget betas. 
By the way, i took a sleeping pill about an hour ago, and i'm kind of hallucinating, so please forgive any strange stuff or grammar errors in this post. I did my best. I need to post this before i flop on the keyboard.
I just want to say thank you again for the response and the attempts to reproduce the problem i am having. I'd really like to help in any other way that i can. Let me know if there's anything i can do to help.
That's about the sum of it. Do with that information what you will. I would use it to fix whatever is broken.
I believe i haven't insulted anyone here. Egos may be damaged, but that's what happens in debates. 