BOSD 0x4E PFN_LIST_CORTUPT (mainly while booting)

Page 1 of 4 123 ... LastLast

  1. Posts : 44
    Windows 7 Professional x64
       #1

    BOSD 0x4E PFN_LIST_CORRUPT (mainly while booting)


    Hello (again) Guys,

    recently my PC started to give me the above mentioned BSOD 0x4E. It mainly happens while booting ~during the part where the lightballs start to form the Windows 7 Logo. One time it happend shortly after I got into Windows and today for the first time after the PC was running for a while.

    I'll run Memtest84+ tonight and see if I get errors. Already did chkdsk and sfc with no errors.

    Basic System Infos:

    OS: Windows 7 Prof x64 retail (University Licence)
    Age: System was bought around January/February so Hardware and OS are from that time.

    Motherbord: ASUS P7P55D Rev 1
    CPU: Intel Core i5 760
    RAM: G.Skill F3-12800CL9-2GBNQ 4gig
    GPU: Nvidia GeForce GTX 460
    HDD: 500gig Samsung HD501LJ (the only old component in the system its ~4y old)
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Tenhi said:
    Hello (again) Guys,

    recently my PC started to give me the above mentioned BSOD 0x4E. It mainly happens while booting ~during the part where the lightballs start to form the Windows 7 Logo. One time it happend shortly after I got into Windows and today for the first time after the PC was running for a while.

    I'll run Memtest84+ tonight and see if I get errors. Already did chkdsk and sfc with no errors.

    Basic System Infos:

    OS: Windows 7 Prof x64 retail (University Licence)
    Age: System was bought around January/February so Hardware and OS are from that time.

    Motherbord: ASUS P7P55D Rev 1
    CPU: Intel Core i5 760
    RAM: G.Skill F3-12800CL9-2GBNQ 4gig
    GPU: Nvidia GeForce GTX 460
    HDD: 500gig Samsung HD501LJ (the only old component in the system its ~4y old)

    These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


    1-Memtest.


    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 6 or7 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    RAM - Test with Memtest86+



    2-Driver verifier

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Driver Verifier - Enable and Disable
      My Computer


  3. Posts : 44
    Windows 7 Professional x64
    Thread Starter
       #3

    Thanks for the fast reply. I'll run Memtest when I go to sleep and see if I get Errors and will do the verifier thing tomorrow. I will post the results tomorrow evening because the diffrent timezones *sigh*

    Oh and also is it needed to run Memtest from CD? I got the USB Version because I have no CDs here atm... is there a diffrence?
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Tenhi said:
    Thanks for the fast reply. I'll run Memtest when I go to sleep and see if I get Errors and will do the verifier thing tomorrow. I will post the results tomorrow evening because the diffrent timezones *sigh*

    Oh and also is it needed to run Memtest from CD? I got the USB Version because I have no CDs here atm... is there a diffrence?

    Sounds like a plan. USB is fine
      My Computer


  5. Posts : 44
    Windows 7 Professional x64
    Thread Starter
       #5

    Hello zigzag3143,

    I let Memtest run through the night. 10h+, 14 Passes and no Errors. I tested it with my normal Setup (2 Sticks, Slot 1 and 3)... should I test again with a single Stick?

    Oh and I will start to look into the Driver Verifier now. Will report if something happens.

    Edit: Oh and I forgott to say that in the Report it says I have no anti virus software but I have a University Licence of Sophos Antivirus running that is up to date. Also another thing that I noticed, some of the BSODs didnt create minidumps? or they got deleted. I had BSODs with rdyboost.sys as cause. I unpluged some of my USB devices (Headset, Printer) and now only my mouse and 2 HDDs are present (the HDDs are switched off during the booting routine).
      My Computer


  6. Posts : 44
    Windows 7 Professional x64
    Thread Starter
       #6

    Ok used the Driver Verifier. The moment I tried to restart after the Verifier was active I got a BSOD during the Windows Logo. Had to use the Repair Disc to restor the System to be able to post.

    I'll add the new dumpfile. Looks like it was caused by Daemon Tools...
      My Computer


  7. Posts : 44
    Windows 7 Professional x64
    Thread Starter
       #7

    After the recovery the system ran for a while then I got the old 0x4E again. Didnt uninstall Deamon Tools yet. Will do that right now.

    Here the Minidump of the recent crash.

    Edit: uninstalled Deamon Tools.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    Tenhi said:
    After the recovery the system ran for a while then I got the old 0x4E again. Didnt uninstall Deamon Tools yet. Will do that right now.

    Here the Minidump of the recent crash.

    Edit: uninstalled Deamon Tools.
    This was Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd. I would remove it at least to test.
      My Computer


  9. Posts : 44
    Windows 7 Professional x64
    Thread Starter
       #9

    Hey zigzag3143,

    I already removed Deamon Tools yesterday night. Searched for the File you linked, no trace of it on the PC. Should I run the Driver Verifier again?
      My Computer


  10. Posts : 44
    Windows 7 Professional x64
    Thread Starter
       #10

    Just started the Driver Verifer again after uninstalling Deamon Tools. First time after restart I got into Windows but it crashed short after. 2nd restart crashed during Windows Logo. 3rd restart got into Windows but crashed after a few mins.

    Will post the Minidumps.
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:41.
Find Us