BSOD ntoskrnl

Page 2 of 5 FirstFirst 1234 ... LastLast

  1. Posts : 29
    Window 7 Premium 64bit
    Thread Starter
       #11

    I have attached a new file set for the dmp files. Not sure if the dumps are in this because using events viewer or BlueSreenView I didn't see any entries for BSOD for when I had the drivers test on. I've tried just by process of elimination to figure out which ones cause the crash but haven't finished. Not sure if I'll find the one this way.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #12

    gjrewerts said:
    I have attached a new file set for the dmp files. Not sure if the dumps are in this because using events viewer or BlueSreenView I didn't see any entries for BSOD for when I had the drivers test on. I've tried just by process of elimination to figure out which ones cause the crash but haven't finished. Not sure if I'll find the one this way.
    Blue screen view is notoriously in-accurate.

    Your most recent is not verified and is related to memory corruption

    These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

    If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!



    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    2-Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Driver Verifier - Enable and Disable


    Further Reading
    Using Driver Verifier to identify issues with Windows drivers for advanced users

      My Computer


  3. Posts : 29
    Window 7 Premium 64bit
    Thread Starter
       #13

    I have already run the memory test and it passed and there lastest dumps I got after I ran the verifier. I thnk the file that is carshing is bsecfltr.sys which always crashs when I only run it in the verifier.
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #14

    gjrewerts said:
    I have already run the memory test and it passed and there lastest dumps I got after I ran the verifier. I thnk the file that is carshing is bsecfltr.sys which always crashs when I only run it in the verifier.
    Not one of these were verified nor related to bsecfltr.sys. I can find no info for that file in a google search.
      My Computer


  5. Posts : 29
    Window 7 Premium 64bit
    Thread Starter
       #15

    When I run the verifier and select bsecfltr.sys file from Bsecure then when I reboot the system it crashs with the BSOD then the stop address shown is 0xC4 but it doesn't create a dump file. So not sure if this is what is causing my random system crashs?
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #16

    gjrewerts said:
    When I run the verifier and select bsecfltr.sys file from Bsecure then when I reboot the system it crashs with the BSOD then the stop address shown is 0xC4 but it doesn't create a dump file. So not sure if this is what is causing my random system crashs?
    I have no idea what bsecfltr.sys is. I am beginning to think malware.


    Please download the free version of Malwarebytes.
    Update it immediately.
    Do a full system scan
    Let us know the results at the end.



    Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

      My Computer


  7. Posts : 29
    Window 7 Premium 64bit
    Thread Starter
       #17

    bsecfltr.sys is a system file for bsecure a filter and virous scan software. But running Malwarebytes doesn't find any problems with this file or my system.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #18

    gjrewerts said:
    bsecfltr.sys is a system file for bsecure a filter and virous scan software. But running Malwarebytes doesn't find any problems with this file or my system.
    Since bsedfltr.sys is blamed I would remove the application at least to test and replace it with Microsoft Security Essentials

    Microsoft Security Essentials - Free Antivirus for Windows
      My Computer


  9. Posts : 29
    Window 7 Premium 64bit
    Thread Starter
       #19

    I'm really lost as to why my computer is still crashing. So I uninstall the bsecure and installed Microsoft Security Essentials but it still crashes. We have tested the hardware, the memory and the few of the drivers but still not sure why it is crashing?
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #20

    gjrewerts said:
    I'm really lost as to why my computer is still crashing. So I uninstall the bsecure and installed Microsoft Security Essentials but it still crashes. We have tested the hardware, the memory and the few of the drivers but still not sure why it is crashing?
    Still pointing to memory corruption. Since it appears your ram has passed it may be time to start thinking about a clean install.
      My Computer


 
Page 2 of 5 FirstFirst 1234 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:59.
Find Us