Unable to load module .mshake_kernel.cu. (702)

Message boards : Number crunching : Unable to load module .mshake_kernel.cu. (702)
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
pandemonium

Send message
Joined: 2 Oct 17
Posts: 2
Credit: 22,213,625
RAC: 0
Level
Pro
Scientific publications
watwat
Message 48248 - Posted: 25 Nov 2017, 10:02:31 UTC - in response to Message 48227.  

You seem to be correct. I've since had a few more instances of the display driver crashing during crunching and trying to reinitialize the displays. Increasing the virtual memory paging file seemed to alleviate the issue, but not completely fix it.

I will give disabling SLI and then removing the bridge to see if that helps fix the issue once and for all.

Thanks for the input!
ID: 48248 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Zalster
Avatar

Send message
Joined: 26 Feb 14
Posts: 211
Credit: 4,496,324,562
RAC: 0
Level
Arg
Scientific publications
watwatwatwatwatwatwatwat
Message 48399 - Posted: 18 Dec 2017, 3:02:57 UTC - in response to Message 48248.  

I just got this error on one of my machines.

I had just done a clean install of the drivers on Friday. System has been running for 2 days before this happen.

Can't be the temps, they are all low 40s to mid 40s C

Virtual memory was 451.74, physical memory is 173.16

Going to see if the next person is able to process it without any problem.

I read somewhere that it might be kernal panic, caught in a never ending loop.

Guess will have to wait and see. For now, I've removed the host and running other projects to test the stability of the system


ID: 48399 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
PappaLitto

Send message
Joined: 21 Mar 16
Posts: 513
Credit: 4,673,458,277
RAC: 0
Level
Arg
Scientific publications
watwatwatwatwatwatwatwat
Message 48404 - Posted: 18 Dec 2017, 11:42:48 UTC - in response to Message 48399.  

I just got this error on one of my machines.

I had just done a clean install of the drivers on Friday. System has been running for 2 days before this happen.

Can't be the temps, they are all low 40s to mid 40s C

Virtual memory was 451.74, physical memory is 173.16

Going to see if the next person is able to process it without any problem.

I read somewhere that it might be kernal panic, caught in a never ending loop.

Guess will have to wait and see. For now, I've removed the host and running other projects to test the stability of the system


Is there an errored out WU that you can show us?
ID: 48404 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
mmonnin

Send message
Joined: 2 Jul 16
Posts: 338
Credit: 7,987,341,558
RAC: 158
Level
Tyr
Scientific publications
watwatwatwatwat
Message 48410 - Posted: 18 Dec 2017, 14:58:12 UTC - in response to Message 48404.  

I just got this error on one of my machines.

I had just done a clean install of the drivers on Friday. System has been running for 2 days before this happen.

Can't be the temps, they are all low 40s to mid 40s C

Virtual memory was 451.74, physical memory is 173.16

Going to see if the next person is able to process it without any problem.

I read somewhere that it might be kernal panic, caught in a never ending loop.

Guess will have to wait and see. For now, I've removed the host and running other projects to test the stability of the system


Is there an errored out WU that you can show us?


Looks like this one
http://www.gpugrid.net/result.php?resultid=16773843
ID: 48410 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Zalster
Avatar

Send message
Joined: 26 Feb 14
Posts: 211
Credit: 4,496,324,562
RAC: 0
Level
Arg
Scientific publications
watwatwatwatwatwatwatwat
Message 48411 - Posted: 18 Dec 2017, 15:57:33 UTC - in response to Message 48410.  

Yes that is the one.

Looks like the next person finished it without a problem. Don't know what happen with mine.

Computer is in a room with controlled temp, never gets over 74F. Not sure why it happen. Only 1 work unit per card. Full physical CPU core assigned.
ID: 48411 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Previous · 1 · 2

Message boards : Number crunching : Unable to load module .mshake_kernel.cu. (702)

©2025 Universitat Pompeu Fabra