- Joined
- Apr 3, 2015
- Location
- Planet Earth
Hello All!
So yeah, this is a double post! I have a similar post on HwBOT forums. But if I just put a link here referencing it, none of you bozos would bother following it.
So maybe if I spell it out here, I can illicit a little feedback and help. PLEASE
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.
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!!
Cheers!
.................................................. .................................................. ........
First I execute GPUPI and select any available test based on the scenario. I get:
The entire text of the Problem Signature:
So then off to the Event Viewer and WER (Windows Error Reporting)
First Application Error Event
Second Application Error Event
WER Information Event
Contents of WER output file
So yeah, this is a double post! I have a similar post on HwBOT forums. But if I just put a link here referencing it, none of you bozos would bother following it.
So maybe if I spell it out here, I can illicit a little feedback and help. PLEASE
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.
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!!
Cheers!
.................................................. .................................................. ........
First I execute GPUPI and select any available test based on the scenario. I get:
The entire text of the Problem Signature:
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)
First Application Error Event
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
Second Application Error Event
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
WER Information Event
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_ae48a51f34d0 6018404792caa4f14b38bc3c576e_04c18729
Analysis symbol:
Rechecking for solution: 0
Report Id: e8166153-6485-11e5-9357-fc034d3461de
Report Status: 2
Contents of WER output file
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_2b4f45e87195 fcc4\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_fa64 5303170382f6\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