New
#11
Sorry for polluting your thread. Yes, I sent him here cause I wasn't sure I was right.
I need help with BSOD (I was sent here from TomsHardware)
-
-
-
New #13
Hello again. I have been tests the whole day and this is what came up. Though I am pretty sure the porblem has nothing to do with my other two old HDD drive, since the problem seems to be with the NVME one, I still did run tests on the other two just to be sure.
HD Tune Screen shots
C: C Drive (SSD) - Album on Imgur (The SSD which seems to be the problem)
D: D Drive - Album on Imgur
G: G Drive - Album on Imgur
Weirdly enough there is no information under the health tab on the SSD like there are with the other two, however in WD own desktop app (dashboard) it does say the drive is healthy. Screenshot from Dashboard: Imgur: The magic of the Internet.
Chkdsk Results
What is weird about this is that, even though I did chkdsk for the C Drive as well, it doesn't show up in the notepad, when using ChkdskFromEvent.bat, however the two tests I did on my HDDs does. I do have something from 11/06/2020 which seems to be from the C drive (SSD) though.
G:
D:Code:TimeCreated : 02/11/2020 18:20:55 Message : Chkdsk was executed in read/write mode. Checking file system on G: The type of the file system is NTFS. Volume label is Gaming. Stage 1: Examining basic file system structure ... 88832 file records processed. File verification completed. Phase duration (File record verification): 927.47 milliseconds. 1 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. 0 bad file records processed. Phase duration (Bad file record checking): 0.27 milliseconds. Stage 2: Examining file name linkage ... 3 reparse records processed. 90060 index entries processed. Index verification completed. Phase duration (Index verification): 2.23 seconds. 0 unindexed files scanned. Phase duration (Orphan reconnection): 6.58 milliseconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.65 milliseconds. 3 reparse records processed. Phase duration (Reparse point and Object ID verification): 1.11 milliseconds. Stage 3: Examining security descriptors ... Cleaning up 4 unused index entries from index $SII of file 9. Cleaning up 4 unused index entries from index $SDH of file 9. Cleaning up 4 unused security descriptors. Security descriptor verification completed. Phase duration (Security descriptor verification): 13.62 milliseconds. 614 data files processed. Phase duration (Data attribute verification): 0.26 milliseconds. Stage 4: Looking for bad clusters in user file data ... 88816 files processed. File data verification completed. Phase duration (User file recovery): 1.07 hours. Stage 5: Looking for bad, free clusters ... 159084731 free clusters processed. Free space verification is complete. Phase duration (Free space recovery): 0.00 milliseconds. Windows has scanned the file system and found no problems. No further action is required. 976759807 KB total disk space. 340215292 KB in 88039 files. 20988 KB in 616 indexes. 0 KB in bad sectors. 184599 KB in use by the system. 65536 KB occupied by the log file. 636338928 KB available on disk. 4096 bytes in each allocation unit. 244189951 total allocation units on disk. 159084732 allocation units available on disk. Total duration: 1.07 hours (3862202 ms).
C: (From 11/06/2020)Code:TimeCreated : 02/11/2020 14:25:02 Message : Chkdsk was executed in read/write mode. Checking file system on D: The type of the file system is NTFS. Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid. Volume label is Dvs. Stage 1: Examining basic file system structure ... 76544 file records processed. File verification completed. Phase duration (File record verification): 841.84 milliseconds. 2 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. 0 bad file records processed. Phase duration (Bad file record checking): 0.28 milliseconds. Stage 2: Examining file name linkage ... 69 reparse records processed. 86722 index entries processed. Index verification completed. Phase duration (Index verification): 7.39 seconds. 0 unindexed files scanned. Phase duration (Orphan reconnection): 9.74 milliseconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.68 milliseconds. 69 reparse records processed. Phase duration (Reparse point and Object ID verification): 1.32 milliseconds. Stage 3: Examining security descriptors ... Cleaning up 20 unused index entries from index $SII of file 9. Cleaning up 20 unused index entries from index $SDH of file 9. Cleaning up 20 unused security descriptors. Security descriptor verification completed. Phase duration (Security descriptor verification): 10.70 milliseconds. 5089 data files processed. Phase duration (Data attribute verification): 0.35 milliseconds. Stage 4: Looking for bad clusters in user file data ... 76528 files processed. File data verification completed. Phase duration (User file recovery): 4.45 minutes. Stage 5: Looking for bad, free clusters ... 239436652 free clusters processed. Free space verification is complete. Phase duration (Free space recovery): 0.00 milliseconds. Windows has scanned the file system and found no problems. No further action is required. 976759807 KB total disk space. 18824932 KB in 59504 files. 15940 KB in 5091 indexes. 0 KB in bad sectors. 172323 KB in use by the system. 65536 KB occupied by the log file. 957746612 KB available on disk. 4096 bytes in each allocation unit. 244189951 total allocation units on disk. 239436653 allocation units available on disk. Total duration: 4.58 minutes (275381 ms).
-ReduksCode:TimeCreated : 11/06/2020 02:20:19 Message : Chkdsk was executed in scan mode on a volume snapshot. Checking file system on \Device\HarddiskVolume3 Volume label is SSD. Stage 1: Examining basic file system structure ... 183808 file records processed. File verification completed. Phase duration (File record verification): 1.14 seconds. 4029 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. 0 bad file records processed. Phase duration (Bad file record checking): 0.01 milliseconds. Stage 2: Examining file name linkage ... 93 reparse records processed. 262032 index entries processed. Index verification completed. Phase duration (Index verification): 3.27 seconds. Phase duration (Orphan reconnection): 0.00 milliseconds. Found 2 lost files (...\NvBackend <0x1,0x22b0e>, ...\accounts <0x1,0x22b69>); requesting reconnection to index "$I30" of directory "\Device\HarddiskVolume3\found.000" was not able to send command for self-healing due to lack of memory. Phase duration (Orphan recovery to lost and found): 0.00 milliseconds. 93 reparse records processed. Phase duration (Reparse point and Object ID verification): 1.02 milliseconds. Stage 3: Examining security descriptors ... Security descriptor verification completed. Phase duration (Security descriptor verification): 12.27 milliseconds. 39113 data files processed. Phase duration (Data attribute verification): 0.00 milliseconds. CHKDSK is verifying Usn Journal... Usn Journal verification completed. Windows has found problems that must be fixed offline. Please run "chkdsk /f" to fix the issues. 976122483 KB total disk space. 68462252 KB in 140577 files. 95040 KB in 39116 indexes. 281607 KB in use by the system. 65536 KB occupied by the log file. 907283584 KB available on disk. 4096 bytes in each allocation unit. 244030620 total allocation units on disk. 226820896 allocation units available on disk. Total duration: 4.50 seconds (4503 ms). ------------------------------------------------------------------- --- Stage 1: Examining basic file system structure ... Stage 2: Examining file name linkage ... CHKDSK is scanning unindexed files for reconnect to their original directory. 0 unindexed files recovered to original directory. CHKDSK is recovering remaining unindexed files. "chkdsk /scan" is aborting due to self-healing command failure: 0xc0000102 "chkdsk /f" will be required to repair the volume. Lost and found is located at \found.000 Stage 3: Examining security descriptors ...
-
New #14
I found you: Ztruker | Tom's Hardware Forum
Do you think it is helpful to ask a question below? I have an account there.
Forum Feedback | Tom's Hardware Forum
-
New #15
When available post results for the steps in post #7.
-
-
New #17
Hey everyone I ran even more tests today. Here are the results.
Sea Tools for Windows (Long generic test)
Imgur: The magic of the Internet
HD Sentinel (I apologize for the text being in Danish, I tried to change the language, but for the live of me I could not find a way to change it. If anyone know how to change it, let me know and I will reupload the screenshots in English. I hope it still makes at least a little sense though)
Imgur: The magic of the Internet
I ran chkdsk /b /r as well, but can't seem to find the results from it.
I only tested the SSD, since I'm 95% sure it has nothing to do with the HDDs, but if you want me to tests the HDDs as well, I will do so. Thanks
-Reduks
-
New #18
Upload a new V2.
Please use English as the default language:
https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10
Please test all drives.
-
-
New #19
Hey. I have tried my best to change the language to English, I have followed both of the guides you have linked to including this one: Change System UI Language in Windows 10 to the letter. However the language still does not change.
New V2 File:
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Sea Tools for Windows (Long generic test) for the HDDs:
Imgur: The magic of the Internet
Screenshots from HD Sentinel for the HDDs (Still in Danish though, so might be useless)
D: D Drive - Album on Imgur
G: G drive - Album on Imgur
-
New #20
Please run: Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.
Search for C:\windows\memory.dmp > save to downloads folder > post a share link into this thread using one drive, drop box, or google drive
Code:LastWriteTime Size (MB) FullName ------------- --------- -------- 11/1/2020 7:28:52 PM 1036.04 C:\Windows\MEMORY.DMP
For any BSOD:
a) run the V2 log collector to collect new log files
b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
Quote
Related Discussions
