I've been having problems with the new build. It often stalls on bootup, as described in this thread:
Windows Just Stops During Boot
The other night I got a "DRIVER_UNMAPPING_INVALID_VIEW" BSOD that I can't figure out. It was suggested that I post here. I hope someone can help figure this out.
Here is the V2 log:
Attachment 262647
Hi Gurn Blanston,
The log files displayed RAM overclock (3200).
The CPU supports RAM speeds up to 2933.
The logs displayed drive problems: bad block and drive file system corruption.
If there are recurrent BSOD with misbehaving drivers after returning to stock and fixing the drive they can be troubleshooted.
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}
12) 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
13) Make sure that there is no over clocking while troubleshooting
14) To ensure that there are no improper bios settings please reset the bios.
How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
3 Easy Ways to Clear CMOS (Reset BIOS)
How to Clear CMOS (AKA Reset BIOS Settings)
15) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.
C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Type: Y
reboot
16) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10
17) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan
18) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US
19) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10
Take Screenshot in Windows 10
How to Upload and Post Screenshots and Files at Ten Forums
Last edited by zbook; 11 Jan 2020 at 05:48.
Thanks zbook. I will do all of that and post back.
Here's steps 1 through 15:
Microsoft Windows [Version 10.0.18363.535]
(c) 2019 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 /scanhealth
Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Image Version: 10.0.18363.535
[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Image Version: 10.0.18363.535
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
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>chkdsk /scan
The type of the file system is NTFS.
Volume label is Main Boot.
Stage 1: Examining basic file system structure ...
1244160 file records processed.
File verification completed.
17378 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
64190 reparse records processed.
Found an unneeded link ($FILE_NAME: "2019-1~4.LOG") in index "$I30" of directory "\Users\Bryan\AppData\Local\Corsair\CUE\logs <0x33,0x262a>"
... repaired online.
1616512 index entries processed.
Index verification completed.
2 unindexed files scanned.
1 unindexed files recovered to lost and found.
Found missing Index entry for file "\Users\Bryan\AppData\Local\AMD\CN\RGStats.db <0x8,0xe7781>" from index "\??\C:\found.000" of directory "$I30"
... repaired online.
Found lost file "\Users\Bryan\AppData\Local\Corsair\CUE\logs\2019-11-17T20-22-36.log <0x1fb,0x2a>"; requesting reconnection to index "$I30" of directory "\Users\Bryan\AppData\Local\Corsair\CUE\logs <0x33,0x262a>"
... repaired online.
64190 reparse records processed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
186177 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has found problems and they were all fixed online.
No further action is required.
976270332 KB total disk space.
252846864 KB in 1013346 files.
536312 KB in 186179 indexes.
0 KB in bad sectors.
1357172 KB in use by the system.
65536 KB occupied by the log file.
721529984 KB available on disk.
4096 bytes in each allocation unit.
244067583 total allocation units on disk.
180382496 allocation units available on disk.
C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\EIGHT-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk5\\Partition1"'
Property(s) update successful.
C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\EIGHT-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk5\\Partition1"'
Property(s) update successful.
C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE
C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7
C:\WINDOWS\system32>bcdedit /enum {badmemory}
RAM Defects
-----------
identifier {badmemory}
C:\WINDOWS\system32>
This may take a bit to answer. My network port keeps shutting down now. Arrrgh.
1) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.
C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Type: Y
reboot
2) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10
The motherboard went up in smoke. It's a total loss, so I guess that was the problem.
Thanks for your help. I'm marking this as solved.
What had happened?
Doing a chkdsk overnight and in the morning it had shut down, when I powered on again, smoke came out.
Sucks to be me.
Quote