TechSpot

Daily BSODs on Win7, Ntoskrnl

By Kexecute
Nov 1, 2010
Post New Reply
  1. Hello

    I've got an issue with daily BSODs,

    The BSODs come in row, so i usually get 2-3 in a row and then my computer boots up well

    I've looked at the minidumps, but my technical knowlegde is limited, so i can't really spot the problem, though the minidump thinks Ntoskrnl is the cause

    So if any would be kind to look at them and give me some advice
     

    Attached Files:

  2. Jonathan King

    Jonathan King TS Rookie Posts: 128

    Hello,

    Start by uninstalling the Asus PC Probe utility. Especially this older one is known to cause BSODs.
    Code:
    ghaio.sys    Mon May 30 05:34:05 2005 (429ADE0D)
    Next, remove Daemon Tools or similar programs, as they are using SPTD. SPTD is a driver known to cause BSODs since Vista.
    Code:
    aagr6zj9.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7) -- a driver dynamically allocated by SPTD
    sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
    Remove SPTD itself with this tool: http://www.duplexsecure.com/download/SPTDinst-v174-x64.exe

    While not blamed, Avast is known to cause some BSODs. I suggest you remove it with this tool: http://files.avast.com/files/eng/aswclear5.exe

    MSE is the recommended replacement:

    http://www.microsoft.com/security_essentials

    Update your Realtek NIC drivers: http://218.210.127.131/downloads/do...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
    Code:
    Rt64win7.sys Thu Jul 30 07:58:43 2009 (4A718AF3)
    Update or remove LogMeIn:
    Code:
    hamachi.sys  Thu Feb 19 05:36:41 2009 (499D3639)
    If the BSODs persist, could you upload a full BSOD report? Follow the directions here: http://www.jcgriff2.com/BSODpostinstructions.html

    Zip up the output folder, and upload it to Rapidshare or a similar site.

    ...Summary of the Dumps:
    Code:
    [font=lucida console]
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Nov  1 06:15:14.265 2010 (UTC - 4:00)
    System Uptime: 0 days 0:01:47.434
    BugCheck 1E, {ffffffffc0000096, fffff80003c680fa, 0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+1ba )
    BUGCHECK_STR:  0x1E_c0000096
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Nov  1 02:53:55.416 2010 (UTC - 4:00)
    System Uptime: 0 days 0:04:01.585
    BugCheck 50, {fffff880095748e8, 0, fffffa8004683012, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42837 )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]
     
  3. Kexecute

    Kexecute TS Rookie Topic Starter

    Thanks for the fast response

    It was really helpful, i've had no BSODs after rebooting twice :)

    But, should i install a newer version of the probe utility?
     
  4. Jonathan King

    Jonathan King TS Rookie Posts: 128

    You can if you want, I don't think the new one causes BSODs.

    I don't recommend it, as it would be another useless program hogging up RAM and affecting performance, but if you see a need for it, go ahead.
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...