BSOD when updating W10 Insider Preview (installation)

plloiuujn · 24 Nov 2017

Can anybody read into this? I'm having issues with the 17040 build and 17046 build. Both crashing from BSOD in the installation phase.

Code:

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000004, Pool header has been corrupted
Arg2: 0000000000000000, Pointer to pool header
Arg3: 0000000000000000, First part of pool header contents
Arg4: ffffd70c73298018, 0

0: kd> k
 # Child-SP          RetAddr           Call Site
00 ffffee81`acf95278 fffff803`54762d7e nt!KeBugCheckEx
01 ffffee81`acf95280 fffff803`54b02213 nt!ExFreePoolWithTag+0x1d4e
02 ffffee81`acf95360 fffff803`549ac8cd nt!MiBuildImageControlArea+0x15565b
03 ffffee81`acf953f0 fffff803`549aad78 nt!MiCreateImageFileMap+0x3d5
04 ffffee81`acf955c0 fffff803`549d782e nt!MiCreateNewSection+0x228
05 ffffee81`acf95730 fffff803`549d6eed nt!MiCreateImageOrDataSection+0x2ce
06 ffffee81`acf95820 fffff803`549d6dc4 nt!MiCreateSection+0xdd
07 ffffee81`acf95980 fffff803`549d6be5 nt!MmCreateSection+0xe4
08 ffffee81`acf95a00 fffff803`5463c253 nt!NtCreateSection+0x155
09 ffffee81`acf95a90 00007ff9`a01fc704 nt!KiSystemServiceCopyEnd+0x13
0a 00000069`f177e9d8 00000000`00000000 0x00007ff9`a01fc704

It seems I'm the only one in the insider thread with this issues.

I'll post the whole dump file when I get home from work.

zbook · 24 Nov 2017

See posting instructions:
Language - Add, Remove, and Change in Windows 10 General Tips Tutorials
BSOD - Posting Instructions - Windows 10 Forums

plloiuujn · 24 Nov 2017

I already said I'll post it in conformity with the rules when I get home.

This was just a part of the memory.dmp that I posted in the Insider thread a few days ago and thought it might ring some bells until I finished my program at work for today.

philc43 · 24 Nov 2017

I saw your original insider post and also the replies from @Spectrum. Can't really add any more at this stage, if you can share (on onedrive or dropbox) the full memory.dmp file that might help.

plloiuujn · 25 Nov 2017

Attachment 165462

Here it is.

philc43 · 25 Nov 2017

doriandiaconu said:

Attachment 165462

Here it is.

Did you look to see if the full kernel dump was present? The zip file just contains mini-dump files. Look in the C:\Windows directory for a file called memory.dmp - it will be too large to upload hence my request to share it via OneDrive. It might not provide any more information to help but it is worth a try.

philc43 · 25 Nov 2017

You are not the only one with this issue - see here

zbook · 25 Nov 2017

The logs reported corruption on the drive file system.
All of the bugchecks were C2 Bad pool caller with pool header corruption.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restoreheath
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) chkdsk /x /f /r
This may take many hours so plan to run overnight
6) Use the information in this link to find the chkdsk report in the event viewer:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

7)Run HDTune: 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
8) If HD Tune does not display the Health (SMART) report on the Samsung drive please use Samsung Magician to test SMART and display the health report.

9) 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 test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
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.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

Code:

Event[2730]:  Log Name: System  Source: Ntfs  Date: 2017-11-18T16:29:54.830  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-1FK4B9B  Description: A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown.  The file system structures need to be scanned and fixed offline.

Code:

Event[2778]:  Log Name: System  Source: Ntfs  Date: 2017-11-18T16:36:35.829  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-1FK4B9B  Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure.  The file reference number is 0x9e000000001676.  The name of the file is "\$WINDOWS.~BT\Sources\Rollback\EFI\Microsoft\Boot".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

Code:

Event[2877]:  Log Name: System  Source: Ntfs  Date: 2017-11-19T09:42:50.093  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-1FK4B9B  Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure.  The file reference number is 0x9e000000001676.  The name of the file is "\$WINDOWS.~BT\Sources\Rollback\EFI\Microsoft\Boot".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

Code:

Event[328]:  Log Name: System  Source: Microsoft-Windows-Directory-Services-SAM  Date: 2017-11-09T20:08:15.841  Event ID: 16953  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-1FK4B9B  Description: The password notification DLL KDCPW failed to load with error 126. Please verify that the notification DLL path defined in the registry, HKLM\System\CurrentControlSet\Control\Lsa\Notification Packages, refers to a correct and absolute path (<drive>:\<path>\<filename>.<ext>) and not a relative or invalid path. If the DLL path is correct, please validate that any supporting files are located in the same directory, and that the system account has read access to both the DLL path and any supporting files.  Contact the provider of the notification DLL for additional support. Further details can be found on the web at http://go.microsoft.com/fwlink/?LinkId=245898.

Code:

Event[4800]:  Log Name: System  Source: Microsoft-Windows-Directory-Services-SAM  Date: 2017-11-25T10:53:10.646  Event ID: 16953  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-1FK4B9B  Description: The password notification DLL KDCPW failed to load with error 126. Please verify that the notification DLL path defined in the registry, HKLM\System\CurrentControlSet\Control\Lsa\Notification Packages, refers to a correct and absolute path (<drive>:\<path>\<filename>.<ext>) and not a relative or invalid path. If the DLL path is correct, please validate that any supporting files are located in the same directory, and that the system account has read access to both the DLL path and any supporting files.  Contact the provider of the notification DLL for additional support. Further details can be found on the web at http://go.microsoft.com/fwlink/?LinkId=245898.

Code:

Event[3272]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-11-20T20:18:49.742  Event ID: 98  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-1FK4B9B  Description: Volume C: (\Device\HarddiskVolume4) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

Code:

11/18/2017 11:26 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffff868da81a5018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111817-5734-01.dmp
\\?\C:\WINDOWS\TEMP\WER-42562-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E63.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E74.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8EA3.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_11ead86cc95c4e36fb7976d06d12e1c2a67bfcb_00000000_cab_02d18e9e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 249f25d6-c7e8-41b5-bfd3-9e7839df5e74
Report Status: 4
Hashed bucket: 
Cab Guid: 011/20/2017 9:42 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffff8b0962d12018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112017-6671-01.dmp
\\?\C:\WINDOWS\TEMP\WER-77906-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8CD9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8D37.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8D48.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_1faab59f24dcf13a564e4329e9a9dec07f3dbf7_00000000_cab_02cd8d56

Analysis symbol: 
Rechecking for solution: 0
Report Id: cf51c205-9628-4d6d-92a9-28ab0e9874cf
Report Status: 4
Hashed bucket: 
Cab Guid: 011/20/2017 8:19 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffff8e8b831aa018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112017-6359-01.dmp
\\?\C:\WINDOWS\TEMP\WER-23484-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER487D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4929.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4959.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_e669e25491c6f22fb0b6bc29e53608c5cbfe6f_00000000_cab_02c94968

Analysis symbol: 
Rechecking for solution: 0
Report Id: bf629b54-493c-4575-8b42-6a48fdf9212a
Report Status: 4
Hashed bucket: 
Cab Guid: 011/23/2017 6:26 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffa800ad5e0018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112317-5890-01.dmp
\\?\C:\WINDOWS\TEMP\WER-42921-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER528B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5356.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5386.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_8590d074f159e1d99ddbd95abfcf85a6dcc785_00000000_cab_02ca5394

Analysis symbol: 
Rechecking for solution: 0
Report Id: df426ff9-8dee-4ac8-b573-bae03b7be5e5
Report Status: 4
Hashed bucket: 
Cab Guid: 011/23/2017 5:35 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffb1044e6cf018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112317-5937-01.dmp
\\?\C:\WINDOWS\TEMP\WER-45687-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB59.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC15.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC45.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_3d302ab91e4930cc4a4920e9774e64c6cfc12_00000000_cab_02cdcc53

Analysis symbol: 
Rechecking for solution: 0
Report Id: 28c41238-db90-441d-98d3-d87b944a9f04
Report Status: 4
Hashed bucket: 
Cab Guid: 011/18/2017 2:31 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffc104988fd018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111817-7562-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9937-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD9F0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDA7C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAAC.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_6558ea9166c25cefcae035d4ea14fa9da489502f_00000000_cab_02d5dabb

Analysis symbol: 
Rechecking for solution: 0
Report Id: 577aa40f-8a29-4b13-882f-3b08ef4725a5
Report Status: 4
Hashed bucket: 
Cab Guid: 011/19/2017 9:13 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffcd8e0760b018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111917-13546-01.dmp
\\?\C:\WINDOWS\TEMP\WER-54671-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1A64.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B2F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B6E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_4797dd10ca1bfaf7a083aa31b7bde68512df22da_00000000_cab_02da1b7d

Analysis symbol: 
Rechecking for solution: 0
Report Id: ec60567c-de91-420a-90b3-aa2d2b8db91e
Report Status: 4
Hashed bucket: 
Cab Guid: 011/21/2017 7:06 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffd70c73298018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112117-6171-01.dmp
\\?\C:\WINDOWS\TEMP\WER-84312-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF48C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF4EA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF51A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_56791962d7c97b217d07d7fc6683d26bc8b5fd_00000000_cab_02d5f519

Analysis symbol: 
Rechecking for solution: 0
Report Id: 47323196-4083-4501-9fa6-aa3e2faea072
Report Status: 4
Hashed bucket: 
Cab Guid: 011/20/2017 7:31 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffda0f883ee018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112017-5390-01.dmp
\\?\C:\WINDOWS\TEMP\WER-31500-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8289.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83A2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83D2.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_bbcd686da3ea1248d491e95e679b4a9490a32_00000000_cab_02d18400

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9c45506a-a72a-4170-b8f6-e0f7d726dd90
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

11/18/2017 2:32 PM    Windows Error Reporting    Fault bucket 0xc2_4_nt!MiBuildImageControlArea, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 4193f136-083f-4501-8970-b6725f368b88

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffc104988fd018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111817-7562-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9937-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD9F0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDA7C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAAC.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_6558ea9166c25cefcae035d4ea14fa9da489502f_00000000_cab_294218cd

Analysis symbol: 
Rechecking for solution: 0
Report Id: 577aa40f-8a29-4b13-882f-3b08ef4725a5
Report Status: 268435456
Hashed bucket: 
Cab Guid: 011/23/2017 5:35 PM    Windows Error Reporting    Fault bucket 0xc2_4_nt!MiBuildImageControlArea, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 511e83c9-b0db-4323-8b66-988dd2e0fce6

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffb1044e6cf018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112317-5937-01.dmp
\\?\C:\WINDOWS\TEMP\WER-45687-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB59.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC15.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC45.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_3d302ab91e4930cc4a4920e9774e64c6cfc12_00000000_cab_16fa1042

Analysis symbol: 
Rechecking for solution: 0
Report Id: 28c41238-db90-441d-98d3-d87b944a9f04
Report Status: 268435456
Hashed bucket: 
Cab Guid: 011/21/2017 7:06 PM    Windows Error Reporting    Fault bucket 0xc2_4_nt!MiBuildImageControlArea, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 58f68ec3-49d2-4f9d-a33d-274e75d3bdbb

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffd70c73298018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112117-6171-01.dmp
\\?\C:\WINDOWS\TEMP\WER-84312-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF48C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF4EA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF51A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_56791962d7c97b217d07d7fc6683d26bc8b5fd_00000000_cab_06b238c9

Analysis symbol: 
Rechecking for solution: 0
Report Id: 47323196-4083-4501-9fa6-aa3e2faea072
Report Status: 268435456
Hashed bucket: 
Cab Guid: 011/20/2017 9:42 PM    Windows Error Reporting    Fault bucket 0xc2_4_nt!MiBuildImageControlArea, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 782215c8-d062-4b62-a1c0-8933c9c20b21

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffff8b0962d12018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112017-6671-01.dmp
\\?\C:\WINDOWS\TEMP\WER-77906-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8CD9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8D37.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8D48.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_1faab59f24dcf13a564e4329e9a9dec07f3dbf7_00000000_cab_1491b2d0

Analysis symbol: 
Rechecking for solution: 0
Report Id: cf51c205-9628-4d6d-92a9-28ab0e9874cf
Report Status: 268435456
Hashed bucket: 
Cab Guid: 011/20/2017 7:32 PM    Windows Error Reporting    Fault bucket 0xc2_4_nt!MiBuildImageControlArea, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 7b4b0aa8-79d4-4ff8-a793-de30e237ee12

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffda0f883ee018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112017-5390-01.dmp
\\?\C:\WINDOWS\TEMP\WER-31500-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8289.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83A2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83D2.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_bbcd686da3ea1248d491e95e679b4a9490a32_00000000_cab_1db5ca11

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9c45506a-a72a-4170-b8f6-e0f7d726dd90
Report Status: 268435456
Hashed bucket: 
Cab Guid: 011/18/2017 11:27 AM    Windows Error Reporting    Fault bucket 0xc2_4_nt!MiBuildImageControlArea, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 829fa4f9-332a-4e79-b2a4-33048d9f8f1f

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffff868da81a5018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111817-5734-01.dmp
\\?\C:\WINDOWS\TEMP\WER-42562-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E63.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E74.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8EA3.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_11ead86cc95c4e36fb7976d06d12e1c2a67bfcb_00000000_cab_16b20e5e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 249f25d6-c7e8-41b5-bfd3-9e7839df5e74
Report Status: 268435456
Hashed bucket: 
Cab Guid: 011/19/2017 9:13 AM    Windows Error Reporting    Fault bucket 0xc2_4_nt!MiBuildImageControlArea, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 8543714f-4878-412b-8385-daf4e53ba4a3

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffcd8e0760b018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111917-13546-01.dmp
\\?\C:\WINDOWS\TEMP\WER-54671-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1A64.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B2F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B6E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_4797dd10ca1bfaf7a083aa31b7bde68512df22da_00000000_cab_043a54ae

Analysis symbol: 
Rechecking for solution: 0
Report Id: ec60567c-de91-420a-90b3-aa2d2b8db91e
Report Status: 268435456
Hashed bucket: 
Cab Guid: 011/20/2017 8:19 PM    Windows Error Reporting    Fault bucket 0xc2_4_nt!MiBuildImageControlArea, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: a3217262-7a7b-404c-a311-6667103b1ae2

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffff8e8b831aa018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112017-6359-01.dmp
\\?\C:\WINDOWS\TEMP\WER-23484-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER487D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4929.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4959.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_e669e25491c6f22fb0b6bc29e53608c5cbfe6f_00000000_cab_1b05967e

Analysis symbol: 
Rechecking for solution: 0
Report Id: bf629b54-493c-4575-8b42-6a48fdf9212a
Report Status: 268435456
Hashed bucket: 
Cab Guid: 011/23/2017 6:26 PM    Windows Error Reporting    Fault bucket 0xc2_4_nt!MiBuildImageControlArea, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: de0869a0-ecf0-47ad-b65c-feac3758cd8c

Problem signature:
P1: c2
P2: 4
P3: 0
P4: 0
P5: ffffa800ad5e0018
P6: 10_0_17035
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112317-5890-01.dmp
\\?\C:\WINDOWS\TEMP\WER-42921-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER528B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5356.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5386.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_8590d074f159e1d99ddbd95abfcf85a6dcc785_00000000_cab_24c68989

Analysis symbol: 
Rechecking for solution: 0
Report Id: df426ff9-8dee-4ac8-b573-bae03b7be5e5
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0

plloiuujn · 26 Nov 2017

philc43 said:

You are not the only one with this issue - see here

Damn

. Can't do a rollback to the previous version

plloiuujn · 26 Nov 2017

@zbook

Code:

Microsoft Windows [Version 10.0.17035.1000]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32> sfc /scannow

Beginning 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 /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17035.1000

Image Version: 10.0.17035.1000

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>