I was eager to update to new version 7.5.0 x64 ... for testing. All earlier test versions have worked for me without any problems.

I have not changed any settings or hardware in my computer. Today I was running the 7.4.42 x64 version until I updated to 7.5.0 x64.

It doesn't start. When I click on the boincmgr.exe I can see on the Windows Task Manager that a new process is trying to start, but then that process disappeares right away. I can't even see its name. The Boinc Manager window doesn't show up at all. Not even flashes.

I run the installer as administrator and installation seem to finish without any problems. In the end of installation process there is the window with an option to start Boinc right away. If I choose to start it from there, it doesn't start. And Boinc Manager doesn't start directly from the exe-file.

I tried to start Boinc Manager with "run as administrator" and even with all compability modes, but it didn't help. I did a reboot after installing 7.5.0 to see if that would help, but it didn't help.

My computer has Windows 7 64bit Pro with service pack 1.

I would be happy to send somekind of Boinc-generated error report, but there aren't any.

Do you have any suggestions how to make that 7.5.0 x64 run in this machine. All previous test versions have run smoothly. Are there perhaps some new technical requirements or need for some additional packages or something like that... ?

Thanks for any help with this!

First off, try to download the installer again. You said in another post that you 'guessed' at the name of the installer, perhaps that you guessed wrong or that the download was somehow fumbled.

The new 7.5 Change Log thread will always have links to the newest clients. Just click, tell where to save, download. Wait for the download to be completely in before installing. When using Internet Explorer or a similar browser that asks if it should run it or save it, save it. Run the installer only after it's completely downloaded. Save it to a different directory, preferably even a different drive/partition than you saved the original file. Do not overwrite the original file, just in case.

When it's downloaded, uninstall present BOINC 7.5.0 through Add/Remove Programs, then start the new installer. See how that goes.

---

Okay, here's what I tried:

1. I downloaded the installer (http://boinc.berkeley.edu/dl/boinc_7.5.0_windows_x86_64.exe) this time with a different web browser (Chrome). I saved the file into physically different HDD than before.

2. I uninstalled present BOINC (it was now 7.4.42 x64 again... I had installed that one back already). I did this from the Windows "Add/Remove Programs".

3. I deleted the empty BOINC program folder which uninstallation had left there. I kept my BOINC data directory (and all the material in it), which is located in different disk partition. I renamed the folder with a new name.

4. I used two different registry cleaning softwares to wipe the registry through to get rid of any possible "remains". I have used the same programs for many years already.

5. I restarted Windows.

6. I shut down the antivirus software (it has been in use for a long time and never before has caused any conflict when installing BOINC, even when it has been ON).

7. I went to my new downolad folder and run the BOINC-installer "as administrator".

8. I chose a completely new program folder for BOINC and chose my newly renamed data folder for BOINC data.

9. Installation finished succesfully and gave an option to start BOINC Manager. I waited until the creation of a Windows restore point had finished (it was ignited by the installation). Then I chose to start BOINC.

10. Nothing happened.

11. I opened up Windows Task Manager to see processes.
boinctray.exe was running, but nothing more from BOINC.

12. I clicked Windows START and tried to start BOINC Manager from there. Now I saw boincmgr.exe visit process list for half a second. Then it was gone.
boinctray.exe kept running smoothly.

13. I went to BOINC program folder and tried to start boincmgr.exe from there. I saw it visit process list for half a second. Then it was gone.

14. I ended boinctray.exe process. Then I tried to start it from the program folder. It started again and run fine.

15. I tried to start boincmgr.exe with "as administrator" and also with different combinations of compability modes + "as administrator" or without it. No luck.

16. I tried to start boinc.exe . It run and went through the CPU benchmarking. There was nothing abnormal on the texts it displayed on the command prompt. I had halted computation before I uninstalled BOINC. Any computation processes are not running right now.


I guess I could operate BOINC via the command prompt, but BOINC Manager doesn't want to work.

edit: Yep, I entered "boinccmd --set_run_mode always" and both the CPU and GPU tasks started (same amount of them as before).

edit2: I said boinctray.exe is running. Yes, it can run, but I noticed now the tray icon isn't actually showing up! BOINC doesn't seem to be able to display any kind of graphical life signs.

Additional info about the tray icon:

Control Panel\All Control Panel Items\Notification Area Icons ...
There... I have a tick on this box: "Always show all icons and notifications on the taskbar". That one at least shouldn't stop the tray icon from showing up.

Boinc tray is the mouse and keyboard idle detection program, it doesn't need to show itself,

Claggy

The icon you see in the tray - err, "notification area" - when BOINC is running doesn't come from boinctray.exe - silly name - but from boincmgr.exe

Well, I downloaded and installed v7.5.0 (x64 version) over an hour ago, and it's run smooth as silk ever since. It might be worth Richie hunting through the .txt files in the BOINC directories, especially any with 'err' in the name.

Likewise, I've downloaded and installed Boinc 7.5.0 x64 on my i5-3210M laptop, Boinc Manager started and is running O.K here too.

Claggy

So BOINC can run fine (if started with boinc.exe), you only have a problem with running BOINC Manager (the GUI)?

* In the BOINC Data directory, open stderrgui.txt, stdoutgui.txt. Are there any entries in here for around the time BOINC Manager didn't want to start? If so, what?
* Which program directory did you install BOINC into?
* Which program directory was BOINC using before?
* When checking in C:\Program Files (x86)\ is there a BOINC directory there?
- If so, what's in it?
* When checking in C:\Program Files\ is there a BOINC directory there?
- If so, what's in it?
* Have you checked in Windows Event Viewer (Start->Search, type Event->click Event Viewer), in the Windows Logs->Application, if there is any mention of what's happening to BOINC Manager?
* Which anti virus and other anti malware programs are you using?
- Have you ever put the BOINC programs directory and its data directory up as exclusive zones in these programs, not to be actively scanned by them?
- Even with your main AV not started, Windows will have protection of its own. Check that Windows Defender doesn't do weird things.
* Is BOINC Manager allowed through your firewall?
- If you can set separate ports for it, did you set it to work on TCP 43416?
* Do you have any program developing/compiling programs/peripherals installed that you think we should know about? Any hard linked wxWidgets or sorts?

---

* Is BOINC Manager allowed through your firewall?
- If you can set separate ports for it, did you set it to work on TCP 43416?

Er, that would be 31416 (pi), unless they've changed it recently?

Just awake, couldn't remember. :)
Thx

---

So BOINC can run fine (if started with boinc.exe), you only have a problem with running BOINC Manager (the GUI)??

Yes, that's correct.

* In the BOINC Data directory, open stderrgui.txt, stdoutgui.txt. Are there any entries in here for around the time BOINC Manager didn't want to start? If so, what?

stderrgui.txt
That file is empty and has size of 0KB.

stdoutgui.txt
That file has size of 8KB, but it has been modified last time about a year ago.

* Which program directory did you install BOINC into?

I have configured Windows to install all programs to F: drive by default (already about two years ago)... and there are directories "F:\Program Files" and "F:\Program Files (x86)".

For this latest fresh installation I decided to make a BOINC program directory directly under the root:
F:\BOINC_7.5.0

I have installed earlier versions to a few different locations (also directly under root folder, like this time) and haven't had any problem with that.

* Which program directory was BOINC using before?

F:\Program Files\BOINC

* When checking in C:\Program Files (x86)\ is there a BOINC directory there?
- If so, what's in it?
* When checking in C:\Program Files\ is there a BOINC directory there?
- If so, what's in it?

I checked those related locations on drives F: and C: . There were no signs of any BOINC folders.

* Which anti virus and other anti malware programs are you using?
- Have you ever put the BOINC programs directory and its data directory up as exclusive zones in these programs, not to be actively scanned by them?
- Even with your main AV not started, Windows will have protection of its own.

Avast Free... only. I have disabled the module which would perform active system scanning. Only the web browser protection is ON.

Check that Windows Defender doesn't do weird things.
* Is BOINC Manager allowed through your firewall?
- If you can set separate ports for it, did you set it to work on TCP 43416?

I have turned off Windows Defender for at least some months ago. I feel I don't need it running in this computer. Windows Firewall is ON. I don't know if it allowed this latest boincmgr.exe to go through. I have never made any rules for BOINC files before. Now I made new rules in Windows Firewall to let boincmgr.exe to have any kind of traffic. Then I tried to start boincmgr.exe. I still doesn't start.

* Do you have any program developing/compiling programs/peripherals installed that you think we should know about? Any hard linked wxWidgets or sorts?

I don't think I have.

* Have you checked in Windows Event Viewer (Start->Search, type Event->click Event Viewer), in the Windows Logs->Application, if there is any mention of what's happening to BOINC Manager?

I'll continue this in another message...

also something may be running on the computer, like the last update MS update that is now causing problems. (MS screwed up something in the last few updates)

my 2 cents....

That might have something to do with this. Or maybe this Windows installation has broken already long time ago. This has been working well, but maybe there is something messed up underhood. I remember one thing now:

I was willing to try the new IE about a year ago (it must have been the new version 11... and I wanted to try the 64bit version of it). I updated my older IE to that 64bit version... and what I got was this same kind of behaviour: IE never started. Well, it shortly flashed on the screen, but that was all it did.

I really tried to find a solution for that and used google for hours and tried this and that, installing and uninstalling old or new IE a dozen times. What was interesting then... If I remember correct, also the older IE never run anymore. And that came after I had tried to upgrade to the 64bit version. After that, I uninstalled IE and felt relaxed. I didn't need it but would had liked to try it anyway. IE just didn't want.

-----------------------------------------

Just to mention... I wanted to try 7.5.0 x64 also on two other computers last night. They have Windows 10 build 10049. These installations were succesfull and also the BOINC Manager GUI runs on them. No problems.

In that case, care to try if BOINC 7.5.0 32bit works?

---

* Have you checked in Windows Event Viewer (Start->Search, type Event->click Event Viewer), in the Windows Logs->Application, if there is any mention of what's happening to BOINC Manager?

There are some lines which have "BOINC Manager" or "boinctray" or "boinc.exe"... but I have difficulties on reading which of my actions has generated which event.

I tried now to start boincmgr.exe so that it flashed half a second in Windows Task Manager process list. Then I refreshed Event Viewer Application event list. There hadn't been generated any new event messages. If a failed "start" of boincmgr.exe generates something, that information doesn't seem to end up on this specific event list.

I searched for "boinc" events and all they are "Information" Level, not errors or warnings.

I don't know if these are any useful, but here are some examples from last night (~24 hours ago):

----------------------------------------------
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-08T00:59:22.000000000Z" />
<EventRecordID>19142</EventRecordID>
<Channel>Application</Channel>
<Computer>ownPC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>PCA2</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>boinctray.exe</Data>
<Data>7.5.0.0</Data>
<Data>BOINC System Tray for Windows</Data>
<Data>BOINC client</Data>
<Data>Space Sciences Laboratory</Data>
<Data>200</Data>
<Data>-1</Data>
<Data />
<Data />
<Data />
<Data />
<Data>C:\Users\Richie\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_boinctray.exe_ebf0fac9ed6e8903efc96dceb855b6228fe8215_0ebb4da2</Data>
<Data />
<Data>0</Data>
<Data>7df0c974-dd8a-11e4-ab67-00248c3d3d44</Data>
<Data>4</Data>
</EventData>
</Event>
----------------------------------------------
----------------------------------------------

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-08T00:59:22.000000000Z" />
<EventRecordID>19141</EventRecordID>
<Channel>Application</Channel>
<Computer>ownPC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>PCA2</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>boinctray.exe</Data>
<Data>7.5.0.0</Data>
<Data>BOINC System Tray for Windows</Data>
<Data>BOINC client</Data>
<Data>Space Sciences Laboratory</Data>
<Data>200</Data>
<Data>-1</Data>
<Data />
<Data />
<Data />
<Data>C:\Users\Richie\AppData\Local\Temp\{10257b78-bc2d-41c5-bb65-ae0f534aa707}\appcompat.txt C:\Users\Richie\AppData\Local\Temp\Tab4D7C.tmp</Data>
<Data />
<Data />
<Data>0</Data>
<Data>7df0c974-dd8a-11e4-ab67-00248c3d3d44</Data>
<Data>0</Data>
</EventData>
</Event>
----------------------------------------------
----------------------------------------------

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-08T00:59:07.000000000Z" />
<EventRecordID>19140</EventRecordID>
<Channel>Application</Channel>
<Computer>ownPC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>PCA2</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>boincmgr.exe</Data>
<Data>7.5.0.0</Data>
<Data>BOINC Manager for Windows</Data>
<Data>BOINC client</Data>
<Data>Space Sciences Laboratory</Data>
<Data>200</Data>
<Data>-1</Data>
<Data />
<Data />
<Data />
<Data />
<Data>C:\Users\Richie\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_boincmgr.exe_6fddb912696355a27485625a9b8fd4162ca7515_08131238</Data>
<Data />
<Data>0</Data>
<Data>74e24d29-dd8a-11e4-ab67-00248c3d3d44</Data>
<Data>4</Data>
</EventData>
</Event>
----------------------------------------------
----------------------------------------------

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-08T00:59:07.000000000Z" />
<EventRecordID>19139</EventRecordID>
<Channel>Application</Channel>
<Computer>ownPC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>PCA2</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>boincmgr.exe</Data>
<Data>7.5.0.0</Data>
<Data>BOINC Manager for Windows</Data>
<Data>BOINC client</Data>
<Data>Space Sciences Laboratory</Data>
<Data>200</Data>
<Data>-1</Data>
<Data />
<Data />
<Data />
<Data>C:\Users\Richie\AppData\Local\Temp\{7ef82caf-2d36-4c41-beb9-541f5b9da7ed}\appcompat.txt C:\Users\Richie\AppData\Local\Temp\Tab1220.tmp</Data>
<Data />
<Data />
<Data>0</Data>
<Data>74e24d29-dd8a-11e4-ab67-00248c3d3d44</Data>
<Data>0</Data>
</EventData>
</Event>
----------------------------------------------
----------------------------------------------

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-08T00:58:57.000000000Z" />
<EventRecordID>19138</EventRecordID>
<Channel>Application</Channel>
<Computer>ownPC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>PCA2</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>boinc.exe</Data>
<Data>7.5.0.0</Data>
<Data>BOINC client</Data>
<Data>BOINC client</Data>
<Data>Space Sciences Laboratory</Data>
<Data>200</Data>
<Data>-1</Data>
<Data />
<Data />
<Data />
<Data />
<Data>C:\Users\Richie\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_boinc.exe_57cbbe4544bce0f5472719be334dbfb7338574a2_050eeced</Data>
<Data />
<Data>0</Data>
<Data>69727099-dd8a-11e4-ab67-00248c3d3d44</Data>
<Data>4</Data>
</EventData>
</Event>
----------------------------------------------
----------------------------------------------

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-08T00:58:57.000000000Z" />
<EventRecordID>19137</EventRecordID>
<Channel>Application</Channel>
<Computer>ownPC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>PCA2</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>boinc.exe</Data>
<Data>7.5.0.0</Data>
<Data>BOINC client</Data>
<Data>BOINC client</Data>
<Data>Space Sciences Laboratory</Data>
<Data>200</Data>
<Data>-1</Data>
<Data />
<Data />
<Data />
<Data>C:\Users\Richie\AppData\Local\Temp\{6a00505b-0a7f-4af0-8bfe-f18840277afa}\appcompat.txt C:\Users\Richie\AppData\Local\Temp\TabECC4.tmp</Data>
<Data />
<Data />
<Data>0</Data>
<Data>69727099-dd8a-11e4-ab67-00248c3d3d44</Data>
<Data>0</Data>
</EventData>
</Event>
----------------------------------------------
----------------------------------------------

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-08T00:58:48.000000000Z" />
<EventRecordID>19136</EventRecordID>
<Channel>Application</Channel>
<Computer>ownPC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>PCA2</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>boinccmd.exe</Data>
<Data>7.5.0.0</Data>
<Data>BOINC Command Line Client</Data>
<Data>BOINC client</Data>
<Data>Space Sciences Laboratory</Data>
<Data>200</Data>
<Data>-1</Data>
<Data />
<Data />
<Data />
<Data />
<Data>C:\Users\Richie\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_boinccmd.exe_f639fa349f06c4bff9071b5e96a467c46a49c75_0ea6c754</Data>
<Data />
<Data>0</Data>
<Data>69727098-dd8a-11e4-ab67-00248c3d3d44</Data>
<Data>4</Data>
</EventData>
</Event>
----------------------------------------------
----------------------------------------------

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-08T00:58:48.000000000Z" />
<EventRecordID>19135</EventRecordID>
<Channel>Application</Channel>
<Computer>ownPC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>PCA2</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>boinccmd.exe</Data>
<Data>7.5.0.0</Data>
<Data>BOINC Command Line Client</Data>
<Data>BOINC client</Data>
<Data>Space Sciences Laboratory</Data>
<Data>200</Data>
<Data>-1</Data>
<Data />
<Data />
<Data />
<Data>C:\Users\Richie\AppData\Local\Temp\{668daa81-7eb5-4be1-8f63-b96ee2ab1ad0}\appcompat.txt C:\Users\Richie\AppData\Local\Temp\TabC72A.tmp</Data>
<Data />
<Data />
<Data>0</Data>
<Data>69727098-dd8a-11e4-ab67-00248c3d3d44</Data>
<Data>0</Data>
</EventData>
</Event>
----------------------------------------------
----------------------------------------------

In that case, care to try if BOINC 7.5.0 32bit works?

I'll try that in a minute.
_______________________________

BOINC 7.5.0 32bit is now installed... and BOINC Manager doesn't show up. Symptoms are the same as with 64bit version. BOINC client itself is able to start and is working (CPU & GPU are crunching).

I was willing to try the new IE about a year ago (it must have been the new version 11... and I wanted to try the 64bit version of it). I updated my older IE to that 64bit version... and what I got was this same kind of behaviour: IE never started. Well, it shortly flashed on the screen, but that was all it did.

I really tried to find a solution for that and used google for hours and tried this and that

Ever tried all the steps on http://www.thewindowsclub.com/internet-explorer-freezes-crashes-hangs? Because if you manage to fix IE, by fixing Windows, you'll probably also fix this problem with BOINC Manager.

---

[quote]* In the BOINC Data directory, open stderrgui.txt, stdoutgui.txt. Are there any entries in here for around the time BOINC Manager didn't want to start? If so, what?

stderrgui.txt
That file is empty and has size of 0KB.

stdoutgui.txt
That file has size of 8KB, but it has been modified last time about a year ago.

GUI log files have been in %APPDATA%\BOINC since 7.2/4.

Ever tried all the steps on http://www.thewindowsclub.com/internet-explorer-freezes-crashes-hangs? Because if you manage to fix IE, by fixing Windows, you'll probably also fix this problem with BOINC Manager.

Thanks for giving that link. I might consider trying those steps, but not right now. It would require installing IE again and I'm not too excited to do that. I don't trust it wouldn't cause some new abnormalities for this otherwise stable system. BOINC is also working "enough" for me at the moment.. I could go back to 7.4.42 if I need GUI.

[quote]* In the BOINC Data directory, open stderrgui.txt, stdoutgui.txt. Are there any entries in here for around the time BOINC Manager didn't want to start? If so, what?

stderrgui.txt
That file is empty and has size of 0KB.

stdoutgui.txt
That file has size of 8KB, but it has been modified last time about a year ago.

GUI log files have been in %APPDATA%\BOINC since 7.2/4.

Okay, I found them at C:\Users\Richie\AppData\Roaming\BOINC

stderrgui.txt is 9KB and it has about hundred times an "ASSERT" line like this:

ASSERT: Report generated in "C:\Users\Richie\AppData\Local\Temp\BOINC Manager_dbgrpt-3580-20150405T083806.zip".

I went to "C:\Users\Richie\AppData\Local\Temp\" but there were no BOINC folders. I think CCleaner might have removed them already as I have used it today.

I tried to start boincmgr.exe again and that generated a folder
"C:\Users\Richie\AppData\Local\Temp\BOINC Manager_dbgrpt-4208-20150410T081304"
and that same folder also as a zip-folder.

They contain two files:
BOINC Manager.dmp
BOINC Manager.xml

I opened BOINC Manager.xml and it says this:

--------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<report version="1.0" kind="exception">
<system description="Windows 7 (build 7601, Service Pack 1), 64-bit edition"/>
<modules>
<module path="F:\BOINC_7500_32\boincmgr.exe" address="00e40000" size="00723000" version="7.5.0.0"/>
<module path="C:\Windows\SysWOW64\ntdll.dll" address="77720000" size="00180000" version="6.1.7601.18247"/>
<module path="C:\Windows\syswow64\kernel32.dll" address="75900000" size="00110000" version="6.1.7601.18409"/>
<module path="C:\Windows\syswow64\KERNELBASE.dll" address="76040000" size="00047000" version="6.1.7601.18409"/>
<module path="F:\BOINC_7500_32\MSVCR100.dll" address="738b0000" size="000bf000" version="10.0.40219.1"/>
<module path="F:\BOINC_7500_32\MSVCP100.dll" address="742b0000" size="00069000" version="10.0.40219.1"/>
<module path="C:\Windows\syswow64\USER32.dll" address="75da0000" size="00100000" version="6.1.7601.17514"/>
<module path="C:\Windows\syswow64\GDI32.dll" address="76090000" size="00090000" version="6.1.7601.18275"/>
<module path="C:\Windows\syswow64\LPK.dll" address="75a10000" size="0000a000" version="6.1.7601.18768"/>
<module path="C:\Windows\syswow64\USP10.dll" address="752c0000" size="0009d000" version="1.626.7601.18454"/>
<module path="C:\Windows\syswow64\msvcrt.dll" address="75cf0000" size="000ac000" version="7.0.7601.17744"/>
<module path="C:\Windows\syswow64\ADVAPI32.dll" address="75790000" size="000a0000" version="6.1.7601.18247"/>
<module path="C:\Windows\SysWOW64\sechost.dll" address="75110000" size="00019000" version="6.1.7600.16385"/>
<module path="C:\Windows\syswow64\RPCRT4.dll" address="753f0000" size="000f0000" version="6.1.7601.18532"/>
<module path="C:\Windows\syswow64\SspiCli.dll" address="750b0000" size="00060000" version="6.1.7601.18779"/>
<module path="C:\Windows\syswow64\CRYPTBASE.dll" address="750a0000" size="0000c000" version="6.1.7600.16385"/>
<module path="C:\Windows\syswow64\SHELL32.dll" address="76690000" size="00c4b000" version="6.1.7601.18762"/>
<module path="C:\Windows\syswow64\SHLWAPI.dll" address="75c30000" size="00057000" version="6.1.7601.17514"/>
<module path="C:\Windows\system32\WSOCK32.dll" address="74f50000" size="00007000" version="6.1.7600.16385"/>
<module path="C:\Windows\syswow64\WS2_32.dll" address="772e0000" size="00035000" version="6.1.7601.17514"/>
<module path="C:\Windows\syswow64\NSI.dll" address="75b90000" size="00006000" version="6.1.7600.16385"/>
<module path="C:\Windows\syswow64\WININET.dll" address="76120000" size="001d5000" version="11.0.9600.17689"/>
<module path="C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll" address="776f0000" size="00004000" version="6.2.9200.16492"/>
<module path="C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll" address="764d0000" size="00004000" version="6.2.9200.16492"/>
<module path="C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll" address="75220000" size="00004000" version="6.2.9200.16492"/>
<module path="C:\Windows\system32\version.DLL" address="72860000" size="00009000" version="6.1.7600.16385"/>
<module path="C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll" address="76300000" size="00003000" version="6.2.9200.16492"/>
<module path="C:\Windows\syswow64\normaliz.DLL" address="754e0000" size="00003000" version="6.1.7600.16385"/>
<module path="C:\Windows\syswow64\iertutil.dll" address="75500000" size="00232000" version="11.0.9600.17689"/>
<module path="C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll" address="75b80000" size="00005000" version="6.2.9200.16492"/>
<module path="C:\Windows\syswow64\USERENV.dll" address="75c00000" size="00017000" version="6.1.7601.17514"/>
<module path="C:\Windows\syswow64\profapi.dll" address="754f0000" size="0000b000" version="6.1.7600.16385"/>
<module path="F:\BOINC_7500_32\sqlite3.dll" address="6a4c0000" size="0009b000" version="3.8.1.0"/>
<module path="C:\Windows\syswow64\ole32.dll" address="75a20000" size="0015c000" version="6.1.7601.17514"/>
<module path="C:\Windows\syswow64\OLEAUT32.dll" address="76440000" size="0008f000" version="6.1.7601.18679"/>
<module path="C:\Windows\system32\OLEACC.dll" address="74bb0000" size="0003c000" version="7.0.0.0"/>
<module path="C:\Windows\syswow64\COMDLG32.dll" address="75130000" size="0007b000" version="6.1.7601.17514"/>
<module path="C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll" address="6f6c0000" size="0019e000" version="6.10.7601.17514"/>
<module path="C:\Windows\system32\WINSPOOL.DRV" address="6f4f0000" size="00051000" version="6.1.7601.17514"/>
<module path="C:\Windows\system32\IMM32.DLL" address="751c0000" size="00060000" version="6.1.7601.17514"/>
<module path="C:\Windows\syswow64\MSCTF.dll" address="75830000" size="000cc000" version="6.1.7601.18731"/>
<module path="C:\Windows\system32\uxtheme.dll" address="6f640000" size="00080000" version="6.1.7600.16385"/>
<module path="C:\Windows\system32\dwmapi.dll" address="6fa40000" size="00013000" version="6.1.7600.16385"/>
<module path="C:\Windows\system32\RASAPI32.dll" address="728b0000" size="00052000" version="6.1.7600.16385"/>
<module path="C:\Windows\system32\rasman.dll" address="72890000" size="00015000" version="6.1.7600.16385"/>
<module path="C:\Windows\system32\rtutils.dll" address="71300000" size="0000d000" version="6.1.7601.17514"/>
<module path="C:\Windows\syswow64\CLBCatQ.DLL" address="75230000" size="00083000" version="2001.12.8530.16385"/>
<module path="C:\Windows\SysWOW64\ieframe.dll" address="6b0f0000" size="00c42000" version="11.0.9600.17690"/>
<module path="C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll" address="74da0000" size="00004000" version="6.2.9200.16492"/>
<module path="C:\Windows\system32\SXS.DLL" address="71400000" size="0005f000" version="6.1.7601.17514"/>
<module path="C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll" address="74d90000" size="00004000" version="6.2.9200.16492"/>
<module path="C:\Windows\syswow64\urlmon.dll" address="76540000" size="0014b000" version="11.0.9600.17689"/>
<module path="C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll" address="75ba0000" size="00004000" version="6.2.9200.16492"/>
<module path="C:\Windows\system32\CRYPTSP.dll" address="72560000" size="00017000" version="6.1.7601.18741"/>
<module path="C:\Windows\system32\rsaenh.dll" address="72520000" size="0003b000" version="6.1.7600.16385"/>
<module path="C:\Windows\system32\RpcRtRemote.dll" address="71e80000" size="0000e000" version="6.1.7601.17514"/>
<module path="C:\Windows\system32\apphelp.dll" address="706c0000" size="0004c000" version="6.1.7601.17514"/>
<module path="C:\Windows\SysWOW64\mshtml.dll" address="62860000" size="012d8000" version="11.0.9600.17690"/>
<module path="C:\Windows\system32\Secur32.dll" address="712f0000" size="00008000" version="6.1.7601.18779"/>
<module path="C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll" address="70620000" size="00004000" version="6.2.9200.16492"/>
<module path="C:\Windows\system32\IPHLPAPI.DLL" address="72920000" size="0001c000" version="6.1.7601.17514"/>
<module path="C:\Windows\system32\WINNSI.DLL" address="72910000" size="00007000" version="6.1.7600.16385"/>
<module path="C:\Windows\system32\mswsock.dll" address="71b40000" size="0003c000" version="6.1.7601.18254"/>
<module path="C:\Windows\System32\wship6.dll" address="71210000" size="00006000" version="6.1.7600.16385"/>
<module path="C:\Windows\system32\dbghelp.dll" address="6a3d0000" size="000eb000" version="6.1.7601.17514"/>
</modules>
<context>
<exception code="c0000005" name="ACCESS_VIOLATION" address="00ef4a90"/>
<registers>
<eax>ffffffff</eax>
<ebx>00368870</ebx>
<ecx>00000000</ecx>
<edx>00000000</edx>
<esi>00368458</esi>
<edi>000000fc</edi>
<ebp>001cf538</ebp>
<esp>001cf4f8</esp>
<eip>00ef4a90</eip>
<cs>00000023</cs>
<ds>0000002b</ds>
<es>0000002b</es>
<fs>00000053</fs>
<gs>0000002b</gs>
<ss>0000002b</ss>
<flags>00010286</flags>
</registers>
</context>
<stack>
<frame level="0"/>
<frame level="1"/>
<frame level="2"/>
<frame level="3"/>
<frame level="4"/>
<frame level="5"/>
<frame level="6"/>
<frame level="7"/>
<frame level="8"/>
<frame level="9"/>
<frame level="10"/>
<frame level="11"/>
<frame level="12" function="BaseThreadInitThunk" offset="00000012"/>
<frame level="13" function="RtlInitializeExceptionChain" offset="00000063"/>
<frame level="14" function="RtlInitializeExceptionChain" offset="00000036"/>
</stack>
</report>
--------------------------------------------

Some kind of access violation there seems to have happened.

* edit: stdoutgui.txt has been modified last time a month ago, so it probably doesn't contain any information related to this problem.