New
#11
Windows tracks physical pages of memory using a table called the Page Frame Database. This database (which actually is just a big one-dimensional array) is indexed by physical page number. As a result, the page frame database is typically referred to as the Page Frame Number list or PFN. This ususaly accours for one ot two reasons, the first is being memory corruption. If their is a buggy driver in the system that is writing on memory that it doesn't own it could easily corrupt one of it's PFN lists or entires. So as suggested all ready try removing the nvida driver as explained and then reinatall it. Or you could just let windows install a driver and see if the issue still appears. Bad pool lits or header. Once again a driver issue. Just a thought you said you ran memtest have you tried it with one stick in at a time? Also try just using 1 stick after doing the driver reinastall. I would also like to have a look at what CPU-z lists as your memory and timings. Could you Copy and Paste screen shots of it on both sticks? CPUID Thanks. Fabe