Windows 10: NTOSKRNL.EXE and other BSODs even after clean windows installation

Discus and support NTOSKRNL.EXE and other BSODs even after clean windows installation in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello All, Have been having various problems with my windows 10 (even after a fresh install last night) and PC lately as it has been constantly blue... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by hyperphoenix, Nov 29, 2017.

  1. NTOSKRNL.EXE and other BSODs even after clean windows installation


    Hello All,

    Have been having various problems with my windows 10 (even after a fresh install last night) and PC lately as it has been constantly blue screening with various errors.

    I have run memtest for 9 and a half hours and didn't find any issues - have updated all my old drivers and even tried uninstalling certain programs to try and fix this issue, which is still happening.

    Here is a link to some of my minidumps - most seemed to be the cause of ntoskrnl.exe, win32kbase.sys and cmudacmudaxp.sys.

    I feel like the BSOD's usually occur when I'm playing music or listening to something through discord, google chrome etc.

    Minidumps: https://www.dropbox.com/sh/7r7e4yh7y51p540/AADj6U1Immie...

    PC specs are 4770k (not overclocked), MSI B85-e45, 16gb ram (ripjaws), Sandisk SSD and Seagate barracuda HDD, Asus Xonar DGX, Galax gtx 1060 6gb and a 520w Antec PSU with 80+ Bronze efficiency.

    Cheers for any help

    :)
     
    hyperphoenix, Nov 29, 2017
    #1
  2. chadrada Win User

    Windows 10 ntoskrnl.exe bsod

    A clean install doesn't work either, I have done several clean installs, checked all my stuff, replaced my video card, and I still get the ntoskrnl.exe bsod. I agree with you, it is a Microsoft problem in the software.
     
    chadrada, Nov 29, 2017
    #2
  3. Mauldoon Win User
    Blue screen crashes with new pc

    It has been about 2 hours since doing a clean boot and I received a new BSOD:

    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)

    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802E8DF8834, 0x0, 0xFFFFFFFFFFFFFFFF)

    Error: KMODE_EXCEPTION_NOT_HANDLED

    file path: C:\WINDOWS\system32\ntoskrnl.exe

    BlueScreenView highlights ntoskrnl.exe and partmgr.sys as the cause.

    Here is the new Dump file Dump.zip
     
    Mauldoon, Nov 29, 2017
    #3
  4. philc43 Win User

    NTOSKRNL.EXE and other BSODs even after clean windows installation

    Hello and welcome to TenForums *Smile

    Just so you know, we rely on more than the mini-dumps to help us with the analysis of crashes involving the BSOD. That is why we ask all posters to provide the full set of log files as requested at the top of the page. Thanks!
     
    philc43, Nov 29, 2017
    #4
  5. Zip file of full set of logs has been added, thanks for the response
     
    hyperphoenix, Nov 29, 2017
    #5
  6. philc43 Win User
    There are a number of problems revealed by the logs and crash dumps. Lets take things step by step.

    The BSOD could be memory corruption caused by a faulty driver or possibly the RAM itself. You have tested the RAM but it is not time that counts it is the number of passes. Make sure you have over 8 passes of the Memtest86+ to be sure you have tested the RAM for faults. This could take as much as 24 hours to complete.




    NTOSKRNL.EXE and other BSODs even after clean windows installation [​IMG]
    Diagnostic Test
    NTOSKRNL.EXE and other BSODs even after clean windows installation [​IMG]
    RAM TEST

    NTOSKRNL.EXE and other BSODs even after clean windows installation [​IMG]
    Run MemTest86+ - Test RAM - Windows 10 Forums


    NTOSKRNL.EXE and other BSODs even after clean windows installation [​IMG]
    Note
    NTOSKRNL.EXE and other BSODs even after clean windows installation [​IMG]


    MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

    Make a photo of the result and post it.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat so that you find the faulty one(s).


    The one driver which is highlighted in the crash dumps is cmudaxp.sys (dated Tue Jun 2 10:11:20 2015 (556D7338)). Please try to update this ASUS Xonar DGX Audio Device if you can find a newer driver from the device manufacturer.


    Other things we can work on later are the fact that update to W10 Ver 1709 is continually failing.

    There is also file corruption on Volume E:\ but I am not sure what drive that is?
     
    philc43, Nov 29, 2017
    #6
  7. NTOSKRNL.EXE and other BSODs even after clean windows installation [​IMG]
    Run MemTest86+ - Test RAM - Windows 10 Forums


    NTOSKRNL.EXE and other BSODs even after clean windows installation [​IMG]
    Note
    NTOSKRNL.EXE and other BSODs even after clean windows installation [​IMG]


    MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

    Make a photo of the result and post it.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat so that you find the faulty one(s).


    The one driver which is highlighted in the crash dumps is cmudaxp.sys (dated Tue Jun 2 10:11:20 2015 (556D7338)). Please try to update this ASUS Xonar DGX Audio Device if you can find a newer driver from the device manufacturer.


    Other things we can work on later are the fact that update to W10 Ver 1709 is continually failing.

    There is also file corruption on Volume E:\ but I am not sure what drive that is? I will run the memtest overnight again and report back - I have done this for a total of 5 passes over two tests with no errors but will give it another go. Computer has been stable for the last few hours which is strange as I haven't changed anything. I did do a clean install of the windows 10 version of cmudaxp.sys just today (latest version) so i'm not sure why it's still playing up. My SSD is the local disk C: and my storage HDD is labled G: so i'm not sure what on earth volume E is - might've been the USB I was using for memtest or something earlier today.
     
    hyperphoenix, Nov 29, 2017
    #7
  8. NTOSKRNL.EXE and other BSODs even after clean windows installation

    8 passes of memtest with no worries or errors has been completed
     
    hyperphoenix, Nov 30, 2017
    #8
  9. zbook New Member
    For Memtest86_ version 5.01 please use a camera or smart phone camera to take a picture and post an image into the thread.
     
    zbook, Nov 30, 2017
    #9
  10. Still getting blue screens but this time it's only from NTOSKRNL.EXE not anything else - didn't take a photo of the memtest results unfortunately
     
    hyperphoenix, Nov 30, 2017
    #10
  11. zbook New Member
    It is best to post images of all tests into the thread so that they can be verified.
    Sometimes it takes passes into the 20s to find malfunctioning RAM.
    With multiple misbehaving hardware drivers it may be necessary to repeat the RAM testing.

    The logs indicated that the drive has bad blocks.
    Also corruption of the Master File Table (MFT) was reported in the logs many times.
    This included multiple languages.

    1) Run HD Tune on all drives: (free version)
    HD Tune website
    2) Post into the thread images of:
    Health tests (SMART)
    Benchmark
    Full error scan
    The error scan can be run overnight.
    Please make sure that you post the 3 images into the thread for verification.
    Take Screenshot in Windows 10 General Tips Tutorials

    3) Open administrative command prompt and type or copy and paste:
    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) chkdsk /x /f /r C:
    This may take many hours so plan to run overnight.
    8) Use the information in this link to find the chkdsk report in the event viewer and post into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
    9) run chkdsk /x /f /r on all drives changing C: to the applicable drive letter.

    10) Uninstall the Nvidia graphics driver using DDU.
    Official Display Driver Uninstaller DDU Download
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    Re-install from MSI website.
    If a suitable driver is not available on the MSI website you can use the Nvidia website.
    Make sure that "clean install" is checked and only install the graphics and PhysX drivers.

    11) Using device manager update rt640x64.sys
    Updating a driver. - Microsoft Community
    rt640x64 Realtek RT640 NT Driver c:\windows\system32\drivers\rt640x64.sys

    12) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials

    Code: Realtek PCIe GBE Family Controller Adapter Type Ethernet 802.3 Product Type Realtek PCIe GBE Family Controller Installed Yes PNP Device ID PCI\VEN_10EC&DEV_8168&SUBSYS_78171462&REV_0C\4&2BCECA6C&0&00E2 Last Reset 11/30/2017 6:16 PM Index 0 Service Name rt640x64 IP Address 10.0.0.45, fe80::441e:c43b:2414:aed3, fd55:cd2:c168:0:79d3:b81c:6d2d:8336, fd55:cd2:c168:0:441e:c43b:2414:aed3 IP Subnet 255.255.255.0, 64, 128, 64 Default IP Gateway 10.0.0.138 DHCP Enabled Yes DHCP Server 10.0.0.138 DHCP Lease Expires 11/30/2017 9:38 PM DHCP Lease Obtained 11/30/2017 8:38 PM MAC Address ‪44:8A:5B:97:A4:FD‬ I/O Port 0x0000D000-0x0000D0FF Memory Address 0xF7100000-0xF7100FFF Memory Address 0xF2100000-0xF2103FFF IRQ Channel IRQ 4294967293 Driver c:\windows\system32\drivers\rt640x64.sys (10.23.1003.2017, 986.96 KB (1,010,648 bytes), 11/28/2017 7:04 PM)[/quote] Code: Name NVIDIA GeForce GTX 1060 6GB PNP Device ID PCI\VEN_10DE&DEV_1C03&SUBSYS_11D710DE&REV_A1\4&1610F4F8&0&0008 Adapter Type GeForce GTX 1060 6GB, NVIDIA compatible Adapter Description NVIDIA GeForce GTX 1060 6GB Adapter RAM (1,048,576) bytes Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumd.dll Driver Version 23.21.13.8831 INF File oem22.inf (Section136 section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1080 x 144 hertz Bits/Pixel 32 Memory Address 0xF6000000-0xF70FFFFF Memory Address 0xE0000000-0xFEAFFFFF Memory Address 0xF0000000-0xF1FFFFFF I/O Port 0x0000E000-0x0000EFFF IRQ Channel IRQ 16 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_c791f781cd94491f\nvlddmkm.sys (23.21.13.8831, 16.20 MB (16,989,296 bytes), 11/30/2017 4:11 PM)[/quote] Code: The device, \Device\Harddisk1\DR1, has a bad block.[/quote] Code: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: 11/29/2017 5:21 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff800eb0b65ad P4: ffff9b815a97a878 P5: ffff9b815a97a0b0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112917-4765-01.dmp \\?\C:\Windows\TEMP\WER-5609-0.sysdata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_6b3f26be193f4df83dd8d718aa5ea83d4465b6a_00000000_cab_0e943066 Analysis symbol: Rechecking for solution: 0 Report Id: efb21e96-c5e8-436b-83eb-3a6a43d1c9ad Report Status: 2048 Hashed bucket: 11/29/2017 5:21 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff800eb0b65ad P4: ffff9b815a97a878 P5: ffff9b815a97a0b0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112917-4765-01.dmp \\?\C:\Windows\TEMP\WER-5609-0.sysdata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_6b3f26be193f4df83dd8d718aa5ea83d4465b6a_00000000_02c82385 Analysis symbol: Rechecking for solution: 0 Report Id: efb21e96-c5e8-436b-83eb-3a6a43d1c9ad Report Status: 4 Hashed bucket: 11/28/2017 10:10 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffffa700e2ff25e0 P4: ffffa700e2ff2538 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112817-3640-01.dmp \\?\C:\Windows\Temp\WER-5500-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_925de5408f8324b41f1bc8a8cbe5fc405996f721_00000000_cab_0e981d3c Analysis symbol: Rechecking for solution: 0 Report Id: 8b0396d8-4373-42bd-8970-12ef4bea4dbe Report Status: 2050 Hashed bucket: 11/28/2017 10:10 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffffa700e2ff25e0 P4: ffffa700e2ff2538 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112817-3640-01.dmp \\?\C:\Windows\Temp\WER-5500-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_925de5408f8324b41f1bc8a8cbe5fc405996f721_00000000_02c41cbf Analysis symbol: Rechecking for solution: 0 Report Id: 8b0396d8-4373-42bd-8970-12ef4bea4dbe Report Status: 4 Hashed bucket: 11/30/2017 2:35 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8032ceacb7b P4: 0 P5: ffffffffffffffff P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4875-01.dmp \\?\C:\Windows\TEMP\WER-6140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_dd6f2c16f76c5ab15d855ea5aa79478b02f7ac_00000000_cab_15c4516b Analysis symbol: Rechecking for solution: 0 Report Id: 025ccd3e-b340-4bec-b7ff-26f5f331b227 Report Status: 2050 Hashed bucket: 11/30/2017 2:35 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8032ceacb7b P4: 0 P5: ffffffffffffffff P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4875-01.dmp \\?\C:\Windows\TEMP\WER-6140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_dd6f2c16f76c5ab15d855ea5aa79478b02f7ac_00000000_02f04f0a Analysis symbol: Rechecking for solution: 0 Report Id: 025ccd3e-b340-4bec-b7ff-26f5f331b227 Report Status: 4 Hashed bucket: 11/30/2017 6:36 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff806992ce3cc P4: 0 P5: ffffffffffffffff P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4843-01.dmp \\?\C:\Windows\TEMP\WER-5968-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_234593014e3036eda284e2e1f5e841b37d738_00000000_cab_123856ea Analysis symbol: Rechecking for solution: 0 Report Id: 145f1384-e585-4b4d-9b67-cb0b0495cbd3 Report Status: 2048 Hashed bucket: 11/30/2017 6:36 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff806992ce3cc P4: 0 P5: ffffffffffffffff P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4843-01.dmp \\?\C:\Windows\TEMP\WER-5968-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_234593014e3036eda284e2e1f5e841b37d738_00000000_02f847e6 Analysis symbol: Rechecking for solution: 0 Report Id: 145f1384-e585-4b4d-9b67-cb0b0495cbd3 Report Status: 4 Hashed bucket: 11/30/2017 1:17 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: ffff8142f69d512c P4: ffffe401ca5bafb0 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-7890-01.dmp \\?\C:\Windows\TEMP\WER-9343-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_bf3147359c6a6d3d86662e7f54348a1858b55c_00000000_cab_0d1835d5 Analysis symbol: Rechecking for solution: 0 Report Id: 22a6e423-754a-473b-b4b9-452a27bbd324 Report Status: 2048 Hashed bucket: 11/30/2017 1:17 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: ffff8142f69d512c P4: ffffe401ca5bafb0 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-7890-01.dmp \\?\C:\Windows\TEMP\WER-9343-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_bf3147359c6a6d3d86662e7f54348a1858b55c_00000000_02f03364 Analysis symbol: Rechecking for solution: 0 Report Id: 22a6e423-754a-473b-b4b9-452a27bbd324 Report Status: 4 Hashed bucket: 11/29/2017 1:50 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: ffffd203bce53c9b P4: ffff9500fe3b6fb0 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112917-4437-01.dmp \\?\C:\Windows\TEMP\WER-5218-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_e23e1435463cc9d34bdcb5af728826bc452024c9_00000000_cab_0ee8222e Analysis symbol: Rechecking for solution: 0 Report Id: 43e3ba6f-4c33-4e9e-bce6-9d0e92a16db1 Report Status: 2050 Hashed bucket: 11/29/2017 1:50 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: ffffd203bce53c9b P4: ffff9500fe3b6fb0 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112917-4437-01.dmp \\?\C:\Windows\TEMP\WER-5218-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_e23e1435463cc9d34bdcb5af728826bc452024c9_00000000_02d01f6e Analysis symbol: Rechecking for solution: 0 Report Id: 43e3ba6f-4c33-4e9e-bce6-9d0e92a16db1 Report Status: 4 Hashed bucket: 11/28/2017 3:07 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff80187c92a25 P4: ffffcc00ec35e9a0 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112917-4781-01.dmp \\?\C:\Windows\Temp\WER-6031-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_64e19cf349d3ba7d56dfccfed77a8132de867c5_00000000_cab_0df43c7c Analysis symbol: Rechecking for solution: 0 Report Id: 17939be1-d572-4113-a2cd-d0c5aa1c8792 Report Status: 2048 Hashed bucket: 11/28/2017 3:06 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff80187c92a25 P4: ffffcc00ec35e9a0 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112917-4781-01.dmp \\?\C:\Windows\Temp\WER-6031-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_64e19cf349d3ba7d56dfccfed77a8132de867c5_00000000_02c42431 Analysis symbol: Rechecking for solution: 0 Report Id: 17939be1-d572-4113-a2cd-d0c5aa1c8792 Report Status: 4 Hashed bucket: 11/30/2017 5:15 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff802a8e4990c P4: ffff8580a04e4c30 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5328-01.dmp \\?\C:\Windows\TEMP\WER-6609-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_91b06959b942df64398ca068e2d72dbe8b7bca46_00000000_cab_0b485236 Analysis symbol: Rechecking for solution: 0 Report Id: 1d5ee1a5-66c6-4abb-829f-72d78f293d73 Report Status: 2048 Hashed bucket: 11/30/2017 5:15 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff802a8e4990c P4: ffff8580a04e4c30 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5328-01.dmp \\?\C:\Windows\TEMP\WER-6609-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_91b06959b942df64398ca068e2d72dbe8b7bca46_00000000_02e84584 Analysis symbol: Rechecking for solution: 0 Report Id: 1d5ee1a5-66c6-4abb-829f-72d78f293d73 Report Status: 4 Hashed bucket: 11/29/2017 2:29 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: ffff95a52fecd058 P3: 0 P4: fffff802e58efe57 P5: 2 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-3781-01.dmp \\?\C:\Windows\TEMP\WER-4390-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_231219e572c4a7705dcde62494dccce72473ed99_00000000_cab_0e681e65 Analysis symbol: Rechecking for solution: 0 Report Id: 189f5485-5269-42a4-8fa0-322fbca9a02b Report Status: 2050 Hashed bucket: 11/29/2017 2:29 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: ffff95a52fecd058 P3: 0 P4: fffff802e58efe57 P5: 2 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-3781-01.dmp \\?\C:\Windows\TEMP\WER-4390-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_231219e572c4a7705dcde62494dccce72473ed99_00000000_02c81c80 Analysis symbol: Rechecking for solution: 0 Report Id: 189f5485-5269-42a4-8fa0-322fbca9a02b Report Status: 4 Hashed bucket: 11/29/2017 12:56 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: ffffc792796184a8 P3: 0 P4: fffff800f805fe57 P5: 2 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112917-4640-01.dmp \\?\C:\Windows\TEMP\WER-5281-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_42b2be4ded3e5325735c622467b98a4de1ce094_00000000_cab_0ee4225c Analysis symbol: Rechecking for solution: 0 Report Id: fa7ecee5-fb6c-4995-9bb2-347d65d37edf Report Status: 2050 Hashed bucket: 11/29/2017 12:56 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: ffffc792796184a8 P3: 0 P4: fffff800f805fe57 P5: 2 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112917-4640-01.dmp \\?\C:\Windows\TEMP\WER-5281-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_42b2be4ded3e5325735c622467b98a4de1ce094_00000000_02c42088 Analysis symbol: Rechecking for solution: 0 Report Id: fa7ecee5-fb6c-4995-9bb2-347d65d37edf Report Status: 4 Hashed bucket: 11/28/2017 12:40 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7f P2: 8 P3: ffffde0182d9db30 P4: fff7de0185416710 P5: fffff80158bc435f P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112817-4250-01.dmp \\?\C:\Windows\Temp\WER-4968-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7f_6857a2d47f663d785e9eb04f76655d68bc1fbd8_00000000_cab_0e041ccf Analysis symbol: Rechecking for solution: 0 Report Id: 5777f045-2960-4e4b-8d00-0709a4510f14 Report Status: 2050 Hashed bucket: 11/28/2017 12:40 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7f P2: 8 P3: ffffde0182d9db30 P4: fff7de0185416710 P5: fffff80158bc435f P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\112817-4250-01.dmp \\?\C:\Windows\Temp\WER-4968-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7f_6857a2d47f663d785e9eb04f76655d68bc1fbd8_00000000_02c01bf4 Analysis symbol: Rechecking for solution: 0 Report Id: 5777f045-2960-4e4b-8d00-0709a4510f14 Report Status: 4 Hashed bucket: 11/30/2017 6:23 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: 100000000ae0 P3: 2 P4: 0 P5: fffff802116c84fe P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4546-01.dmp \\?\C:\Windows\TEMP\WER-5515-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_d1aa30f6d478f91a24d4cf832cf4e18727e5a76_00000000_cab_124c4853 Analysis symbol: Rechecking for solution: 0 Report Id: 4e1a0f64-32ba-483e-800a-894cd6c87679 Report Status: 2048 Hashed bucket: 11/30/2017 6:23 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: 100000000ae0 P3: 2 P4: 0 P5: fffff802116c84fe P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4546-01.dmp \\?\C:\Windows\TEMP\WER-5515-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_d1aa30f6d478f91a24d4cf832cf4e18727e5a76_00000000_02f8469e Analysis symbol: Rechecking for solution: 0 Report Id: 4e1a0f64-32ba-483e-800a-894cd6c87679 Report Status: 4 Hashed bucket: 11/30/2017 5:50 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: ffff8f82fb790b00 P3: 2 P4: 0 P5: fffff8027ef87cdd P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5140-01.dmp \\?\C:\Windows\TEMP\WER-5937-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_f73ac2d6fde234b9cac290438cb96378e3199_00000000_cab_19785ddf Analysis symbol: Rechecking for solution: 0 Report Id: 89afa42e-aea2-49a1-a187-fd7680ac4e7f Report Status: 2050 Hashed bucket: 11/30/2017 5:50 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: ffff8f82fb790b00 P3: 2 P4: 0 P5: fffff8027ef87cdd P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5140-01.dmp \\?\C:\Windows\TEMP\WER-5937-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_f73ac2d6fde234b9cac290438cb96378e3199_00000000_02f85989 Analysis symbol: Rechecking for solution: 0 Report Id: 89afa42e-aea2-49a1-a187-fd7680ac4e7f Report Status: 4 Hashed bucket: 11/30/2017 12:39 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: ffffd68b0fb727a0 P3: 2 P4: 0 P5: fffff8023aa0fdc1 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5187-01.dmp \\?\C:\Windows\TEMP\WER-5750-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_82e4fe131faa31c0e1524d18d1f3f5f550428687_00000000_cab_0d002b84 Analysis symbol: Rechecking for solution: 0 Report Id: 4a3f134b-9bef-4402-9cf4-22a46c8fb7eb Report Status: 2050 Hashed bucket: 11/30/2017 12:39 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: ffffd68b0fb727a0 P3: 2 P4: 0 P5: fffff8023aa0fdc1 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5187-01.dmp \\?\C:\Windows\TEMP\WER-5750-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_82e4fe131faa31c0e1524d18d1f3f5f550428687_00000000_02f02932 Analysis symbol: Rechecking for solution: 0 Report Id: 4a3f134b-9bef-4402-9cf4-22a46c8fb7eb Report Status: 4 Hashed bucket: 11/30/2017 1:42 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: ffff8581ca4aae50 P3: ffff8581ca4aa6d6 P4: 3701a8 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5406-01.dmp \\?\C:\Windows\TEMP\WER-6171-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c1_ede2218cb5ee25716b8a331d6162b6f1d4832ef3_00000000_cab_0c942c5f Analysis symbol: Rechecking for solution: 0 Report Id: 9438cc0f-2dba-489b-9409-7c63038fb0f9 Report Status: 2050 Hashed bucket: 11/30/2017 1:42 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: ffff8581ca4aae50 P3: ffff8581ca4aa6d6 P4: 3701a8 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5406-01.dmp \\?\C:\Windows\TEMP\WER-6171-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c1_ede2218cb5ee25716b8a331d6162b6f1d4832ef3_00000000_02ec28a6 Analysis symbol: Rechecking for solution: 0 Report Id: 9438cc0f-2dba-489b-9409-7c63038fb0f9 Report Status: 4 Hashed bucket: 11/30/2017 3:59 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: ffff8586acd72cf0 P3: ffff8586acd72bb6 P4: 970310 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5984-02.dmp \\?\C:\Windows\TEMP\WER-7187-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c1_b933b06dd7f4462635e4d1d265b265aee567394_00000000_cab_11845350 Analysis symbol: Rechecking for solution: 0 Report Id: 4768099b-bc46-42ad-9216-21b10e8c7e8e Report Status: 2048 Hashed bucket: 11/30/2017 3:59 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: ffff8586acd72cf0 P3: ffff8586acd72bb6 P4: 970310 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5984-02.dmp \\?\C:\Windows\TEMP\WER-7187-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c1_b933b06dd7f4462635e4d1d265b265aee567394_00000000_02ec46bd Analysis symbol: Rechecking for solution: 0 Report Id: 4768099b-bc46-42ad-9216-21b10e8c7e8e Report Status: 4 Hashed bucket: 11/30/2017 6:50 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: ffffc103f90a2cf0 P3: ffffc103f90a282f P4: bb0310 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4750-01.dmp \\?\C:\Windows\TEMP\WER-6328-0.sysdata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c1_21afec6d7970eb544b52d81b3ea9afa13a2fbad9_00000000_cab_12084bdd Analysis symbol: Rechecking for solution: 0 Report Id: 62d8a07b-00b8-4bdd-a9ec-d9250e01d89d Report Status: 2048 Hashed bucket: 11/30/2017 6:50 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: ffffc103f90a2cf0 P3: ffffc103f90a282f P4: bb0310 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4750-01.dmp \\?\C:\Windows\TEMP\WER-6328-0.sysdata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c1_21afec6d7970eb544b52d81b3ea9afa13a2fbad9_00000000_02f84a86 Analysis symbol: Rechecking for solution: 0 Report Id: 62d8a07b-00b8-4bdd-a9ec-d9250e01d89d Report Status: 4 Hashed bucket: 11/30/2017 4:10 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: ffffda8744d86ab0 P3: ffffda8744d8606e P4: 7f0550 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4328-01.dmp \\?\C:\Windows\TEMP\WER-5125-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c1_844eab0e2cb185739b816c561a0f77a532bc14_00000000_cab_113c4546 Analysis symbol: Rechecking for solution: 0 Report Id: 2a1120b5-6c3e-4633-86e2-84d797a3fd89 Report Status: 2048 Hashed bucket: 11/30/2017 4:10 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: ffffda8744d86ab0 P3: ffffda8744d8606e P4: 7f0550 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4328-01.dmp \\?\C:\Windows\TEMP\WER-5125-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c1_844eab0e2cb185739b816c561a0f77a532bc14_00000000_02f44100 Analysis symbol: Rechecking for solution: 0 Report Id: 2a1120b5-6c3e-4633-86e2-84d797a3fd89 Report Status: 4 Hashed bucket: 11/30/2017 8:16 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: fffff880efcb8dc0 P3: fffff880efcb8827 P4: a70238 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5125-01.dmp \\?\C:\Windows\TEMP\WER-6640-0.sysdata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c1_b8d66a3da9ed9680389a47b562208c8cdafd59c0_00000000_cab_12984e8d Analysis symbol: Rechecking for solution: 0 Report Id: 886c2cd2-8d75-4e8b-9638-effa3273d47a Report Status: 2048 Hashed bucket: 11/30/2017 8:16 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c1 P2: fffff880efcb8dc0 P3: fffff880efcb8827 P4: a70238 P5: 32 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5125-01.dmp \\?\C:\Windows\TEMP\WER-6640-0.sysdata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c1_b8d66a3da9ed9680389a47b562208c8cdafd59c0_00000000_02f44d74 Analysis symbol: Rechecking for solution: 0 Report Id: 886c2cd2-8d75-4e8b-9638-effa3273d47a Report Status: 4 Hashed bucket: 11/30/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 62 P3: ffffd40f2e3fde60 P4: ffffd40f2e0c5e90 P5: 7 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4859-01.dmp \\?\C:\Windows\TEMP\WER-5843-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_efa0c078fa3f4375e9cd112472b635f275d53444_00000000_cab_0c442b07 Analysis symbol: Rechecking for solution: 0 Report Id: e0ad3737-6a29-4ccd-a5a1-e387857676c1 Report Status: 2050 Hashed bucket: 11/30/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 62 P3: ffffd40f2e3fde60 P4: ffffd40f2e0c5e90 P5: 7 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-4859-01.dmp \\?\C:\Windows\TEMP\WER-5843-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_efa0c078fa3f4375e9cd112472b635f275d53444_00000000_02f42838 Analysis symbol: Rechecking for solution: 0 Report Id: e0ad3737-6a29-4ccd-a5a1-e387857676c1 Report Status: 4 Hashed bucket: 11/30/2017 12:28 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c5 P2: 73 P3: 2 P4: 0 P5: fffff8031c063037 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5984-01.dmp \\?\C:\Windows\TEMP\WER-6750-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c5_8cbf6919ae1facf5d6ae816ef20a21b8746c6_00000000_cab_0fbc28b5 Analysis symbol: Rechecking for solution: 0 Report Id: 1fd7f134-50fa-40a7-8df5-263a2a161b1b Report Status: 2050 Hashed bucket: 11/30/2017 12:28 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c5 P2: 73 P3: 2 P4: 0 P5: fffff8031c063037 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\113017-5984-01.dmp \\?\C:\Windows\TEMP\WER-6750-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c5_8cbf6919ae1facf5d6ae816ef20a21b8746c6_00000000_02c82635 Analysis symbol: Rechecking for solution: 0 Report Id: 1fd7f134-50fa-40a7-8df5-263a2a161b1b Report Status: 4 Hashed bucket:[/quote]
    Code: A corruption was discovered in the file system structure on volume G:. A file system index structure contains entries that violate ordering rules. The file reference number is 0xb0000000002d6. The name of the file is "\Steam\appcache\httpcache\a1". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION". The corrupted subtree is rooted at entry number 0 of the index block located at Vcn 0x4.[/quote] Code: A corruption was discovered in the file system structure on volume E:. A corruption was found in a file system index structure. The file reference number is 0x1000000000462. The name of the file is "\drivers\realtek_pcielan_7_mb_v7.107.0518.2017". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".[/quote] Code: A corruption was discovered in the file system structure on volume E:. The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x10000000004bd. The name of the file is "\drivers\realtek_pcielan_7_mb_v7.107.0518.2017\README\WIN7\French\AdvProperties.html".[/quote] Code: A corruption was discovered in the file system structure on volume E:. A corruption was found in a file system index structure. The file reference number is 0x10000000004ca. The name of the file is "\drivers\realtek_pcielan_7_mb_v7.107.0518.2017\README\WIN7\German". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".[/quote] Code: A corruption was discovered in the file system structure on volume E:. A corruption was found in a file system index structure. The file reference number is 0x10000000004d8. The name of the file is "\drivers\realtek_pcielan_7_mb_v7.107.0518.2017\README\WIN7\Hebrew". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".[/quote] Code: A corruption was discovered in the file system structure on volume E:. The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x10000000004e7. The name of the file is "\drivers\realtek_pcielan_7_mb_v7.107.0518.2017\README\WIN7\Hungarian\AdvProperties.html".[/quote] Code: A corruption was discovered in the file system structure on volume E:. The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x10000000004f5. The name of the file is "\drivers\realtek_pcielan_7_mb_v7.107.0518.2017\README\WIN7\Italian\AdvProperties.html".[/quote] Code: A corruption was discovered in the file system structure on volume E:. The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1000000000503. The name of the file is "\drivers\realtek_pcielan_7_mb_v7.107.0518.2017\README\WIN7\Japanese\AdvProperties.html".[/quote]
     
    zbook, Nov 30, 2017
    #11
  12. Have completed CMD commands and a few other tasks including updating the rt640x64 Realtek RT640 NT Driver and turning off windows fast startup.

    Am downloading the latest Nvidia drivers now in preparation for DDU which will be done after this HD Tune Pro error scan on my HDD (already completed on my SSD).

    Will upload everything that's been completed so far as my internet is slow as and I still have to wait on the benchmark tests for HD Tune Pro as well as the DDU.

    Computer restarts to do the C: drive test but then seems to get stuck on 11% - have included photo in the Dropbox. It then restarts and goes into windows normally

    Computer BSOD just then, just over halfway through the HD Tune Pro error scan on my HDD and was already showing 3 red squares with 9 errors in the listbox.

    Also drive E: was the USB I was using for memtest.

    Just completed read tests for both drives photos in dropbox.

    I'm thinking I might start deleting the bunch of unplayed steam games I have stored on the HDD soon - they're just taking up space and causing errors.

    Added new logs just in case.DESKTOP-RPUHOPI-Sat_12_02_2017__03051_76.zip

    Images: Dropbox - Tests

    Chkdsk log in event viewer for C:
    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 ... 282368 file records processed. File verification completed. 7961 large file records processed. 0 bad file records processed.

    Stage 2: Examining file name linkage ... 349596 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 97 unused index entries from index $SII of file 0x9.Cleaning up 97 unused index entries from index $SDH of file 0x9.Cleaning up 97 unused security descriptors.Security descriptor verification completed. 33615 data files processed. CHKDSK is verifying Usn Journal... 41202216 USN bytes processed. Usn Journal verification completed.

    Stage 4: Looking for bad clusters in user file data ... 282352 files processed. File data verification completed.

    Stage 5: Looking for bad, free clusters ... 41462116 free clusters processed. Free space verification is complete.CHKDSK discovered free space marked as allocated in the volume bitmap.Windows has made corrections to the file system.No further action is required. 233849855 KB total disk space. 67500392 KB in 149014 files. 103748 KB in 33616 indexes. 0 KB in bad sectors. 397251 KB in use by the system. 65536 KB occupied by the log file. 165848464 KB available on disk. 4096 bytes in each allocation unit. 58462463 total allocation units on disk. 41462116 allocation units available on disk.Internal Info:00 4f 04 00 c2 c8 02 00 5d b7 L: 05 00 00 00 00 00 .O......].......7a L: 00 00 00 60 00 00 00 L: 00 00 00 00 00 00 00 00 z...`...........

    Windows has finished checking your disk.Please wait while your computer restarts.

    Chkdsk log in event viewer for G:
    Chkdsk was executed in read/write mode.
    Checking file system on G:
    The type of the file system is NTFS.Volume dismounted. All opened handles to this volume are now invalid.Volume label is Barra Storage.

    Stage 1: Examining basic file system structure ... 407040 file records processed. File verification completed. 505 large file records processed. 0 bad file records processed.

    Stage 2: Examining file name linkage ... 489322 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...Security descriptor verification completed. 41142 data files processed. CHKDSK is verifying Usn Journal... 263416 USN bytes processed. Usn Journal verification completed.

    Stage 4: Looking for bad clusters in user file data ...
    Read failure with status 0xc000009c at offset 0x14f9926000 for 0x10000 bytes.
    Read failure with status 0xc000009c at offset 0x14f9932000 for 0x1000 bytes.
    Windows replaced bad clusters in file 61118of name \BITDEF~1\ANTIVI~1\avc3\AV79DE~2\avcuf32.dll.

    Read failure with status 0xc000009c at offset 0x4da7f16000 for 0x10000 bytes.
    Read failure with status 0xc000009c at offset 0x4da7f19000 for 0x1000 bytes.
    Read failure with status 0xc000009c at offset 0x4da7f1a000 for 0x10000 bytes.
    Read failure with status 0xc000009c at offset 0x4da7f23000 for 0x1000 bytes.
    Read failure with status 0xc000009c at offset 0x4da81e4000 for 0x10000 bytes.
    Read failure with status 0xc000009c at offset 0x4da81e4000 for 0x1000 bytes.
    Read failure with status 0xc000009c at offset 0x4da81e5000 for 0x10000 bytes.
    Read failure with status 0xc000009c at offset 0x4da81f2000 for 0x1000 bytes.
    Read failure with status 0xc000009c at offset 0x4da84b3000 for 0x10000 bytes.
    Read failure with status 0xc000009c at offset 0x4da84c0000 for 0x1000 bytes.
    Windows replaced bad clusters in file 109791of name \Steam\STEAMA~1\common\grid 2\grid2.exe.

    Read failure with status 0xc000009c at offset 0x4da8d17000 for 0x10000 bytes.
    Read failure with status 0xc000009c at offset 0x4da8d1d000 for 0x1000 bytes.
    Windows replaced bad clusters in file 109801of name \Steam\STEAMA~1\common\DIRT3C~1\audio\DICTIO~1\dd_mec\ME73CD~1.WIP.

    Read failure with status 0xc000009c at offset 0x2220f9000 for 0xb000 bytes.
    Read failure with status 0xc000009c at offset 0x2220fa000 for 0x1000 bytes.
    Windows replaced bad clusters in file 128367of name \OSU\Songs\115950~1\SOFT-H~2.WAV.Read failure with status 0xc000009c at offset 0x4da6456000 for 0x10000 bytes

    .Read failure with status 0xc000009c at offset 0x4da645c000 for 0x1000 bytes.
    Read failure with status 0xc000009c at offset 0x4da645d000 for 0x9000 bytes
    .Read failure with status 0xc000009c at offset 0x4da6460000 for 0x1000 bytes.
    Windows replaced bad clusters in file 193828of name \Steam\STEAMA~1\common\DIRT3C~1\tracks\LOCATI~1\usa\aspen\route_6\PROGRE~1.XML. 407024 files processed.
    File data verification completed.An unspecified error occurred (75736e6a726e6c2e 4f8).
     
    hyperphoenix, Nov 30, 2017
    #12
  13. philc43 Win User

    NTOSKRNL.EXE and other BSODs even after clean windows installation

    Please post up new logfiles after you get new BSOD crashes so that we can follow the progress and monitor the causes. @zbook has now taken over so I'll leave you to work through his instructions.
     
    philc43, Nov 30, 2017
    #13
  14. HD Tune Pro:
    ST1000DM003-9YN162
    Error ScanScanned data : 838 gB
    Damaged Blocks : 0.4 %
    Elapsed Time : 1:23:111
    Error at 8837 MB (LBA 18100128)
    2 Error at 86014 MB (LBA 176157024)
    3 Error at 318153 MB (LBA 651578080)
    4 Error at 318180 MB (LBA 651632736)
    5 Error at 318180 MB (LBA 651632864)
    6 Error at 318182 MB (LBA 651638496)
    7 Error at 318182 MB (LBA 651638624)
    8 Error at 318185 MB (LBA 651644384)
    9 Error at 318194 MB (LBA 651661536)
     
    hyperphoenix, Nov 30, 2017
    #14
  15. zbook New Member
    When reporting results into the thread please post with images:
    Take Screenshot in Windows 10 General Tips Tutorials

    For example:
    When Memtest86+ version completes testing there is an image displaying the RAM, Passes, Errors, etc.
    When HD Tune completes testing there are tabs with images on each tab.
    Take Screenshot in Windows 10 General Tips Tutorials


    For any difficulty posting images please use one drive or drop box share links.

    The latest BSOD were all bugcheck C1:
    Bug Check 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
    The SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION bug check has a value of 0x000000C1.
    This indicates that the driver wrote to an invalid section of the special pool.


    1) Please post a completed error scan for: ST1000DM003-9YN162
    2) Make a brand new restore point.
    3) Backup all of the files on this drive.
    4) Make a backup image using Macrium (if possible.....this tool may not work on drives with bad blocks or problems with chkdsk)
    Macrium Software | Your Image is Everything
    Backup and Restore with Macrium Reflect Backup Restore Tutorials
    5) Run chkdsk /x /f /r again on drive C: and G:
    6) Use the information in this link to find the chkdsk reports in the event viewer and post the results into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
     
    zbook, Nov 30, 2017
    #15
Thema:

NTOSKRNL.EXE and other BSODs even after clean windows installation

Loading...
  1. NTOSKRNL.EXE and other BSODs even after clean windows installation - Similar Threads - NTOSKRNL EXE BSODs

  2. BSOD after clean boot / ntoskrnl.

    in Windows 10 BSOD Crashes and Debugging
    BSOD after clean boot / ntoskrnl.: Hi there, I reinstalled my computer but I am getting a blue screen error. The error which I got is "driver power state failure" ntoskrnl. I examined the minidump file with a software called bsview. I'm sharing my minidumb file on the drive. Can you help me with this...
  3. BSOD even after clean install of Windows

    in Windows 10 BSOD Crashes and Debugging
    BSOD even after clean install of Windows: Hi guys, I've been having BSODs randomly throughout the day for the past 2 weeks, did all kinds of debugging trying to address it with no luck. Just did a fresh install last night and ran windows memtest with no error overnight but this morning I got 2 more BSOD. System...
  4. BSOD persists even after a clean install

    in Windows 10 BSOD Crashes and Debugging
    BSOD persists even after a clean install: The last few days I found my Windows 10 encountering BSOD, with a few other minor problems I was having, I just decided to do a fresh install. Even during the setup process and ever since the the blue screen still continues. For the sake of it, I have some driver updates and...
  5. BSOD Even After Clean Windows Install

    in Windows 10 BSOD Crashes and Debugging
    BSOD Even After Clean Windows Install: About a month or two ago I started getting BSOD while gaming. I tried a bunch of troubleshooting steps and nothing worked, so I decided to go for a clean Windows install. I didn't keep any personal files. I didn't get a BSOD for a few days, then it started up again. I get one...
  6. Random BSODs even after clean install

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs even after clean install: Hello all! I am facing a serious issue with my main desktop computer at the moment. About 4 hours ago, I tried to run a new updated game, but it was unable to start. I then proceeded to update my graphics drivers NVIDIA Dedicated GPU, and I got presented with a BSOD. I do...
  7. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  8. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  9. Mulitple BSOD even after clean installation

    in Windows 10 BSOD Crashes and Debugging
    Mulitple BSOD even after clean installation: Hello, I have been getting BSOD (probably all of them, I took pictures and almost everytime it was different...) on and on for a while now. I did clean reset my computer but it did not solve anything. Here is a link to my dmp files and system info:...
  10. BSODs after clean Windows 10 install playing Rust, ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    BSODs after clean Windows 10 install playing Rust, ntoskrnl: I recently bought a new SSD, installed Windows 7 Pro, updated to Windows 10 as a clean install and updated all my drivers for my chipset, GPU, sound, lan & USB 3.0. I verified each driver is compatible. Issues I've been having lately are slow browsing through websites,...
Tags: