Questions and Answers :
Windows :
Wu failed with error -1073741674
Message board moderation
Author | Message |
---|---|
Send message Joined: 26 Aug 04 Posts: 16 Credit: 409,831 RAC: 0 |
Please see the attached message log: Project Time ID Message Work climateprediction.net 6/17/2005 09:20:00 562 Deferring communication with project for 59 seconds Work --- 6/17/2005 09:20:00 561 request_reschedule_cpus: process exited Work climateprediction.net 6/17/2005 09:20:00 560 Unrecoverable error for result 44dx_100214237_1 ( - exit code -1073741674 (0xc0000096)) Work Einstein@Home 6/17/2005 09:19:47 559 Pausing result H1_0270.5__0270.6_0.1_T19_Fin1_1 (left in memory) Work --- 6/17/2005 09:19:47 558 Suspending computation and network activity - user is active Work SETI@home 6/17/2005 09:03:28 557 Pausing result 05no03aa.15866.20848.247158.107_4 (left in memory) Work Einstein@Home 6/17/2005 09:03:28 556 Resuming result H1_0270.5__0270.6_0.1_T19_Fin1_1 using einstein version 4.79 Work --- 6/17/2005 09:03:28 555 schedule_cpus: time 3600.076656 The interesting thing about this log entry is that then failure occured about 13 seconds after BOINC had suspended for user activity. Ntoe also that the climate work unit that failed was not executing at the time of the failure. This is a WIN XP machine running BOINC 4.43 |
Send message Joined: 5 Sep 04 Posts: 7629 Credit: 24,240,330 RAC: 0 |
This error code seems to be something to do with windows, rather than BOINC. It has been getting reported a lot lately. If you do a google search on the string of numbers there are a few mentions, but nothing really helpfull. It could be that something in Windows doesn't like some versions of BOINC, but no one can figure it out. Les |
Send message Joined: 31 Oct 04 Posts: 336 Credit: 3,316,482 RAC: 0 |
0xC0000096 EXCEPTION_PRIV_INSTRUCTION The instruction is not allowed in the current ring (inport, outport & control register manipulation usually). No fix, other than 'dont do that' It led to a -5 error in BOINC. Such a thing can happen, when program code gets overwritten in memory and the CPU tries to execute some code that isn't thought to be executes. The cause can be a data pointer that is not initialized properly or an array overflow. Using arrays of function pointers and then using a pointer out of the array bounds are another quite common reason. The trickle 24 crashes I had seem to have a quite similar reason so there might be something wrong. |
©2024 cpdn.org