Windows 7 64bit when run updates get BSOD

[lleemon]

Was running XP Pro and then Server 2003 on this pc, got a Windows 7 Pro OEM, intalled and when I try to run updates it keeps throwing MEMORY_MANAGEMENT BSOD.

1) Ran https://www.sysnative.com/apps/SysnativeBSODCollectionApp.exe
Got a few message box that said something like the following:
C:\Windows\SysWow64\nvgf2um.dll is neither not designed to run on Windows or it contains an error.
C:\Windows\SysWow64\nvd3dum.dll is neither not designed to run on Windows or it contains an error.

2) Attached zip


Any ideas I am open. Thanks.


SPECS
· OS - Windows 7
· x64 (64-bit)
· What was original installed OS on system? Windows XP Pro
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Probably OEM XP
· Age of system (hardware): 2008
· Age of OS installation - have you re-installed the OS? Just bought Windows 7

· CPU: Intel Core 2 Quad Q6600 Processor BX80562Q6600 - 2.40GHz, 8MB Cache, 1066MHz FSB, Kentsfield, Quad-Core, Retail, Socket 775, Processor with Fan
· Video Card: XFX GeForce 8600 GT Video Card - 512MB DDR2, PCI Express, SLI Ready, (Dual Link) DVI, VGA, HDTV, Video Card
· MotherBoard - XFX nForce 680i LT SLI Motherboard, NVIDIA, Socket 775, ATX, Audio, PCI Express, SLI Ready, Gigabit LAN, S/PDIF, USB 2.0 & Firewire, Serial ATA, RAID
· Power Supply - Ultra / X-Finity / 600-Watt / ATX / 135mm Fan / SATA-Ready / SLI-Ready / Black / APFC / Energy Efficient Power Supply
Memory: OCZ SLI-Ready Edition Dual Channel 2048MB PC6400 DDR2 800MHz Memory (2 x 1024MB)

· System Manufacturer: XFX
· Exact model number: nForce 680i LT

· Laptop or Desktop: Desktop

 

[Patrick]

0: kd> .bugcheck
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`0103dd90 00000000`0000ffff 00000000`00000000

0: kd> dt nt!_MMPFN fffffa800103dd90
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`40002110 _MMPTE
   +0x010 VolatilePteAddress : 0xfffff6fb`40002110 Void
   +0x010 Lock             : 0n1073750288
   +0x010 PteLong          : 0xfffff6fb`40002110
   +0x018 u3               : <unnamed-tag>
   +0x01c UsedPageTableEntries : 0xffff
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

Looking at the pointer regarding the PTEs, we can see the # of used page table entries fell below zero. With that said, especially given your recent upgrade from XP > 7, you probably have a driver on your system causing this problem that's outdated/buggy from the XP days.

Let's enable verifier and see what's causing it:

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

- Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

Any other questions can most likely be answered by this article:

Using Driver Verifier to identify issues with Windows drivers for advanced users