1) Message boards : Number crunching : Will n-body ever end? 1.64 (Message 66545) Posted 22 Jul 2017 by Mani Post: Hi again! Since I have not gotten any advice as yet, and the deadline for the n-body app in question is only 36 hours away with 34008 days estimated left, I have aborted the job, aborted the other n-body jobs in the queue, and disallowed new n-body jobs. I have other Milkyway, non n-body, jobs which will miss their deadlines otherwise.

2) Message boards : Number crunching : Will n-body ever end? 1.64 (Message 66543) Posted 18 Jul 2017 by Mani Post: Hi! I have been running a 4 CPU n-body app for over two days now. It says that it has progressed 0.013%, which it has said since it started, and that it has 17414 days left to go. It is now 17 July 2017, the due date is 7/23/2017, and no other CPU task is being allowed to run. Will it ever end? Should I abort it? Should I just not run n-body apps? It is running on an AMD A10-7850K.

3) Message boards : Number crunching : GRAPHICS DRIVER FAULT - infinite loop (Message 66498) Posted 30 Jun 2017 by Mani Post: Hi! I am having a problem running Milkway on my AMD A10-7850K APU. It can run along fine for a while, and then I check my computer and I have a Blue Screen. I have the Windows debugger dump file included followed by the BOINC startup event log. Windows Bluescreen Dump Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\063017-39608-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred srv*e:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: srv*e:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: No .natvis files found at E:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers. Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600 Machine Name: Kernel base = 0xfffff800`03c0f000 PsLoadedModuleList = 0xfffff800`03e51750 Debug session time: Fri Jun 30 08:02:50.529 2017 (UTC - 7:00) System Uptime: 2 days 9:04:57.716 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ ................................................................ ....................... Loading User Symbols Loading unloaded module list ................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck EA, {fffffa8045907b50, 0, 0, 0} *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* THREAD_STUCK_IN_DEVICE_DRIVER (ea) The device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself or with the device driver programming the hardware incorrectly. If the kernel debugger is connected and running when watchdog detects a timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx() and detailed message including bugcheck arguments will be printed to the debugger. This way we can identify an offending thread, set breakpoints in it, and hit go to return to the spinning code to debug it further. Because KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck information in this case. The arguments are already printed out to the kernel debugger. You can also retrieve them from a global variable via "dd watchdog!g_WdBugCheckData l5" (use dq on NT64). On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is interrupted by hardware interrupt and ISR or DPC routine is running at the time of the bugcheck (this is because the timeout's work item can be delivered and handled on the second CPU and the same time). If this is the case you will have to look deeper at the offending thread's stack (e.g. using dds) to determine spinning code which caused the timeout to occur. Arguments: Arg1: fffffa8045907b50, Pointer to a stuck thread object. Do .thread then kb on it to find the hung location. Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object. Arg3: 0000000000000000, Pointer to offending driver name. Arg4: 0000000000000000, Number of times this error occurred. If a debugger is attached, this error is not always fatal -- see DESCRIPTION below. On the blue screen, this will always equal 1. Debugging Details: ------------------ SYSTEM_SKU: SKU SYSTEM_VERSION: System Version BIOS_DATE: 03/10/2016 BASEBOARD_PRODUCT: A88XM-PLUS BASEBOARD_VERSION: Rev X.0x BUGCHECK_P1: fffffa8045907b50 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FAULTING_THREAD: 45907b50 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT CPU_COUNT: 4 CPU_MHZ: ff9 CPU_VENDOR: AuthenticAMD CPU_FAMILY: 15 CPU_MODEL: 30 CPU_STEPPING: 1 CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0xEA PROCESS_NAME: milkyway_1.46_ CURRENT_IRQL: 0 ANALYSIS_VERSION: 10.0.10240.9 amd64fre LAST_CONTROL_TRANSFER: from fffff88005044f63 to fffff80003c7fe40 STACK_TEXT: fffff880`1610a6f8 fffff880`05044f63 : 00000000`000000ea fffffa80`45907b50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx fffff880`1610a700 fffff880`05045112 : fffff880`1610a7d8 fffff880`1135a890 fffff880`1610a7d8 fffff880`1610a8c0 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37 fffff880`1610a770 fffff880`112f8970 : fffffa80`19956000 00000000`00000000 fffff880`1610a8c0 fffff880`1135a87c : dxgkrnl!TdrTimedOperationDelay+0xbe fffff880`1610a7b0 fffffa80`19956000 : 00000000`00000000 fffff880`1610a8c0 fffff880`1135a87c 00000000`00002710 : atikmdag+0x56970 fffff880`1610a7b8 00000000`00000000 : fffff880`1610a8c0 fffff880`1135a87c 00000000`00002710 00000000`00000028 : 0xfffffa80`19956000 STACK_COMMAND: .thread 0xfffffa8045907b50 ; kb FOLLOWUP_IP: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 fffff880`05044f63 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 58e7a92e IMAGE_VERSION: 6.1.7601.23764 FAILURE_BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys PRIMARY_PROBLEM_CLASS: X64_0xEA_IMAGE_dxgkrnl.sys ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xea_image_dxgkrnl.sys FAILURE_ID_HASH: {b58a0dfd-90f3-63cd-1b07-7ce1b53744cb} Followup: MachineOwner --------- ******* This is the end of the dump. Following is the BOINC startup event log: ******* BOINC Manager - Event Log 6/30/2017 10:32:51 AM | | Starting BOINC client version 7.6.33 for windows_x86_64 6/30/2017 10:32:51 AM | | log flags: file_xfer, sched_ops, task 6/30/2017 10:32:51 AM | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8 6/30/2017 10:32:51 AM | | Data directory: E:\BOINC 6/30/2017 10:32:51 AM | | Running under account Mani 6/30/2017 10:32:54 AM | | CUDA: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version 382.05, CUDA version 8.0, compute capability 5.0, 2048MB, 1693MB available, 1539 GFLOPS peak) 6/30/2017 10:32:54 AM | | OpenCL: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version 382.05, device version OpenCL 1.2 CUDA, 2048MB, 1693MB available, 1539 GFLOPS peak) 6/30/2017 10:32:54 AM | | OpenCL: AMD/ATI GPU 0: AMD Radeon(TM) R7 Graphics (driver version 2348.3, device version OpenCL 2.0 AMD-APP (2348.3), 3583MB, 3583MB available, 737 GFLOPS peak) 6/30/2017 10:32:54 AM | | App version needs CAL but GPU doesn't support it 6/30/2017 10:32:54 AM | Milkyway@Home | Application uses missing ATI GPU 6/30/2017 10:32:54 AM | | Host name: Lucna 6/30/2017 10:32:54 AM | | Processor: 4 AuthenticAMD AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G [Family 21 Model 48 Stepping 1] 6/30/2017 10:32:54 AM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni ssse3 fma cx16 sse4_1 sse4_2 popcnt aes f16c syscall nx lm avx svm sse4a osvw ibs xop skinit wdt lwp fma4 tce tbm topx page1gb rdtscp fsgsbase bmi1 6/30/2017 10:32:54 AM | | OS: Microsoft Windows 7: Ultimate x64 Edition, Service Pack 1, (06.01.7601.00) 6/30/2017 10:32:54 AM | | Memory: 29.94 GB physical, 89.83 GB virtual 6/30/2017 10:32:54 AM | | Disk: 786.47 GB total, 90.29 GB free 6/30/2017 10:32:54 AM | | Local time is UTC -7 hours 6/30/2017 10:32:54 AM | | VirtualBox version: 5.1.22 6/30/2017 10:32:54 AM | | Config: don't compute while AgeOfConan.exe is running 6/30/2017 10:32:54 AM | | Config: don't compute while AgeOfConanDX10.exe is running 6/30/2017 10:32:54 AM | | Config: don't compute while ConanPatcher.exe is running 6/30/2017 10:32:54 AM | | Config: don't compute while firefox.exe is running 6/30/2017 10:32:54 AM | | Config: don't compute while PaintDotNet.exe is running 6/30/2017 10:32:54 AM | | Config: don't compute while PerfectDisk.exe is running 6/30/2017 10:32:54 AM | | Config: don't compute while Persbackup.exe is running 6/30/2017 10:32:54 AM | | Config: don't compute while vmware-vmx.exe is running 6/30/2017 10:32:54 AM | | Config: don't compute while WWTExplorer.exe is running 6/30/2017 10:32:54 AM | | Config: don't use GPUs while AgeOfConan.exe is running 6/30/2017 10:32:54 AM | | Config: don't use GPUs while AgeOfConanDX10.exe is running 6/30/2017 10:32:54 AM | Asteroids@home | URL http://asteroidsathome.net/boinc/; Computer ID 4775; resource share 100 6/30/2017 10:32:54 AM | BURP | URL http://burp.renderfarming.net/; Computer ID 69559; resource share 100 6/30/2017 10:32:54 AM | Cosmology@Home | URL http://www.cosmologyathome.org/; Computer ID 96686; resource share 100 6/30/2017 10:32:54 AM | duchamp | URL https://sourcefinder.theskynet.org/duchamp/; Computer ID 28; resource share 100 6/30/2017 10:32:54 AM | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 5907909; resource share 100 6/30/2017 10:32:54 AM | Milkyway@Home | URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 194269; resource share 100 6/30/2017 10:32:54 AM | orbit@home | URL http://orbit.psi.edu/oah/; Computer ID 39093; resource share 100 6/30/2017 10:32:54 AM | pogs | URL http://pogs.theskynet.org/pogs/; Computer ID 677434; resource share 100 6/30/2017 10:32:54 AM | Rosetta@home | URL http://boinc.bakerlab.org/rosetta/; Computer ID 1306347; resource share 100 6/30/2017 10:32:54 AM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 5445086; resource share 100 6/30/2017 10:32:54 AM | pogs | General prefs: from pogs (last modified 18-Feb-2016 17:15:25) 6/30/2017 10:32:54 AM | pogs | Host location: none 6/30/2017 10:32:54 AM | pogs | General prefs: using your defaults 6/30/2017 10:32:54 AM | | Reading preferences override file 6/30/2017 10:32:54 AM | | Preferences: 6/30/2017 10:32:54 AM | | max memory usage when active: 13797.95MB 6/30/2017 10:32:54 AM | | max memory usage when idle: 13797.95MB 6/30/2017 10:32:54 AM | | max disk usage: 97.05GB 6/30/2017 10:32:54 AM | | suspend work if non-BOINC CPU load exceeds 65% 6/30/2017 10:32:54 AM | | (to change preferences, visit a project web site or select Preferences in the Manager) 6/30/2017 10:32:54 AM | Einstein@Home | [error] no project URL in task state file 6/30/2017 10:32:55 AM | | Suspending computation - an exclusive app is running 6/30/2017 10:32:55 AM | | Suspending network activity - an exclusive app is running

©2024 Astroinformatics Group