BSOD in Desktop

Page 7 of 10 FirstFirst ... 56789 ... LastLast

  1. Posts : 14,901
    Windows 10 Pro
       #61

    Do you need the partition/drive Disco?
      My Computers


  2. Posts : 52
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       #62

    Sorry, dont understand. what disco are you talk about ?
      My Computer


  3. Posts : 14,901
    Windows 10 Pro
       #63

    From your chkdsk log
    Code:
    Chkdsk was executed in read/write mode.  
    
    Checking file system on G:
    The type of the file system is NTFS.
    Volume label is Disco (500Gb).
    Write failure with status 0xc0000015 at offset 0x7471060200 for 0x200 bytes.
    Do you need this partition/drive?
      My Computers


  4. Posts : 52
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       #64

    Ho, yes i get it.
    Yes , what i have in disk G: is very important. i Need it.
    Why you ask that,Should i buy another and make copy?

    Have another BSOD with >critical process died>.
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #65

    The same write failure was present again in the log, the error means NT_STATUS_NONEXISTENT_SECTOR what I believe simply means bad sector(s).

    I would like you to try something.
    Shrink the G: partition a little (size does not matter), I believe the bad sector(s) is/are at the end of the partition.
    Format the new partition, run chkdsk with parameter /r on it and upload the chkdsk log.

    When posting new BSODs, run the DM Log Collector, a text file means nothing to us in most cases.
      My Computers


  6. Posts : 52
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       #66

    By the way, what ntoskrnl.exe driver is ?
    why it show so many time ?

    there it is the log
    Im running the same command chkdsk /r, in drive G 'Disco' so you can see.
    Thank you!
      My Computer


  7. Posts : 14,901
    Windows 10 Pro
       #67

    Ntoskrnl.exe is a file from the Windows Kernel. Windows files are blamed by default when there is nothing else to be blamed in the stack. This is a reason why analysts are necessary, to find the root cause as Windows files are never the real cause.

    That looks like a clean log :)
    Please format the partition again, add it to the G: partition and run chkdsk with parameter /r again on it.
      My Computers


  8. Posts : 52
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       #68

    there is the log of drive G, that i did last night.

    I will do what you say now, format and add J: to G:
    Last edited by rstudio; 24 Jul 2016 at 04:02.
      My Computer


  9. Posts : 14,901
    Windows 10 Pro
       #69

    The log of drive G is clean too :)
      My Computers


  10. Posts : 52
    Microsoft Windows 10 Pro 64-bit
    Thread Starter
       #70

    here is the log of drive G ,after add J: to G:
    It look clean too..
      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 16:39.
Find Us




Windows 10 Forums