none
Blue Screen Problem - Windows 7

    Question

  • Hi I've been having a problem with Windows 7 for the past few months I did post up previously about it and was advised to remove Norton 360. I also found out that 1 of my 3 sticks of Ram was messed up so now I'm running on 4Gig of Ram instead of 6 Gig. Attached are the Mini Dumps for the last 2 blue screens and the XML file from the latests

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7600.2.0.0.256.48
      Locale ID:    2057

    Additional information about the problem:
      BCCode:    4e
      BCP1:    0000000000000099
      BCP2:    000000000000CEBC
      BCP3:    0000000000000002
      BCP4:    000000000000CEBA
      OS Version:    6_1_7600
      Service Pack:    0_0
      Product:    256_1

    Files that help describe the problem:
      C:\Windows\Minidump\061210-16816-01.dmp
      C:\Users\simon\AppData\Local\Temp\WER-29562-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    http://cid-f2d226d46836e620.office.live.com/self.aspx/.Public/WER-29562-0.sysdata.xml
    http://cid-f2d226d46836e620.office.live.com/self.aspx/.Public/061210-16816-01.dmp

    http://cid-f2d226d46836e620.office.live.com/self.aspx/.Public/060810-21403-01.dmp

    I would be very grateful for any advice that can be given

    KR
    Simon

     

     

    • Edited by bigsim20 Saturday, June 12, 2010 1:51 PM Chnged URLs to Hyperlinks
    Saturday, June 12, 2010 1:44 PM

Answers

  • Hi,

     

    According to the minidump files, you still have problem with the RAM or the motherboard cannot handle the RAM normally.

     

    Based on the current situation, I suggest you install only one RAM stick to check the result.

     

    You may also consider to update the BIOS and the motherboard chipset drivers to improve the system stability.

     

    Regards,


    Arthur Li - MSFT
    Monday, June 14, 2010 4:59 AM
    Moderator

All replies

  • Bug Check 0x4E: PFN_LIST_CORRUPT

    The PFN_LIST_CORRUPT bug check has a value of 0x0000004E. This indicates that the page frame number (PFN) list is corrupted.

    Probably caused by : memory_corruption

    Please check your RAM for errors! To do this, please download this tool:

    http://www.memtest.org/

    and run it for several hours.


    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, June 12, 2010 2:01 PM
  • You reported details of bugcheck 0x4e - as indicated, that's PFN_LIST_CORRUPT, which is memory corruption.  It may be due to faulty RAM or faulty/incompatible drivers.

    Your specific PFN_LIST_CORRUPT bugchecks were due to reason code 0x99 - "A page table entry (PTE) or PFN is corrupt.".

    You have one old/stale driver on your system (stale drivers are often suspect due to compatibility concerns): speedfan.sys 9/24/2006 

    The Comodo software is also suspect, as is ASACPI.sys 7/15/2009 (awful close to Win 7 RTM - little time to test that driver with released version of Win7!).

    Consider removing the speedfan driver and checking the behavior.  Else, run chkdsk, sfc /scannow, and verifier as described below.

     

    For dealing with Blue Screens, general guidance follows:

    Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

    Also consider running SFC /SCANNOW.

    Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're  using the latest BIOS.

    Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of  modules for a while, and see how things go. Then try the other modules.

    If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

    For memory corruption cases such as you seem to be experiencing, it can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out  of the dialog.

    Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot  completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

    Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive, and provide a link.

    • Proposed as answer by No.Compromise Tuesday, June 15, 2010 11:08 AM
    Saturday, June 12, 2010 6:09 PM
  • Hi

    Thanks for the advice. I performed a Windows Memory Diagnostic and it said there was a problem. I then ran memtest as recommended by Andre.Ziegler and yourself see below for screenshot and I couldn't find any errors but as you said it still not might be OK

    http://cid-f2d226d46836e620.office.live.com/self.aspx/.Public/DSC00034.JPG

     

    I have un-installed Speed Fan. Can you recommend a good free virus scanner that won't conflict with Windows 7?

    KR

    Simon

    Sunday, June 13, 2010 3:06 PM
  • Did you note the errors that WMD reported?  Did you test the RAM module on its own, or with other modules in the system?  

    I'll avoid recommending something, and state that a common AV product that people seem to be using with no ill effects is Microsoft Security Essentials. 

    Have you enabled verifier on any drivers at this point, or have you run SFC and/or chkdsk?

    How frequently dod you encounter the bugchecks?  Do you have more recent crash dumps than the 2 you provided?

    • Proposed as answer by No.Compromise Tuesday, June 15, 2010 11:08 AM
    Sunday, June 13, 2010 4:26 PM
  • Hi,

     

    According to the minidump files, you still have problem with the RAM or the motherboard cannot handle the RAM normally.

     

    Based on the current situation, I suggest you install only one RAM stick to check the result.

     

    You may also consider to update the BIOS and the motherboard chipset drivers to improve the system stability.

     

    Regards,


    Arthur Li - MSFT
    Monday, June 14, 2010 4:59 AM
    Moderator
  • Hi I haven't had time to make any system changes, been a tad busy the last couple of days

     

    I've got a new dump file for you though. It happened this evening. It Blue Screens about every Two to Three days of use.

     

     


    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7600.2.0.0.256.48
      Locale ID:    2057

    Additional information about the problem:
      BCCode:    1a
      BCP1:    0000000000000403
      BCP2:    FFFFF68000038878
      BCP3:    B5B0000127EE2867
      BCP4:    FFFFF6FC400A01B8
      OS Version:    6_1_7600
      Service Pack:    0_0
      Product:    256_1

    Files that help describe the problem:
      C:\Windows\Minidump\061510-18735-01.dmp
      C:\Users\simon\AppData\Local\Temp\WER-42463-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

     

    http://cid-f2d226d46836e620.office.live.com/self.aspx/.Public/061510-18735-01.dmp

    http://cid-f2d226d46836e620.office.live.com/self.aspx/.Public/WER-42463-0.sysdata.xml

    Tuesday, June 15, 2010 7:26 PM
  • This one was bugcheck 0x1a - MEMORY_MANAGEMENT - "This indicates that a severe memory management error occurred."

    The reason code you got (0x403) does not appear to be documented, so the precise meaning is difficult to infer. In the context of your previous problems, faulty RAM seems a stronger possibility now. Cycle through your RAM modules, using only one or two at a time, to attempt to isolate one that may be faulty.  Double-check BIOS settings with respect to RAM timings and the like.  Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test.  Note current BIOS settings and restore BIOS defaults, changing those values you know need to be changed, ensure that RAM and CPU are compatible with the motherboard.  Update the BIOS if possible.  If you're overclocking, stop.

    Tuesday, June 15, 2010 8:29 PM
  • Thanks for all you advice I will take a look see btw I got another bluescreen

     

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7600.2.0.0.256.48
      Locale ID:    2057

    Additional information about the problem:
      BCCode:    1a
      BCP1:    0000000000005003
      BCP2:    FFFFF70001080000
      BCP3:    000000000000F68A
      BCP4:    0000F6870401ED14
      OS Version:    6_1_7600
      Service Pack:    0_0
      Product:    256_1

    Files that help describe the problem:
      C:\Windows\Minidump\061810-17955-01.dmp
      C:\Users\simon\AppData\Local\Temp\WER-36301-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

     

    http://cid-f2d226d46836e620.office.live.com/self.aspx/.Public/061810-17955-01.dmp

    http://cid-f2d226d46836e620.office.live.com/self.aspx/.Public/WER-36301-0.sysdata.xml

    • Proposed as answer by Ali Elsaid Friday, June 25, 2010 8:15 PM
    Friday, June 18, 2010 7:26 PM
  • Same type of bugcheck - MEMORY_MANAGEMENT, with another undocumented reason code.  Previous suggestions stand...

    The latest dump does show one stale driver - seehcri.sys 1/9/2008, related to Sony Ericsson Mobile Communications.  Seems unlikely that this would be involved because it didn't show up in a previous dump, but worth noting.

    Friday, June 18, 2010 7:59 PM