1.    3 Weeks Ago #1
    Join Date : Oct 2017
    Posts : 5
    Windows 10

    Bsod kmode exception not handled


    Hello all,

    I have just experienced a BSOD on my Windows 10 desktop, which displayed the following error code:

    KMODE EXCEPTION NOT HANDLED

    I have attached the dump file zip, created immediately after the system restarted.

    I have made two hardware changes recently (2 weeks ago), and the system has been running rock solid, 24 hours per day since then, with no errors or BSOD's.

    1: I installed a new graphics card (driver is up to date)
    2: I upgraded my RAM from 8 GB to 16 GB

    Any help on what has caused this BSOD would be greatly appreciated,

    Many thanks,

    Andy.
    Bsod kmode exception not handled Attached Files
      My ComputerSystem Spec
  2.    3 Weeks Ago #2
    Join Date : Apr 2017
    Posts : 8,560
    windows 10 professional version 1607 build 14393.969 64 bit

    Hi studsr,

    Welcome to the BSOD forum.

    Open administrative command prompt and type or copy and paste these commands:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) 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
    4) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials
    5) Update Realtek NICDRV 8169 PCIe GBE Family Controller driver rt640x64.sys
    Updating a driver: Updating a driver. - Microsoft Community
    6) Make sure that there is no over clocking while troubleshooting.

    7) Sometimes there are problems in the bios that produce bsod.

    The BIOS: BIOS Version/Date American Megatrends Inc. 2501, 21/07/2014

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

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

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

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

    12) Please make a backup image with Macrium:

    Macrium Software | Macrium Reflect Free:
    Macrium Software | Your Image is Everything
    Macrium Software | Macrium Reflect Free

    13) 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

    14) Post a kernal memory dump into the thread using a one drive or drop box share link:
    memory dump file:
    %SystemRoot%\MEMORY.DMP or
    C:\Windows\MEMORY.DMP
    Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

    15) Run memtest86+ version 5.01 for at least 8 passes.
    Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.

    Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool

    The testing is done not by time but by passes.
    The more passes the better.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a pass when there is malfunctioning RAM.
    There is 16 GB of RAM on the computer with 4 GB modules on 4 DIMM.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    Again the more passes the better.
    If all RAM pass when tested 1 at a time after failing when tested together test the next DIMM with 1 RAM module for 8 or more passes. This will help to differentiate malfunctioning RAM from malfunctioning DIMM /Motherboard.

    Memtest86+ - Advanced Memory Diagnostic Tool
    Memtest86+ - Advanced Memory Diagnostic Tool

    Microsoft Community
    Memory problems. - Microsoft Community

    MemTest86+ - Test RAM Windows 10 BSOD Tutorials
    MemTest86+ - Test RAM BSOD Tutorials

    16) When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image of the results into the thread.

    17) Run HDTune on each drive
    http://www.hdtune.com/
    to check the health,
    scan for errors, no quick scan but full scan
    run a benchmark.

    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    the health,
    the error scan,
    the benchmark incl. following
    transfer rate,
    access time,
    burst rate,
    cpu usage.
    Take Screenshot in Windows 10 General Tips Tutorials

    17) Open administrative command prompt and type or copy and paste:
    chkdsk /x /r
    This may take many hours to run so plan to run overnight.
    18) Find the chkdsk report in the event.vwr and post the information into the thread using the information in this link: Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

    18) Open Ccleaner > windows tab > scroll to system and advanced > post an image into the thread

    19) In the left lower corner search type clean > open disk cleanup > click ok > scroll to system error memory dumps and system created Windows error reporting > post an image into the thread


    Code:
    Event[13516]:  Log Name: System  Source: Microsoft-Windows-Kernel-Boot  Date: 2017-10-18T14:35:43.685  Event ID: 29  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Desktop  Description: Windows failed fast startup with error status 0xC00000D4.
    Code:
    Event[13948]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:13.586  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13949]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:13.624  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13950]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:13.639  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13951]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:13.659  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13952]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:13.767  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13953]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:13.800  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13954]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:13.954  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13955]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:13.974  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13956]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:13.989  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13957]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:14.039  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13958]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:14.053  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13959]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:14.073  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13960]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:14.087  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13961]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:14.101  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13962]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:14.120  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13963]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:44:17.782  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13964]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:45:33.647  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13965]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:45:41.268  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13966]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:45:55.773  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13967]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:46:01.012  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13968]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:46:07.169  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.Event[13969]:  Log Name: System  Source: cdrom  Date: 2017-10-22T15:46:13.168  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: An error was detected on device \Device\CdRom0 during a paging operation.
    Code:
    Event[13947]:  Log Name: System  Source: Display  Date: 2017-10-22T13:52:45.818  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Desktop  Description: Display driver nvlddmkm stopped responding and has successfully recovered.
    rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver http://www.realtek.com.tw/downloads/...&GetDown=false

    Code:
    Name    [00000003] Realtek PCIe GBE Family ControllerAdapter Type    Ethernet 802.3
    Product Type    Realtek PCIe GBE Family Controller
    Installed    Yes
    PNP Device ID    PCI\VEN_10EC&DEV_8168&SUBSYS_84321043&REV_06\4&11EB9DBD&0&00E4
    Last Reset    25/10/2017 14:48
    Index    3
    Service Name    rt640x64
    IP Address    192.168.1.75, fe80::ece3:93ab:3f10:b12a
    IP Subnet    255.255.255.0, 64
    Default IP Gateway    192.168.1.254
    DHCP Enabled    Yes
    DHCP Server    192.168.1.254
    DHCP Lease Expires    26/10/2017 14:49
    DHCP Lease Obtained    25/10/2017 14:49
    MAC Address    ‪10:BF:48:BA:D4:68‬
    I/O Port    0x0000D000-0x0000D0FF
    Memory Address    0xF2104000-0xF2104FFF
    Memory Address    0xF2100000-0xF2103FFF
    IRQ Channel    IRQ 4294967293
    Driver    c:\windows\system32\drivers\rt640x64.sys (10.21.811.2017, 985.48 KB (1,009,128 bytes), 13/01/2016 09:21)
    Code:
    rt640x64    Realtek RT640 NT Driver    c:\windows\system32\drivers\rt640x64.sys    Kernel Driver    Yes    Manual    Running    OK    Normal    No    Yes
    Code:
    22/07/2017 12:42    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 124
    P2: 0
    P3: ffffa78a740f0028
    P4: be200000
    P5: 5110a
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\072217-22953-01.dmp
    \\?\C:\Windows\Temp\WER-62859-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA43A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA4E6.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA506.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_6cc67f41cadb4f3f83be681ecbf892bd9d279_00000000_cab_08bdc06c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: ba7d8518-c8df-4c40-920b-56060b456ad5
    Report Status: 2049
    Hashed bucket:22/07/2017 12:42    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 124
    P2: 0
    P3: ffffa78a740f0028
    P4: be200000
    P5: 5110a
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\072217-22953-01.dmp
    \\?\C:\Windows\Temp\WER-62859-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA43A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA4E6.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA506.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_6cc67f41cadb4f3f83be681ecbf892bd9d279_00000000_039da543
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: ba7d8518-c8df-4c40-920b-56060b456ad5
    Report Status: 4
    Hashed bucket:
    12/09/2017 12:20    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 124
    P2: 0
    P3: ffffca88098e9028
    P4: be200000
    P5: 5110a
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\091217-26687-01.dmp
    \\?\C:\Windows\Temp\WER-47625-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6651.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A87.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AA8.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_f4b5491a3188480b7ed52bdf88f875506d2053_00000000_cab_243ff250
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 7a587e4f-6123-476a-8688-eaf89206977f
    Report Status: 2049
    Hashed bucket:
    12/09/2017 12:18    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 124
    P2: 0
    P3: ffffca88098e9028
    P4: be200000
    P5: 5110a
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\091217-26687-01.dmp
    \\?\C:\Windows\Temp\WER-47625-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6651.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A87.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AA8.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_f4b5491a3188480b7ed52bdf88f875506d2053_00000000_03966c2d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 7a587e4f-6123-476a-8688-eaf89206977f
    Report Status: 4
    Hashed bucket:
    25/10/2017 13:56    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1e
    P2: ffffffffc000001d
    P3: fffff802a0b4769f
    P4: ffffc30117693028
    P5: ffffc30117692870
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\102517-24515-01.dmp
    \\?\C:\Windows\Temp\WER-100687-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD9C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD9D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERADAE.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_401193ba1b75e2f8381b87d6b6cc5deb61b2e41_00000000_cab_147f2095
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: a2f5858f-057c-48de-8e21-6f63dae032a6
    Report Status: 2049
    Hashed bucket:
    25/10/2017 13:51    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1e
    P2: ffffffffc000001d
    P3: fffff802a0b4769f
    P4: ffffc30117693028
    P5: ffffc30117692870
    P6: 10_0_15063
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\102517-24515-01.dmp
    \\?\C:\Windows\Temp\WER-100687-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD9C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD9D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERADAE.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_401193ba1b75e2f8381b87d6b6cc5deb61b2e41_00000000_03a6adf9
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: a2f5858f-057c-48de-8e21-6f63dae032a6
    Report Status: 4
    Hashed bucket:
    Code:
    01/06/2017 10:07    Windows Error Reporting    Fault bucket , type 0
    Event Name: ScriptedDiagFailure
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: Microsoft Corporation.BlueScreenDiagnostic.1.0
    P2: Default
    P3: 1.0.0.0
    P4: Default
    P5: 
    P6: 
    P7: 
    P8: 
    P9: 
    P10: 
    
    Attached files:
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Microsoft Corpor_90d593cc5dc8619a1b947a3e26af5ec0803fc0_00000000_1168a97b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 81e6562e-f9c5-45e6-b447-a06dfef61712
    Report Status: 4
    Hashed bucket:
    Code:
    01/06/2017 10:07    Windows Error Reporting    Fault bucket 126099534364, type 5
    Event Name: ScriptedDiagFailure
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: Microsoft Corporation.BlueScreenDiagnostic.1.0
    P2: Default
    P3: 1.0.0.0
    P4: Default
    P5: 
    P6: 
    P7: 
    P8: 
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAAA4.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_Microsoft Corpor_90d593cc5dc8619a1b947a3e26af5ec0803fc0_00000000_395cb11c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 81e6562e-f9c5-45e6-b447-a06dfef61712
    Report Status: 268435456
    Hashed bucket: 151632db3730fdd4fece4bf44251dd87
    Last edited by zbook; 3 Weeks Ago at 11:29.
      My ComputerSystem Spec
  3.    3 Weeks Ago #3
    Join Date : Oct 2017
    Posts : 5
    Windows 10
    Thread Starter

    Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>
      My ComputerSystem Spec
  4.    3 Weeks Ago #4
    Join Date : Oct 2017
    Posts : 5
    Windows 10
    Thread Starter

    Click image for larger version. 

Name:	Capture.JPG 
Views:	1 
Size:	54.7 KB 
ID:	160209
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
BSOD kmode exception not handled boot loop
Hi, today I got a very ridiculous problem with my computer. First of all, CPU, RAM & mainboard are new since january (System Infos in my profile) I was away for a few minutes after watching youtube videos and I saw that my pc was in a boot loop...
BSOD Crashes and Debugging
BSOD Kmode exception not handled
Hello everyone! I bought a new pc and when I did fresh install of Windows 10 on SSD, as soon as Windows loaded (after welcome screen) I got these errors: OneDriverSetup.exe cannot start WerFault.exe dllhost.exe and than BSOD with error...
BSOD Crashes and Debugging
BSOD KMODE Exception Not Handled Netio.Sys
Hello, and thanks very much for providing this service. I've been getting intermittent Netio.sys BSODs, typically while browsing using Chrome, or doing nothing. I was having a bunch of them in September, but they seemed to go away for a time. Now...
BSOD Crashes and Debugging
BSOD browsing on chrome - KMODE EXCEPTION NOT HANDLED (igdkmd64.sys)
Hi all. I had a previous problem which was different to this current one that just occurred, before it wouldn't boot sometimes or able to wake from sleep and get BSODs, my laptop has been working for last few months after a complete clean...
BSOD Crashes and Debugging
BSOD - Kmode Exception Not Handled - Netio.sys
Hello, I recently have been having a few BSOD's and they all point to netio.sys. Unfortunately it happens very random with me doing different tasks. I'm unable to duplicate it. I've have run a System File checker on it and that's come back...
BSOD Crashes and Debugging
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 20:15.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums