pfn_list_corrupt and memory_management

venax

Well-Known Member
#1
Hello
I i m new on this forum, thanks in advance to anyone who is reading this ...
as the title say my problem is with pfn_list_corrupt and memory_management have already reinstalled windows thinking that was something bad with filesystem , but I still have this problem! Then i thought rams were broken , but after 8 hours i got 0 errors. And they are random , if i m play bsod , if the pc is idle BSOD ..
My pc
i7 2600k
ud4 z68
8 gb corsair vengeance
gtx 470
cooler master m520
View attachment 18671


sorry for my english!
 


Trouble

Noob Whisperer
#2
Hello and welcome to the forum.
Code:
BugCheck 4E, {99, 115842, 0, 134442}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
PFN_LIST_CORRUPT (4e)
[COLOR=#ff0000][U][B]Typically caused by drivers passing bad memory descriptor lists[/B][/U][/COLOR] (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000115842, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000134442, 0
Start by addressing an issue with this driver
RTCore64.sys 5/25/2005 (known issues with Windows 7) usually associated with RivaTuner but may also be EVGA Precision or MSI Afterburner and possibly a couple other software packages. Either update, or uninstall or as a last resort search for and rename RTCore64.sys to RTCore64.OLD (probably here C:\Windows\System32\Drivers but may also be elsewhere).
After resolving the driver issue above, if Blue Screens persist;
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Then:
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area http://windows7forums.com/windows-7...you-filling-your-system-specs.html#post235529 .
Good luck
Randy
 


venax

Well-Known Member
#3
after i renamed rtcore64.sys (it s in the msi afterburner folder ) doesn t work anymore . will i have to make this compromise or is there another way to fix it? because i realy need msi afterburner ...

THANKS for your answer !
 


Trouble

Noob Whisperer
#4
Not sure exactly, have you checked for a newer more recent version of that particular software? It may perhaps no longer include that particular driver or maybe has a more recent version of that driver that doesn't cause the problem.
The real question is..... have your BSODs stopped?

EDIT: http://event.msi.com/vga/afterburner/download.htm not sure if this is what you need or not??

EDIT AGAIN: Just downloaded and extracted the latest beta version 220Beta12.zip and the version of RTCore64.sys contained in that looks like it has a date of 2/1/2012. You might give that a try and see what happens. I can't say for sure personally because I don't use it.
Regards
Randy
 


Last edited:

venax

Well-Known Member
#5
well the version that i have it s not the beta and rtcore64.sys has a date of 27/05/2010...

no, after i renamed that file after 15 minutes i got a bsod..
 


Trouble

Noob Whisperer
#6
The version that is listed in all your dump files is dated May 25th 2005. So you need to continue searching for it
C:\Windows\System32\Drivers
and
C:\Windows\SysWOW64\Drivers
and anywhere else it may be and consider renaming all instances and replacing with the latest version.
And attach you latest dump files as they are created and go back to here http://windows7forums.com/blue-scre...ist_corrupt-memory_management.html#post252825 and follow up on adding the additional files as recommended.
 


venax

Well-Known Member
#8
View attachment 18678 Something strange that i noticed: yesterday while the pc was turning off i got a bsod , and this is not the first time that happens when i m turning off i will post the bsod later
 


Last edited:

Trouble

Noob Whisperer
#9
Another
(LATEST DUMP FILE)
Code:
BugCheck 4E, {99, 159ca1, 3, 1998ff}

[COLOR=#ff0000][U][B]Probably caused by : memory_corruption[/B][/U][/COLOR] ( nt!MiBadShareCount+4c )
[COLOR=#ff0000][U][B]PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists[/B][/U][/COLOR] (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000159ca1, page frame number
Arg3: 0000000000000003, current page state
Arg4: 00000000001998ff, 0
BUGCHECK_STR:  0x4E_99
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80003160d7c to fffff800030d7c40
STACK_TEXT:  
fffff880`0742c088 fffff800`03160d7c : 00000000`0000004e 00000000`00000099 00000000`00159ca1 00000000`00000003 : nt!KeBugCheckEx
fffff880`0742c090 fffff800`0307f9ef : 00000000`00000000 fffffa80`0382ce00 0000000f`ffffffff fffff800`0325bc80 : nt!MiBadShareCount+0x4c
fffff880`0742c0d0 fffff800`030cd671 : eae00001`00000000 fffff680`00041d70 00000000`00000200 000fffff`00000001 : nt! ?? ::FNODOBFM::`string'+0x336da
fffff880`0742c150 fffff800`030c4e62 : fffff800`03260900 fffffa80`00000000 fffffa80`092b6060 fffffa80`092b63f8 : nt!MiDecommitPages+0x1a1
fffff880`0742c9e0 fffff800`030d6ed3 : ffffffff`ffffffff 00000000`019be4f8 00000000`019be4f0 80000000`00004000 : nt!NtFreeVirtualMemory+0x382
fffff880`0742cae0 00000000`779a14fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`019be478 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779a14fa
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`03160d7c cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!MiBadShareCount+4c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
I know you have already said that you have tested your memory but you did not say how you went about it so.....
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+
Additionally launch an elevated command prompt and type
chkdsk C: /R
hit enter
answer yes "Y" when prompted
Let it finish all five stages and see what that produces.
AND see if you can obtain a vendor specific proprietary hard disk testing utility from your drive manufacturer and use that to test your hard disk as well. A partial list here http://www.carrona.org/hddiag.html
Your current memory settings look good except for the command rate which is presently set at 1T and I would expect to see 2T. You can either use your System BIOS to set your timings manually or you can try enabling XMP (eXtreme Memory Profile) in your system's BIOS and see if the makes the requisite adjustments automatically.
Go here GIGABYTE - Motherboard - Socket 1155 - GA-Z68X-UD4-B3 (rev. 1.0) and download and install the latest driver for your Etron USB 3.0 Driver (version 105).
 


Last edited:

venax

Well-Known Member
#10
YEAH i forgot to say how i tested the rams. I already did 8 hours of memtest and as i said 0 errrors ... i ll try with only one stick individually.

my primary disk is an Intel SSD and it s OK. Could the problem be in the secondary HDD?
 


Trouble

Noob Whisperer
#12
Are you using an external device (like a USB thumb drive) as a readyboost device?
Code:
BugCheck 1A, {1236, fffffa8008d61d00, fffffa8008d61d50, 1cb9a5}
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000001236, The subtype of the bugcheck.
Arg2: fffffa8008d61d00
Arg3: fffffa8008d61d50
Arg4: 00000000001cb9a5
BUGCHECK_STR:  0x1a_1236
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80003181dab to fffff8000308ec40
STACK_TEXT:  
fffff880`03b70978 fffff800`03181dab : 00000000`0000001a 00000000`00001236 fffffa80`08d61d00 fffffa80`08d61d50 : nt!KeBugCheckEx
fffff880`03b70980 fffff880`0195deb2 : 00000000`000009be fffffa80`08d61d00 fffffa80`07760118 00000000`000009bf : nt!MmFreePagesFromMdl+0x31b
fffff880`03b709e0 fffff880`0195d7df : fffffa80`07760118 00000000`00000000 fffffa80`07801ef0 00000000`00000000 : rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+0x4e
fffff880`03b70a40 fffff880`0195c4ce : fffffa80`077600b0 00000000`00000001 fffffa80`077600b0 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCleanup+0x183
fffff880`03b70a80 fffff880`0195ba27 : fffffa80`077600b0 00000000`00000001 fffffa80`077600b0 fffff800`0322f2b8 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStCleanup+0x7a
fffff880`03b70ac0 fffff880`0195b98a : fffff880`0197e8f0 00000000`00000008 fffffa80`077600b0 fffff880`0197e870 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmStoreMgrCallback+0x4b
fffff880`03b70b00 fffff880`019824b8 : fffff880`0197e870 fffff800`0322f2b8 00000000`00000000 00000000`00000001 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmCleanup+0x9a
fffff880`03b70b30 fffff800`03099001 : fffff880`019824ec fffffa80`06705b60 00000000`00000000 00000000`0000055a : rdyboost!SmdRBContextShutdown+0x94
fffff880`03b70b70 fffff800`03329fee : 00000000`00000000 fffffa80`06705b60 00000000`00000080 fffffa80`066ecb30 : nt!ExpWorkerThread+0x111
fffff880`03b70c00 fffff800`030805e6 : fffff880`03974180 fffffa80`06705b60 fffff880`0397f0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b70c40 00000000`00000000 : fffff880`03b71000 fffff880`03b6b000 fffff880`03b707d0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  kb
FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e
fffff880`0195deb2 33d2            xor     edx,edx
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: rdyboost
IMAGE_NAME:  rdyboost.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7982e
FAILURE_BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e
BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e
 


venax

Well-Known Member
#13
no i m not using it ... if i plug an usb thumb drive i can t even activate readyboost
 


Trouble

Noob Whisperer
#14
Rapidly running out of ideas here.
Do me a favor and remove (uninstall) Kaspersky completely. Use the programs and features applet in the control panel and then follow that up with the vendor specific proprietary removal tool from here Removal tool for Kaspersky Lab products
Kaspersky is one of, if not my all time favorite AV / MW solution but it is possible that there is an issue with its' present state or condition that may be causing the issue. This is just temporary and you can either temporarily replace it with Microsoft Security Essentials or re-install it after a complete cleanup of all remnants, but I would really like to see if Blue Screens continue without it on the machine. Up to you
Regards
Randy
 


venax

Well-Known Member
#15
WOOOOOOOOOOOOOOW NO MORE BSOD AFTER 3 DAYS! i didn t remove kaspersky, thanks for your advice and your time who helped me to solve this problem
 


venax

Well-Known Member
#16
View attachment 18839

NOOOO i spoke too soon :((((( another BSOD today , i will unistal kaspersky too
 


Trouble

Noob Whisperer
#17
View attachment 18839

NOOOO i spoke too soon :((((( another BSOD today , i will unistal kaspersky too
Actually I kinda expected as much when you posted that your problem was magically cured without saying what you had done to resolve it.
So since your latest BSOD happened when playing BF3, I'll refer you back to a post I made earlier
Your current memory settings look good except for the command rate which is presently set at 1T and I would expect to see 2T. You can either use your System BIOS to set your timings manually or you can try enabling XMP (eXtreme Memory Profile) in your system's BIOS and see if the makes the requisite adjustments automatically.
See if that adjusts your memory's command rate to 2T and also you should probably consider disabling EIST (Enhanced Intel Speedstep Technology) and see if that helps resolve the issue.
 


venax

Well-Known Member
#18
yeah you right...

I already enabled XMP and I manually configured the timings
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.