7 BSOD in 30 minutes???

[flaskmaster]

I have a custom built pc that, up until the last week has worked flawlessly. Here are the specs:

Amd fx-8350 cpu
Msi 790 gaming mobo
Msi GTX 970 gaming GPU
16Gb G.skill Ripjaws X
Rosewill quark 850W PSU
SanDisk 240 SSD plus
Seagate 2tb HD
Lepa dual mount top radiator

I originally bought a 750ti gpu, but quickly realized it wasn't enough, so I upgraded. The os is win 10, free upgrade from oem win 7.

For months, it has been fine. Over the last week, I have gotten random BSOD. Each time I get a different error. Tonight, I sat down and wrote down each error that I got while running diagnostics:

DPC_WATCHDOG_VIOLATION
MEMORY_MANAGEMENT
BAD_POOL_HEADER
SYSTEM_SERVICE_EXCEPTION
CRITICAL_PROCESS_DIED
IRQL_NOT_LESS_OR_EQUAL

All of these errors occurred within 30 min. Between boots I tried to run sfc/scannow, but could never finish. I was able to download a hdd tester (I don't remember which) but smart tests showed ok on both drives, no sign of failures.

Also, games seemed to "disappear." At one point uplay told me that the division wasn't installed, so I had to reinstall. I made it thru the 35Gb download, only to crash 2 minutes into the game. Tonight, I tried to load up steam, and it told me steam wasn't installed.

It almost seems like the ssd is failing, but all tests I ran showed the drive is fine.

 

[smorizio]

look in windows error log if you see power errors it could be your power supply. start with 16g of ram if it two stick of 8g pull one and run memtest on the ram. download hardware info 64 bit set it to sensor and logging see if the power supply rails are holding. the last issue could be a bad cpu..try running amd cpu test.

 

[Dark Lord of Tech]

If it's not overclocked , driver and \ or hardware issues.

 

[flaskmaster]

All the event log says is "the previous system shutdown at #date was unexpected." Event 6008. What else would you like? I'm left to use my phone.

Update: System seems to be stable for right now. MSI does have a built-in OC feature in the BIOS, so it is OC to 4.2 I booted in safe mode and disabled my printer, which seemed to be the only thing that had an ! next to it. My event viewer shows the following:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-04-13T00:37:24.123689500Z" />
<EventRecordID>18291</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Rinzler</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">26</Data>
<Data Name="BugcheckParameter1">0x41792</Data>
<Data Name="BugcheckParameter2">0xfffff6800000bbd8</Data>
<Data Name="BugcheckParameter3">0x10000000000</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>

I'm pretty sure this "event" isn't related, it's just an error that shows that the PC hadn't shut down correctly. What else would you like?

Update 2: I try to run sfc/scannow via elevated command prompt, and it only makes it to around 15-20% before I get:

Windows Resource Protection could not perform the requested operation.

 

[Colif]

this should help with sfc not completing: https://www.infopackets.com/news/9620/how-fix-sfc-scannow-fails-wont-complete

also, download this and run a scan: http://www.resplendence.com/whocrashed
it will look at error logs and prepare a report on all the errors, spelling it out so people can understand them

post results here if a cause isn't obvious

 

[flaskmaster]

Colif, this is even more confusing:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 4/13/2016 12:32:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041216-4750-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6800000BBD8, 0x10000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/13/2016 12:32:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6800000BBD8, 0x10000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/13/2016 12:30:22 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041216-8109-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x138DE)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680000089D8, 0x10000000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: Avast Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software MEMORY_MANAGEMENT



On Wed 4/13/2016 12:02:29 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041216-6312-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF6BC80A33060, 0x2, 0x0, 0xFFFFF803E9327360)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/13/2016 12:00:55 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041216-8375-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x138DE)
Bugcheck code: 0xEF (0xFFFFE001A939C840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: Avast Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software CRITICAL_PROCESS_DIED



On Tue 4/12/2016 11:58:08 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041216-9250-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801969E353B, 0xFFFFD00028505AA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 4/12/2016 11:51:47 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041216-8640-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1E429)
Bugcheck code: 0x19 (0xD, 0xFFFFC000B122C000, 0x903E492AAD340F36, 0x903E4B2AAD340F36)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: Avast Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software BAD_POOL_HEADER



On Tue 4/12/2016 11:49:01 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041216-8437-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x13654)
Bugcheck code: 0x1A (0x41284, 0x17420000, 0x38D1, 0xFFFFF58010804000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: Avast Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software MEMORY_MANAGEMENT



On Tue 4/12/2016 11:46:04 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041216-9656-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000299938, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 4/12/2016 11:43:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041216-8687-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockIpiRoutine+0x15)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Colif]

Well. Half of them point at Avast so I would make sure you have the right version - maybe even uninstall and reinstall it. Fixing avast may fix the entire thing but SFC still doesn't work...

the solution to memory management errors is run sfc... so did you do that fix to sfc? (when you get to the part about booting into safe mode - the easiest way to booting into safe mode in win 10 is hold down the shift key when restarting pc)

 

[flaskmaster]

Colif,

Really sorry for the long delay. I performed a clean install of Win 7 (I originally bought a Win 7 DVD with the free upgrade to Win 10), and installed all relevant drivers. Seems to be more stable, but I still run into MEMORY_MANAGEMENT BSOD. So I followed your link and managed to get the sfc /scannow to 100%, but it still seemed to be unable to fix all the errors. Here's the log:

2016-04-18 18:46:12, Info CSI 00000009 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:12, Info CSI 0000000a [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:13, Info CSI 0000000c [SR] Verify complete
2016-04-18 18:46:13, Info CSI 0000000d [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:13, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:13, Info CSI 00000010 [SR] Verify complete
2016-04-18 18:46:13, Info CSI 00000011 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:13, Info CSI 00000012 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:13, Info CSI 00000014 [SR] Verify complete
2016-04-18 18:46:13, Info CSI 00000015 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:13, Info CSI 00000016 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:13, Info CSI 00000018 [SR] Verify complete
2016-04-18 18:46:13, Info CSI 00000019 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:13, Info CSI 0000001a [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:14, Info CSI 0000001c [SR] Verify complete
2016-04-18 18:46:14, Info CSI 0000001d [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:14, Info CSI 0000001e [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:14, Info CSI 00000020 [SR] Verify complete
2016-04-18 18:46:14, Info CSI 00000021 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:14, Info CSI 00000022 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:15, Info CSI 00000024 [SR] Verify complete
2016-04-18 18:46:15, Info CSI 00000025 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:15, Info CSI 00000026 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:15, Info CSI 00000028 [SR] Verify complete
2016-04-18 18:46:15, Info CSI 00000029 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:15, Info CSI 0000002a [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:15, Info CSI 0000002c [SR] Verify complete
2016-04-18 18:46:16, Info CSI 0000002d [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:16, Info CSI 0000002e [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:16, Info CSI 00000030 [SR] Verify complete
2016-04-18 18:46:16, Info CSI 00000031 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:16, Info CSI 00000032 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:17, Info CSI 00000034 [SR] Verify complete
2016-04-18 18:46:17, Info CSI 00000035 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:17, Info CSI 00000036 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:17, Info CSI 00000038 [SR] Verify complete
2016-04-18 18:46:17, Info CSI 00000039 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:17, Info CSI 0000003a [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:18, Info CSI 0000003c [SR] Verify complete
2016-04-18 18:46:18, Info CSI 0000003d [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:18, Info CSI 0000003e [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:19, Info CSI 00000041 [SR] Verify complete
2016-04-18 18:46:19, Info CSI 00000042 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:19, Info CSI 00000043 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:21, Info CSI 00000047 [SR] Verify complete
2016-04-18 18:46:21, Info CSI 00000048 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:21, Info CSI 00000049 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:22, Info CSI 0000004c [SR] Verify complete
2016-04-18 18:46:22, Info CSI 0000004d [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:22, Info CSI 0000004e [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:23, Info CSI 00000051 [SR] Verify complete
2016-04-18 18:46:23, Info CSI 00000052 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:23, Info CSI 00000053 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:24, Info CSI 00000055 [SR] Verify complete
2016-04-18 18:46:24, Info CSI 00000056 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:24, Info CSI 00000057 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:27, Info CSI 0000007c [SR] Verify complete
2016-04-18 18:46:27, Info CSI 0000007d [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:27, Info CSI 0000007e [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:28, Info CSI 00000080 [SR] Verify complete
2016-04-18 18:46:28, Info CSI 00000081 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:28, Info CSI 00000082 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:29, Info CSI 00000084 [SR] Verify complete
2016-04-18 18:46:29, Info CSI 00000085 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:29, Info CSI 00000086 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:30, Info CSI 00000088 [SR] Verify complete
2016-04-18 18:46:30, Info CSI 00000089 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:30, Info CSI 0000008a [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:31, Info CSI 0000008c [SR] Verify complete
2016-04-18 18:46:31, Info CSI 0000008d [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:31, Info CSI 0000008e [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:33, Info CSI 00000090 [SR] Verify complete
2016-04-18 18:46:33, Info CSI 00000091 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:33, Info CSI 00000092 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:36, Info CSI 000000b5 [SR] Verify complete
2016-04-18 18:46:36, Info CSI 000000b6 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:36, Info CSI 000000b7 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:37, Info CSI 000000b9 [SR] Verify complete
2016-04-18 18:46:37, Info CSI 000000ba [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:37, Info CSI 000000bb [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:42, Info CSI 000000bd [SR] Verify complete
2016-04-18 18:46:42, Info CSI 000000be [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:42, Info CSI 000000bf [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:43, Info CSI 000000c3 [SR] Verify complete
2016-04-18 18:46:43, Info CSI 000000c4 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:43, Info CSI 000000c5 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:43, Info CSI 000000c7 [SR] Verify complete
2016-04-18 18:46:43, Info CSI 000000c8 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:43, Info CSI 000000c9 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:44, Info CSI 000000cb [SR] Verify complete
2016-04-18 18:46:44, Info CSI 000000cc [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:44, Info CSI 000000cd [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:48, Info CSI 000000e0 [SR] Verify complete
2016-04-18 18:46:48, Info CSI 000000e1 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:48, Info CSI 000000e2 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:49, Info CSI 000000e4 [SR] Verify complete
2016-04-18 18:46:49, Info CSI 000000e5 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:49, Info CSI 000000e6 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:49, Info CSI 000000e8 [SR] Verify complete
2016-04-18 18:46:49, Info CSI 000000e9 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:49, Info CSI 000000ea [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:50, Info CSI 000000ec [SR] Verify complete
2016-04-18 18:46:50, Info CSI 000000ed [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:50, Info CSI 000000ee [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:51, Info CSI 000000f0 [SR] Verify complete
2016-04-18 18:46:51, Info CSI 000000f1 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:51, Info CSI 000000f2 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:53, Info CSI 000000f5 [SR] Verify complete
2016-04-18 18:46:54, Info CSI 000000f6 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:54, Info CSI 000000f7 [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:54, Info CSI 000000f9 [SR] Verify complete
2016-04-18 18:46:55, Info CSI 000000fa [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:55, Info CSI 000000fb [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:55, Info CSI 000000fd [SR] Verify complete
2016-04-18 18:46:55, Info CSI 000000fe [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:55, Info CSI 000000ff [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:55, Info CSI 00000101 [SR] Cannot repair member file [l:30{15}]"mqmigplugin.dll" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:46:56, Info CSI 00000103 [SR] Cannot repair member file [l:30{15}]"mqmigplugin.dll" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:46:56, Info CSI 00000104 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:46:56, Info CSI 00000107 [SR] Could not reproject corrupted file [ml:520{260},l:172{86}]"\??\C:\Windows\System32\migwiz\dlmanifests\Microsoft-Windows-msmq-messagingcoreservice"\[l:30{15}]"mqmigplugin.dll"; source file in store is also corrupted
2016-04-18 18:46:56, Info CSI 00000109 [SR] Verify complete
2016-04-18 18:46:56, Info CSI 0000010a [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:56, Info CSI 0000010b [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:57, Info CSI 0000010d [SR] Cannot repair member file [l:30{15}]"adwsmigrate.dll" of Microsoft-Windows-Migration-ReplacementManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:46:57, Info CSI 0000010f [SR] Cannot repair member file [l:30{15}]"tsmigplugin.dll" of Microsoft-Windows-Migration-ReplacementManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:46:57, Info CSI 00000111 [SR] Cannot repair member file [l:30{15}]"adwsmigrate.dll" of Microsoft-Windows-Migration-ReplacementManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:46:57, Info CSI 00000112 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:46:57, Info CSI 00000114 [SR] Cannot repair member file [l:30{15}]"tsmigplugin.dll" of Microsoft-Windows-Migration-ReplacementManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:46:57, Info CSI 00000115 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:46:57, Info CSI 00000118 [SR] Could not reproject corrupted file [ml:520{260},l:178{89}]"\??\C:\Windows\System32\migwiz\replacementmanifests\microsoft-activedirectory-webservices"\[l:30{15}]"adwsmigrate.dll"; source file in store is also corrupted
2016-04-18 18:46:57, Info CSI 0000011b [SR] Could not reproject corrupted file [ml:520{260},l:212{106}]"\??\C:\Windows\System32\migwiz\replacementmanifests\Microsoft-Windows-TerminalServices-AppServer-Licensing"\[l:30{15}]"tsmigplugin.dll"; source file in store is also corrupted
2016-04-18 18:46:57, Info CSI 0000011d [SR] Verify complete
2016-04-18 18:46:57, Info CSI 0000011e [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:57, Info CSI 0000011f [SR] Beginning Verify and Repair transaction
2016-04-18 18:46:59, Info CSI 00000121 [SR] Verify complete
2016-04-18 18:46:59, Info CSI 00000122 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:46:59, Info CSI 00000123 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:03, Info CSI 00000137 [SR] Verify complete
2016-04-18 18:47:03, Info CSI 00000138 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:03, Info CSI 00000139 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:04, Info CSI 0000013f [SR] Verify complete
2016-04-18 18:47:04, Info CSI 00000140 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:04, Info CSI 00000141 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:10, Info CSI 00000143 [SR] Verify complete
2016-04-18 18:47:10, Info CSI 00000144 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:10, Info CSI 00000145 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:11, Info CSI 00000148 [SR] Verify complete
2016-04-18 18:47:11, Info CSI 00000149 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:11, Info CSI 0000014a [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:12, Info CSI 0000014c [SR] Cannot repair member file [l:24{12}]"msoobeui.dll" of Microsoft-Windows-OOBE-Machine-UI, Version = 6.1.7601.17591, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:47:13, Info CSI 0000014e [SR] Cannot repair member file [l:24{12}]"msoobeui.dll" of Microsoft-Windows-OOBE-Machine-UI, Version = 6.1.7601.17591, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:47:13, Info CSI 0000014f [SR] This component was referenced by [l:154{77}]"Package_1_for_KB2534111~31bf3856ad364e35~amd64~~6.1.1.0.2534111-2_neutral_GDR"
2016-04-18 18:47:13, Info CSI 00000152 [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\System32\oobe"\[l:24{12}]"msoobeui.dll"; source file in store is also corrupted
2016-04-18 18:47:13, Info CSI 00000154 [SR] Verify complete
2016-04-18 18:47:14, Info CSI 00000155 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:14, Info CSI 00000156 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:15, Info CSI 00000158 [SR] Verify complete
2016-04-18 18:47:15, Info CSI 00000159 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:15, Info CSI 0000015a [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:16, Info CSI 0000015c [SR] Verify complete
2016-04-18 18:47:16, Info CSI 0000015d [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:16, Info CSI 0000015e [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:17, Info CSI 00000160 [SR] Verify complete
2016-04-18 18:47:17, Info CSI 00000161 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:17, Info CSI 00000162 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:17, Info CSI 00000166 [SR] Verify complete
2016-04-18 18:47:18, Info CSI 00000167 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:18, Info CSI 00000168 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:22, Info CSI 0000016a [SR] Verify complete
2016-04-18 18:47:22, Info CSI 0000016b [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:22, Info CSI 0000016c [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:24, Info CSI 0000016f [SR] Verify complete
2016-04-18 18:47:24, Info CSI 00000170 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:24, Info CSI 00000171 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:25, Info CSI 00000174 [SR] Verify complete
2016-04-18 18:47:25, Info CSI 00000175 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:25, Info CSI 00000176 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:26, Info CSI 00000178 [SR] Verify complete
2016-04-18 18:47:27, Info CSI 00000179 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:27, Info CSI 0000017a [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:27, Info CSI 0000017c [SR] Cannot repair member file [l:20{10}]"diagER.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:47:27, Info CSI 0000017e [SR] Cannot repair member file [l:22{11}]"win32ui.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:47:28, Info CSI 00000180 [SR] Cannot repair member file [l:20{10}]"diagER.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:47:28, Info CSI 00000181 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2016-04-18 18:47:28, Info CSI 00000183 [SR] Cannot repair member file [l:22{11}]"win32ui.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:47:28, Info CSI 00000184 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2016-04-18 18:47:28, Info CSI 00000187 [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\System32\oobe"\[l:20{10}]"diagER.dll"; source file in store is also corrupted
2016-04-18 18:47:28, Info CSI 0000018a [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\System32\oobe"\[l:22{11}]"win32ui.dll"; source file in store is also corrupted
2016-04-18 18:47:29, Info CSI 0000018d [SR] Verify complete
2016-04-18 18:47:29, Info CSI 0000018e [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:29, Info CSI 0000018f [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:30, Info CSI 00000191 [SR] Verify complete
2016-04-18 18:47:30, Info CSI 00000192 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:30, Info CSI 00000193 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:32, Info CSI 00000195 [SR] Verify complete
2016-04-18 18:47:32, Info CSI 00000196 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:32, Info CSI 00000197 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:33, Info CSI 00000199 [SR] Verify complete
2016-04-18 18:47:33, Info CSI 0000019a [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:33, Info CSI 0000019b [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:34, Info CSI 0000019e [SR] Verify complete
2016-04-18 18:47:34, Info CSI 0000019f [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:34, Info CSI 000001a0 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:35, Info CSI 000001a2 [SR] Verify complete
2016-04-18 18:47:35, Info CSI 000001a3 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:35, Info CSI 000001a4 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:36, Info CSI 000001a7 [SR] Verify complete
2016-04-18 18:47:37, Info CSI 000001a8 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:37, Info CSI 000001a9 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:38, Info CSI 000001ac [SR] Verify complete
2016-04-18 18:47:38, Info CSI 000001ad [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:38, Info CSI 000001ae [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:39, Info CSI 000001b1 [SR] Verify complete
2016-04-18 18:47:40, Info CSI 000001b2 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:40, Info CSI 000001b3 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:41, Info CSI 000001b5 [SR] Verify complete
2016-04-18 18:47:42, Info CSI 000001b6 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:42, Info CSI 000001b7 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:43, Info CSI 000001ba [SR] Verify complete
2016-04-18 18:47:43, Info CSI 000001bb [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:43, Info CSI 000001bc [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:44, Info CSI 000001be [SR] Verify complete
2016-04-18 18:47:44, Info CSI 000001bf [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:44, Info CSI 000001c0 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:45, Info CSI 000001c2 [SR] Verify complete
2016-04-18 18:47:45, Info CSI 000001c3 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:45, Info CSI 000001c4 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:45, Info CSI 000001c6 [SR] Verify complete
2016-04-18 18:47:45, Info CSI 000001c7 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:45, Info CSI 000001c8 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:47, Info CSI 000001ca [SR] Verify complete
2016-04-18 18:47:47, Info CSI 000001cb [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:47, Info CSI 000001cc [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:48, Info CSI 000001ce [SR] Verify complete
2016-04-18 18:47:48, Info CSI 000001cf [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:48, Info CSI 000001d0 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:48, Info CSI 000001d2 [SR] Verify complete
2016-04-18 18:47:48, Info CSI 000001d3 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:48, Info CSI 000001d4 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:50, Info CSI 000001d6 [SR] Verify complete
2016-04-18 18:47:50, Info CSI 000001d7 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:50, Info CSI 000001d8 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:54, Info CSI 000001da [SR] Verify complete
2016-04-18 18:47:54, Info CSI 000001db [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:54, Info CSI 000001dc [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:55, Info CSI 000001de [SR] Verify complete
2016-04-18 18:47:55, Info CSI 000001df [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:55, Info CSI 000001e0 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:56, Info CSI 000001e2 [SR] Verify complete
2016-04-18 18:47:56, Info CSI 000001e3 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:56, Info CSI 000001e4 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:56, Info CSI 000001e6 [SR] Verify complete
2016-04-18 18:47:57, Info CSI 000001e7 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:57, Info CSI 000001e8 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:57, Info CSI 000001ea [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:47:57, Info CSI 000001ec [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:47:57, Info CSI 000001ed [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:47:57, Info CSI 000001f0 [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\System32\oobe"\[l:28{14}]"background.bmp"; source file in store is also corrupted
2016-04-18 18:47:57, Info CSI 000001f2 [SR] Verify complete
2016-04-18 18:47:57, Info CSI 000001f3 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:57, Info CSI 000001f4 [SR] Beginning Verify and Repair transaction
2016-04-18 18:47:58, Info CSI 000001f6 [SR] Verify complete
2016-04-18 18:47:58, Info CSI 000001f7 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:47:58, Info CSI 000001f8 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:00, Info CSI 00000200 [SR] Verify complete
2016-04-18 18:48:00, Info CSI 00000201 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:00, Info CSI 00000202 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:01, Info CSI 00000204 [SR] Verify complete
2016-04-18 18:48:01, Info CSI 00000205 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:01, Info CSI 00000206 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:02, Info CSI 00000208 [SR] Verify complete
2016-04-18 18:48:02, Info CSI 00000209 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:02, Info CSI 0000020a [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:03, Info CSI 0000020c [SR] Verify complete
2016-04-18 18:48:03, Info CSI 0000020d [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:03, Info CSI 0000020e [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:04, Info CSI 00000210 [SR] Verify complete
2016-04-18 18:48:04, Info CSI 00000211 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:04, Info CSI 00000212 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:06, Info CSI 00000215 [SR] Verify complete
2016-04-18 18:48:06, Info CSI 00000216 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:06, Info CSI 00000217 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:07, Info CSI 00000219 [SR] Verify complete
2016-04-18 18:48:07, Info CSI 0000021a [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:07, Info CSI 0000021b [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:07, Info CSI 0000021d [SR] Verify complete
2016-04-18 18:48:08, Info CSI 0000021e [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:08, Info CSI 0000021f [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:11, Info CSI 00000224 [SR] Verify complete
2016-04-18 18:48:11, Info CSI 00000225 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:11, Info CSI 00000226 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:13, Info CSI 00000229 [SR] Verify complete
2016-04-18 18:48:13, Info CSI 0000022a [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:13, Info CSI 0000022b [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:14, Info CSI 0000022f [SR] Verify complete
2016-04-18 18:48:15, Info CSI 00000230 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:15, Info CSI 00000231 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:17, Info CSI 0000023d [SR] Verify complete
2016-04-18 18:48:17, Info CSI 0000023e [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:17, Info CSI 0000023f [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:19, Info CSI 00000245 [SR] Verify complete
2016-04-18 18:48:19, Info CSI 00000246 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:19, Info CSI 00000247 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:20, Info CSI 00000249 [SR] Verify complete
2016-04-18 18:48:20, Info CSI 0000024a [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:20, Info CSI 0000024b [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:21, Info CSI 0000024f [SR] Verify complete
2016-04-18 18:48:21, Info CSI 00000250 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:21, Info CSI 00000251 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:22, Info CSI 00000253 [SR] Verify complete
2016-04-18 18:48:22, Info CSI 00000254 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:22, Info CSI 00000255 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:24, Info CSI 0000027a [SR] Verify complete
2016-04-18 18:48:24, Info CSI 0000027b [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:24, Info CSI 0000027c [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:25, Info CSI 0000027e [SR] Verify complete
2016-04-18 18:48:25, Info CSI 0000027f [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:25, Info CSI 00000280 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:26, Info CSI 00000282 [SR] Verify complete
2016-04-18 18:48:26, Info CSI 00000283 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:26, Info CSI 00000284 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:26, Info CSI 00000286 [SR] Verify complete
2016-04-18 18:48:27, Info CSI 00000287 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:27, Info CSI 00000288 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:27, Info CSI 00000296 [SR] Verify complete
2016-04-18 18:48:27, Info CSI 00000297 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:27, Info CSI 00000298 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:29, Info CSI 0000029e [SR] Verify complete
2016-04-18 18:48:29, Info CSI 0000029f [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:29, Info CSI 000002a0 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:31, Info CSI 000002aa [SR] Verify complete
2016-04-18 18:48:31, Info CSI 000002ab [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:31, Info CSI 000002ac [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:32, Info CSI 000002ae [SR] Verify complete
2016-04-18 18:48:32, Info CSI 000002af [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:32, Info CSI 000002b0 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:33, Info CSI 000002b2 [SR] Verify complete
2016-04-18 18:48:33, Info CSI 000002b3 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:33, Info CSI 000002b4 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:33, Info CSI 000002b6 [SR] Verify complete
2016-04-18 18:48:33, Info CSI 000002b7 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:33, Info CSI 000002b8 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:34, Info CSI 000002ba [SR] Verify complete
2016-04-18 18:48:34, Info CSI 000002bb [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:34, Info CSI 000002bc [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:35, Info CSI 000002be [SR] Verify complete
2016-04-18 18:48:35, Info CSI 000002bf [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:35, Info CSI 000002c0 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:36, Info CSI 000002c2 [SR] Verify complete
2016-04-18 18:48:36, Info CSI 000002c3 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:36, Info CSI 000002c4 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:39, Info CSI 000002de [SR] Verify complete
2016-04-18 18:48:39, Info CSI 000002df [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:39, Info CSI 000002e0 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:44, Info CSI 000002e2 [SR] Verify complete
2016-04-18 18:48:44, Info CSI 000002e3 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:44, Info CSI 000002e4 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:45, Info CSI 000002e6 [SR] Verify complete
2016-04-18 18:48:45, Info CSI 000002e7 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:45, Info CSI 000002e8 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:46, Info CSI 000002ea [SR] Verify complete
2016-04-18 18:48:46, Info CSI 000002eb [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:46, Info CSI 000002ec [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:46, Info CSI 000002f0 [SR] Verify complete
2016-04-18 18:48:46, Info CSI 000002f1 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:46, Info CSI 000002f2 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:47, Info CSI 000002f4 [SR] Verify complete
2016-04-18 18:48:47, Info CSI 000002f5 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:47, Info CSI 000002f6 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:48, Info CSI 000002f8 [SR] Verify complete
2016-04-18 18:48:48, Info CSI 000002f9 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:48, Info CSI 000002fa [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:49, Info CSI 000002fc [SR] Verify complete
2016-04-18 18:48:49, Info CSI 000002fd [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:49, Info CSI 000002fe [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:50, Info CSI 00000301 [SR] Verify complete
2016-04-18 18:48:50, Info CSI 00000302 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:50, Info CSI 00000303 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:50, Info CSI 00000305 [SR] Verify complete
2016-04-18 18:48:50, Info CSI 00000306 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:50, Info CSI 00000307 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:51, Info CSI 00000309 [SR] Verify complete
2016-04-18 18:48:51, Info CSI 0000030a [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:51, Info CSI 0000030b [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:53, Info CSI 0000030d [SR] Verify complete
2016-04-18 18:48:53, Info CSI 0000030e [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:53, Info CSI 0000030f [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:53, Info CSI 00000312 [SR] Verify complete
2016-04-18 18:48:53, Info CSI 00000313 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:53, Info CSI 00000314 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:54, Info CSI 00000316 [SR] Verify complete
2016-04-18 18:48:55, Info CSI 00000317 [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:55, Info CSI 00000318 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:55, Info CSI 0000031a [SR] Verify complete
2016-04-18 18:48:56, Info CSI 0000031b [SR] Verifying 100 (0x0000000000000064) components
2016-04-18 18:48:56, Info CSI 0000031c [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:56, Info CSI 0000031e [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:56, Info CSI 00000320 [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:56, Info CSI 00000321 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:48:56, Info CSI 00000324 [SR] Could not reproject corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\SysWOW64\oobe"\[l:28{14}]"background.bmp"; source file in store is also corrupted
2016-04-18 18:48:57, Info CSI 00000326 [SR] Verify complete
2016-04-18 18:48:57, Info CSI 00000327 [SR] Verifying 44 (0x000000000000002c) components
2016-04-18 18:48:57, Info CSI 00000328 [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:57, Info CSI 0000032a [SR] Verify complete
2016-04-18 18:48:57, Info CSI 0000032b [SR] Repairing 6 components
2016-04-18 18:48:57, Info CSI 0000032c [SR] Beginning Verify and Repair transaction
2016-04-18 18:48:57, Info CSI 0000032e [SR] Cannot repair member file [l:30{15}]"mqmigplugin.dll" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:57, Info CSI 00000330 [SR] Cannot repair member file [l:30{15}]"adwsmigrate.dll" of Microsoft-Windows-Migration-ReplacementManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:57, Info CSI 00000332 [SR] Cannot repair member file [l:30{15}]"tsmigplugin.dll" of Microsoft-Windows-Migration-ReplacementManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:57, Info CSI 00000334 [SR] Cannot repair member file [l:24{12}]"msoobeui.dll" of Microsoft-Windows-OOBE-Machine-UI, Version = 6.1.7601.17591, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:57, Info CSI 00000336 [SR] Cannot repair member file [l:20{10}]"diagER.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:57, Info CSI 00000338 [SR] Cannot repair member file [l:22{11}]"win32ui.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:57, Info CSI 0000033a [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:57, Info CSI 0000033c [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:57, Info CSI 0000033e [SR] Cannot repair member file [l:24{12}]"msoobeui.dll" of Microsoft-Windows-OOBE-Machine-UI, Version = 6.1.7601.17591, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:57, Info CSI 0000033f [SR] This component was referenced by [l:154{77}]"Package_1_for_KB2534111~31bf3856ad364e35~amd64~~6.1.1.0.2534111-2_neutral_GDR"
2016-04-18 18:48:57, Info CSI 00000342 [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\System32\oobe"\[l:24{12}]"msoobeui.dll"; source file in store is also corrupted
2016-04-18 18:48:58, Info CSI 00000344 [SR] Cannot repair member file [l:30{15}]"adwsmigrate.dll" of Microsoft-Windows-Migration-ReplacementManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:58, Info CSI 00000345 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:48:58, Info CSI 00000347 [SR] Cannot repair member file [l:30{15}]"tsmigplugin.dll" of Microsoft-Windows-Migration-ReplacementManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:58, Info CSI 00000348 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:48:58, Info CSI 0000034b [SR] Could not reproject corrupted file [ml:520{260},l:178{89}]"\??\C:\Windows\System32\migwiz\replacementmanifests\microsoft-activedirectory-webservices"\[l:30{15}]"adwsmigrate.dll"; source file in store is also corrupted
2016-04-18 18:48:58, Info CSI 0000034e [SR] Could not reproject corrupted file [ml:520{260},l:212{106}]"\??\C:\Windows\System32\migwiz\replacementmanifests\Microsoft-Windows-TerminalServices-AppServer-Licensing"\[l:30{15}]"tsmigplugin.dll"; source file in store is also corrupted
2016-04-18 18:48:58, Info CSI 00000350 [SR] Cannot repair member file [l:20{10}]"diagER.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:58, Info CSI 00000351 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2016-04-18 18:48:58, Info CSI 00000353 [SR] Cannot repair member file [l:22{11}]"win32ui.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:58, Info CSI 00000354 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2016-04-18 18:48:58, Info CSI 00000357 [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\System32\oobe"\[l:20{10}]"diagER.dll"; source file in store is also corrupted
2016-04-18 18:48:58, Info CSI 0000035a [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\System32\oobe"\[l:22{11}]"win32ui.dll"; source file in store is also corrupted
2016-04-18 18:48:58, Info CSI 0000035c [SR] Cannot repair member file [l:30{15}]"mqmigplugin.dll" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:58, Info CSI 0000035d [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:48:58, Info CSI 00000360 [SR] Could not reproject corrupted file [ml:520{260},l:172{86}]"\??\C:\Windows\System32\migwiz\dlmanifests\Microsoft-Windows-msmq-messagingcoreservice"\[l:30{15}]"mqmigplugin.dll"; source file in store is also corrupted
2016-04-18 18:48:58, Info CSI 00000362 [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:58, Info CSI 00000363 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:48:58, Info CSI 00000366 [SR] Could not reproject corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\SysWOW64\oobe"\[l:28{14}]"background.bmp"; source file in store is also corrupted
2016-04-18 18:48:58, Info CSI 00000368 [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-04-18 18:48:58, Info CSI 00000369 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2016-04-18 18:48:58, Info CSI 0000036c [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\System32\oobe"\[l:28{14}]"background.bmp"; source file in store is also corrupted
2016-04-18 18:48:58, Info CSI 0000036e [SR] Repair complete
2016-04-18 18:48:58, Info CSI 0000036f [SR] Committing transaction
2016-04-18 18:48:58, Info CSI 00000373 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

 

[Colif]

Not 100% sure about this but I don't think you can stay on Win 7 as though you bought the win 7 DVD you used the win 10 upgrade and that would have converted your licence after one month of install - unless you have only had win 10 installed a few weeks, then maybe.

Other problem with Win 7 is you cannot use DISM to repair your image, it only exists in win 8 & 10

Now if you on win 10 you can run the second command on this page: http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/system-file-check-sfc-scan-and-repair-system-files/bc609315-da1f-4775-812c-695b60477a93

 

[Colif]

I won't pretend to know what that all means. I can see a lot of references to your processor in there in relation to the errors. If you still getting memory errors it could be a hardware problem or did you reinstall Avast again? It caused some of them last time...

I been trying to work out what ntkrnlmp.exe does, I can work out half of it, its something to do with ntoskrnl which is the Kernal of Windows. All your memory management errors seem to refer to it.

Have you done a memtest on your memory? I would just to write it off as a problem: http://www.memtest86.com/

 

[flaskmaster]

Sorry for the delay, with work and kids I can only spend so much time on my pc.

I installed win 7 and updated all the drivers and I believe all of the updates. I tried a stand-alone win 10 updater, it seemed to keep trying to download an iso, but never completed. So I kept do loading win 7 updates. I never installed avast, and the current build seems to be stable for now. Currently I pit the memtest on a USB drive, and last I checked it was at 91% after 4 hours. I had some stuff to do and now it's back to 58% after 5 hours, but no errors so far. I'm no expert but that seems to be excessive.

Edit: Saw some posts where 8-12 hours seems to be the norm. Gonna let it run overnight amd see what happens.

 

[Colif]

take whatever time you need, i am not going anywhere

Its your problem, I am just helping

 

[flaskmaster]

13 hours, zero errors running memtest. I'm left with manually updating to Win 10 I suppose. Last time I found a standalone Win 10 downloader. It would download the ISO, and then just sit there. I never had this problem last time. But since then I've download the several hundred Win 7 updates. I assume this would probably be the next best step.

 

[flaskmaster]

OK so while attempting to run the Win 10 readiness tool, my system crashed 3 times. I redownloaded the WhoCrashed program, and got this:

On Wed 4/20/2016 11:52:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042016-7300-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008CD0B28, 0xFFFFF88008CD0380, 0xFFFFF880012B5C04)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 4/20/2016 11:52:18 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008CD0B28, 0xFFFFF88008CD0380, 0xFFFFF880012B5C04)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 4/20/2016 11:45:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042016-7410-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8800120DEB3)
Bugcheck code: 0x50 (0xFFFFF9A00AAF3970, 0x0, 0xFFFFF8800120DEB3, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

I'm looking up Win 7 ntfs.sys errors, which seemed to be a big thing. Could this be caused by a bad SSD driver???

 

[Colif]

Check if its got latest firmware, its worth a look: http://kb.sandisk.com/app/answers/detail/a_id/15108/~/sandisk-ssd-dashboard-support-information

i think the driver would be on your motherboard, not specific to the ssd itself.

Win 7 chipset drivers can be found here: link

strange they don't have win 8 or win 10 chipset drivers though.

 

[flaskmaster]

I updated the MSI BIOS, used the SanDisk SSD Dashboard to confirm the SSD is working fine. The Win 10 update tool sat for hours "downloading" with seemingly zero results. I went out of town for the weekend, thought everything was OK. I loaded up a game, and within 10 minutes it crashed:

On Sun 4/24/2016 6:14:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042416-8065-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74080)
Bugcheck code: 0x50 (0xFFFFF684006D4D30, 0x0, 0xFFFFF80002EAEC8B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 4/24/2016 6:14:28 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF684006D4D30, 0x0, 0xFFFFF80002EAEC8B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I can't seem to update to Win 10, and I'm again at a loss. I was sure it was fixed.

 

[lodders]

1) When I upgraded to windows 10, the PC behaved very strangely until I updated the BIOS, but you have already done that....

2) If I have a complicated problem, I try to make it simpler, so I suggest you try running your PC with one HDD, one memory stick, and onboard graphics. If it doesn't crash, start adding components until you find what causes the problem.