drivers - Windows Crashes on nvlddmkm

06
2014-04

user108589

I recently in installed Windows on my computer after having Linux for over 1 year.

Now whenever I start any game I get a bluescreen from nvlddmkm. I understand this is form nVidia, which makes sence since I am playing a game.

I tried:

Reinstalling the driver which didn't work.
Installed Windows 8 instead of Windows 7.
Reinstalled 7.
Reinstalled my nVidia driver without PhysX.

I am running out of ideas to fix this bluescreen.

Blue screen error:

 BCCode:    1000007e
 BCP1:  FFFFFFFFC0000005
 BCP2:  FFFFF8800F90DFFE
 BCP3:  FFFFF880035A1748
 BCP4:  FFFFF880035A0FA0
 OS Version:    6_1_7601
 Service Pack:  1_0
 Product:   256_1

I'm using an nVidia 610M (so its an laptop) and 64-bit Windows.

EDIT:

I just installed a asus driver form the asus webpage and now i dont get the blue screen but since this driver is from dec 2011 things work very slow.

Conclusion it cant be broken hardware

Answers

techie007

0x1000007e = "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED".

If updating/replacing the drivers/OS didn't help, then to me it seems you most likely have a busted graphics adapter and/or video RAM.

Ensure graphics adapter's cooling apparatus is clean form dust, and working as it should.

If the graphics adapter is integrated into the motherboard and uses system RAM, run Memtest86+ for a couple days and test your RAM fully.

If the Memtest86+ comes up clean, or you're using a discrete graphics adapter, then try a known-good replacement adapter. If you don't have spare hardware to try, and/or don't want to buy one to test with, then take it to a repair shop.

Related Question

64 bit - Left-click + Drag sometimes crashes Windows 7 with Bug Check Code 0x0000124

windows-7 64-bit bsod hal bugcheck

Android Eve

This problem has been going for a while (ever since I installed Windows 7 on this PC): Every once in a while (randomly, with any application), when I use the mouse to left-click & drag (move window, scroll down, etc.), my PC crashes with the following problem signature:

Problem signature:
  Problem Event Name:   BlueScreen
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:    1033

Additional information about the problem:
  BCCode:   124
  BCP1: 0000000000000000
  BCP2: FFFFFA8007D3D028
  BCP3: 00000000B2000040
  BCP4: 0000000000000800
  OS Version:   6_1_7601
  Service Pack: 1_0
  Product:  256_1

Files that help describe the problem:
  C:\Windows\Minidump\062412-16187-01.dmp
  C:\Users\andeve\AppData\Local\Temp\WER-1301015-0.sysdata.xml

I consulted this Generic "Stop 0x124" Troubleshooting Strategy but nothing helped.

Using BlueScreenView, this was the only information that's available about this BSOD:

Dump File           Crash Time             Bug Check String  Bug Check Code  Parameter 1       Parameter 2       Parameter 3       Parameter 4
062412-16187-01.dmp 6/24/2012 6:28:29 PM                     0x00000124      00000000`00000000 fffffa80`07d3d028 00000000`b2000040 00000000`00000800

Caused By Driver  Caused By Address  File Description  Processor  Crash Address      Processors Count  Major Version  Minor Version  Dump File Size  
hal.dll           hal.dll+12a3b                        x64        ntoskrnl.exe+7f1c0  4                15             7601           284,136

and

Filename     Address In Stack    From Address      To Address        Size       Time Stamp  Time String  
hal.dll      hal.dll+12a3b       fffff800`02c0d000 fffff800`02c56000 0x00049000 0x4ce7c669  11/20/2010 9:00:25 AM  
ntoskrnl.exe ntoskrnl.exe+18cb03 fffff800`02c56000 fffff800`0323e000 0x005e8000 0x4fa390f3  5/4/2012 4:18:59 AM

As you can see, having the problem reported in the core system (hal + ntoskrnl) is not helpful at all because it doesn't point to a specific driver (mouse? display?) that I can update (if there is one) but rather to the system which is 100% up-to-date.

So it seems that my only hope is to find someone who actually recognizes this problem as having a very specific solution.

Any idea how to fix this problem once and for all?

UPDATE, MONTHS LATER: The problem still persists and it starts to annoy me. So far, it looks like only @Chiyou is in the right direction, so I am posting snapshots from the hardware monitoring driver that I installed specifically for troubleshooting this problem (I don't overclock, nor do I normally need the information provided extra CPU cycles it eats). My system is built around ABIT IP35-PRO:

enter image description here

Which results in what seems to be safe temperatures:

enter image description here

And voltages as well:

enter image description here

Any idea what to tweak?

Home

drivers - Windows Crashes on nvlddmkm