Windows 10: keep getting random BSOD after updating windows from 8.1 to windows 10 Solved

Page 1 of 7 123 ... LastLast
  1.    02 Sep 2017 #1

    keep getting random BSOD after updating windows from 8.1 to windows 10


    PC keeps crashing while playing game like elite dangerous and seems to crash randomly. I have tested numerous things like updating display adapter drivers 4 times, increased ram voltage ( recommended is 1.5 volts but since I have 4 ram sticks 1.5 might have been a strain so I bumped it to 1.55v) I have checked every single drivers for everything on this rig, everything is up to date... I really hope this pc has a hardware issue and not driver issue as honestly I am lost at this point... I have tried so many things its not even funny. I even contacted windows support and they couldn't find the problem either. Thanks for the help, I have been looking for a solution for over a month now and it is really getting irritating at this point. If there is any missing info, just ask and I will provide it to you :)
      My ComputerSystem Spec


  2. Posts : 8,733
    windows 10 professional version 1607 build 14393.969 64 bit
       03 Sep 2017 #2

    HI Maelstrom ,

    Welcome to Ten Forums.

    There were a lot of corruption events for the drive files.
    There were multiple misbehaving drivers.

    1) open administrative command prompt and type or copy and paste:
    2) chkdsk /x /f /r
    This may take many hours so plan to run overnight
    3) post the chkdsk event.vwr report into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    4) sfc /scannow
    5) dism /online /cleanup-image /restorehealth
    6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
    7) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.

    The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.

    If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.

    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller Download version 17.0.7.2

    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    NVIDIA

    8) Uninstall Avast AV
    Avast Uninstall Utility | Download aswClear for Avast Removal

    9) Turn on Windows defender

    10) Uninstall Malwarebytes using control panel

    11) Run HD Sentinel:Hard Disk Sentinel - HDD health and temperature monitoringWhen it has completed please use the Microsoft snipping to make images and post them into the thread.Take Screenshot in Windows 10 Windows 10 General Tips Tutorials Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    12) Update e1i63x64.sys
    Updating a driver: https://answers.microsoft.com/en-us/...=1436753520149

    13) Please update your system specs:
    How To Fill Out Your System Specs How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Please include: PSU, cooler, case, peripherals (mouse, keyboard, joystick) and anything attached to the computer by wireless or wired (printer, headset, xbox, etc)

    14) Make sure that there is no over clocking while troubleshooting.

    Sometimes there are problems in the bios that produce bsod.

    The bios in your computer:

    BIOS Version/Date Intel Corp. MCH8710H.86A.0047.2013.0606.1508, 6/6/2013

    15) Please check to see if this is the most up to date version.

    16) To ensure that there are no improper bios settings please reset the bios.

    Sometimes there can be failure to boot after resetting the bios.

    17) So please make sure your files are backed up.

    18) Please make a backup image with Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Your Image is Everything

    19) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings

    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    20) Run memtest86+ version 5.01 for at least 8 passes.

    This may take many hours so plan to run it overnight.Memtest86+ - Advanced Memory Diagnostic Tool
    When Memtest86+ has completed 8 or more runs use a camera or smart phone camera to take a picture and post an image into the thread.
    The computer has 32 GB RAM
    Memtest86+ version 5.01 is run not by time but by passes. The more passes the better.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hrs /GB RAM
    Just 1 error is a fail and you can abort testing.
    With 32 GB ram you can test 2 RAM modules at the same time to check the multi channel feature.
    All tests should be for at least 8 passes.
    For every test please use a camera or smart phone camera to take pictures and post images into the thread.
    Microsoft Community
    MemTest86+ - Test RAM Windows 10 BSOD Tutorials





    aswSnx.SYS avast! Virtualization Driver http://support.avast.com/


    e1i63x64.sys Intel(R) Gigabit Adapter NDIS 6.x driver https://downloadcenter.intel.com/

    mwac.sys Malwarebytes Web Access Control
    If it's blamed in a BSOD, it may be due to an outdated version of BitDefender 2016. Ensure that BitDefender is updated to the latest version. Fix came out around 02 July 2016
    Support: http://www.malwarebytes.org/support/consumer/
    Download: http://www.malwarebytes.org/downloads/

    nvlddmkm.sys nVidia Video drivers http://www.nvidia.com/Download/index.aspx
    Get from OEM for laptops

    Code:
    Event[4754]:  Log Name: System  Source: Ntfs  Date: 2017-08-19T12:08:25.016  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-EDOMB4N  Description: A corruption was discovered in the file system structure on volume ??.A corruption was found in a file system index structure.  The file reference number is 0x9000000000009.  The name of the file is "<unable to determine file name>".  The corrupted index attribute is ":$SII:$INDEX_ALLOCATION".
    Code:
    7/9/2017 6:21 PM    Windows Error Reporting    Fault bucket 0x1E_c000001d_BAD_IP_e1i63x64!RECEIVE::RxIndicateNBLs, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 01eea7ac-4d81-48ee-b171-7bd985e003de
    
    Problem signature:
    P1: 1e
    P2: ffffffffc000001d
    P3: fffff80e6f3def6f
    P4: ffff9500816f6b58
    P5: ffff9500816f63a0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\070917-24062-01.dmp
    \\?\C:\Windows\Temp\WER-162796-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDE11.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDEBD.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDECE.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_b352cab2fa5dd89609fca51e2844136969235f_00000000_cab_0a9b0689
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: eb447a0b-1d36-436b-8ba0-767aa3125baf
    Report Status: 268435456
    Hashed bucket:7/9/2017 4:24 AM    Windows Error Reporting    Fault bucket 0x1E_c000001d_BAD_IP_e1i63x64!RECEIVE::RxIndicateNBLs, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: a0984d36-bea0-4476-968b-ed8d22998a52
    
    Problem signature:
    P1: 1e
    P2: ffffffffc000001d
    P3: fffff80a33b8ef6f
    P4: ffffd000d2b7eb58
    P5: ffffd000d2b7e3a0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\070917-23078-01.dmp
    \\?\C:\Windows\Temp\WER-123968-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER167C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BFA.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C97.tmp.txt
    \\?\C:\Windows\Temp\WER6A9.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_16f947994205f4864497b5e94f2faca6f4dc15_00000000_cab_1babd0cb
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a2451133-4797-423d-8c51-f720fe99e262
    Report Status: 268435456
    Hashed bucket:
    Code:
    8/23/2017 11:38 AM    Windows Error Reporting    Fault bucket 0x1E_c0000005_R_nvlddmkm!CDisplayMgr::setVidPnSourceAddress, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: f6626ed2-c378-4deb-afc6-e1b0d8496860
    
    Problem signature:
    P1: 1e
    P2: ffffffffc0000005
    P3: fffff803b7a80df9
    P4: 0
    P5: ffffffffffffffff
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\082317-23937-01.dmp
    \\?\C:\Windows\Temp\WER-160843-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1048.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER122C.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER126C.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_f79d19d9c2d192160745459eec32787bffb8218_00000000_cab_15d53197
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 49cd2afb-890b-40f9-8cf8-46e98f7e9e2d
    Report Status: 268435456
    Hashed bucket:
    
    8/29/2017 10:33 AM    Windows Error Reporting    Fault bucket 0x3B_nvlddmkm!CNvLAllocation::freeDxgMdls, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 9f8966f3-3124-4c8e-b842-1d65a8c9bcb5
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff8016d2a3896
    P4: ffff810066428280
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\082917-21390-01.dmp
    \\?\C:\Windows\Temp\WER-167562-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2915.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2992.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29B2.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_e1c3cb32ed24257c4fc8a8879d3931f4054a91d_00000000_cab_1e6b739b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 6a0fb5d7-d328-44e6-bb24-873d2dc18050
    Report Status: 268435456
    Hashed bucket:
    Code:
    9/1/2017 7:52 PM    Windows Error Reporting    Fault bucket 0x193_DxgkrnlLiveDump:804_Status_0xC000009A_Driver_nvlddmkm_failed_DdiStartDevice_dxgkrnl!DxgCreateLiveDumpWithWdLogs, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: ea92b530-d900-418d-bb20-20cf29d77cc5
    
    Problem signature:
    P1: 193
    P2: 804
    P3: ffffffffc000009a
    P4: 108
    P5: fffff80150866ab8
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20170901-1552.dmp
    \\?\C:\Windows\Temp\WER-2316281-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B8E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B9E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7BAE.tmp.txt
    \\?\C:\Windows\Temp\WER9A23.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_1968d630809358ce3cf7a793e6592acc80d4_00000000_cab_20a39b5b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 1a728ebc-cfba-49b3-8e2b-8dfdd899886b
    Report Status: 268435456
    Hashed bucket:
    Code:
    Name    NVIDIA GeForce GTX 970PNP Device ID    PCI\VEN_10DE&DEV_13C2&SUBSYS_85081043&REV_A1\4&10C62994&0&0008
    Adapter Type    GeForce GTX 970, NVIDIA compatible
    Adapter Description    NVIDIA GeForce GTX 970
    Adapter RAM    (1,048,576) bytes
    Installed Drivers    nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um,nvwgf2um
    Driver Version    10.18.13.5906
    INF File    oem5.inf (Section044 section)
    Color Planes    Not Available
    Color Table Entries    4294967296
    Resolution    5040 x 1050 x 59 hertz
    Bits/Pixel    32
    Memory Address    0xF6000000-0xF6FFFFFF
    Memory Address    0xE0000000-0xEFFFFFFF
    Memory Address    0xF0000000-0xF1FFFFFF
    I/O Port    0x0000E000-0x0000E07F
    IRQ Channel    IRQ 16
    I/O Port    0x000003B0-0x000003BB
    I/O Port    0x000003C0-0x000003DF
    Memory Address    0xA0000-0xBFFFF
    Driver    c:\windows\system32\drivers\nvlddmkm.sys (10.18.13.5906, 10.71 MB (11,228,488 bytes), 9/1/2017 4:38 PM)
    Code:
    Name    [00000001] Intel(R) Ethernet Connection I217-VAdapter Type    Ethernet 802.3
    Product Type    Intel(R) Ethernet Connection I217-V
    Installed    Yes
    PNP Device ID    PCI\VEN_8086&DEV_153B&SUBSYS_20498086&REV_04\3&11583659&0&C8
    Last Reset    9/2/2017 10:52 PM
    Index    1
    Service Name    e1dexpress
    IP Address    192.168.2.11, fe80::ed3b:2954:283f:8421
    IP Subnet    255.255.255.0, 64
    Default IP Gateway    192.168.2.1
    DHCP Enabled    Yes
    DHCP Server    192.168.2.1
    DHCP Lease Expires    9/5/2017 10:59 PM
    DHCP Lease Obtained    9/2/2017 10:59 PM
    MAC Address    ‪7C:05:07:3B:3A:38‬
    Memory Address    0xF7100000-0xF711FFFF
    Memory Address    0xF7139000-0xF7139FFF
    IRQ Channel    IRQ 4294967291
    Driver    c:\windows\system32\drivers\e1d65x64.sys (12.15.25.6712, 543.99 KB (557,048 bytes), 8/15/2017 10:52 PM)
    Last edited by zbook; 03 Sep 2017 at 15:18.
      My ComputerSystem Spec

  3.    03 Sep 2017 #3

    alright thanks so much for all the info! Will do all of the following and really don't mind doing it anyways, bought a gaming laptop exactly for this porpuse! Anyways, is it possible the the cause would be my 3-4 year old harddrive?

    chkdsk /x /f /r gave the following messages The type of file system is NTFS. Cannot lock current drive.
    Chkdsk cannot run because the volume is in use by another process. Would you like to schedual this volume to be checked the next time your system restarts? Y/N

    I said yes, restarted the computer and nothing ever happends... same with windows image, file is corrupted, went to windows website to talk in live chat with the guys there and even they couldn't help me. Called the guys at the computer store (they are the ones who clean installed windows 10) and they told me they didn't leave the disk image because it was unstable or something like that... I highly doubt that is true and suspect it to be a reason to dick around but yeah, don't have a single easy solution at the moment...

    alright sfc /scannow works, pretty sure I did that one in the past and came clean
    okay so scan is done and came out as clean
    Last edited by Maelstrom; 03 Sep 2017 at 13:33.
      My ComputerSystem Spec


  4. Posts : 8,733
    windows 10 professional version 1607 build 14393.969 64 bit
       03 Sep 2017 #4

    1) Please post results from each step into the thread.
    2) Please use a camera or smart phone camera when necessary so that all results are posted.
    3) open administrative command prompt and type: chkdsk /scan
    4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
    5)
    Run Sea tools for windows on your drive using SMART, short and long generic tests:

    How to use SeaTools for Windows
    http://www.seagate.com/support/downl...ls-win-master/
    How to use SeaTools for Windows
    http://www.seagate.com/support/downloads/seatools/


    also run:
    Western Digital software and downloads:
    Software and Firmware Downloads | WD Support
      My ComputerSystem Spec

  5.    03 Sep 2017 #5

    Yeah will do, currently managed to make chkdsk /f /r /x work and its really slowly doing it. its been stuck at 12% for an hour now. Don't know if boot sector write safe option has any effect on this since I enabled that feature yesterday... so let me know if I need to disable that and restart the chkdsk if not I will leave it running and will update you on every single step later since I have things to do. Thanks alot fot the help, can't believe you guys do this for free, you are really life savers xD anyways I will be back later and will take photos once done with every step and will post a very long reply detailing every step will images if needed fo each step. might take a day or two depending on the speed of the harddrive scan since I can't do much about that...
      My ComputerSystem Spec


  6. Posts : 8,733
    windows 10 professional version 1607 build 14393.969 64 bit
       03 Sep 2017 #6

    It is normal behavior for chkdsk /x /f /r to remain at a number in the teens before it completes the evaluation and repair of the drive files. It may take many hours so plan to allow it to run as long as it needs to run to fix the drive corruption.


    Windows will generate a chkdsk report in event.vwr.
    This link has information on how to find the txt file to post into the thread:

    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
      My ComputerSystem Spec

  7.    03 Sep 2017 #7

    alright will check it once its done.. in a few days lol this harddrive has more than 500GB used up and it can hold 1TB so it shouldnt take that long. Before I sent it to the shop the harddrive had started writing something like 400GB of invisible files and the new windows fresh install fixed that by the looks of it so at least it has plenty of room to transfer all file contents to the other unused 500GB space.

    - alright welp scan completed itself will give you the results
    Last edited by Maelstrom; 03 Sep 2017 at 17:05.
      My ComputerSystem Spec

  8.    03 Sep 2017 #8

    - System
    - Provider
    [ Name] Microsoft-Windows-Wininit
    [ Guid] {206f6dea-d3c5-4d10-bc72-989f03c8b84b}
    [ EventSourceName] Wininit
    - EventID 1001
    [ Qualifiers] 16384
    Version 0
    Level 4
    Task 0
    Opcode 0
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2017-09-03T22:03:33.311294700Z
    EventRecordID 21915
    Correlation
    - Execution
    [ ProcessID] 0
    [ ThreadID] 0
    Channel Application
    Computer DESKTOP-EDOMB4N
    Security

    - EventData
    Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... 970240 file records processed. File verification completed. 8540 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 1290698 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Cleaning up 9 unused index entries from index $SII of file 0x9. Cleaning up 9 unused index entries from index $SDH of file 0x9. Cleaning up 9 unused security descriptors. Security descriptor verification completed. 160230 data files processed. CHKDSK is verifying Usn Journal... 40572320 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... 970224 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 119443702 free clusters processed. Free space verification is complete. Windows has scanned the file system and found no problems. No further action is required. 976247807 KB total disk space. 496960356 KB in 784176 files. 402836 KB in 160231 indexes. 0 KB in bad sectors. 1109807 KB in use by the system. 65536 KB occupied by the log file. 477774808 KB available on disk. 4096 bytes in each allocation unit. 244061951 total allocation units on disk. 119443702 allocation units available on disk. Internal Info: 00 ce 0e 00 4b 68 0e 00 c7 3e 19 00 00 00 00 00 ....Kh...>...... 06 0a 00 00 af 12 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.
    - System
    - Provider
    [ Name] Microsoft-Windows-Wininit
    [ Guid] {206f6dea-d3c5-4d10-bc72-989f03c8b84b}
    [ EventSourceName] Wininit
    - EventID 1001
    [ Qualifiers] 16384
    Version 0
    Level 4
    Task 0
    Opcode 0
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2017-09-03T18:41:50.181600400Z
    EventRecordID 21884
    Correlation
    - Execution
    [ ProcessID] 0
    [ ThreadID] 0
    Channel Application
    Computer DESKTOP-EDOMB4N
    Security

    - EventData
    Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... 970240 file records processed. File verification completed. 8540 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 1290712 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Cleaning up 334 unused index entries from index $SII of file 0x9. Cleaning up 334 unused index entries from index $SDH of file 0x9. Cleaning up 334 unused security descriptors. Security descriptor verification completed. 160237 data files processed. CHKDSK is verifying Usn Journal... 39581960 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 976247807 KB total disk space. 497235752 KB in 785223 files. 403028 KB in 160238 indexes. 0 KB in bad sectors. 1108783 KB in use by the system. 65536 KB occupied by the log file. 477500244 KB available on disk. 4096 bytes in each allocation unit. 244061951 total allocation units on disk. 119375061 allocation units available on disk. Internal Info: 00 ce 0e 00 69 6c 0e 00 f8 44 19 00 00 00 00 00 ....il...D...... 07 0a 00 00 af 12 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.

    - System
    - Provider
    [ Name] Microsoft-Windows-Wininit
    [ Guid] {206f6dea-d3c5-4d10-bc72-989f03c8b84b}
    [ EventSourceName] Wininit
    - EventID 1001
    [ Qualifiers] 16384
    Version 0
    Level 4
    Task 0
    Opcode 0
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2017-07-13T16:30:47.570838900Z
    EventRecordID 2603
    Correlation
    - Execution
    [ ProcessID] 0
    [ ThreadID] 0
    Channel Application
    Computer DESKTOP-EDOMB4N
    Security

    - EventData
    Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... 952576 file records processed. File verification completed. 7337 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 1267872 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Cleaning up 631 unused index entries from index $SII of file 0x9. Cleaning up 631 unused index entries from index $SDH of file 0x9. Cleaning up 631 unused security descriptors. Security descriptor verification completed. 157649 data files processed. CHKDSK is verifying Usn Journal... 38243224 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... 952560 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 123253414 free clusters processed. Free space verification is complete. Windows has scanned the file system and found no problems. No further action is required. 976247807 KB total disk space. 481749088 KB in 777241 files. 396504 KB in 157650 indexes. 0 KB in bad sectors. 1088555 KB in use by the system. 65536 KB occupied by the log file. 493013660 KB available on disk. 4096 bytes in each allocation unit. 244061951 total allocation units on disk. 123253415 allocation units available on disk. Internal Info: 00 89 0e 00 1f 43 0e 00 4a 07 19 00 00 00 00 00 .....C..J....... c7 09 00 00 6e 12 00 00 00 00 00 00 00 00 00 00 ....n........... Windows has finished checking your disk. Please wait while your computer restarts.


    edit: I went into system information and saw the conflicts/sharing tab, this is the info it gives in case you need it as I think there might be some useful stuff in here...

    Attachment 151786 Attachment 151787
      My ComputerSystem Spec


  9. Posts : 8,733
    windows 10 professional version 1607 build 14393.969 64 bit
       03 Sep 2017 #9

    Okay. Perform steps 14 -19 then 7 - 10, then 12, then perform the others in any order. Take advantage of the evening/night as the Memtest86+ test can be started in the evening. See the typical time period for testing.
      My ComputerSystem Spec

  10.    03 Sep 2017 #10

    could you shed some light on the bios because I have been confused about this one since there doesn't seem to be a version for it that supports windows 10... it seems like it stops at 8.1.
    Nevermind, just finally understood how the download page works lol not the most obvious UI...
      My ComputerSystem Spec


 
Page 1 of 7 123 ... LastLast

Related Threads
BSOD When Updating to Windows 10 Anniversary in BSOD Crashes and Debugging
Hi, I am trying to update to Windows 10 Anniversary but I keep getting a bluescreen error. 103957 103707 http://i.imgur.com/rJ1y4tl.jpg I've retried it a few times and keep getting the IRQ error in the image above... which I think is a...
Hey everyone, I experienced this issue yesterday when attempting to upgrade to the Windows 10 Anniversary Update. About 70% through, a Blue Screen appeared with the error code IRQL_NOT_LESS_OR_EQUAL. I have used Bluescreenview to find the address...
Hi support! Since last sunday 29 of May, I have had the BSOD crashes 4 - 8 times a day. I have rolled back, repaired and reinstalled my windows 10 and still get more or less the same errors (I think). I tried with sfc /scannow only for it to...
Random BSOD Windows 10 in BSOD Crashes and Debugging
Hey Guys, since a few days i'm facing with random bluescreens appearing on my notebook. I hope anyone of you can help me! Note: I noticed that not everytime when a BSOD appears (with the same error message) a dump file is created. So I got...
BSOD while updating to Windows 10 in Installation and Upgrade
Greetings. So I've been trying to update to WIN 10 a lot of times since it came out. Unfortunately the update fails around 80-90% and a BSOD shows up. The BSOD says something like Kernel Inpage Error. I've tried to update from Windows Update, the...
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 04:11.
Find Us