BSOD on windows 10 and 7 but not on XP

Page 1 of 4 123 ... LastLast

  1. Posts : 26
    Windows 10 Pro x64
       #1

    BSOD on windows 10 and 7 but not on XP


    Hello, so some time ago I got windows 7 64 bit, but it BSODed all the time. So I upgraded to win10 as I thought it may fix it. I can switch between XP and 10 freely on my PC and win10 is BSODing every 5 minutes or so and XP is totally fine. I tried everything on 7 and 10 and I still have no clue what the cause for the BSODs is and if it is even the same for both OSs.
    Thanks for reading.

    Edit: XP is 32 bit, 7 and 10 is 64 bit
    Last edited by noname42; 13 Aug 2015 at 10:27.
      My Computer


  2. Posts : 2
    Windows 10 Home 64 bit
       #2

    Try updating or removing firefox.
      My Computer


  3. Posts : 26
    Windows 10 Pro x64
    Thread Starter
       #3

    I just did a fresh windows 10 reinstall and it still BSODs (I don't have firefox installed yet)

    Edit: 16 hours memtest 86+, 8 passes, 0 errors
    Last edited by noname42; 12 Aug 2015 at 08:01.
      My Computer


  4. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #4

    Looking at your dumps (0x1A, 0x1E and 0x139) it's pretty open as to what the problem could be, I'm not ruling out hardware yet but let's rule out some other things first. It's possible that a driver is causing the issue so we'll see if we can make any poke their head out.




    Diagnostic Test

     DRIVER VERIFIER


    Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums

    warning   Warning
    Make a System Restore point before enabling Driver Verifier.
    Note   Note
    Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

    Post any resulting dump files.
      My Computer


  5. Posts : 26
    Windows 10 Pro x64
    Thread Starter
       #5

    Here are 4 minidumps that happened after enabling driver verifier.
      My Computer


  6. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #6

    Finally we have a culprit, Avast. Please uninstall Avast and use native Defender coupled with MalwareBytes.

    Note   Note
    Make sure you uncheck the 'Enable Free Trial' box when installing.



    Code:
    ffffd000`22619e88  fffff800`c5600d77Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for aswSnx.sys
    *** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
     aswSnx+0x50d77
      My Computer


  7. Posts : 26
    Windows 10 Pro x64
    Thread Starter
       #7

    Already tried that, but I guess I'll remove it again.
    Btw: Thanks for the help.

    Edit: ok, maybe the trojans were the problem...
    Last edited by noname42; 13 Aug 2015 at 15:39.
      My Computer


  8. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #8

    Trojans? What picked those up?
      My Computer


  9. Posts : 26
    Windows 10 Pro x64
    Thread Starter
       #9

    I installed MalwareBytes and ran it and it found some trojans
      My Computer


  10. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #10

    Run a round of SuperAntiSpyware as linked in my signature, full scans of both would be best.
      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 20:07.
Find Us




Windows 10 Forums