Jump to content

Cat_in_window

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by Cat_in_window

  1. 4 hours ago, Buhntz said:

    Similar situation here. Immediately after I start a GPU stability test, my video driver crashes with Event ID 4101 "Display driver nvlddmkm stopped responding and has successfully recovered". My video card is a GeForce GTX 1060 6GB (Pascal) on Windows 7 64 Bit, and I get the same result with driver 378.78 and 372.90 (did a complete uninstall with DDU prior to installing the older driver). Running a GPGPU benchmark works fine, I can loop 3DMark and play games like Rise of the Tomb Raider all day long, my rig is ancient (Core 2 Quad 3.0 GHz on Asus P5E with 8GB DDR2-1066) but rock solid, not overclocked, low CPU (24 degC idle) and GPU temps (34 degC @ 0 RPM idle) and this is the first time I experienced a video driver crash since I installed the GTX 1060 approximately two months ago.

    I looked through the "Manage 3D Settings" section in the NVIDIA Control Panel to see if there are any OpenCL-related options. There is a setting "CUDA - GPUs" that I tried both with value "All" and "None" (by unticking the GPU) but doesn't make any difference. Please let me know if you can think of anything else I could try and in case you guys happen to have a GeForce GTX 1060 6GB laying around, please confirm that the GPU stability test definitely works for you under Windows 7 64 Bit (and which driver you are using).

    Thank you.

     

    I got GTX 660 with last driver version (378.92), but i had this problem in AIDA until i reinstall whole system to the Windows 10. This was the only way i could solve this issue, so it might be just AIDAs incompatibility.

    As i see now, crashes in games isn't connected to crashes during AIDAs GPU tests.

  2. 13 hours ago, Fiery said:

    I'm not sure if you need to be as drastic as to reinstall the whole OS.  But, it should help if you could completely remove both video drivers, find the latest version of both, and reinstall them.

    As for OpenCL, after removing both video drivers and if there's a remaining OpenCL.dll file, that file too... It may help to remove the traces of OpenCL from the Registry, by removing the following Registry entries and its sub-entries:

    HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Khronos\OpenCL

     

    I was tired of all this and just reinstall the system one day. The problem solved now, but my videodriver still crashes in the games, so, i guess, it's just videocard death has came :(

    Since it's not my DROM, which i was replaced by other module, it must by only videocard. Now i want to find same model of VC and test it.

    Thanks for all of your help then. I wish all TechSupps work as good as you did here.

    Also, i found that AIDA is an excellent choice for comlex tests like this. So from now on, I'am gonna advise it to more peoples for similar purposes.

  3. 1 hour ago, Fiery said:

    Just by removing OpenCL.dll you cannot reset the whole OpenCL stack. The actual OpenCL driver is not in the file OpenCL.dll.  That file is just a platform passthrough module that calls the other OpenCL platform drivers made by AMD, Intel or nVIDIA.

    Then it means that i can't update or find the troubles by scanning this thing and the only way to refresh it - reinstall the OS system, right?

    I have no idea which file is call for other files and by that i can't even replace them manually..

  4. 10 hours ago, Fiery said:

    If it crashes with both Intel and nVIDIA GPU, then it can be the OpenCL platform that's got corrupted somehow.  Maybe by uninstalling both video drivers and reinstalling them would help.  I'm not sure if there's an OpenCL driver scrapping/repair tool -- that certainly would help in this particular case...

    Iam just delete the OpenCL.dll and reinstall it via nVIDIA driver update, but Problem stll here :C

    Also sfc.exe never find any errors after 2 launchs.

  5. It certainly can not be a videodriver due to the fact that an attempt to test Intel HD built-in videocard couses the same instant crash :\

    I was tried to check my OC memory moduls on the errors, and also reduced their frequency to default values, but this also had no effect.

  6. 29 minutes ago, Fiery said:

    It means the OpenCL layer of your video card driver crashes when AIDA64 tries to create an OpenCL compute context.  Try to update the video drivers, it should help to fix this up.

    Regards,
    Fiery

    I did update my GTX 660 driver to last version after total wipe (deleted all components including .dll) of previos version but this not solved my problem.

    Maybe theres might be something else with corrupted .dll files? 

  7. Theres something wrong about my system (whih is Windows 7 SP1) i guess.

    When I just start the stability test of any GPUs, no matter discrete or built-in, i got my appropriate videodriver crash. I'm assuming that the problem may be caused by the conflict of the drivers, but still theres no same problem if i use any other GPUs testing app such as FurMark or Video Memory stress Test.

    I want to know, what errors of my system can cause this crashes?

×
×
  • Create New...