Blue screen error!!!


  1. Posts : 18
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
       #1

    BSOD, code: 0x0000007e.. zip file included!


    Hey! :)
    I've started getting this blue screen problem whenever I turn on my laptop and my windows boots! It does work on safe mode though.. Here's the message:

    BCCODE: 10000007e
    BCP1:FFFFFFFFC0000006
    BCP2:FFFFF80002AB222B
    BCP3:FFFFF880061CE6E8
    BCP4:FFFFF880061CDF40

    Any Idea how to fix it? I'd be so thankful if you save my laptop;D
      My Computer


  2. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #2

    When you've booted into Safe Mode follow the instructions below. It looks like your hard drive's failing.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000006, fffff80002aa222b, fffff88005fea6e8, fffff88005fe9f40}
    
    Probably caused by : hardware_disk
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000006, The exception code that was not handled
    Arg2: fffff80002aa222b, The address that the exception occurred at
    Arg3: fffff88005fea6e8, Exception Record Address
    Arg4: fffff88005fe9f40, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    
    FAULTING_IP: 
    nt!RtlImageNtHeaderEx+3f
    fffff800`02aa222b 66390a          cmp     word ptr [rdx],cx
    
    EXCEPTION_RECORD:  fffff88005fea6e8 -- (.exr 0xfffff88005fea6e8)
    ExceptionAddress: fffff80002aa222b (nt!RtlImageNtHeaderEx+0x000000000000003f)
       ExceptionCode: c0000006 (In-page I/O error)
      ExceptionFlags: 00000000
    NumberParameters: 3
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000050000
       Parameter[2]: 00000000c0000185
    Inpage operation failed at 0000000000050000, due to I/O error 00000000c0000185
    
    CONTEXT:  fffff88005fe9f40 -- (.cxr 0xfffff88005fe9f40;r)
    rax=fffff88005feab00 rbx=0000000000000000 rcx=0000000000005a4d
    rdx=0000000000050000 rsi=fffff8a000009c00 rdi=0000000000000001
    rip=fffff80002aa222b rsp=fffff88005fea928 rbp=0000000000000000
     r8=0000000000000000  r9=fffff88005fea968 r10=0000000000000000
    r11=0000000000000000 r12=fffff8a000009c00 r13=0000000000000000
    r14=0000000000000000 r15=fffff88002f69f40
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    nt!RtlImageNtHeaderEx+0x3f:
    fffff800`02aa222b 66390a          cmp     word ptr [rdx],cx ds:002b:00000000`00050000=????
    Last set context:
    rax=fffff88005feab00 rbx=0000000000000000 rcx=0000000000005a4d
    rdx=0000000000050000 rsi=fffff8a000009c00 rdi=0000000000000001
    rip=fffff80002aa222b rsp=fffff88005fea928 rbp=0000000000000000
     r8=0000000000000000  r9=fffff88005fea968 r10=0000000000000000
    r11=0000000000000000 r12=fffff8a000009c00 r13=0000000000000000
    r14=0000000000000000 r15=fffff88002f69f40
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    nt!RtlImageNtHeaderEx+0x3f:
    fffff800`02aa222b 66390a          cmp     word ptr [rdx],cx ds:002b:00000000`00050000=????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000050000
    
    EXCEPTION_PARAMETER3:  00000000c0000185
    
    IO_ERROR: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
    
    BUGCHECK_STR:  0x7E
    
    EXCEPTION_STR:  0xc0000006_c0000185
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    FOLLOWUP_IP: 
    +3f
    00000000`00050000 ??              ???
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware_disk
    
    IMAGE_NAME:  hardware_disk
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    STACK_COMMAND:  kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk
    
    BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk


    Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

    Run chkdsk. Disk Check
      My Computer


  3. Posts : 18
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #3

    Thanks for your reply!:)
    when I run checkdisk it automatically cancels itself and I don't even get to read its error message as it goes too fast! also about seatools, it seems that It can only perform Short Drive Self Test, Short Generic Test and Long Generic test. they all pass except the Short drive test.
      My Computer


  4. Posts : 18
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #4

    I've just tried running checkdisk using scheduled check and It gives me messages like:
    "File record segment xxxx is unreadable."
      My Computer


  5. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #5

    It does sound to me like the HDD is failing. What did SeaTools say when it failed the Short Test?
      My Computer


  6. Posts : 18
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #6

    it just fails and when I waited to get a message it just showed me an error from microsoft NEt. framework with this detail:



    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.InvalidOperationException: An error occurred creating the form. See Exception.InnerException for details. The error is: External component has thrown an exception. ---> System.Runtime.InteropServices.SEHException: External component has thrown an exception.
    at SeaToolsforWindows.frmViewLog.InitializeComponent()
    at SeaToolsforWindows.frmViewLog..ctor()
    --- End of inner exception stack trace ---
    at SeaToolsforWindows.My.MyProject.MyForms.Create__Instance__[T](T Instance)
    at SeaToolsforWindows.frmSTXMain.ViewLogFileMenuItem_Click(Object sender, EventArgs e)
    at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
    at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
    at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
    at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
    at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
    at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
    at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
    at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    at System.Windows.Forms.ToolStrip.WndProc(Message& m)
    at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    ----------------------------------------
    SeaToolsforWindows
    Assembly Version: 1.2.0.10
    Win32 Version: 1.2.0.10
    CodeBase: file:///C:/Program%20Files%20(x86)/Seagate/SeaTools%20for%20Windows/SeaToolsforWindows.exe
    ----------------------------------------
    Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 11.0.50709.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    ----------------------------------------
    System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18036 built by: FX45RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34108 built by: FX45W81RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
    ----------------------------------------
    System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
    ----------------------------------------
    SpawnCLR
    Assembly Version: 1.0.5030.18498
    Win32 Version: 1.2.0.10
    CodeBase: file:///C:/Program%20Files%20(x86)/Seagate/SeaTools%20for%20Windows/SpawnCLR.DLL
    ----------------------------------------
    CustomMarshalers
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/CustomMarshalers/v4.0_4.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

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

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
      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 00:43.
Find Us