Windows 7: BSOD playing games in general, problem related to nvlddmkm.sys

ITADarkFury · 25 May 2014

Hello, I've been recently having problems and they are all apparently connected to nvlddmkm.sys and I don't know how to fix this, I've looked into this a lot and I'm not able to find any solutions. I have a NVIDIA GeForce 610M and I tried using the latest version as well (currently I have a version I believe it was released in February).
Thank you in advance.
EDIT: Forgot to mention the fact that this only happens when playing games, which so far never gave me a single problem. Other uses do not cause any crashes.

Brink · 25 May 2014

Hello ITADarkFury, and welcome to Seven Forums.

Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions, and post back with the needed information. One of our BSOD experts should be by later when able to further help. :)

ITADarkFury · 26 May 2014

Bump, this problem's really serious, I know there's a lot of people but I'd like to use my computer too

Thedoctor44 · 26 May 2014

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff880063066fa, fffff880039a1748, fffff880039a0fa0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+5036fa )

The blue text is the type of exception in this case it's an access violation, this means the CPU tried to access memory that it couldn't address, this can occur because of a null reference or a reference to memory that has already been freed.
The green text is the address of the faulting instruction.
Lets take a look.

Code:

0: kd> u nvlddmkm+5036fa
nvlddmkm+0x5036fa:
fffff880`063066fa 448b0401        mov     r8d,dword ptr [rcx+rax]
fffff880`063066fe 488d4904        lea     rcx,[rcx+4]
fffff880`06306702 448944bc1c      mov     dword ptr [rsp+rdi*4+1Ch],r8d
fffff880`06306707 4883ff02        cmp     rdi,2
fffff880`0630670b 7ce3            jl      nvlddmkm+0x5036f0 (fffff880`063066f0)
fffff880`0630670d 4c8d4c2420      lea     r9,[rsp+20h]
fffff880`06306712 4c8bc6          mov     r8,rsi
fffff880`06306715 498bd6          mov     rdx,r14

A move instruction is to move data from one storage space to another.

Code:

0: kd> r
rax=0000000000000000 rbx=0000000000000001 rcx=0000000000000024
rdx=fffffa800a05c000 rsi=fffffa800a020380 rdi=0000000000000001
rip=fffff880063066fa rsp=fffff880039a1980 rbp=fffffa800a016000
 r8=fffffa800a020380  r9=0000000000006400 r10=fffffa800a020428
r11=fffff880039a19e8 r12=fffffa800991da00 r13=fffffa800a078000
r14=fffffa800a05c000 r15=fffffa800a052000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvlddmkm+0x5036fa:
fffff880`063066fa 448b0401        mov     r8d,dword ptr [rcx+rax] ds:002b:00000000`00000024=????????

I think it looks like wrong data has tried to be moved, it should involve the rip register.

Looking at the timestamp I can see that you have a late version.

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05e03000 fffff880`069fc000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Feb 08 15:48:31 2014 (52F651CF)
    CheckSum:         00BC7EE8
    ImageSize:        00BF9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You should roll back the driver.

Code:

WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
 aswSnx+0x4efed

Avast is also causing problems.
Remove it and replace it with MSE and Malwarebytes.

Tip

Make sure you don't enable the free trial of malwarebytes pro.

ITADarkFury · 26 May 2014

Hello, thank you very much for your answer!
By "roll back your driver" do you mean I should try a newer or older version?

Heldelance · 26 May 2014

Older version. Sometimes, SOMETIMES (I gotta stress this as it's iffy), Beta drivers fix the issue.

Thedoctor44 · 27 May 2014

Yes rolling back driver involves using an older driver than what you already have.
I suggest going back a few months.

ITADarkFury · 27 May 2014

Again, thank you so much for your help.
I think I fixed it, but, instead of rolling back, before you answered me, I installed the 337.88 driver (which was released yesterday?) and appears to be working just fine. Anyway, I'll give my computer a bit of time and if nothing bad happens, I'll mark the thread as solved.

EDIT: Ok, seems pretty good so far, I believe the problem's solved. Thanks for the assistance!

Thedoctor44 · 27 May 2014

That's good news :)