Various BSODs ntoskrnl.exe


  1. Posts : 1
    Italy
       #1

    Various BSODs ntoskrnl.exe


    Hello,
    on January I bought a new pc with this hardware:

    AMD FX 6300
    4GB DDR3 CORSAIR VENGEANCE 1600
    AMD XFX R7 260X
    HDD SEAGATE 1TB
    ALI EVGA 430W
    ASRock 970 PRO R 2.0

    Since January I ave a lot of BSODs randomly and I can't find the causes a part the drivers that caused it but it didn't helped me...
    I tried to format/change OS (W 8.1, format and again W 8.1, W7 enterprise, format w7 ultimate) but the BSODs continue to appears...

    I attached what You request.

    Hoping to solve this problem...
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to the forum.

    Please remove the below:

    AODDriver2.sys Tue Feb 11 17:06:52 2014 (52FA044C)
    AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7[br][br]Part of AMD Fuel[br][br]Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys
    Driver Reference Table - AODDriver2.sys

    Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
    • Click on the
    • Type CMD on Search
    • Left click and Run as Administrator
    • Type SFC /scannow

    Full tutorial here:

    Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

    Upload a screenshot of your hard disk using Crystal Disk Info:

    Make scans with the following:

    Kaspersky TDSSKiller

    ESET online scanner:

    Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

    The goal is to test all the RAM sticks and all the motherboard slots.

    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    *Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    *If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    *If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    *If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    *If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
       Information
    Errors are sometimes found after 8 passes.

       Tip
    Memtest should be done overnight.

    Code:
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Debug session time: Fri Aug 15 02:13:52.918 2014 (UTC + 6:00)
    System Uptime: 0 days 1:31:39.104
    BugCheck 1E, {0, 0, 0, 0}
    Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Debug session time: Wed Aug 13 06:41:46.439 2014 (UTC + 6:00)
    System Uptime: 0 days 0:21:47.610
    BugCheck A, {fffff00005801f00, 2, 1, fffff80002a8fc42}
    Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+82 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Debug session time: Tue Aug 12 16:02:53.481 2014 (UTC + 6:00)
    System Uptime: 0 days 0:02:26.307
    BugCheck 50, {fffff8000402a598, 0, fffff8000300f7d0, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4518f )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      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 19:27.
Find Us