Too little to read; what does it say?
Sorry for the late response and maybe you have it solved or since moved on to a different solution. But, here is what I have for you anyway.
What did your event log say? "Side-by-side" I have seen before when developing code working with [well, I shouldn't say precisely, so just say custom hardware with it's own firmware which isn't an embedded OS] and a Windows USB driver to interface with it where the firmware developers [using a proprietary C++ compiler and library for the hardware] didn't have the Microsoft developer tools on their system that we did, so on some machines we found the same error and when working with the hardware. This tends to happen when the C++ run-time libraries on your machine are not up to date [and that was the case with us] such that you get a cryptic side by side error in your event log and in your application if it bubbles it up which GUIMiner apparently did [I suspect it doesn't have a global handler
].
Under Administrator tools, look at your event view and see if you can find the entries. Windows Logs->Applications is the most likely place. Possibly "Applications and Services Logs"->"Hardware Event" if it caused a fault in your hardware. Easy answer ... make sure you are up to date with Windows Updates, however this may or may not be enough depending upon the OS and what you have installed]. Another answer, get all the recent C++ run-time installations and install them manually and see if that helps .. and it should [if you are a Windows Software Developer and have Visual Studio on your machine, then if you have version 2008 or 2010, you SHOULD have the libraries installed already].
Here is an older link that describes it, but it applies equally to later versions except for the actual file names and version numbers of course.
http://msdn.microsoft.com/en-us/library/ms235624%28v=vs.80%29.aspxHere are the links to the x86 (32-bit) libraries which is certainly what GUIMiner is using [I didn't check, but it is a front end and not worth the effort to compile against 64-bit most likely]. You may want to find the x64 (64-bit) versions as well just so you are current on both fronts if you are running a 64-bit version of Windows.
So, if you haven't already solved the problem, or somebody else runs into this, give it a try. I know a lot of people run old hacked and illegal versions of Windows XP and don't get updates (better to buy it than risk missing the security updates), and this should help those people as well, although it is not my goal to help such people ... buy a licensed copy ... OEM if you need it.
Anybody having trouble before and finds this works for them, please let me know how this works for you. Donations appreciated if you feel generous.