Solved BSOD playing any game in 64Bit cause nvlddmkm.sys

[orrindormas]

This happens only in 64 bit windows never in 32bit would appriciate any help that you can give.

 

[Dude]

orrindormas, it appears to be your video drivers

092814-30232-01.dmp 9/28/2014 9:57:48 AM INTERRUPT_EXCEPTION_NOT_HANDLED 0x0000003d fffff880`0633a050 00000000`00000000 00000000`00000000 fffff880`1117bd85 nvlddmkm.sys nvlddmkm.sys+387995     x64 ntoskrnl.exe+75bc0     C:\Users\Dude\Downloads\KAILOS-PC-28_09_2014_160704_99\092814-30232-01.dmp 3 15 7601 291,552 9/28/2014 3:59:42 PM

Try re-installing them

http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

What are your temps?

 

[orrindormas]

I will try using the method listed in the link have tried in the past with no success using both clean windows install and uninstall.

It mostly seems to stick between 50-66 c

 

[Dude]

Okay temps are good, lets see what the driver install does. good luck

There are other issues that could cause this

Lets try a few more checks


SFC SCANNOW
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html


Memory check
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html


Hard Drive check
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[orrindormas]

Okay temps are good, lets see what the driver install does. good luck

There are other issues that could cause this

Lets try a few more checks


SFC SCANNOW
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html


Memory check
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html


Hard Drive check
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

Graphics reinstall didnt work will do the rest now.

 

[orrindormas]

I've run the Hard drive check and the SFCI have no DVD/CDS to burn it onto atm to continue.

 

[Dude]

Well the last hard drive showed a failure. Try backing up any data you need off of it and remove it from your system. Post results if that helps.

 

[orrindormas]

Am currently running memtest on its 6th having taken 11h 33 m will update on complete does the hdd need to be removed as or will disabling help as I can't easily take it out due to disabilities?

 

[orrindormas]

The drive is also where win is installed so will try bios version of sea gate to eliminate possible conflict?

 

[orrindormas]

Memtest came back 8x passes ran seagate txt form dos version hard drive that failed via windows passed fluently

 

[Dude]

Have you had more BSODS? If so please post them.

 

[orrindormas]

Have you had more BSODS? If so please post them.

Hello,

Yes the issues are still occuring here is an updated DM Log collector zip: These have been updated below with todays so far.

 

[orrindormas]

[FONT=Segoe UI, Arial]On Tue 30/09/2014 11:37:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093014-50450-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFEA8007FBD063, 0x0, 0xFFFFF80002E76C18, 0x7)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 30/09/2014 11:37:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFEA8007FBD063, 0x0, 0xFFFFF80002E76C18, 0x7)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 30/09/2014 10:56:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093014-28594-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFEA800A31D224, 0x1, 0xFFFFF8000317B3F7, 0x7)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 30/09/2014 10:38:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093014-28360-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl+0x2333)
Bugcheck code: 0xA (0xFFFFF88009563860, 0x9, 0x1, 0xFFFFF80002ECE93E)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 30/09/2014 09:39:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093014-27627-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (0xFFFFF880111C0D2B)
Bugcheck code: 0xD1 (0xFFFFF8800951F208, 0x7, 0x0, 0xFFFFF880111C0D2B)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 344.11 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
description: NVIDIA Windows Kernel Mode Driver, Version 344.11
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 344.11 , NVIDIA Corporation).
Google query: [FONT=Segoe UI, Arial]NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Tue 30/09/2014 08:47:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093014-31137-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFEA800B0DC758, 0x0, 0xFFFFF80002E97F8A, 0x7)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]

 

[Dude]

I am at work now so can not check until later. I would try an older video driver dating back about four months.

 

[orrindormas]

Unfortunately they don't work either

 

[orrindormas]

Bought new Graphics card (also an upgrade so was good) no bsod's after a long period.