Avkaya Posted March 10, 2011 Report Share Posted March 10, 2011 (edited) Hello everyone, First of all, I'm sorry if I'm doing it wrong by posting a new topic about this annoying error. I think nearly all of you should have heard/read about this. 3 or 4 days ago, while doing the same things as I was doing before. I got a BSOD about nvlddmkm.sys and system rebooted itself. I didn't do any updates, software or hardware change/modification. I just bought a new laptop stand-cooler but it was 2 days before the error, and installed ie9 3 days before (I mean there's nothing related to error I got.) I tried almost everything. I read tens of sites, forums, discussions, and I know that there's no specific reason or solution to nvlddmkm.sys error. Thats why I registered here. I don't want to send my laptop to service because I know that it's going to take at least 2 weeks, and I dont want to surrender. I tried newest driver from nvidia's official site, 258.96 from here and so on. What's weird is that when I disable or uninstall my video driver, I have no errors. But no matter which I install, every driver gives me error. First 2 days, I got many BSOD's. Then, it decreased but started to freeze when I move my laptop. For example, I use my pc very well on the table, I get tired and take it on the sofa, freeze. If there's a sound playing at that moment, it turns into an annoying loop of half a second. But if driver is disabled or uninstalled, no matter how hard I shake my pc (yes, I shook it) there's no freeze or BSOD. Today, I cleaned all the dust out of my pc, and I use cooler, so its nothing about heating also. I took this report with bluescreenview if it helps you to understand what the problem is:mavi ekran hatası.txt Again, I apologize if I'm doing anything wrong. And there may be some grammatical errors also. Just tell me what to do, I really don't use forums and I dont know much. Thank you in advance. Edited March 10, 2011 by Avkaya Quote Link to comment Share on other sites More sharing options...
Guest _NowakP Posted April 20, 2011 Report Share Posted April 20, 2011 Hello, recently I bought an Acer 5750G laptop with i3-2310M 2.1GHz CPU and GeForce GT540m GPU. Anytime I want to play games like Lineage 2 or League Of Legends, I get a BSOD after some time. Sometimes when I restart and launch the game afterwards I just get about 2 minutes of gameplay before the next BSOD. I've tried many different drivers starting with the original Acer ones and ending on 270.61 . Always ended the same way with a BSOD. The 'nvlddmkm.sys' file seems to be responsible. I've looked through a bunch of minidump files and they all seem to be the same: Loading Dump File [C:\Windows\Minidump\041811-17971-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 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50 Debug session time: Mon Apr 18 15:18:15.159 2011 (UTC + 2:00) System Uptime: 0 days 3:24:21.579 ********************************************************************* * 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 0n2 *** 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 0n2 *** 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, {fffffa80048654e0, fffff880106bb070, ffffffffc000009a, 4} *** WARNING: Unable to verify timestamp for mssmbios.sys *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys ***** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : nvlddmkm.sys ( nvlddmkm+7e2070 ) Followup: MachineOwner --------- Is there any fix for this? Is there any fix for this? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.