PFN_LIST_CORRUPT (0x4E)
If the first parameter is a 1:
1 - 1
2 - ListHead value which was corrupt
3 - number of pages available
4 - 0
If the first parameter is a 2:
1 - value 2
2 - entry in list being removed
3 - highest physical page number
4 - reference count of entry being removed
-----Original Message-----
From: Jaiswal, Niraj [mailto:xxxxx@netapp.com]
Sent: Monday, February 26, 2001 12:49 PM
To: NT Developers Interest List
Subject: [ntdev] RE: [NTDev] Bugcheck codes 0x4E not documented
It’s documented as PFN_LIST_CORRUPT. This is a Win2K Executive
character-mode STOP message. It indicates the memory management
page file number (PFN) list is corrupted.
http://www.microsoft.com/WINDOWS2000/en/messages/5224.htm
Niraj
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Monday, February 26, 2001 10:03 AM
To: NT Developers Interest List
Subject: [ntdev] [NTDev] Bugcheck codes 0x4E not documented
Anyone have any information on this bugcheck code? The WiDbg docs do not
document it?
*** Fatal System Error: 0x0000004e
(0x00000007,0x00000000,0x00000001,0x00000000)
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com
You are currently subscribed to ntdev as: xxxxx@netapp.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com