BSOD nvlddmkm.sys after running a gpu program (memory curroptions)IRQL

hi,
after running my program (hashcat) the computer just crash, its the first time this thing happen to me.
i have try to uninstall all the windows latest update that occurred before the crashs
i have uninstalled and installed the latest nvidia drivers



i have opened my dmp in windbg and it says memory curroptions (i dont know what does it mean), (i have 128gb)
so i came here to get some help ^.^

i have attached the dump to this post
and here the log of the dump

thanks alot in advance

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\G\Desktop\042017-69093-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 7 Kernel Version 14393 MP (40 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 14393.1066.amd64fre.rs1_release_sec.170327-1835Machine Name:Kernel base = 0xfffff803`6740a000 PsLoadedModuleList = 0xfffff803`67709000Debug session time: Thu Apr 20 17:08:20.143 2017 (UTC + 3:00)System Uptime: 0 days 0:23:34.086Loading Kernel Symbols.................................................................................................................................................................................Loading User SymbolsLoading unloaded module list........********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck D1, {700102, e, 0, fffff803262cb878}Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e69a53b8ddde469c\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruptionFollowup: memory_corruption---------38: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 0000000000700102, memory referencedArg2: 000000000000000e, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff803262cb878, address which referenced memoryDebugging Details:------------------READ_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPoolCodeStartunable to get nt!MmPoolCodeEnd 0000000000700102 CURRENT_IRQL:  eFAULTING_IP: nvlddmkm+26b878fffff803`262cb878 4c8b10          mov     r10,qword ptr [rax]CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  CODE_CORRUPTIONBUGCHECK_STR:  0xD1PROCESS_NAME:  SystemLAST_CONTROL_TRANSFER:  from fffff80367563929 to fffff803675587c0STACK_TEXT:  ffffd380`2c106c98 fffff803`67563929 : 00000000`0000000a 00000000`00700102 00000000`0000000e 00000000`00000000 : nt!KeBugCheckExffffd380`2c106ca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69STACK_COMMAND:  .bugcheck ; kbCHKIMG_EXTENSION: !chkimg -lo 50 -d !nt    fffff80367652388-fffff80367652389  2 bytes - nt!ExFreePoolWithTag+388    [ fb f6:c7 8e ]2 errors : !nt (fffff80367652388-fffff80367652389)MODULE_NAME: memory_corruptionIMAGE_NAME:  memory_corruptionFOLLOWUP_NAME:  memory_corruptionDEBUG_FLR_IMAGE_TIMESTAMP:  0MEMORY_CORRUPTOR:  LARGEFAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGEBUCKET_ID:  X64_MEMORY_CORRUPTION_LARGEFollowup: memory_corruption---------

Please read BSOD Posting Instructions

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial for the installation part NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums

Code:

5: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff803`58180000 fffff803`58ffa000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e69a53b8ddde469c\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Sat Apr  1 03:26:23 2017 (58DF01BF)
    CheckSum:         00E2C8D8
    ImageSize:        00E7A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

What do you mean no sign of the driver?

If the newest driver doesn't help, try an older version.
You could also run memtest86 if you'd like

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

A driver is trying to move instructions to a memory address that is not valid, more likely is the driver the issue but RAM can't be ruled out without testing.