Random BSOD's for weeks


  1. Posts : 2
    MS Windows 7 Enterprise 64-bit SP1
       #1

    Random BSOD's for weeks


    Hi Guys,

    It's not often that I even post something on a forum, because usually I can find a solution by looking at other peoples posts. However this time, I couldn't find much..
    The problem is that I'have had since building my system in january is random BSOD's;

    DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
    KMODE_EXCEPTION_NOT_HANDLED
    BAD_POOL_HEADER
    IRQL_NOT_LESS_OR_EQUAL
    MEMORY_MANAGEMENT
    DRIVER_VERIFIER_DETECTED_VIOLATION
    DRIVER_IRQL_NOT_LESS_OR_EQUAL
    SYSTEM_SERVICE_EXCEPTION

    I've Attached the jcgriff2 files and I've also included a link tot my hardware specs;

    Profiel van water1309 | Tweakers.net Tweaker Gallery

    My OS is a windows 7 x64 system. I have Windows Security Essentials installed and mostly use portable apps. If I had to guess the source is either my CPU or something with the SSD..

    Hopefully someone here can help me out!
    Thanks in advance!

    Andrew
    Random BSOD's for weeks Attached Files
    Last edited by water1309; 09 Apr 2012 at 13:27. Reason: adding dumpfiles
      My Computer


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

    Various issues releated to various software including a driver verified crash Related to AsUpIO.sys Signed by from ASUSTeK Computer Inc..

    All of these drivers are from before win 7 was released and need updating before we can investigate the underlying (memory I suspec) cause


    Old drivers

    Code:
    aabed2.sys    3/20/2008 6:34:12 AM       
    E1G6032E.sys    5/28/2008 7:14:51 PM        
    dsNcAdpt.sys    3/30/2009 10:33:33 PM        
    AtiPcie.sys    5/5/2009 11:00:22 AM       
    RtHDMIVX.sys    6/24/2009 6:23:22 AM       
    ASMMAP64.sys    7/2/2009 5:13:26 AM        
    AsUpIO.sys    7/5/2009 10:21:38 PM
    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
      My Computer


  3. Posts : 2
    MS Windows 7 Enterprise 64-bit SP1
    Thread Starter
       #3

    Thanks for the reply!

    I've looked into the outdated drivers. I found that aabed2.sys is the most recent driver and a lot of people in the netherlands use it because it comes with a bank card reader.
    For AtiPcie.sys and RtHDMIVX.sys I couldn't find much except what devices they are for. No luck in updating those...

    So maybe someone could help me with these drivers. Otherwise I think it could be hardware related indeed...
    Random BSOD's for weeks Attached Files
    Last edited by water1309; 10 Apr 2012 at 15:47.
      My Computer


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

    water1309 said:
    Thanks for the reply!

    I've looked into the outdated drivers. I found that aabed2.sys is the most recent driver and a lot of people in the netherlands use it because it comes with a bank card reader.
    For AtiPcie.sys and RtHDMIVX.sys I couldn't find much except what devices they are for. No luck in updating those...

    So maybe someone could help me with these drivers. Otherwise I think it could be hardware related indeed...

    Aabed2.sys should be re-installed in compatibility mode
    To install an older driver in win 7 you need to install it in compatibility mode
    Compatibility Mode


    Related to
    AsUpIO.sys Signed by from ASUSTeK Computer Inc.. driver verified an named in two crashes.

    The overall effect is memory corruption.




    These crashes were caused by memory corruption/exception (Cx05) 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!!!

    * If you have raid update its Driver.




    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-7 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+



    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.

    So, I'd suggest that you first backup your stuff 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).

    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 "Special Pool", "Force Pending I/O Requests" and "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.

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    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. You did create a restore point didnt you?
    Using Driver Verifier (Windows Drivers)
      My Computer


 

  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 05:47.
Find Us