SysWOW64\ntdll.dll Errors

Still it is nVidia display driver.

Code:

*******************************************************************************
*                                                                             *
*                        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
Probably caused by : nvlddmkm.sys ( nvlddmkm+20b541 )

Just the same, essentially identical crash reports.

You boot in Advanced Boot Options, 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? Video Card - Stress Test with Furmark?

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

Arc said:

You boot in Advanced Boot Options, 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? Video Card - Stress Test with Furmark?

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.

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:

Code:

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.