Random BSOD (Kernel-Power) 0xa3a039d898bc46ff, 0xb3b7465eeb391655


  1. Posts : 2
    Windows 7 64bit
       #1

    Random BSOD (Kernel-Power) 0xa3a039d898bc46ff, 0xb3b7465eeb391655


    I have been having random BSOD for the past year now and they happen at any time. I have noticed though, that it may be HDD related as some times I will be clicking on a link etc and I get a BSOD.

    I ran CHKDSK just before and when I came back to check after leaving it to finish the 5th pass, I saw it had BSOD again.

    Files attached and any help will greatly help.
      My Computer


  2. Posts : 2
    Windows 7 64bit
    Thread Starter
       #2

    Anyone got a clue to my issue?
      My Computer


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

    Welcome to the Forum.

    Reduce items at start-up: Startup Programs - Change

    Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

    dtsoftbus01.sys Thu Jun 20 13:22:51 2013 (51C2ADCB)
    Daemon Tools driver [br] Possible BSOD issues in Win7
    Driver Reference Table - dtsoftbus01.sys

    Daemon Tools/Alchohol is known to cause BSODs:
    How to remove sptd.sys from system
    Registry and SPTD problems | DAEMON Pro Help

    Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

    AVG is contributing to your BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

    Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

    Microsoft Security Essentials - Free Antivirus for Windows

    Malwarebytes - Free

    Good and Free system security combination.

    Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

    ESET online scanner: Free Online Virus Scanner | ESET

    Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

    Run a Hard Drive test: https://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html


    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

    HECIx64.sys Wed Oct 20 05:33:43 2010 (4CBE2AD7)
    Intel Management Engine Interface
    Driver Reference Table - HECIx64.sys

    Rt64win7.sys Tue Sep 27 20:50:33 2011 (4E81E2B9)
    Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
    Driver Reference Table - Rt64win7.sys

    tap0901t.sys Wed Sep 16 12:02:43 2009 (4AB07F83)
    TAP-Win32 Adapter V9 or[br]Google Earth or Tunngle (P2P VPN software)
    Driver Reference Table - tap0901t.sys

    Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

    Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

    Check for heating issues using Speccy or HWmonitor

    Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

    If this does not provide stability. Test RAM.

    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
    Do this test overnight, before going to bed.


    BSOD Summary
    Code:
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sun Feb 23 22:46:10.234 2014 (UTC + 6:00)
    System Uptime: 0 days 0:21:55.451
    BugCheck 109, {a3a039d898bc46ff, b3b7465eeb391655, fffff800032207c0, 1}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0x109
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sun Feb 23 20:39:52.562 2014 (UTC + 6:00)
    System Uptime: 0 days 2:27:23.780
    BugCheck 109, {a3a039d89b9474f5, b3b7465eee11444b, fffff800032207be, 1}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0x109
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Thu Feb 13 17:52:20.622 2014 (UTC + 6:00)
    System Uptime: 0 days 1:48:00.636
    BugCheck 109, {a3a039d89bf5d573, b3b7465eee72a4c9, fffff8000321fc60, 1}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+38870 )
    BUGCHECK_STR:  0x109
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Feb 11 20:11:48.610 2014 (UTC + 6:00)
    System Uptime: 0 days 5:11:20.000
    BugCheck A, {28, 2, 0, fffff80002f17d80}
    Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  avgrsa.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      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 00:57.
Find Us