BSOD randomly occuring

By vinod · 6 replies
Mar 2, 2009
  1. Hey guys,

    Have been getting the BSOD for the past 2 weeks or so.At first,I thought it might be a virus or a malware.But cleaned the pc using Malware bytes and AVG.Still no hits whatsoever.But yet,this is happening.

    The latest one was 30mins back.And this is the error code I obtained from the event log.

    "The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x001902fe, 0xf13d6304, 0xf13d6000, 0xf76679e7)."

    I have attached the minidumps of the last 3 crashes.I hope someone can help me figure out the problem.Thanks! :)

  2. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    When you cleaned the PC was there viruses, malware, and or trojans present?
  3. vinod

    vinod TS Rookie Topic Starter

    Yes,AVG detected some trojans etc.All of 'em were moved to the Virus Vault!
  4. vinod

    vinod TS Rookie Topic Starter

    Hey guys,

    Encountered another BSOD a few mins back.And this is the error code from it.

    "The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf9fc966, 0xf0a41240, 0x00000000)"
  5. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    There is a strong possiblity that you may still be infected. I suggest you go to the Virus and Malware forum and read and follow the 8 Steps Guide.

    As for your minidumps they are as follows:

    0xD1 - these are caused by either faulty drivers or buggy software and yet yours says hardware. It can also be caused by faulty or mismatched RAM, or a damaged pagefile. If the suggestions below don't help then check to see if a) your RAM is set properly, b) if they match, and c) run memtest on your RAM.


    One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message.

    Though a Windows driver was cited as the probable cause these are too general to be of much help. However, it was noted that driver FILTNT.sys was unable to be loaded and this belongs to your Outpost firewall. Try updating.

    A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software.

    Run ChkDsk in your run box and do a full harddrive diagnostics on your harddrive by using the free utility from your harddrive manuafacturer that you can get off their website.

    ** Get back to us with the results.

    ** Attach your latest minidump(s).
  6. vinod

    vinod TS Rookie Topic Starter


    Thanks for the reply.I have followed the steps in the virus\malware thread.And all of it has been clean.And also,I had a problem with one of the drives.Ran CHKDSK on it & it seems to have fixed it.

    But still,there have been 2 random reboots after that.I am attaching the minidumps as well as the HJT log!

  7. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    The most significant error was 0x8E and these are almost always caused by hardware (though sometimes by drivers) and particurly corrupted memory.. Unfortunatenly it only said hardware as the probable cause.

    However in the Bucket ID it listed failure at CLI_FAULT and it is a sign of faulty ram or PSU. Run memtest to stress test ram. Follow these steps and get back to us with the results.

    1. Go to and download the latest ISO version. It is free and perfectly safe.

    2. Burn to a CD.

    3. Place CD in your drive and reboot with CD in drive. (You might have to place your drive as first bootable in your BIOS) The test will take over.

    4. Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

    5. If you have errors you have corrupted memory and it needs to be replaced.

    6. Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...