Daily BSOD after 1 hour, then fine for rest of day


  1. Posts : 3
    Win7
       #1

    Daily BSOD after 1 hour, then fine for rest of day


    Hi,
    Have an office computer which bluescreens daily after a certain period of time, but then is fine for the rest of the working day.

    BSOD shows CRITICAL_STRUCTURE_CORRUPTION,
    and bluescreenview shows plenty of
    ntoskrnl.exe+ 14e2a0

    Any thoughts? I'm sure its relating to a driver but I have no idea how to go about finding out which one is most likely at fault.
    Is there a website I can dump one of the DM log files into and have it bring up a list of outdated drivers?

    Thanks for any help!
      My Computer

  2. axe0's Avatar
    Posts : 14,792
    Windows 10 Pro
       #2

    Using more then 1 AV protection causes several problems, including performance problems, accessibility problems (errors when accessing a file for example) and possible bluescreens.

    Remove either Avast or Bitdefender, I would suggest to remove Avast as Avast causes a lot of crashes.
      My Computers


  3. Posts : 3
    Win7
    Thread Starter
       #3

    Ah, the bitdefender was literally only put on there the other day, but the BSOD's have been going for a while.

    we're in the process of removing avast but it's being stubborn.

    Any other ideas?
      My Computer

  4. axe0's Avatar
    Posts : 14,792
    Windows 10 Pro
       #4

    Run driver verifier and create a new thread at BSOD Crashes and Debugging - Windows 8 Forums
    Your system is Windows 8.1, this forum is meant for Windows 10 :)

    Driver verifier is necessary, because the dumps don't hold much.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 109, {a3a01f58ec03d8c1, b3b72bdf3e83d658, fffff803ede60000, 3}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
      My Computers


  5. Posts : 3
    Win7
    Thread Starter
       #5

    Dang. alright. thanks for your help bud. i'll see if driver verifier picks up anything.
      My Computer


 

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

Designer Media Ltd
All times are GMT -5. The time now is 01:18.
Find Us




Windows 10 Forums