Multiple BSOD errors ranging from memory management to other things

[Layback Bear]

What kind of letters do you get in cmd promp now?

 

[rpegaming]

What kind of letters do you get in cmd promp now?

The English kind ...

 

[Layback Bear]

Very good.
Happy computing.

 

[rpegaming]

Crashing

Hey all. You might remember me or you might not. The last time I had this many blue screens a simple reformat worked. I haven't yet tried that since I thought there might be some hope that it might be something that isn't ram. Long story short...On my lost OS install my OS did not blue screen a single time for any reason...Right after I re-formatted the PC, it has started blue-screening non-stop for memory management and/or memory pool corruption. Due to it happening before the reformat, then not doing it at all for the OS install for a year, and then doing it again for the next install has led me to believe it's a driver issue.

I'd like to add that I do have verifier enabled, but that's because I'm fairly certain I have a driver issue..


I'm going to try uninstalling MSE. It seems like that may actually be the culprit..


So far no BSOD after removing MSE..

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]41790[/COLOR], [COLOR="SeaGreen"]fffffa8003986c40[/COLOR], [COLOR="Orange"]ffff[/COLOR], 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Usual causes:  Device driver, memory, kernel

2: kd> [COLOR="SeaGreen"]dt nt!_MMPFN fffffa8003986c40[/COLOR]
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`400003e8 _MMPTE
   +0x010 VolatilePteAddress : 0xfffff6fb`400003e8 Void
   +0x010 Lock             : 0n1073742824
   +0x010 PteLong          : 0xfffff6fb`400003e8
   +0x018 u3               : <unnamed-tag>
   +0x01c UsedPageTableEntries : [COLOR="Red"]0xffff[/COLOR]
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

It seems that the page table page has become corrupt, by a device driver causing the reference count to below drop zero. The reference count is incremented by a page is locked, and then decremented when the reference count drops below zero. So basically, a device driver has been unlocking a physical page more times than it locked the page.

2: kd> [COLOR="SeaGreen"]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`0480a000 fffff880`052ef000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Fri Jun 21 10:06:16 2013[/COLOR] (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please check you have the latest WHQL version for your nVidia graphics card driver - NVIDIA Driver Downloads - Advanced Search

Version: 320.49
Release Date for Desktops and Notebooks : July 1st 2013
In Device Manager: 9.18.13.2049

 

[rpegaming]

[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]41790[/COLOR], [COLOR="SeaGreen"]fffffa8003986c40[/COLOR], [COLOR="Orange"]ffff[/COLOR], 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Usual causes:  Device driver, memory, kernel

2: kd> [COLOR="SeaGreen"]dt nt!_MMPFN fffffa8003986c40[/COLOR]
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`400003e8 _MMPTE
   +0x010 VolatilePteAddress : 0xfffff6fb`400003e8 Void
   +0x010 Lock             : 0n1073742824
   +0x010 PteLong          : 0xfffff6fb`400003e8
   +0x018 u3               : <unnamed-tag>
   +0x01c UsedPageTableEntries : [COLOR="Red"]0xffff[/COLOR]
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

It seems that the page table page has become corrupt, by a device driver causing the reference count to below drop zero. The reference count is incremented by a page is locked, and then decremented when the reference count drops below zero. So basically, a device driver has been unlocking a physical page more times than it locked the page.

2: kd> [COLOR="SeaGreen"]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`0480a000 fffff880`052ef000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Fri Jun 21 10:06:16 2013[/COLOR] (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please check you have the latest WHQL version for your nVidia graphics card driver - NVIDIA Driver Downloads - Advanced Search

Version: 320.49
Release Date for Desktops and Notebooks : July 1st 2013
In Device Manager: 9.18.13.2049

My video drivers are up to date and I still have not had any BSOD since I removed Microsoft Security Essentials. (Before I uninstalled it I would crash every 30 minutes to 2 hours. Now I haven't crashed in 24 )

 

[x BlueRobot]

Okay that's good to know