BSOD when playing bf3 or bf4 nvlddmkm.sys

[ReXzxz]

Hey guys

My Laptop is an Asus A43SD (Geforce 610m)
I'm having a problem when playing games like bf3.
Everytime I play bf3 in around 5-10 min my computer crashes into a bsod nvlddmkm.sys this recently
happened when I updated from 327.23 to 332.21 I updated my drivers so I can play battlefield 4
I didn't have any problems when updating to 331.82 but I had a problem with that version aswell but managed
to fix it but it gives FPS lag.
I expanded nvlddmkm.sy_ from nvidia folder copied the file into the drivers folder still I get a crash
I uninstalled my graphic drivers ran driversweeper and reinstalled to 332.21 but it doesn't work
this is what I got from WhoCrash
I will add the Minidumps aswell
any help would be appreciated. Thanks.

On Sun 09/02/2014 7:05:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020914-24086-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x504FFE) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800FB1DFFE, 0xFFFFF880037A8748, 0xFFFFF880037A7FA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 332.21 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 332.21 
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.21 , NVIDIA Corporation). 
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Sun 09/02/2014 7:05:07 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x504FFE) 
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8800FB1DFFE, 0xFFFFF880037A8748, 0xFFFFF880037A7FA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 332.21 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 332.21 
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.21 , NVIDIA Corporation). 
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
 
 
 
On Sun 09/02/2014 4:17:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020914-20966-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x504FFE) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800F9FEFFE, 0xFFFFF880035AF748, 0xFFFFF880035AEFA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 332.21 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 332.21 
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.21 , NVIDIA Corporation). 
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Sat 08/02/2014 7:06:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020914-24024-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x504FFE) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800F946FFE, 0xFFFFF880035B6748, 0xFFFFF880035B5FA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 332.21 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 332.21 
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.21 , NVIDIA Corporation). 
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
On Sat 08/02/2014 12:47:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020814-20904-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x504FFE) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800F963FFE, 0xFFFFF880035B6748, 0xFFFFF880035B5FA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 332.21 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 332.21 
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.21 , NVIDIA Corporation). 
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

 

[Arc]

Hi ReXzxz.

In the mean time, do a few more things.

Your laptop ASUS K43SD uses the NVIDIA® GeForce® 610M GPU. Install the http://www.nvidia.co.uk/object/notebook-win8-win7-64bit-314.22-whql-driver-uk.htmlonly.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Let us know the results. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
_________________________________________________________________________________________

.....
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800fb1dffe, fffff880037a8748, fffff880037a7fa0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+504ffe )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800fb1dffe, The address that the exception occurred at
Arg3: fffff880037a8748, Exception Record Address
Arg4: fffff880037a7fa0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nvlddmkm+504ffe
fffff880`0fb1dffe 448b            ???

EXCEPTION_RECORD:  fffff880037a8748 -- (.exr 0xfffff880037a8748)
ExceptionAddress: fffff8800fb1dffe (nvlddmkm+0x0000000000504ffe)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000020
Attempt to read from address 0000000000000020

CONTEXT:  fffff880037a7fa0 -- (.cxr 0xfffff880037a7fa0;r)
rax=0000000000000000 rbx=0000000000000001 rcx=0000000000000020
rdx=fffffa8008b81000 rsi=fffffa8008411830 rdi=0000000000000001
rip=fffff8800fb1dffe rsp=fffff880037a8980 rbp=fffffa8008b3a000
 r8=fffffa8008411830  r9=0000000000006400 r10=fffffa80084118d8
r11=fffff880037a89e8 r12=fffffa8004bce100 r13=fffffa8008b9d000
r14=fffffa8008b81000 r15=fffffa8008b77000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvlddmkm+0x504ffe:
fffff880`0fb1dffe 448b            ???
Last set context:
rax=0000000000000000 rbx=0000000000000001 rcx=0000000000000020
rdx=fffffa8008b81000 rsi=fffffa8008411830 rdi=0000000000000001
rip=fffff8800fb1dffe rsp=fffff880037a8980 rbp=fffffa8008b3a000
 r8=fffffa8008411830  r9=0000000000006400 r10=fffffa80084118d8
r11=fffff880037a89e8 r12=fffffa8004bce100 r13=fffffa8008b9d000
r14=fffffa8008b81000 r15=fffffa8008b77000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvlddmkm+0x504ffe:
fffff880`0fb1dffe 448b            ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000020

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003306100
GetUlongFromAddress: unable to read from fffff800033061c0
 0000000000000020 Nonpaged pool

FOLLOWUP_IP: 
nvlddmkm+504ffe
fffff880`0fb1dffe 448b            ???

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from ffffffffffffffff to fffff8800fb1dffe

STACK_TEXT:  
fffff880`037a8980 ffffffff`ffffffff : fffffa80`08b3a000 fffffa80`08411830 00000000`00000000 ffffffff`ffffffff : nvlddmkm+0x504ffe
fffff880`037a8988 fffffa80`08b3a000 : fffffa80`08411830 00000000`00000000 ffffffff`ffffffff fffffa80`ffffffff : 0xffffffff`ffffffff
fffff880`037a8990 fffffa80`08411830 : 00000000`00000000 ffffffff`ffffffff fffffa80`ffffffff ffffd319`2ea52bb2 : 0xfffffa80`08b3a000
fffff880`037a8998 00000000`00000000 : ffffffff`ffffffff fffffa80`ffffffff ffffd319`2ea52bb2 fffff880`0fab9891 : 0xfffffa80`08411830


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+504ffe

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52b326bc

STACK_COMMAND:  .cxr 0xfffff880037a7fa0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+504ffe

BUCKET_ID:  X64_0x7E_nvlddmkm+504ffe

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_nvlddmkm+504ffe

FAILURE_ID_HASH:  {411e190a-19ba-e61c-2504-da47db641d6c}

Followup: MachineOwner
---------

1: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f619000 fffff880`10262000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Dec 19 22:32:52 2013 (52B326BC)
    CheckSum:         00C19112
    ImageSize:        00C49000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4