I seem to have found a Windows 10 / BIONC and/or S@H problem

Message boards : Number crunching : I seem to have found a Windows 10 / BIONC and/or S@H problem
Message board moderation

To post messages, you must log in.

AuthorMessage
Mike Ryan

Send message
Joined: 24 Jun 99
Posts: 46
Credit: 24,363,752
RAC: 47
United States
Message 1707353 - Posted: 1 Aug 2015, 15:51:55 UTC

Windows 10 seems to be having issues opening / closing / then re-opening certain programs when BIONC is running. Here's one instance I can get to happen pretty consistently:

Open the notification panel from the standard shortcut in the task bar. Close then try to re-open. Nothing happens (notification bar does not open) for anywhere from several seconds to several minutes [yeah, not exaggerating - several minutes].

However, if I snooze BIONC the notifications (or other stuck program) will immediately open. I've also seen this behavior with several other built in programs such at the photo viewer. This seems to usually happen when I try to re-open a just closed program or task. But that might just be my workflow. I so far have NOT seen this issue with any programs but those included with W10. For example, I have no problem opening-closing-opening Office programs, etc.

This is a new-built computer that initially had a clean install of Windows 10 preview installed (early July) and currently is running Windows 10 Pro. (haven't figured out where they're hiding the exact build number yet...)

System specs:
Intel i5-4590
ASRock H97M Pro4 Motherboard BIOS 1.90
16GB (2x8) Kingston HyperX Savage DDR3 1600 @ CAS 9-9-9
240GB SanDisk SSD Plus

S@H itself seems to be chugging along just fine, I've been averaging about 3500 credits per day running 5 work units at a time (one on each core plus one on the internal GPU).

Haven't seen this particular issue listed here for BOINC on W10, so thought I'd add my two cents.
ID: 1707353 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1707409 - Posted: 1 Aug 2015, 19:02:25 UTC

I was having similar issues with Windows 10. However I had not yet started BOINC. I sense there may be an update coming.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1707409 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1707411 - Posted: 1 Aug 2015, 19:16:05 UTC - in response to Message 1707353.  

I guess I'm seeing that, too, on my Win 10 guinea pig. Every time I need to do anything besides run BOINC, I've learned to first suspend Seti@home, or else wait a very long time for mouse clicks to register and/or windows to open. I just assumed it was because I've got a major issue with Win 10 only recognizing 2 of 8 cores (both of which are running S@h tasks), and with 4 GPUs running 2 tasks each, there aren't a lot of CPU cycles left for anything else. But if others are experiencing similar problems, perhaps it runs deeper. It should be interesting to see if others have similar experiences.
ID: 1707411 · Report as offensive
Profile Zombu2
Volunteer tester

Send message
Joined: 24 Feb 01
Posts: 1615
Credit: 49,315,423
RAC: 0
United States
Message 1707412 - Posted: 1 Aug 2015, 19:16:24 UTC

I've had no such problems so far could be machine specific to a certain combination of hardware they prolly patch it soon
I came down with a bad case of i don't give a crap
ID: 1707412 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1707439 - Posted: 1 Aug 2015, 21:44:49 UTC - in response to Message 1707412.  
Last modified: 1 Aug 2015, 21:46:54 UTC

I've had no such problems so far could be machine specific to a certain combination of hardware they prolly patch it soon

My best guess at the moment is that it might be related to the iGPU driver v4256. I had to download the latest one from Intel. As Windows 10 refused to accept the ones I was using for the Windows 7 & 8.1 installations.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1707439 · Report as offensive
Mike Ryan

Send message
Joined: 24 Jun 99
Posts: 46
Credit: 24,363,752
RAC: 47
United States
Message 1707548 - Posted: 2 Aug 2015, 2:50:31 UTC - in response to Message 1707439.  
Last modified: 2 Aug 2015, 2:52:57 UTC

My best guess at the moment is that it might be related to the iGPU driver v4256. I had to download the latest one from Intel. As Windows 10 refused to accept the ones I was using for the Windows 7 & 8.1 installations.

Could be the issue -- the Intel driver update utility tells me that my driver (specifically version 10.18.15.4256) is up-to-date. I don't see anything newer available.

Oh and I see that I clobbered BOINC as "BIONC" in my original posts. Sorry about that. Guess that happens when you grow up watching the BIONIC Man/Woman series on TV.
ID: 1707548 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1707568 - Posted: 2 Aug 2015, 4:10:57 UTC - in response to Message 1707548.  

My best guess at the moment is that it might be related to the iGPU driver v4256. I had to download the latest one from Intel. As Windows 10 refused to accept the ones I was using for the Windows 7 & 8.1 installations.

Could be the issue -- the Intel driver update utility tells me that my driver (specifically version 10.18.15.4256) is up-to-date. I don't see anything newer available.

Oh and I see that I clobbered BOINC as "BIONC" in my original posts. Sorry about that. Guess that happens when you grow up watching the BIONIC Man/Woman series on TV.

The 4256 iGPU driver release is from July 28th. So I wouldn't expect anything new to appear anytime soon.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1707568 · Report as offensive
Profile Zombu2
Volunteer tester

Send message
Joined: 24 Feb 01
Posts: 1615
Credit: 49,315,423
RAC: 0
United States
Message 1707586 - Posted: 2 Aug 2015, 4:39:45 UTC

i can honestly say i have no issue with the intel igpu driver it works flawless on my i7 nuc and the i5 nuc
I came down with a bad case of i don't give a crap
ID: 1707586 · Report as offensive
Profile ivan
Volunteer tester
Avatar

Send message
Joined: 5 Mar 01
Posts: 783
Credit: 348,560,338
RAC: 223
United Kingdom
Message 1707825 - Posted: 2 Aug 2015, 19:54:47 UTC - in response to Message 1707586.  

i can honestly say i have no issue with the intel igpu driver it works flawless on my i7 nuc and the i5 nuc

My little Celeron J1900 box (£130 at eBuyer) runs as a Win10 test-bed. AFAIK it's up to date with everything Microsoft throws at it. It frequently hangs on GPU jobs, and I have to abort them. Pity, because when they do run to completion they have about 60% of the performance of one of the four CPU cores...
ID: 1707825 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1708120 - Posted: 3 Aug 2015, 16:39:07 UTC - in response to Message 1707825.  
Last modified: 3 Aug 2015, 16:39:35 UTC

i can honestly say i have no issue with the intel igpu driver it works flawless on my i7 nuc and the i5 nuc

My little Celeron J1900 box (£130 at eBuyer) runs as a Win10 test-bed. AFAIK it's up to date with everything Microsoft throws at it. It frequently hangs on GPU jobs, and I have to abort them. Pity, because when they do run to completion they have about 60% of the performance of one of the four CPU cores...

Were you having issues before Windows 10 on that box? My J1900 is humming along perfectly happy, but is also using driver v4061 instead of v4252. It is also staying on Windows 7. So there is also that I guess.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1708120 · Report as offensive
Mike Ryan

Send message
Joined: 24 Jun 99
Posts: 46
Credit: 24,363,752
RAC: 47
United States
Message 1709157 - Posted: 6 Aug 2015, 6:06:51 UTC

Found another issue - possibly related. My recent average credit is hovering around 4,400 - so I'm getting plenty of "regular" work crunching through my computer. However, most of the AstroPulse units that are being churned on my i5-4590's internal GPU (HD-4600) result in compute errors - here are the latest examples:

http://setiathome.berkeley.edu/result.php?resultid=4295408186
http://setiathome.berkeley.edu/result.php?resultid=4295408190
http://setiathome.berkeley.edu/result.php?resultid=4291176636

All have the same error status:
-226 (0xffffffffffffff1e) ERR_TOO_MANY_EXITS

Not too sure about the graphics driver being at fault, because when non-AstroPulse work units are crunched on the GPU they finish correctly (and generally quite quickly).

I saw some suggestion that there was not enough RAM dedicated to the GPU, but I've got mine set at the highest setting (512 MB) my BIOS allows.

Any ideas?
ID: 1709157 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 1709201 - Posted: 6 Aug 2015, 12:17:00 UTC - in response to Message 1709157.  
Last modified: 6 Aug 2015, 13:12:47 UTC

I saw some suggestion that there was not enough RAM dedicated to the GPU, but I've got mine set at the highest setting (512 MB) my BIOS allows.

Any ideas?


Keep in mind that 512MB is the bare minimum for crunching, and there are various things running on your system that will consume part of that video RAM. For example, a single display monitor running at 1920 x 1080 resolution requires 2,073,600 bits of RAM, or about 253 Megabytes of RAM - and that's just for the static image! That isn't counting all the fancy effects and animations found in Aero.

Crunching at the bare minimum of video RAM practically necessitates that you should turn off all Aero effects to free up as much RAM as possible.

[Edit] I just remembered that Windows 10 may not have a way to turn off all the advanced UI effects.
ID: 1709201 · Report as offensive
Mike Ryan

Send message
Joined: 24 Jun 99
Posts: 46
Credit: 24,363,752
RAC: 47
United States
Message 1709559 - Posted: 7 Aug 2015, 1:37:14 UTC
Last modified: 7 Aug 2015, 1:41:53 UTC

Here's one more odd thing I found RE: crunching AstroPulse units... my preferences are set to NOT process AstroPulse data - so I shouldn't be seeing any of them in the first place. I found that setting on the project preferences page. I tried clicking it back on then off then saved just to make sure that it is set to ignore AstroPulse.

[EDIT] Never mind on this one. I see I have "accept work from other projects if no work is available" checked. So at some point we must have run out of standard S@H work so my computer grabbed some AP work too. Fixing that option to ONLY run S@H v. 7 since it seems the AP units usually result in errors.
ID: 1709559 · Report as offensive
Mike Ryan

Send message
Joined: 24 Jun 99
Posts: 46
Credit: 24,363,752
RAC: 47
United States
Message 1729568 - Posted: 27 Sep 2015, 16:34:54 UTC
Last modified: 27 Sep 2015, 16:36:13 UTC

Just a quick update to this thread - since no fix has thus far come from the folks at Microsoft:

Just to re-state the problem - some programs basically hang instead of launching while I'm running BIONC. Eventually (sometimes after several minutes) the hung program(s) will start - but the delay is substantial and basically makes for a very bad user experience under Windows 10. Whenever seen, I was able to manually fix the problem by snoozing BOINC.

Instead of waiting for MS to fix this (as I've never had the same problem going all the way back to Windows 98) I've simply gone into my computing preferences and set them to suspend computing (of BIONC) "while computer is in-use".

This seems to have solved the issue 100%, and the few minutes I actually use this particular computer a day does not cut into the number of work unit credits generated. I still average about 4650 credits per day on the S@H client.

Perhaps it should be considered to set this option in the BIONC computing preferences by default on new installs in order to play more friendly with Windows 10?
ID: 1729568 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 1729571 - Posted: 27 Sep 2015, 16:40:52 UTC
Last modified: 27 Sep 2015, 16:44:17 UTC

I dunno.
Guess I was always blessed with a certain mix of hardware that I have never seen such problems.
All Intel, all nVidia.
And no freaking 10.
The crunchers are all on XP pro...that might explain a lot.

It all just freaking works for me.
Drivers are a mix, but all work.
The kitties get the job done.....meow.
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 1729571 · Report as offensive

Message boards : Number crunching : I seem to have found a Windows 10 / BIONC and/or S@H problem


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.