BSOD after changing from 4GB to 8GB SODIMM RAM

Please follow - Blue Screen of Death (BSOD) Posting Instructions

I have edited the post so it now complys with the posting instructions.

:)

Code:

BugCheck 1A, {41790, fffffa80018ed6f0, ffff, 0}

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

Code:

Usual causes:  Device driver, memory, kernel

It appears that the page table is corrupt, this is used to store the mappings between virtual and physical memory addresses. Furthermore, we can see that the reference count for the number of PTE's has dropped below zero, when a PFN is locked against a virtual address range, then the reference count is incremented, although, when a PFN is unlocked then the reference count is decremented. A device driver has been unlocking physical pages more often than locking the physical pages, thus causing the reference count to below zero.

Code:

kd> dt nt!_MMPFN fffffa80018ed6f0
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`40001d58 _MMPTE <-- PTE linked to current PFN
   +0x010 VolatilePteAddress : 0xfffff6fb`40001d58 Void
   +0x010 Lock             : 0n1073749336
   +0x010 PteLong          : 0xfffff6fb`40001d58
   +0x018 u3               : <unnamed-tag>
   +0x01c UsedPageTableEntries : 0xffff
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

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

From another (Stop 0x24) bugcheck,

Code:

kd> lmvm athrx
start             end                 module name
fffff880`06c2d000 fffff880`06ffc000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Fri Nov 23 04:51:22 2012 (50AF00CA)
    CheckSum:         003B74A3
    ImageSize:        003CF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update your Atheros driver either from your motherboard support page, or check the Device Manager for the model number of your network adapter and then update from the Atheros website - ATHEROS drivers for Microsoft Windows (Atheros?????)

Remove:

Code:

Start Menu\Programs\DAEMON Tools Lite

Arc said:

Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Daemon Tools uses a driver called sptd.sys, which is known to cause BSODs with Windows 7. It is recommend you remove this program, and use Windows own in-built features or ImgBurn.

Upon running driver verifier, I got a bluescreen at startup stating that usbfilter.sys, a driver from AMD, has been trying to use memory after it has been freed.

What should I do?

Look for an updated driver on AMD's website, or just uninstall it.

Thanks for the help so far.
:)

New Dump Files:

Code:

BugCheck D5, {fffff98007dc0df0, 0, fffff88004e961aa, 0}

*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys

Could not read faulting driver name
Probably caused by : usbfilter.sys ( usbfilter+41aa )

Code:

Usual causes:  Device driver

The above driver has referenced a memory address which was already freed, and then produced a page fault.

Code:

TRAP_FRAME:  fffff88002f89280 -- (.trap 0xfffff88002f89280)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88002f89478
rdx=fffff98007dc0dc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004e961aa rsp=fffff88002f89410 rbp=0000000000000002
 r8=0000000000000000  r9=fffff88004e961a5 r10=0000000000000100
r11=fffff8000300ae80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbfilter+0x41aa:
fffff880`04e961aa 8b4230          mov     eax,dword ptr [rdx+30h] ds:fffff980`07dc0df0=????????

Code:

kd> lmvm usbfilter
start             end                 module name
fffff880`04e92000 fffff880`04e9f000   usbfilter T (no symbols)           
    Loaded symbol image file: usbfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\usbfilter.sys
    Image name: usbfilter.sys
    Timestamp:        Tue Dec 22 08:26:22 2009 (4B3082AE)
    CheckSum:         0000DFD8
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your AMD USB Filter driver seems to be causing the problem, and is part of your chipset, please update your chipset driver from your motherboard support page or from here - Support & Drivers

Ok now there is another problem,

while using my computer tonight I had another BSOD that said that ntfs.sys had an error because
it had a "PAGE FAULT IN NON-PAGED AREA".

I have attached the new dump files.
Also keep in mind that I was using driver verifier to check if there was any other issues with faulty drivers.

Thanks :)