TechSpot

Win XP SP2 Sudden Crashes. Need help.

By shervinafshar
Oct 7, 2005
Topic Status:
Not open for further replies.
  1. Hi there,

    My Windows XP Sp2 machine keeps crashing and showing blue page error with messages like "DRIVER IRQ NOT LESS OR EQUAL" and "PAGE FAULT IN NON-PAGED AREA" and reboots. It happens in random time interval, even when there is no software activity. My hardware specs :

    MB Gigabyte 7DXR+ (with last bios update)
    CPU AMD Athlon XP 2000+
    RAM 512 MB DDR Kingston (in 2 128 MB Modules)
    Grphic card ATI Radeon 6500
    HDD Western Digital 40 GB
    Soundcard Creative Soundblaster Live
    Modem Creative Modem Blaster V.92

    Some of the main software I usually have loaded and resident in memory are :
    Google Desktop
    CPU Idle
    Motherboard Monitor
    Norton Antivirus
    Feedreader
    ZoneAlarm Pro with Web Filtering
    Babylon

    And finally I have these major software installed :

    Nero 6 : I've disabled the filter check on startup.
    iTunes 5 : I've disabled the Bonjour services.

    I'm really mixed up about this problem and I don't really have the time to diassemble the PC and check the parts one by one. Even the problem may be raised by a faulty driver which in this case it's out of my abilities to find out. So I'm asking here for help. Here is a few number of the most recent windows dump files related to event 1001.

    I'll be quite thankful if anyone can help.

    Shervin
  2. cpc2004

    cpc2004 TS Rookie Posts: 2,044

    Your minidumps have memory corruption and I believe that it is faulty ram.

    You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

    Suggestion
    1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
    2. Reseat the memory stick to another memory slot
    3. Downclock the ram
    4. Clean the dust inside the computer case
    5. Make sure that the ram is compatible to the motherboard
    If it still crashes, diagnostic which memory stick is faulty
    1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
    2. If you have only one memory stick, replace the ram

    Debug report of your minidump

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs
    3 errors : !Ntfs (f98a95e3-f98a95f3)
    f98a95e0 f6 c5 04 *87 0f 85 01 02 00 00 68 *fc 5b 89 f9 e8 ..........h.[...
    f98a95f0 13 ee fc *75 83 26 00 5f 5e 5b c9 c2 0c 00 90 90 ...u.&._^[......

    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MEMORY_CORRUPTOR: STRIDE
    STACK_COMMAND: .cxr ffffffffede171ec ; kb
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
    BUCKET_ID: MEMORY_CORRUPTION_STRIDE
  3. shervinafshar

    shervinafshar TS Rookie Topic Starter

    Thank you very much. I do appreciate your help. By now when the problem is narrowed to RAM, it's quite easier to solve the problem.
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.