SysWOW64\ntdll.dll Errors

[JackNaylorPE]

Looked at 100's of Yahoo search results on C:\Windows\SysWOW64\ntdll.dll errors with no luck. Happened 3 times while idle and afk in last 2 days

Win7-64, Clevo 170EM / Sager NP9170 Lappie, i7-3720QM, GTX 675M, 16 GB, Seagate Momentus 750 GB)


Log Name: Application
Source: Application Error
Date: 8/30/2012 10:35:32 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Beta
Description:
Faulting application name: client_ryzom_rd.exe, version: 0.0.0.0, time stamp: 0x4f4bd16f
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000005
Fault offset: 0x0002f367
Faulting process id: 0x1e88
Faulting application start time: 0x01cd86ff460435d2
Faulting application path: E:\Ryzom\client_ryzom_rd.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 88e75dbc-f314-11e1-ae76-0090f5d1aa1f
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-08-31T02:35:32.000000000Z" />
<EventRecordID>3653</EventRecordID>
<Channel>Application</Channel>
<Computer>Beta</Computer>
<Security />
</System>
<EventData>
<Data>client_ryzom_rd.exe</Data>
<Data>0.0.0.0</Data>
<Data>4f4bd16f</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec49b8f</Data>
<Data>c0000005</Data>
<Data>0002f367</Data>
<Data>1e88</Data>
<Data>01cd86ff460435d2</Data>
<Data>E:\Ryzom\client_ryzom_rd.exe</Data>
<Data>C:\Windows\SysWOW64\ntdll.dll</Data>
<Data>88e75dbc-f314-11e1-ae76-0090f5d1aa1f</Data>
</EventData>
</Event>

 

[Arc]

Hello, can you post it following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html ?

 

[JackNaylorPE]

I tried that Arc but your diagnostic tool leaves nothing on the desktop. Also C:\Users\name\Desktop has nothing in it. And , yes,program was run as administrator

I copied the files individually and assembled my own zip \file

 

[Arc]

Download and install |MG| Driver Fusion (Driver Sweeper) 1.1.1 Download.

Reboot the computer in http://www.sevenforums.com/tutorials/666-advanced-boot-options.html, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.

Boot normally now. Go to Drivers - Download NVIDIA Drivers, follow option two to search for the appropriate driver for your system automatically, and install it.

Let us know how it worked.

 

[JackNaylorPE]

Using laptop manufacturers latest driver which advises use of only manufacturer certified drivers on their web site.

 

[Anthony]

Why have you got your refresh rate set to 119Hz? Maximum resolution for your monitor is:1920 x 1200 at 60 Hz

Assuming this is your monitor in your System Specs: Documentation

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 406f8, fffff8800feac3b8}

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
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red][B]Probably caused by : nvlddmkm.sys[/B][/COLOR] ( nvlddmkm+2ab3b8 )

Driver Reference Table - nvlddmkm.sys

That is why you are to remove it, and then replace it as properly installed. Ultimate decision is your own.

 

[JackNaylorPE]

Why have you got your refresh rate set to 119Hz? Maximum resolution for your monitor is:1920 x 1200 at 60 Hz

According to Control panel, HD Graphics Adapter is set at 60 Hz. nVida Control panel offers no option to chnage.

 

[Anthony]

OK, Its just that it shows it at 119Hz in MSINFO32.

 

[JackNaylorPE]

Boot normally now. Go to Drivers - Download NVIDIA Drivers, follow option two to search for the appropriate driver for your system automatically, and install it. Let us know how it worked.

Well .... using the method described, there is no driver for the 675M. Doing it manually, I selected the beta option and found 3 beta alternatives, latest one being 306.02 dated August 27. We'll see how it goes.

 

[JackNaylorPE]

Ok....well got a few hours before another crash.

1. Any idea why diagnostic tool not creating desktop folders ?

2. Any suggestion on which oif those files I should be examining and for what ?

 

[Arc]

Still it is nVidia display driver.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 406f8, fffff8800fe0e541}

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
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red][B]Probably caused by : nvlddmkm.sys[/B][/COLOR] ( nvlddmkm+20b541 )

 

[JackNaylorPE]

Yes, it's a given that nvlddmkm.sys isa the problem. What I struggling with is solving it. Uninstalled all things nVidia through control panel, ran Driversweeper in safe mode 10 times and it still leaves a bunch of reg settings. Turned off automatic installs of devices and drivers using gpedit.msc and ran several more times. Afterwards, these reg settings still remain:

True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemDrive%\Program Files\NVIDIA Corporation\Drs\dbInstaller.exe
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemDrive%\Program Files\NVIDIA Corporation\Drs\nvdrsdb.bin
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\DRIVERS\nvlddmkm.sys
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvapi64.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvcompiler.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvcuda.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvcuvenc.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvcuvid.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvd3dumx.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvdecodemft.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvinfo.pb
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvoglv64.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\system32\nvwgf2umx.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\SysWow64\nvapi.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\SysWow64\nvcompiler.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\SysWow64\nvcuda.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\SysWow64\nvcuvenc.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\SysWow64\nvcuvid.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\SysWow64\nvd3dum.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\SysWow64\nvdecodemft.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\SysWow64\nvoglv32.dll
True NVIDIA Display Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemPath%\SysWow64\nvwgf2um.dll


Latest files attached

 

[Arc]

Just the same, essentially identical crash reports.

You boot in http://www.sevenforums.com/tutorials/666-advanced-boot-options.html, go to safe mode (without networking), and then use driver sweeper to remove the driver again.

As a workaround suggestion, you may use your onboard graphics temporarily.

And, have you taken this test already? http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html?

 

[JackNaylorPE]

That last crash was full blown blue screen, not the usual game crash.

You boot in http://www.sevenforums.com/tutorials/666-advanced-boot-options.html, go to safe mode (without networking), and then use driver sweeper to remove the driver again.

That's exactly what I did.....about 20 times. Seems to me something is locking down those reg entries.

As a workaround suggestion, you may use your onboard graphics temporarily.

And, have you taken this test already? http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html?

I ran OCCT but there's a detection thing going on that throttles it. Gonna try kombustor later today.

As a workaround suggestion, you may use your onboard graphics temporarily.

Did that after last post, left lappie in game overnight, crashed before morning. was not video related.

One more question: Driver Sweeper lists categories for nVidia Chipset, nVidia Display and nVidia PhysX. Reinstalling nVidia driver did not restore video chipset section.

Edit 1: Ran Furmark for an hour ..... cut core speed to 520 (from 620) to keep heat below 82. No issues. Also ran memtest86+ thru one pass, no errors. Granted too short to draw conclusions, but hadda get some work done. Will run memtest overnight tonight and Furmark the next.

Still very perplexed as to why PnpLockdownFiles are not being removed w/ Driversweeper.

Edit 2: Ran memtest overnight, (about 9 hours) completed 4 passes, no errors

Edit 3: Ran Furmark full tilt at full core speed for 4 hours. No issues. Ran again on extreme burn..... held solid with 3-4 minutes of bouncing back between 88 and 89C, then hit 90C which is where I had set the alarm and I ended test.

 

[JackNaylorPE]

2 days of effort .... no progress. Anyone have any suggestions on downloadable game benchmarks / demos that I might loop to see if the problem is unique to this one application.

 

[FredeGail]

I'm just going to make you jump into the big thing -- driver verifier.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.

 

[JackNaylorPE]

I can't afford to have this system down atm. I get to "play" on it but it is my primary means of contact when I'm "on call".