Reinstalled windows to pc - pfn list corrupt

By the_gas
Aug 18, 2007
Topic Status:
Not open for further replies.
  1. Nothing overclocked, all drivers are the latest. Can someone look at these dumps and tell me which driver, if any is causing this, pc is just a month or too old.

    Attached Files:

  2. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,202

    The thread on the other forum that I told you about now looks to be resolved. There hasn't been a crash in the nine days since Panda was uninstalled. As you can see below, one of yours has crashed at a Panda file.

    http://www.windowsbbs.com/showthread.php?t=66132

    BugCheck 4E, {99, 0, 0, 0}
    Probably caused by : memory_corruption ( nt!MiDecrementShareCount+3a ) <-- 3 of these.

    STACK_TEXT:
    ac94eb00 805220a8 0000004e 00000099 0002ce51 nt!KeBugCheckEx+0x1b
    ac94eb30 80522e47 02c11000 c06000b0 c0016088 nt!MiDecrementShareCount+0x3a
    ac94eb60 805232fb c06000b0 c0016000 00000000 nt!MiDeletePte+0x1d9
    ac94ec28 805128fc 00000008 02c10fff 00000000 nt!MiDeleteVirtualAddresses+0x1db
    ac94ec68 805d0f8d 01170380 84e22bb0 40010004 nt!MmCleanProcessAddressSpace+0x262
    ac94ecf0 805d1071 40010004 ac94ed4c 804fee65 nt!PspExitThread+0x621
    ac94ecfc 804fee65 84e22bb0 ac94ed48 ac94ed3c nt!PsExitSpecialApc+0x23
    ac94ed4c 805408d7 00000001 00000000 ac94ed64 nt!KiDeliverApc+0x1af
    ac94ed4c 7c90eb94 00000001 00000000 ac94ed64 nt!KiServiceExit+0x59
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    02a6ec70 00000000 00000000 00000000 00000000 0x7c90eb94

    BugCheck 4E, {99, 17ba2, 3, 0}
    Probably caused by : PavProc.sys ( PavProc+14d4 ) <-- Panda.
  3. the_gas

    the_gas Newcomer, in training Topic Starter Posts: 66

    Ok thanks, i do have windows debugger but when i opened one of the above dumps it said this below. I opened up 3 of the dump files i posted above.

    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt+22deb )

    Followup: MachineOwner



    However, you may well be right, as panda is installed on that system, but i just want to double check, as i paid for panda so would ideally like to use it.


    EDIT, peter, i just read that link, thanks for that i hope it will solve the problems. Cheers Bud!
  4. the_gas

    the_gas Newcomer, in training Topic Starter Posts: 66

    Wow, i uninstalled Panda 2007 and the problems went away. I am now using the 2008 version of panda, after they game me an upgrade and no more BSOD's. My 3 month long battle with pfn list courrupt on two pc's is now over. thanks Peter!
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.