BSOD Fun

Camz

Junior Member
Apr 16, 2008
2
0
0
Troubleshooting starter

  1. Overview of the problem
    Random BSODs, not sure of the cause.

  2. Full description of the problem and symptoms

    I built this PC about a month ago.
    It worked fine from day one, after I had updated the BIOS so it recognized my newish CPU(E8400)
    Two weeks later I got a BSOD - "PAGE_IN_NONPAGED_AREA", I couldn't boot after that as it would BSOD when I tried doing anything, Safemode etc, after some googling and reading forums, I thought it might be the RAM, so I pulled one stick, and it worked.

    After another 2 weeks or so of smooth running and no problems at all, I got another BSOD out of the blue, from there on I have been having trouble(about 4 days ago now).
    On Sunday night, I was playing WoW and got a BSOD, rebooted, logged into windows, was loading desktop up etc got another, has chained from there.

    Below is a list of the BSOD errors I have had, since Sunday in the best order I can remember them.

    BAD_POOL_HEADER
    IRQ_NOT_LESS_OR_EQUAL -- STOP:0X7E -- SPTD.SYS
    DRIVER_IRQL_NOT_LESS_OR_EQUAL -- STOP 0XD1 -- NDIS.SYS
    BAD_POOL_CALLER
    STOP 0X24 NTFS.SYS
    BAD_POOL_CALER STOP: 0XC2
    DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP: 0XD1 -- RTL8187.SYS
    DRIVER_IRQL_NOT_LESS_OR_EQUAL -- OXD1 -- KS.SYS
    MULTIPLE_IRL_COMPLETE_REQUESTS -- 0X44
    PAGE_IN_NONPAGED_AREA
    STOP: 0X7E NTFS.SYS

    Above, with a few random STOP:0x7F and 0x8E

    In the middle of those BSODs, I formatted and reinstalled Windows, but to no success, I was getting BSODs while running windows updates, and installing my motherboard and video drivers.

    Again, I thought it might have been the RAM, so I got my hands on some "Corsair TWIN2X2048-8500C5D XMS Dominator DDR2-1066" modules, put them in, wouldnt POST, took a stick out and it worked fine.. (faulty stick? wouldn't run in any of the 4 DIMM slots)
    Booted up, went about my business for a few hours, SUPRISE! another bsod.. ;( "STOP: 0X7E NTFS.SYS"

    Also: When I was trying to repair windows, I got a bsod, which stuffed my installation, so I formatted.



  3. Did it work normally at one time, or has the problem always existed?
    Worked for 2 weeks then got a BSOD chain, pulled a stick of RAM, worked for another 2 weeks fine, which leads me to now.
  4. Is the problem consistent and repeatable, or entirely random, or semi-random?

    Entirely random, although at one point opening Firefox would cause a BSOD.




  5. I already tried these steps:
    Tried different RAM modules, in different slots/combination
    Formatted
    Repairing windows
    Edit: Forgot to mention that I have run memtest86 with no problems



  6. My software:
    • OS: Windows XP Professional Edition with SP2
    • No current antivirus (was using avast! free edition before formatting)
    • No Firewall


  7. My hardware
    • Asus P5K Premium - Wifi-AP
    • E8400, not overclocked
    • XFX 8800GT Xtreme Edition
    • Crucial(1GBx2) Ballistix Tracer, DDR2 PC2-8500 - at 2.2V
    • Thermaltake Toughpower 750W
    • 80gig WesternDigital for OS, and a Seagate Barracuda 320gig for Applications etc

  8. Other information that might be relevant
    (any other information that might be related to the problem)

Any help would be much appreciated! Help me get my machine stable

As I was writing this, I got another BSOD - "PFN_LIST_CORRUPT' - STOP: 0X4E" -- luckily I had saved it into notepad as I was predicting that it would happen.

Can post the minidumps if it'll help

Thanks,
Camz
 

jaqie

Platinum Member
Apr 6, 2008
2,471
1
0
revert to an earlier bios, the earliest you can find. It should be the case that even if the BIOS does not recognize the CPU, the BIOS is not in control of any but the most basic (hence Bios) things, which windows basically takes over for, more or less... no cpu recog. in bios is not near as big of a problem as BSoDs are.
 

Camz

Junior Member
Apr 16, 2008
2
0
0
Originally posted by: jaqie
revert to an earlier bios, the earliest you can find. It should be the case that even if the BIOS does not recognize the CPU, the BIOS is not in control of any but the most basic (hence Bios) things, which windows basically takes over for, more or less... no cpu recog. in bios is not near as big of a problem as BSoDs are.

Hi there,

As I understand the Asus motherboards are not back flashable, only way to backflash them is using the in-windows utility which I'm not so keen about seeing as am getting random bsods
 

jaqie

Platinum Member
Apr 6, 2008
2,471
1
0
thare are third party flashing utilities out there, I have used them on all sorts of cards and mobos.

Failing that, I guess you can just RMA the board since the company seems to have issues with letting you fix it yourself.