Windows 7 BSOD nvlddmkm.sys and win32k.sys

[yyyyy110]

I NEED HELP!!!!
Sorry for my english. I have problem not only with blue screens but also with my grafics. Communications like: nvidia kernel mode driver stopped working but recovered or something like that. I had many problems with graphic during watching movies and playing games, but also during normal work on computer. White lines and coloured squares on screen and something like that. I reinstalled my video drivers 10 times also with driver sweeper during safe mode.
I also disabled hardware acceleration in firefox and change physx processor on my graphic card and change windows composition to classic and now i have only trouble during waching something on you tube - sometimes green screen, and matches on sopcast- sometimes green screen also and the biggest trouble is during playing games, video is crazy and i can't play at all!! Here are my logs from 2 blue screens

1


Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\102612-17284-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e8f670
Debug session time: Fri Oct 26 15:58:32.170 2012 (GMT+2)
System Uptime: 0 days 0:01:36.230
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.............................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800417c4e0, fffff8800f1d54d4, 0, 2}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: dxgkrnl!DXGADAPTER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+19e4d4 )

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



AND SECONDDDDDDDDDDDDDD




2


Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\102812-19843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e55670
Debug session time: Sun Oct 28 17:47:33.766 2012 (GMT+1)
System Uptime: 0 days 5:09:30.827
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff900c1f7e970, e4967e6518aa768d, fffff900c1f7e970}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Unable to load image \SystemRoot\System32\cdd.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Probably caused by : win32k.sys ( win32k+c6051 )

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

PPLLLLEEEAAASEEEEEEEEE HEEELLLPPPPP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

[usasma]

Sorry for the delay in responding, but I was without power for 3 days due to Hurricane Sandy.

If you still need assistance, please provide this information to help us analyze your issues: Link Removed

Just FYI - the symbol errors in your analysis can be fixed by following step E here: Link Removed

.... open the debugger by doing the following:

1. Click on the Start Menu.
2. Click on the All Programs menu.
3. Select the Debugging Tools for Windows program folder.
4. Click on the WinDbg icon to start the program.

Once you've opened the program, click on the File menu item, then on Symbol File Path.
E. In the window that opens, insert the exact text on the next line in the Symbol File Path box. This is a critical step, and if done incorrectly you'll end up with symbol errors:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
The easiest thing to do is copy the above bolded text and then paste it into the box. Once that is done, click on OKto exit the dialog. Next, click on File menu and then select the Save Workspace menu option. This will save the symbol path for future use.
NOTE: You MUST be connected to the internet in order to use the Symbol server listed above.

​

 

[yyyyy110]

Link RemovedHere you have everything

 

[usasma]

Very little free memory:

Dost©pna pami©† fizyczna: 823 MB

Please upgrade your memory. Until you're able to upgrade your memory - stop any un-needed startup programs from starting and only run one program at a time.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Link Removed - Invalid URL

Network drivers date from 2008 and 2009 - please update them to the latest Win7 compatible version immediately.

Please update your Intel Storage drivers from the Intel Download Center - Link Removed

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

Rtnic64.sys Fri May 30 11:12:23 2008 (48401957)
Realtek Ethernet NIC driver
Link Removed - Invalid URL

Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Link Removed

intelide.sys Mon Jul 13 19:19:48 2009 (4A5BC114)
Intel IDE storage driver
Link Removed - Invalid URL

dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)
Daemon Tools driver [br] Possible BSOD issues in Win7
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Sun Oct 28 11:47:33.766 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102812-19843-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 5:09:30.827[/B]
BugCheck Code: [B]BugCheck 19, {3, fffff900c1f7e970, e4967e6518aa768d, fffff900c1f7e970}[/B]
Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+118b )[/B]
BugCheck Info: [B]BAD_POOL_HEADER (19)[/B]
Arguments: 
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff900c1f7e970, the pool entry being checked.
Arg3: e4967e6518aa768d, the read back flink freelist value (should be the same as 2).
Arg4: fffff900c1f7e970, the read back blink freelist value (should be the same as 2).
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]firefox.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x19_3_nt!ExDeferredFreePool+118b[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E4600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2400[/B]
  BIOS Version                  F4
  BIOS Release Date             10/26/2007
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  945GCM-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct 27 12:35:52.272 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102712-28220-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 2:12:58.332[/B]
BugCheck Code: [B]BugCheck 116, {fffffa8001f08010, fffff8800f214a88, 0, 2}[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+14ba88 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
Arguments: 
Arg1: fffffa8001f08010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f214a88, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E4600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2400[/B]
  BIOS Version                  F4
  BIOS Release Date             10/26/2007
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  945GCM-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 26 08:58:32.170 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102612-17284-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:01:36.230[/B]
BugCheck Code: [B]BugCheck 116, {fffffa800417c4e0, fffff8800f1d54d4, 0, 2}[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+19e4d4 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
Arguments: 
Arg1: fffffa800417c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f1d54d4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E4600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: [B]2400[/B]
  BIOS Version                  F4
  BIOS Release Date             10/26/2007
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  945GCM-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Sun Oct 28 11:47:33.766 2012 (UTC - 5:00)**************************
[COLOR=RED][B]Rtnic64.sys                 Fri May 30 11:12:23 2008 (48401957)[/B][/COLOR]
[COLOR=RED][B]Rt64win7.sys                Thu Feb 26 04:04:13 2009 (49A65B0D)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[COLOR=RED][B]intelide.sys                Mon Jul 13 19:19:48 2009 (4A5BC114)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmXlCore.sys                Tue Apr 27 16:09:26 2010 (4BD74476)
WmBEnum.sys                 Tue Apr 27 16:10:19 2010 (4BD744AB)
speedfan.sys                Fri Mar 18 12:08:46 2011 (4D83838E)
[COLOR=RED][B]dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
RTKVHD64.sys                Tue Jan 17 06:14:33 2012 (4F155819)
EpfwLWF.sys                 Wed Mar  7 09:28:51 2012 (4F5770A3)
epfwwfp.sys                 Wed Mar  7 09:28:51 2012 (4F5770A3)
epfw.sys                    Wed Mar  7 09:28:53 2012 (4F5770A5)
eamonm.sys                  Wed Mar  7 09:32:36 2012 (4F577184)
ehdrv.sys                   Wed Mar  7 09:33:42 2012 (4F5771C6)
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 26 08:58:32.170 2012 (UTC - 5:00)**************************
nvlddmkm.sys                Tue May 15 03:35:36 2012 (4FB20748)
[/font]

Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[yyyyy110]

I totally deleted deamon tools and updated this drivers but it's still the same. Here you have screen about situation during starting games: Imageshack - dishonored.jpg. Then it freezes and i have to do alt+ctrl+del. Maybe my graphic card is broken but why it only cause problems during games? I don't know what to do now.

 

[usasma]

Sometimes it takes several different things to fix a problem.
We often see problems like this after fixing BSOD's.

Please generate another set of reports like you did earlier. That way we can check the latest entries in the event viewer logfiles.