SwartHack Posted September 26, 2015 Posted September 26, 2015 Hello All! This has been a problem for me continuously since I started working on this new bench setup. It is new mobo vendor for me(ASUS), but I have done this many times on other vendor platforms, and am pretty familiar with setting up a system from scratch. So here is what I am working with: Asus ROG Maximus Hero VII/Z97:i7-4790k 2x4 gb G.Skill Trident X, 2400 10-12-12-31 EVGA GTX 960 Win7 Pro/x64 I appreciate any help on this as at this point I have no idea what is causing is this and can't track it down for the life of me. But please no suggestions to reinstall/reimage/refresh/etc. as I have already spent days on this and have performed about as many iterations and combinations imaginable. Always fails at the same place, right at the end after step 19. This happens to all 3 tests under several scenarios. Each of the following scenarios were configured after a fresh windows install. In a few cases I tried various versions of windows. Always fails at the same place, right at the end after step 19. 1-No gCard, only using Intel HD graphics drivers. 2-No gCard, only using Intel OpenCL drivers. 3-gCard w/gfx drivers installed, install after Intel HD graphics drivers install. 4-gCard w/gfx drivers installed, w/o install of Intel HD graphics drivers 5-gCard w/gfx drivers installed, with and without Intel OpenCL drivers Here is the chain of events I have followed. I do know that the exception code "c000001d" is very generic and is usually caused by an unhandled illegal instruction. Anyhooo, I am at my wits end here on this and am convinced it can't be a bad mobo or memory. You can see that all the outputs basically say the same thing in different formats. If anyone has any idea of why I repeatedly get this problem, I will owe you all large!! Salud! ............................................................................................................ First I execute GPUPI and select any available test based on the scenario. I get: The entire text of the Problem Signatue: Problem signature: Problem Event Name: APPCRASH Application Name: GPUPI_x64.exe Application Version: 2.2.0.0 Application Timestamp: 55cb3f32 Fault Module Name: MSVCR120.dll Fault Module Version: 12.0.21005.1 Fault Module Timestamp: 524f83ff Exception Code: c000001d Exception Offset: 0000000000095c01 OS Version: 6.1.7600.2.0.0.256.48 Locale ID: 1033 Additional Information 1: 14fd Additional Information 2: 14fdde55016f41d5b9631096204c23b4 Additional Information 3: 4ee6 Additional Information 4: 4ee6aaabb956480472fe11690113ac83 So then off to the Event Viewer and WER (Windows Error Reporting) Faulting application name: GPUPI_x64.exe, version: 2.2.0.0, time stamp: 0x55cb3f32 Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff Exception code: 0xc000001d Fault offset: 0x0000000000095c01 Faulting process id: 0x914 Faulting application start time: 0x01d0f88af9a48b4c Faulting application path: C:\Users\admin\Documents\apps\GPUPI 2.2\GPUPI_x64.exe Faulting module path: C:\Windows\system32\MSVCR120.dll Report Id: 40e19efc-647e-11e5-9e3a-a9634542badf Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Calculates Pi using CUDA/OpenCL because of this error. Program: Calculates Pi using CUDA/OpenCL File: The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: 00000000 Disk type: 0 Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: GPUPI_x64.exe P2: 2.2.0.0 P3: 55cb3f32 P4: MSVCR120.dll P5: 12.0.21005.1 P6: 524f83ff P7: c000001d P8: 0000000000095c01 P9: P10: Attached files: These files may be available here: C:\Users\admin\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_GPUPI_x64.exe_ae48a51f34d06018404792caa4f14b38bc3c576e_04c18729 Analysis symbol: Rechecking for solution: 0 Report Id: e8166153-6485-11e5-9357-fc034d3461de Report Status: 2 Version=1 EventType=APPCRASH EventTime=130877698002556985 ReportType=2 Consent=1 ReportIdentifier=e8166154-6485-11e5-9357-fc034d3461de IntegratorReportIdentifier=e8166153-6485-11e5-9357-fc034d3461de Response.type=4 Sig[0].Name=Application Name Sig[0].Value=GPUPI_x64.exe Sig[1].Name=Application Version Sig[1].Value=2.2.0.0 Sig[2].Name=Application Timestamp Sig[2].Value=55cb3f32 Sig[3].Name=Fault Module Name Sig[3].Value=MSVCR120.dll Sig[4].Name=Fault Module Version Sig[4].Value=12.0.21005.1 Sig[5].Name=Fault Module Timestamp Sig[5].Value=524f83ff Sig[6].Name=Exception Code Sig[6].Value=c000001d Sig[7].Name=Exception Offset Sig[7].Value=0000000000095c01 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7600.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=14fd DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=14fdde55016f41d5b9631096204c23b4 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=4ee6 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=4ee6aaabb956480472fe11690113ac83 UI[2]=C:\Users\admin\Documents\apps\GPUPI 2.2\GPUPI_x64.exe UI[3]=Calculates Pi using CUDA//OpenCL has stopped working UI[4]=Windows can check online for a solution to the problem the next time you go online. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=C:\Users\admin\Documents\apps\GPUPI 2.2\GPUPI_x64.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\system32\kernel32.dll LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll LoadedModule[4]=C:\Windows\system32\WINMM.dll LoadedModule[5]=C:\Windows\system32\msvcrt.dll LoadedModule[6]=C:\Windows\system32\USER32.dll LoadedModule[7]=C:\Windows\system32\GDI32.dll LoadedModule[8]=C:\Windows\system32\LPK.dll LoadedModule[9]=C:\Windows\system32\USP10.dll LoadedModule[10]=C:\Windows\system32\WS2_32.dll LoadedModule[11]=C:\Windows\system32\RPCRT4.dll LoadedModule[12]=C:\Windows\system32\NSI.dll LoadedModule[13]=C:\Users\admin\Documents\apps\GPUPI 2.2\cudart64_70.dll LoadedModule[14]=C:\Windows\system32\OpenCL.dll LoadedModule[15]=C:\Windows\system32\ADVAPI32.dll LoadedModule[16]=C:\Windows\SYSTEM32\sechost.dll LoadedModule[17]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7600.16385_none_2b4f45e87195fcc4\gdiplus.dll LoadedModule[18]=C:\Windows\system32\ole32.dll LoadedModule[19]=C:\Windows\system32\SHELL32.dll LoadedModule[20]=C:\Windows\system32\SHLWAPI.dll LoadedModule[21]=C:\Windows\system32\COMDLG32.dll LoadedModule[22]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa645303170382f6\COMCTL32.dll LoadedModule[23]=C:\Windows\system32\MSVCP120.dll LoadedModule[24]=C:\Windows\system32\MSVCR120.dll LoadedModule[25]=C:\Windows\system32\OLEAUT32.dll LoadedModule[26]=C:\Windows\system32\IMM32.DLL LoadedModule[27]=C:\Windows\system32\MSCTF.dll LoadedModule[28]=C:\Windows\system32\uxtheme.dll LoadedModule[29]=C:\Windows\system32\dwmapi.dll LoadedModule[30]=C:\Windows\System32\nvopencl.dll LoadedModule[31]=C:\Windows\system32\SETUPAPI.dll LoadedModule[32]=C:\Windows\system32\CFGMGR32.dll LoadedModule[33]=C:\Windows\system32\DEVOBJ.dll LoadedModule[34]=C:\Windows\system32\VERSION.dll LoadedModule[35]=C:\Windows\system32\nvapi64.dll LoadedModule[36]=C:\Windows\system32\WINTRUST.dll LoadedModule[37]=C:\Windows\system32\CRYPT32.dll LoadedModule[38]=C:\Windows\system32\MSASN1.dll LoadedModule[39]=C:\Windows\system32\nvcuda.dll LoadedModule[40]=C:\Windows\system32\CRYPTBASE.dll LoadedModule[41]=C:\Windows\system32\nvcompiler.dll LoadedModule[42]=C:\Windows\system32\dbghelp.dll FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Calculates Pi using CUDA//OpenCL AppPath=C:\Users\admin\Documents\apps\GPUPI 2.2\GPUPI_x64.exe Quote
GENiEBEN Posted September 26, 2015 Posted September 26, 2015 Does it crash only on GPU, or cpu as well? I'd get rid of the bundled CUDA dll files, and let the app use the ones you have installed on your system. Wouldn't hurt to install AMD APP SDK either. Btw, stock clocks? Quote
SwartHack Posted September 26, 2015 Author Posted September 26, 2015 Crashes on gpu and cpu tests, same place, same errors. Yeah, I never had to use the Intel OpenCl drivers before on other hardware setups and as I understand shouldn't have to use them. But as I mentioned I did test as well with OpenCL drivers installed by the Intel HD Graphics drivers provided by the vendor and I tried them downloaded from Intel site. Yes, sorry all stock. Quote
_mat_ Posted September 27, 2015 Posted September 27, 2015 Very weird error. Points to either faulty memory or I fucked something up in the code. As the error seems to occur after the last loop (it's just not drawn yet), it will have to do with accumulation of the partial results or the validation of the final sum. Both depend only on system memory, that's why the error happens both on GPU and CPU. The error is not repeatable on my side and was never reported by anyone else, so I guess that your memory is faulty. Try memtest86 and Prime95 with focus on memory for an hour or so and let me know if your system is still stable. Quote
SwartHack Posted September 27, 2015 Author Posted September 27, 2015 err, opps, my bad... Forgot to mention I have tried some other memory as well, as that was one of the first things I thought as well. With a software dev background I do know you are right on with your assessment, as that error usually indicates an illegal memory read/write and/or alloc action. But we all know it is not GPUPI... I tried a pair of pretty pedestrian sticks I had in another rig: 2x8 gb Kingston Fury HyperX 1866 CL10 Same results :-( I will try a memory stress test as you advised... Thanks, Salud Quote
SwartHack Posted September 27, 2015 Author Posted September 27, 2015 So It was recommended to try the AMD OpenCL SDK runtimes, which I had not done... Same results :-( I have been monitoring my registry during this entire process. If someone, anyone with a similar config listed in first post(really any rog maximus VII) could run this at an admin command prompt? I would love a comparison. Thanks!! reg query HKLM /s /f OpenCL Here is the output on my problem child: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Features\C787928896262114DA8F95EBFF7CDC6B OpenCL1x REG_SZ OpenCL OCL1xBinaries REG_SZ OpenCL1x OCL1xSources REG_SZ OpenCL1x OpenCL20 REG_SZ OpenCL OCL20Binaries REG_SZ OpenCL20 OCL20Sources REG_SZ OpenCL20 OpenCL REG_SZ AcceleratedPPSDK HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors C:\Windows\System32\nvopencl.dll REG_DWORD 0x0 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\659F21159C16B21B76DEE649BCEEB52F C787928896262114DA8F95EBFF7CDC6B REG_SZ C?\Program Files (x86)\AMD APP SDK\3.0\bin\x86_64\OpenCL.dll HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\CBBABCF3435C6F1BE4FB05521E3B122A C787928896262114DA8F95EBFF7CDC6B REG_SZ C?\Program Files (x86)\AMD APP SDK\3.0\bin\x86\OpenCL.dll HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\C787928896262114DA8F95EBFF7CDC6B\Features OpenCL1x REG_SZ OpenCL OCL1xBinaries REG_SZ OpenCL1x OCL1xSources REG_SZ 0oHFrKau9?lpgp,'*cDNJv@CwC`8qbIZ8.wXa_&^Ts!CVDN~9J)lK4a8%fQsr]=bkQH,C*!LSAtIIiCHX'LM9[aUEIgd0!7Jc07eo@}GOf!BYMTM8g!PNw@!Q-,Yyoefs6^NoPWZ$6cu=Ff&{FK9B*vVl5P%E(tn]I85HrA1%w^CrCTm[GH_F4QhA1xTq'Qf=YuR&T1RYEaW-twqmkbJIuxl-^2'o&p.Hp~vWM`!2844Px5+.?RsBN60PIevmfu{*c%NCd3~_99^QiC(h[4,y7ekV?mQjYGEwb@dLwHU?D)uE1`3dJDvhT0N+}PFNL$pVn8n4*V3]RJB[ig)5g5z3dK={[D4Tz=P!5*huPdwy11QXP@UZk'3N5?WE(Mz$x?Pgw?(@fRHJ`SH+.^0SJ6d7*s(ns~BBYJFojfglVdMM?@y=gxsbJfQrS{DYx=L2P)w6zS9)lo?E&=dwf1L?lScDI?_wWus{vm52S_PtF=xZ*X&M~$%[}erg}2'PRRUQQ^YF)jqxa$GMxPEjwKNEgvX{bCgHoE@Z(.J48Bh$k-rdF38J2[TJc[Wd9[OyV}cWnPRj@*ONQQ5dBDv{79]J,^LNvY*@=`u*d9ev8iWZs@^XyQ12k)4xnLpEkl~ajU%TG)'hDnxpH%S1diaX`3z2PS@Woj%7NVY-Eln_3@1gNM2%45o2i8pREl,FELcDx3c[2IMp[1MjBMPQg3yL%d5$(}j8WC5&=PK)!.!Q}Yo%jB9eR@?Cs[('L(,PJV`-']+d!H1,F]e++MD=m-iVDBCK6K^xkv5aPD)EzRAd0y{1j$ojGR'UrAxt6z9.b&$UnqGh_.ct0nHyV5IG8$nw]y62@PK(.EH$N&_(^f?E=mq6%[1.h6{Gz%U*v3(3yv3r+bG(NCB~?EL'Rgq45MB,{Eaa?@5qYpfkuxqBJ*mG@=*^75h`oItEYf&]D@1avJy)PH[vFn[_8UmoppjW?68gf9gQ7kWRjlB$@^VHr'57-STN%D6G@1(16h%[^tU7wNL8+-j3Xk5%`QZMP*J]v.Pau$^4W][LYFH{NA%F]TE-oZp{lP-a6iuNjnjCDVzRZx0nw'F6l7O@O(W7b2n4B3FjzZ0cI!wCU')M')u_7B(e)h&ChghfdR[]]eC[11&1*t*upAVZauYKD,Ow-]M2z`wn.2(x_ENT45Py-(Jl@y)gR2-if-JhfEu[9]=a['kRuU-XzyRcqFVqom.`h=AU+PI)nF0~y[M+y_I^o'a-RYV']=]J[PsE?_^TCDy*yW}1u'UqImAbXpfUe-gtw+=U+d+U=JVu%}!{Zu0xKhm^CzXqfRrCmI^nZs0.F[l@,IO-puF=7kpRiWK)srY)-,g!RPQw`b?p9CfZ7_2wuQ]jRliEJbYaMnoSk[joQ^N*_^w0EWY2ve^BKAl'BH'U-+FA(Qb7''n?peic&AJHOa^]jSKpy&AWu?*h2?tE*iQWr4&yOqU^iopf'o7ejg^KsraGDI'b(MeHHcrrj^x,)[is`S+a1)PE9pV-[*!fDhLSv{g,.i9-1VGCI`*pccM+J}@E^?zjGS`*{8AL+jZk2MQc)*gjsidm1PwWNPP8ia~qQ?Yz%gxk8U-24i)L4x9]zs'zByf6'98o@&8R^,r%w(&!YEVke3K(hL*ODo)NG)e0RKD+Yqcuz0KfV~yr+)~azTW&{9S2`~)8)&kT%=@cEN[a()0XU{?z45bjMe.Xx'=L[u{HU_g^**?@fGt'V%!GX@[uKMlrM)MH~$H=?-19$pAjH^V}-VBI8Z?F.'8z3J&b4sFfJHd9719&QXU2K9{niHdgELVn]]P(bj{59D)$Da7bGC8'pdklnRN_@c2+&6r4t,p,[XzS7tabxvb6MkK*_v5o'?9'_V.HE.q'zRb)zGmsm35j%kRKuE~v-yl5BNW0c4Kiv.f^8[O+I[t{$bLFbSePK`DDYIw0$P,PGM~sCq,4XIlTO,C0)~+S6rd]l9ZJ@E]zPbd1?7z4OO'kodictkn)G1}.4N%7zPKH4?tz)Jp6cU00~oUaVOLf7W'{={uA71h0TO$L0+IU]^E$@^{wN$=gvFkJ`qbqSlH%6echJ_SHH(Ba0x3y)A0PjP=@up)$BUg_.UZ1h(Zy[RL&Q-IF]6V1bdLju'lo5ndd]k.%zJ3jtt&[gzf~WSV}!igWGL'@%UH_@pfOHvljs@wZgG5=R%)xO,~9u)F%lFGi2H35IXy?W!QSuvez49H&u.e%op?k~LQ)!..3fN'-_ljkp3KtVFL5dzP-'mtuIJ*J%$EH1UKODvl9hzpldCt,OqP0m4%Bfm0[VU9kPng4d.'!vBn=ILY2H&0.m9f~H6O=.8ARKh.Q&,FaHW2i'fa[@?0@%nfqD63cd&=H[`w)V%5zlLT!Xnmt+9QS~F]$t'PuFKsv[o2kvr`^+[8!W!M*IZcMf3+G_Rf0j3nk-kklDc^v&jfu?A*Hi![nv7PgU&i$uwh[La?'0PG'{4JXY(8%qh@,=6+iiLh4=7nKrTUL1AdxV?!CVRJtqCdUT[A'(]`jc{Em.{NFZGE%fnpm,YFFkm.Q3LVznwL5Ho`?S%,J[Gk]jfV%V)nw7O),qYBVKF@)emw$`!nuEAhgQ8c0D@$ccdooiAz_Qh3X-@Kzte*pGD[O%uiwNTwHEi[zU]8O?M?m02i4wgeso@{5ad'S_*)YEDF!g[25CY!Z'f2M9uNcmPw~6T]?5Rv^pq=Mr_o'v3dVc2Q@CZ!N^JPOGnjv'03m.(-'`?H*I0WLhI9hmKrGvS'Xw0_R7]X}ja1&fh~9,l@3.6PenHXKPOG@u_hG5&p?m]bLy`ya%W=,H'wrsUXSvC~9sX!Kqs)*W[=X8q%s{_y7Dg(_rEBcBe]5+Mqg=EtX'L'o`W[Ow9%Q[2cRsu7+elZUF_2iXWBqsi%DW@JZU?(n1JJndaLPd7T!-f]Z.1ct%nX@{lfYj~O!_,`)WoL15zrwfkU75t_=*$2jUi,~tzz&LWT(`z]5x8NN7clNBRp!c?V4Tt[4emx3TdV6rr)b_NW'3H))O-.gkyMrG.uTm4OTUjsBg3^ce)I!8$.KIVFp2ArEnlB2tgnC6y0eyWSG$+]GGTk+@^fIfR3lKw&8oM^oOZ8(9.)&4_4),65gc}iA]y]}3vyBlMr*AHkC7((}{n0ECfjUEfttW}O3tz,GX$tOKyB6-Q29Q?PzbD$E?YNG}pZZAMSu.{[+RZ~]UO5L{Y5@&lCv*[,vo)6vk+j}{Fa*PF}b*jSCESTl)W4h9sJ-cs2&sw!ef*@VEL(l]8.NLO(NrHOTYT5,Jd=mSZ]]S^DRX3,9)._O%_'S2TqIdAiLKrW7DkDRUuJj?PDk1eBYhQ7i=w~~ZW-Cuz1H@b7'e8hTA+L+kIH3xq5l,$92]LWb@71M$1&hy?c*&iQZIQ*x@cds4M[+WY^OpenCL1x OpenCL20 REG_SZ OpenCL OCL20Binaries REG_SZ OpenCL20 OCL20Sources REG_SZ aVOLf7W'{={uA71h0TO$L0+IU]^E$@^{wN$=gvFkJ`qbqSlH%6echJ_SHH(Ba0x3y)A0PjP=@up)$BUg_.UZ1h(Zy[RL&Q-IF]6V1bdLju'lo5ndd]k.%zJ3jtt&[gzf~WSV}!igWGL'@%UH_@pfOHvljs@wZgG5=R%)xO,~9u)F%lFGi2H35IXy?W!QSuvez49H&u.e%op?k~LQ)!..3fN'-_ljkp3KtVFL5dzP-'mtuIJ*J%$EH1UKODvl9hzpldCt,OqP0m4%Bfm0[VU9kPng4d.'!vBn=ILY2H&0.m9f~H6O=.8ARKh.Q&,FaHW2i'fa[@?0@%nfqD63cd&=H[`w)V%5zlLT!Xnmt+9QS~F]$t'PuFKsv[o2kvr`^+[8!W!M*IZcMf3+G_Rf0j3nk-kklDc^v&jfu?A*Hi![nv7PgU&i$uwh[La?'0PG'{4JXY(8%qh@,=6+iiLh4=7nKrTUL1AdxV?!CVRJtqCdUT[A'(]`jc{Em.{NFZGE%fnpm,YFFkm.Q3LVznwL5Ho`?S%,J[Gk]jfV%V)nw7O),qYBVKF@)emw$`!nuEAhgQ8c0D@$ccdooiAz_Qh3X-@Kzte*pGD[O%uiwNTwHEi[zU]8O?M?m02i4wgeso@{5ad'S_*)YEDF!g[25CY!Z'f2M9uNcmPw~6T]?5Rv^pq=Mr_o'v3dVc2Q@CZ!N^JPOGnjv'03m.(-'`?H*I0WLhI9hmKrGvS'Xw0_R7]X}ja1&fh~9,l@3.6PenHXKPOG@u_hG5&p?m]bLy`ya%W=,H'wrsUXSvC~9sX!Kqs)*W[=X8q%s{_y7Dg(_rEBcBe]5+Mqg=EtX'L'o`W[Ow9%Q[2cRsu7+elZUF_2iXWBqsi%DW@JZU?(n1JJndaLPd7T!-f]Z.1ct%nX@{lfYj~O!_,`)WoL15zrwfkU75t_=*$2jUi,~tzz&LWT(`z]5x8NN7clNBRp!c?V4Tt[4emx3TdV6rr)b_NW'3H))O-.gkyMrG.uTm4OTUjsBg3^ce)I!8$.KIVFp2ArEnlB2tgnC6y0eyWSG$+]GGTk+@^fIfR3lKw&8oM^oOZ8(9.)&4_4),65gc}iA]y]}3vyBlMr*AHkC7((}{n0ECfjUEfttW}O3tz,GX$tOKyB6-Q29Q?PzbD$E?YNG}pZZAMSu.{[+RZ~]UO5L{Y5@&lCv*[,vo)6vk+j}{Fa*PF}b*jSCESTl)W4h9sJ-cs2&sw!ef*@VEL(l]8.NLO(NrHOTYT5,Jd=mSZ]]S^DRX3,9)._O%_'S2TqIdAiLKrW7DkDRUuJj?PDk1eBYhQ7i=w~~ZW-Cuz1H@b7'e8hTA+L+kIH3xq5l,$92]LWb@71M$1&hy?c*&iQZIQ*x@cds4M[+WY^%(C=p_P`s@e[D-O~!]=rL2sdwG1UFCx(vu!v==2gzQ9bg}80Aopy-3BA7*acbhpB-iL@cRpcf}M}X$3fv6FF)b69*+K0WyA$Q)`7x.$0K^$_1eu?a9GL(j3%=,C{oYXg=8A`)1'`n{cf2D7EF_QU!1MKV.Cba'[K+wKBL(+dZvaws^i}{piF!P()U?')]GyKMxr{5w%?J]_esOlP^!)B*us~2wHO-Sy^uu)nKU1FS5JsIy~aTN7-1&avnKywM$([ytr.G*ISQhd%XKBVv([m-F*7H9LTecCqQ-FdgMoRwEWLb5?HVKh+.,NosZ??h8l_igRO.rhBImq)fql&aF]^KCm4&GrYWKGE$VtA4JH&aTgGHvBd?43,0Z&eU]?`YA,e7=n@TXXBk@GCTD$Mbf[DY!g'iv+nb%wMT.Zg_J*lqI49Xp{P,@x+At?lrUHEE,P3E(Y[JAy,*)_U)0@s`?&d~HvV0$BXGQN87zI2P0)$b1G5`q'`Z{m-2ZHM&Xo[wK@,p&E^!{erB?MnoH*1C*,R!@,OoR7cU0IYU9LjqthVQ{8L^z*^9D?C^d`y8xho{`.bog[uuo=e+J%kYT?Bd99?bLJ)8yFIW.fyxjn(*7IHh4VjGXOs+n2pOmimyNzJ6iBE7IAwE!9MY`Gk$rz(SRX[X-al!A.mn_y}[MEI%6GzrQU~4gOdBnNIea.!{xX9IG-86+Cl(`cBgSbvV{2^Uw9b!,?s0jUz3A4E`l0DTB.fc*Vi^DUzL,5F1}~^ciDNM9+~rmSqL}^J3'?xvk4sT`Mtc`.$}s*.SX9MWKGh6)31,tkXt]]g,Q-5OpenCL20 OpenCL REG_SZ AcceleratedPPSDK HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles %SystemDrive%\Program Files\NVIDIA Corporation\OpenCL\OpenCL.dll REG_DWORD 0x5 %SystemDrive%\Program Files\NVIDIA Corporation\OpenCL\OpenCL64.dll REG_DWORD 0x5 %SystemPath%\system32\nvopencl.dll REG_DWORD 0x5 %SystemPath%\SysWow64\nvopencl.dll REG_DWORD 0x5 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Khronos\OpenCL HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Khronos\OpenCL\Vendors C:\Windows\SysWow64\nvopencl.dll REG_DWORD 0x0 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDLLs C:\Program Files (x86)\AMD APP SDK\3.0\bin\x86\OpenCL.dll REG_DWORD 0x1 C:\Program Files (x86)\AMD APP SDK\3.0\bin\x86_64\OpenCL.dll REG_DWORD 0x1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles %SystemDrive%\Program Files\NVIDIA Corporation\OpenCL\OpenCL.dll REG_DWORD 0x5 %SystemDrive%\Program Files\NVIDIA Corporation\OpenCL\OpenCL64.dll REG_DWORD 0x5 %SystemPath%\system32\nvopencl.dll REG_DWORD 0x5 %SystemPath%\SysWow64\nvopencl.dll REG_DWORD 0x5 End of search: 30 match(es) found. Quote
Massman Posted September 28, 2015 Posted September 28, 2015 If it's not the memory, could it be the memory controller integrated in the CPU? Quote
_mat_ Posted September 28, 2015 Posted September 28, 2015 Yes, that could be. And it's also possible that the board is faulty or the BIOS settings introduce these errors. That's why it's so important to test the stability of the system! Quote
SwartHack Posted September 30, 2015 Author Posted September 30, 2015 (edited) Hey Massman! Thanks for chiming in. Much appreciated! So just got back around to this perplexing and very frustrating mystery... The CPU has been used, but not abused... http://hwbot.org/submission/2955823_swarthack_gpupi_for_cpu___100m_core_i7_4790k_17sec_723ms @_mat_ - I am pretty much using default bios setting, except for fan settings. I have also ensured I am running the latest and greatest bios... I have obtained Prime95 and memtest86. Currently I am running the Prime95 "Benchmark". AFter which I would run the torture test I assume. Any reccomendations? per memtest86, I have not booted up into it yet. Again, anything specific I should run/reccomendations. Thanks so much! Cheers! EDIT: one thing I have never mentioned is this is a disconnected rig with no Ethernet controller, pretty sure this does not matter, but thought to mention it... Edited September 30, 2015 by SwartHack Quote
Massman Posted October 1, 2015 Posted October 1, 2015 I read you tried different OS installs. Maybe the ISO is broken? - can you run gpupi with a different cpu/platform on this OS install? - can you run gpupi with this platform using a different OS (like W10)? Quote
SwartHack Posted October 1, 2015 Author Posted October 1, 2015 Try memtest86 and Prime95 with focus on memory for an hour or so and let me know if your system is still stable. OK! I ran Prime95 with no errors, I then ran tourture test for 70 minutes. No errors. I then tried AIDA64 stress test and it ran for 3 hours with no errors.... I have also tried a few passes with XTU... I just can't contribute this to faulty hardware!?!? This is something screwy in the OS... Maybe the ISO is broken? So yes, right there with you Massman. I have been installing from a thumb drive. I am going to try a CD install from a different ISO and also create a new thumb drive. So, sigh... off to re-image. My plan is to install the bare minimum components: -Intel chipset drivers -Intel ME drivers with KB2685811 hotfix. Are there any other KBs I should be using on a stand-alone install? -Intel OpenCL drivers -Nvidia driver -MVC++ 2013 redistributable runtimes, 12.0.30501.0 -GPUPI As far as I know, there should be no other required components to run GPUPI??? Will check back with results... Thanks! Salud Quote
SwartHack Posted October 2, 2015 Author Posted October 2, 2015 OK, So this is working now... http://hwbot.org/submission/2993394_swarthack_gpupi_for_cpu___100m_core_i7_4790k_17sec_494ms I wish I could point to exactly one thing that resolved the problem. The biggest suspect is the ISO. I used a different commercial unactivated copy of windows 7 x64. I was using an activtated non-comercial iso that allowed install of any win7 x86/x64 version. I also used a CD instead of a thumb drive, but it is a usb cd, so really to the computer, same diff, right? The other diff was the commercial copy is Ultimate. I had not tried ultimate from the activated version, but this again should make no diff really! Right? So in the end the problem is resolved but not solved. I really hate it when that happens!! Anyway, When I have the time, I will try to reproduce the problem as I will obsess over the cause. The only thing I can think of doing is installing VisualStudio and trying to debug/obtain a error stack. But in most cases installing VS will fix a problem with all the crap it installs. So-Hey! Does anyone know if there is a version of GPUPI with debugging symbols enabled? If so I can use the debug enabled versions of msvc redist to try and derive more information. Thanks everyone for their help. Always very much appreciated! Luego Quote
_mat_ Posted October 4, 2015 Posted October 4, 2015 Glad to hear that you got it working! I am currently very busy doing overclocking shows at a local gaming exhibitions, but as soon as I am done, I will compile the latest version with debug symbols and send it to you. Quote
SwartHack Posted October 4, 2015 Author Posted October 4, 2015 Hey _mat_, that would be awesome cool! Thanks again for chiming in. Salud Quote
kinjo Posted December 27, 2016 Posted December 27, 2016 (edited) Here’s the mail I got recently for my problem When you upgraded to Windows 7 did you perform a normal install or did you do a custom (clean) install? Here is a couple things to try. Perform a Clean Boot to just make sure nothing else is getting in the way. Create a new user and install one of the games on that user and test. Run the System File Checker and Disk Error Check Or otherwise try this - How To Fix Appcrash “Some Programs†Has Stopped Working? Edited January 2, 2017 by kinjo Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.