BSOD randomly showing up during startup.


  1. Posts : 2
    Windows 7 64bit
       #1

    BSOD randomly showing up during startup.


    Hey all. It's two weeks I'm trying to figure out what's the problem but to no avail. Any help is very appreciated :)
    (I recently changed energy supply and graphic card, don't know if that has anything to do with it)

    I uploaded the DMP file as requested, but that's what it says on BSOD anyway:

    STOP: 0X000000F4 (0X0000000000000003, 0XFFFFFA800BCDFB30, 0XFFFFFA800BCDFE10, 0XFFFFF8000318C460)

    If anyone can help me it'd be greatly appreciated!

    P.S: I also received an error while using SF Diagnostic Tool: it cant find C:Windows/system32/drivers/etc/HOSTS.
    (I ran it as an administrator)
    More detailed information in case that matters:
    ************** Testo dell'eccezione **************
    System.IO.FileNotFoundException: Impossibile trovare il file 'C:\Windows\system32\drivers\etc\HOSTS'.
    Nome file: 'C:\Windows\system32\drivers\etc\HOSTS'
    in Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveFile(CopyOrMove operation, String sourceFileName, String destinationFileName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
    in Microsoft.VisualBasic.FileIO.FileSystem.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
    in Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
    in SF_Diagnostic_Tool.Form1.Button1_Click(Object sender, EventArgs e)
    in System.Windows.Forms.Control.OnClick(EventArgs e)
    in System.Windows.Forms.Button.OnClick(EventArgs e)
    in System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
    in System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    in System.Windows.Forms.Control.WndProc(Message& m)
    in System.Windows.Forms.ButtonBase.WndProc(Message& m)
    in System.Windows.Forms.Button.WndProc(Message& m)
    in System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    in System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Assembly caricati **************
    mscorlib
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    ----------------------------------------
    SF Diagnostic Tool
    Versione assembly: 5.0.0.6
    Versione Win32: 5.0.0.6
    Base di codice: file:///C:/Users/Roberto/Desktop/SF_Diagnostic_Tool.exe
    ----------------------------------------
    Microsoft.VisualBasic
    Versione assembly: 8.0.0.0
    Versione Win32: 8.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    ----------------------------------------
    System
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Windows.Forms
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5460 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5462 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Runtime.Remoting
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
    ----------------------------------------
    Accessibility
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.4927 (NetFXspW7.050727-4900)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    ----------------------------------------
    Microsoft.VisualBasic.resources
    Versione assembly: 8.0.0.0
    Versione Win32: 8.0.50727.4927 (NetFXspW7.050727-4900)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/8.0.0.0_it_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dll
    ----------------------------------------
    System.Windows.Forms.resources
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_it_b77a5c561934e089/System.Windows.Forms.resources.dll
    ----------------------------------------
    mscorlib.resources
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    ----------------------------------------

    ************** Debug JIT **************
    Per attivare il debug JIT, è necessario impostare il valore
    jitDebugging nella sezione system.windows.forms del file di configurazione
    dell'applicazione o del computer (machine.config).
    L'applicazione inoltre deve essere compilata con il debug
    attivato.

    Ad esempio:

    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>

    Quando il debug JIT è attivato, tutte le eccezioni non gestite
    vengono inviate al debugger JIT registrato nel computer,
    anziché essere gestite da questa finestra di dialogo.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Welcome aboard, robrizla.

    In 100812-37908-01.dmp
    Code:
    fffff880`040b9f08  fffff880`04b4cf60Unable to load image BHDrvx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for BHDrvx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
     BHDrvx64+0x9ff60
    In 100912-39624-01.dmp
    Code:
    fffff880`0421ff08  fffff880`04d3cf60Unable to load image BHDrvx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for BHDrvx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
     BHDrvx64+0x9ff60
    In 110212-33446-01.dmp
    Code:
    fffff880`03a38f08  fffff880`04ca9f60Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\Definitions\BASHDefs\20110723.001\BHDrvx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for BHDrvx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
     BHDrvx64+0x9ff60
    BHDrvx64.sys is Symantec Heuristics Driver. Driver Reference Table - BHDrvx64.sys

    So, I would suggest you to uninstall Norton using Norton Removal Tool , and use Microsoft Security Essentials - Microsoft Windows.

    At the same time, as all those are stop 0xF4, you should take care of your storage devices, too.

    1. Update your SSD's Firmware
    2. Reseat the sata and power.
    3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
    4. Seatool for dos: SeaTools | Seagate download
      Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

    Let us know the results.
      My Computer


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

    Unfortunately, today I received another BSOD. I attached it below.
    I didn't do step 1-2-3-4, as I do not know what my SSD Firmware is, or what the SATA is, nor do I know what "burn it in a blank cd" means.
    I did uninstall Norton using the Removal Tool and I analyzed my PC with Microsoft Security Essentials, which said my computer was okay.
    Please let me know what's going on. Thanks alot for any help!
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    I am seeing it is the same BSOD as earlier ....
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F4, {3, fffffa800b2ccb30, fffffa800b2cce10, fffff800031ce460}
    
    ----- ETW minidump data unavailable-----
    Probably caused by : wininit.exe
    
    Followup: MachineOwner
    ---------
    Sata:


    Burn CD:


    Firmware: I could say, if it is needed or not, but you haven't provided all data using the SF Diag Tool.
      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 06:43.
Find Us