MSDN verrät dazu folgendes:
Bug Check 0x4E: PFN_LIST_CORRUPT
The PFN_LIST_CORRUPT bug check has a value of 0x0000004E. This indicates that the page frame number (PFN) list is corrupted.
Parameters
The following parameters are displayed on the blue screen. Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of Parameter 1.
Parameter 1 Parameter 2 Parameter 3 Parameter 4 Cause of Error
0x01 The ListHead value that was corrupted The number of pages available 0 The list head was corrupt.
0x02 The entry in the list that is being removed The highest physical page number The reference count of the entry being removed A list entry was corrupt.
0x07 The page frame number The current share count 0 A driver has unlocked a certain page more times than it locked it.
0x8F New page number Old page number 0 The free or zeroed page listhead is corrupt.
0x99 Page frame number Current page state 0 A page table entry (PTE) or PFN is corrupt.
0x9A Page frame number Current page state The reference count of the entry that is being removed A driver attempted to free a page that is still locked for IO.
Cause
This error is typically caused by a driver passing a bad memory descriptor list. For example, the driver might have called MmUnlockPages twice with the same list.
If a kernel debugger is available, examine the stack trace.
Es handelt sich auf jeden Fall um einen Fehler im Speicher! Daher liegt die Annahme nahe, dass dein Speicher defekt ist, da der Fehler ja erst nach dem Speicherwechsel aufgtreten ist!
Was ich dir auf jeden Fall noch empfehle: Lade die ein Bootbares Image von Memtest runter, und lass das Programm ein paar durchläufe testen!
http://www.computerbase.de/downloads/so ... memtest86/