FREQUENT BSoD

Page 3 of 11 FirstFirst 12345 ... LastLast

  1. Posts : 71
    windows 7 x64
    Thread Starter
       #21

    Thanks, will try these things tonight, i thought t was over!

    No not solved officially, spoke too soon

    I did find a suggestion to try Run sfc /scannow and the cmd window closed itself as fast as it had opened, tried it on my work computer and it ran propperly, not sure whats going on there

    I did notice last night before this BSoD the the computer wasnt able to extract large rar files that worked propperly after restarting, seems things start falling apart in the background before crashing

    What does the SPTD do?
      My Computer


  2. Posts : 17,322
    Win 10 Pro x64
       #22

    did find a suggestion to try Run sfc /scannow and the cmd window closed itself as fast as it had opened
    That has to be run as admin.
      My Computer


  3. Posts : 13,354
    Windows 7 Professional x64
       #23

    It sounds like you didn't open a command prompt frist, just ran the command from the start menu or Run Dialogue.

    Be sure to open cmd.exe first, then enter sfc /scannow in the window.
      My Computer


  4. Posts : 71
    windows 7 x64
    Thread Starter
       #24

    Have been doing a it of reading and it seems a few people have trouble with daemontools, is there a way to check the date when i installed it? i cant remember exactly when it was but it could explain the sudden onset of these errors, i have always run AVG and not had problems like this
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #25

    You could check in the Event Viewer for logs, or check for a restore point before installing Daemon Tools.

    System Restore
      My Computer


  6. Posts : 71
    windows 7 x64
    Thread Starter
       #26

    tied to run sfc /scannow and part way through i got an error and then a min later... BSOD, restarted and then the exact same thing again, have attached the minidumps from these occasions. the error for the second blue screen was MEMORY_MANAGMENT it finally finished without blue screening and it said windows resource protection did not find any integridy violation
    Have also uninstalled sptd.sys using the method described
    Have run every scan on seatools also, all come back ok, the long DST check failed to finish the first time for both drives so i tred it again
    I am going to leave AVG for now as its never caused problems for me before and i actually want to see which thing fixed it (assuming i actually eventuaklly get there)
      My Computer


  7. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #27

    Just a suggestion. When you are troubleshooting, the idea is to eliminate all possible causes of conflicts. AVG has been know to cause BSOD's. Why would you not want to eliminate this possibility? You can always reinstall it once your system is running smoothly. I urge to to follow Jonathan's advice. He knows what he is doing.

    Just so you know, I have run AVG on my system with no problems; but others have definitely had problems with it.
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #28

    I still see both AVG and SPTD on the system.

    Here is the AVG removal tool: http://download.avg.com/filedir/util...removerx64.exe

    Here is the SPTD installer/uninstaller. Just run it and click on Uninstall: http://www.duplexsecure.com/download...t-v169-x64.exe

    ...Summary of the Dumps:
    Code:
    
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Wed Jul 14 01:46:20.400 2010 (UTC - 4:00)
    System Uptime: 0 days 0:13:43.649
    BugCheck 1A, {41284, 3ac0001, 0, fffff70001080000}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
    BUGCHECK_STR:  0x1a_41284
    PROCESS_NAME:  iexplore.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Wed Jul 14 01:31:39.239 2010 (UTC - 4:00)
    System Uptime: 0 days 0:38:28.488
    BugCheck 19, {22, 20000000000, 0, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )
    BUGCHECK_STR:  0x19_22
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    
    Code:
    a02impa9.SYS Tue Jul 14 17:12:55 2009
    avgldx64.sys Wed Feb 10 22:52:31 2010
    avgmfx64.sys Sun Apr 25 17:06:15 2010
    avgtdia.sys  Sun Apr 25 17:09:35 2010 
    sptd.sys     Sun Oct 11 16:55:14 2009
      My Computer


  9. Posts : 71
    windows 7 x64
    Thread Starter
       #29

    This happened before i got a chance to get rid of SPTD witch i have done now i also uninstalled daemontools witch i had to do from the start menu because it disappeared off the add remove programes list possibly when i uninstalled SPTD, if i get another one i will uninstall AVG, i have also switched the ram to the other 2 slots to see if that helps, i ran the windows memory checker and it came back fine, do you think ram could be the problem?
      My Computer


  10. Posts : 13,354
    Windows 7 Professional x64
       #30

    The Windows Memory Diagnostic is not very accurate. If you want to test RAM, follow these instructions:
    JK said:
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
      My Computer


 
Page 3 of 11 FirstFirst 12345 ... LastLast

  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 06:19.
Find Us