BSOD after updating Nvidia drivers

Ok, I ran verifier all day yesterday and had no crashes, however today I got another memory_management crash whilst playing GW2 (verifier was DISABLED).
Minidump attached. I might run verifier again and leave it on for longer.

Code:

BugCheck 1A, {403, fffff68000503998, 9720000027a2b867, fffff68000503898}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3211c )

Code:

2: kd> !thread
GetPointerFromAddress: unable to read from fffff8000dcb8000
THREAD fffffa8006aa7060  Cid 1120.05dc  Teb: 00000000fff86000 Win32Thread: fffff900c2027ab0 RUNNING on processor 2
IRP List:
    Unable to read nt!_IRP @ fffffa800af1b7b0
Not impersonating
GetUlongFromAddress: unable to read from fffff8000dbf7ba4
Owning Process            fffffa800b36f060       Image:         Gw2.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      851285       
Context Switch Count      5961553        IdealProcessor: 0                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x0000000000941823
Stack Init fffff88003dc5c70 Current fffff88003dc57c0
Base fffff88003dc6000 Limit fffff88003dbd000 Call 0
Priority 11 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5

Report back on the findings of Driver Verifier, we may need a Kernel Memory dump.

I've run driver verifier all day and have had no problems. Is there a way to tell if it is running?

When opening it again and checking "Display information about currently verified drivers", all of them are loaded apart from nvbridge.kmd which is "Never Loaded".

This has the description "NVIDIA Compatible Windows Vista ..." (can't see the rest), when I go into "Display existing settings".

Hope this information can be of some use.

To see if Driver Verifier is running, then open a elevated command prompt, and then type this command:

Code:

verifier /query

Also, we may now need a Kernel Memory dump instead, we will retain all the Kernel Mode address space at the time of the crash. Upload the file to a file sharing service such as Skydrive and Dropbox (both which provide free space), and then ensure you upload the file to the Public folder of your account. Once completed, then post the URL of the file in your next post.

Ok, it looks as though I already have it set up by default to produce a kernal memory dump. I assume I should just wait until I blue screen again and then grab the file?

Yes, when a another BSOD happens, then follow the above procedure, by default, it should be saved here:

Code:

C:\Windows\MEMORY.DMP

Is there any at the moment?

Code:

BugCheck 4E, {99, 27a2b, 2, 2af02}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Code:

Usual causes:  Device driver, memory

Code:

2: kd> !pfn 27a2b
    PFN 00027A2B at address FFFFFA800076E810
    flink       00177F05  blink / share count 0002AF02  pteaddress FFFFF8A011053569
    reference count 0000    used entry count  0000      Cached    color 0   Priority 5
    restore pte FA800B46C1B004C0  containing page        1C4EDD  Standby     P      
      Shared

The reference count is not below zero, therefore I believe the problem is not a result of incorrect MDL handling. The physical page, seems can be shared between multiple processes if I'm correct, and is currently located on the Standby list which is allowed. The reason for the crash, could be drivers referencing memory addresses which they do not own.

Code:

2: kd> !pte FFFFF8A011053569
                                           VA fffff8a011053569
PXE at FFFFF6FB7DBEDF88    PPE at FFFFF6FB7DBF1400    PDE at FFFFF6FB7E280440    PTE at FFFFF6FC50088298
contains 000000020FD84863  contains 000000000EDEF863  contains 00000001C2C04863  contains ADA00001C4EDD963
pfn 20fd84    ---DA--KWEV  pfn edef      ---DA--KWEV  pfn 1c2c04    ---DA--KWEV  pfn 1c4edd   -G-DA--KW-V

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

I understand we have ran Driver Verifier before, but this time enable the previous settings with the addition of the Special Pool setting. This is important, because it changes how Windows allocates pages to processes and drivers, each driver is given it's own page of memory instead of having a page shared among different drivers. This setting will be more memory intensive.

Code:

2: kd> !poolval FFFFFA800076E810
Pool page fffffa800076e810 region is Unknown

Validating Pool headers for pool page: fffffa800076e810

Pool page [ fffffa800076e000 ] is __inVALID.

Analyzing linked list...
[ fffffa800076e000 ]: invalid previous size [ 0x2a ] should be [ 0x0 ]
[ fffffa800076e000 --> fffffa800076e500 (size = 0x500 bytes)]: Corrupt region


Scanning for single bit errors...

None found