Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSoD (MEMORY_MANAGEMENT,PFN_LIST_CORRUPT...)


12 May 2012   #1

Windows 7 Professional 64bit
 
 
Random BSoD (0x0000001a, 0x00000109, 0x0000004e, 0x0000003b)

I've just install Wins 7 on my T400 about 2 week ago (it came with Wins Vista OEM)
I've been having many BSOD at random, even idle so I can't figure out what's wrong.
I've use WinDBG but no help

Spec
- Lenovo T400
- Wins 7 Pro x64 (Retail)

Thank you

The common error codes are
0x0000001a, 0x00000109, 0x0000004e, 0x0000003b

When i use WinDBG, almost of the errors probably cause by memory corruption

My System SpecsSystem Spec
.

13 May 2012   #2

Windows 7 Professional 64bit
 
 

After last bsod (in the 1st post), i turned on driver verifier and until now, no more bsod ?
i realy dont have any clue to figure what is the problem :-?
My System SpecsSystem Spec
14 May 2012   #3

Windows 7 Professional 64bit
 
 

hello, no one can help me ?
today, with driver verifier, i have 8 more bsod
My System SpecsSystem Spec
.


14 May 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Please upload the latest crash reports. Also, make sure you check memory and enable Verifier properly.

  • If you are overclocking any hardware, please stop.

  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
    warning   Warning
    Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

    For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
    Once these steps have been followed, it is safe to remove and replace components within your computer.

  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. In Windows 7:
    • Click the Start Menu
    • Type verifier in Search programs and files (do not hit enter)
    • Right click verifier and click Run as administrator
    • Put a tick in Create custom settings (for code developers) and click next
    • Put a tick in Select individual settings from a full list and click next
    • Set up the individual settings as in the image and click next
      Attachment 211730
    • Put a tick in Select driver names from a list
    • Put a tick next to all non-Microsoft drivers.
    • Click Finish.
    • Restart your computer.

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

    When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
    verifier /reset
    -> Restart your computer.
My System SpecsSystem Spec
14 May 2012   #5

Windows 7 Home Premium 64 bit
 
 

definitely run the memory test first as writh stated. In my experience, multiple different BSODs are usually hardware related. Also disconnect all external 3rd party equipment you may be using such as usb, esata, fireware, PC cards, etc.
My System SpecsSystem Spec
14 May 2012   #6

Windows 7 Professional 64bit
 
 

i've also run Memtest86+ (come with Ubuntu installer) and came up with no errors (2 passes)
Before i installed Wins7, my laptop run wins vista very stable so i dont think there is anyproblem with the hardware

I've uploaded all the dmp in the 1st post
I'll try renable Driver Verifier tomorow
My System SpecsSystem Spec
14 May 2012   #7

Windows 7 Home Premium 64 bit
 
 

run in safe mode then.. you'll know if it's a driver
My System SpecsSystem Spec
14 May 2012   #8

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by event3horizon View Post
run in safe mode then.. you'll know if it's a driver
This actually is not a fool proof method for determining whether it is a driver. Safe Mode does not load as many drivers, true, but it also does not stress the hardware in the same way that normal mode does.


Quote   Quote: Originally Posted by hlmasterchief93 View Post
i've also run Memtest86+ (come with Ubuntu installer) and came up with no errors (2 passes)
Before i installed Wins7, my laptop run wins vista very stable so i dont think there is anyproblem with the hardware

I've uploaded all the dmp in the 1st post
I'll try renable Driver Verifier tomorow
As for only running Memtest86+ for 2 passes, I have seen it take up to 21 passes for errors to be found, and we generally recommend at least 7. Obviously, the more, the better.
My System SpecsSystem Spec
14 May 2012   #9

Windows 7 Home Premium 64 bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
Quote   Quote: Originally Posted by event3horizon View Post
run in safe mode then.. you'll know if it's a driver
This actually is not a fool proof method for determining whether it is a driver. Safe Mode does not load as many drivers, true, but it also does not stress the hardware in the same way that normal mode does.
But then nothing ever is fool proof. It doesn't hurt to try. Just a reboot away.
My System SpecsSystem Spec
14 May 2012   #10

Windows 7 Professional 64bit
 
 

Thank you, I've never had bsod on SafeMode. I've used it a bit when I want to use computer but dont want to get bsod (burn disks ...) and when i got 2 bsod in a row.
Right now I'm in safemode after 2 bsod >.<
I'll attach it in 1st post
My System SpecsSystem Spec
Reply

 Random BSoD (MEMORY_MANAGEMENT,PFN_LIST_CORRUPT...)




Thread Tools



Similar help and support threads for2: Random BSoD (MEMORY_MANAGEMENT,PFN_LIST_CORRUPT...)
Thread Forum
Random BSOD, last one (PFN_LIST_CORRUPT) BSOD Help and Support
Memory_Management and PFN_LIST_CORRUPT BSOD Help and Support
Solved PFN_LIST_CORRUPT and MEMORY_MANAGEMENT errors BSOD Help and Support
Crashing, BSoD; Memory_Management, PFN_List_Corrupt and loads more! BSOD Help and Support
Solved Got a BSOD with multiple MEMORY_MANAGEMENT and once PFN_LIST_CORRUPT BSOD Help and Support
BSOD - PFN_List_Corrupt, IRQL..., and now Memory_Management BSOD Help and Support
Regular BSODs (mostly memory_management, pfn_list_corrupt etc.) BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 06:22 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33