The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Abundance of Problems

    Discussion in 'Alienware 17 and M17x' started by NullEntity, Oct 16, 2010.

  1. NullEntity

    NullEntity Notebook Enthusiast

    Reputations:
    2
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    15
    So yesterday morning, I decided I would browse the internet a bit before school. I usually leave my M17xR1 overnight running Folding@home, but for some reason it was in hibernation. I hit the spacebar to wake it up. It starts to come out of hibernation and then BAM, BSOD. The message was PFN_LIST_CORRUPT. I try restarting it again. I'm logged in and have been running for maybe 5 minutes and then again, PFN_LIST_ CORRUPT.

    Later that night, I found that that BSOD is related to bad RAM. So I run the self-diagnostics. It tells me that the RAM failed the integrity test (funnily enough, it was error 2000-0123 at address 0xABC00000). So I test each module on it's own. One of them was bad. This is 3rd party RAM so I RMA it back to Crucial and reinstall my stock RAM. I run the diagnostics one last time to make sure it's not some other hardware error and it passed.

    When I try to boot it up, it just sits at a screen with the '_' character blinking after posting. I let it sit for an hour with no results. It's like it couldn't find an OS, but didn't say it. At that point, I called tech support. He had me go into the BIOS and change the SATA options. After that, it could try to boot into Windows. That lead to another BSOD. Safe mode, BSOD. Startup Repair couldn't find anything. I was at my wits end. Then, I found that I could spam F8 and could get into the boot options menu. I disabled the automatic restart on system crash option. This time, the error was IRQL_NOT_LESS_OR_EQUAL. I finally tried 'Last Known Good Configuration' and it worked!

    Now today, I booted it up, was playing Minecraft for an hour or so and lo and behold, another BSOD. This time it was an error about an Avast driver: aswMonFlt.sys. Anyone have any idea on how to fix this?

    tl;dr: Crapload of BSODs. What I do?
     
  2. Harryboiyeye

    Harryboiyeye Notebook Deity

    Reputations:
    216
    Messages:
    718
    Likes Received:
    36
    Trophy Points:
    41
    I would say that maybe the Mobo is acting up if your are having numerous BSODs. Have you tried reinstalling?
     
  3. blaster

    blaster 1 tequila, 2,3,4,5, floor

    Reputations:
    560
    Messages:
    903
    Likes Received:
    22
    Trophy Points:
    31
    i would call tech support for a mobo replacement
     
  4. The0ne

    The0ne Notebook Consultant

    Reputations:
    37
    Messages:
    229
    Likes Received:
    0
    Trophy Points:
    30
    Sounds very much like a motherboard problem to me as well.
     
  5. NullEntity

    NullEntity Notebook Enthusiast

    Reputations:
    2
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    15
    I tried reinstalling Windows on my second HDD (just swapped the two) and it was acting really funny. Once I got my original drive working, it wouldn't let me format the secondary. I'll call them later today.