Windows 10: BSOD in Desktop

Page 7 of 10 FirstFirst ... 56789 ... LastLast
  1. axe0's Avatar
    Posts : 11,223
    Windows 10 Pro
       23 Jul 2016 #61

    Do you need the partition/drive Disco?
      My ComputersSystem Spec


  2. Posts : 52
    Microsoft Windows 10 Pro 64-bit
       23 Jul 2016 #62

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

  3. axe0's Avatar
    Posts : 11,223
    Windows 10 Pro
       23 Jul 2016 #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 ComputersSystem Spec


  4. Posts : 52
    Microsoft Windows 10 Pro 64-bit
       23 Jul 2016 #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 ComputerSystem Spec

  5. axe0's Avatar
    Posts : 11,223
    Windows 10 Pro
       23 Jul 2016 #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 ComputersSystem Spec


  6. Posts : 52
    Microsoft Windows 10 Pro 64-bit
       23 Jul 2016 #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 ComputerSystem Spec

  7. axe0's Avatar
    Posts : 11,223
    Windows 10 Pro
       23 Jul 2016 #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 ComputersSystem Spec


  8. Posts : 52
    Microsoft Windows 10 Pro 64-bit
       24 Jul 2016 #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 ComputerSystem Spec

  9. axe0's Avatar
    Posts : 11,223
    Windows 10 Pro
       24 Jul 2016 #69

    The log of drive G is clean too
      My ComputersSystem Spec


  10. Posts : 52
    Microsoft Windows 10 Pro 64-bit
       24 Jul 2016 #70

    here is the log of drive G ,after add J: to G:
    It look clean too..
      My ComputerSystem Spec


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

Related Threads
Hi there, My PC is reasonably mature now and after getting a few BSOD's I just thought I was getting a little unlucky every so often. However they are now increasing in frequency and I can't seem to see a recurring theme in-between them. ...
Solved BSOD - windows 10 frozen & no desktop in BSOD Crashes and Debugging
This is my first problem with Win 10 and its Serious! Windows won't re-load properly, so no access to files, error logs or anything. I upgraded to W10 from W7 on a 5-year old desktop computer about 2 months ago. (W7 often went blue-screen on...
Sorry - see Forum BSOD.
Solved BSoD Memory Management at Desktop + Ingame in BSOD Crashes and Debugging
Hey guys, I built a new PC and now I have some troubles getting it to work. I get so many bluescreens, most of them appear when I am on the desktop a few minutes after the PC starts (sometimes I can start playing games, but after a few minutes...
Solved 10041 flashing screen between desktop and BSOD in BSOD Crashes and Debugging
I loaded 10041 over an 8.1 installation. No visible errors. Login was fine. As soon as the desktop starts to load, there is a flashing back and forth with the BSOD. The flashing to the BSOD occurs before any of the icons can load. (making the log...
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 17:40.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums