New
#21
When available please post results from posts #7 and #10.
BSOD even after Windows 10 reset, 0x000000e
-
-
New #22
I completed most of the directions but it crashed on me before I could get everything. I should mention that I swapped out my RAM For a different, slower model and it's still giving me all of these problems.
I'm also trying to reboot into the computer and it's not loading. The circle that swirls under "ASUS" just keeps going forever. I can still get into BIOS though.
I'm really concerned now. Since it wont let me boot into Windows 10, I'm going to run Memtest.
- - - Updated - - -
I was able to complete a memtest with my PC, and my RAM passed every test. I'm attaching the test results to this post, and also I think I might have found what's wrong.
Last time that my computer crashed (shortly after I booted in after the memtest), my HDD (which is attached to my computer via a 3.0 USB port because the HDD wont fit into my mini itx case) wasn't being detected despite being connected to my computer. It took me a few tries to connect it to my computer, and when it did the drive had an icon marking it as "red", then my computer crashed. It didn't create a log file (stayed at 0% after 5 minutes) so I hard reset again.
Now my computer is on again, I've connected the drive again and windows tells me that the drive needs to be repaired. So I repair it, then look at Hard Disk Sentinel, which shows me that this drive can't be assessed. Then when I try to do a Surface test, it takes a few minutes to initialize. By the time it does show the ability for me to test the HDD disconnects from my PC again.
Do you think that the HDD could be the reason why my computer keeps on crashing? Or maybe, the method by which it's connected (USB 3.0). My case (Fractal Design Node 202) can't fit the HDD inside of it, so if this is the case would using another external caddy work...?
So attached are the memtest files (wont let me attach the html so I took pictures of the results) and some screenshots (taken by phone) of the phenomenon.
- - - Updated - - -
Sorry, I just also wanted to add: I was able to get into my computer and I don't know if the Hard Drive is the problem.
I used another application (CrystalDiskInfo) to analyze my 3 drives and they all seem fine. But I'm not an expert. BTW, thank you guys for helping me so far. This is really difficult.
-
New #23
1) For disk management please widen the status column so that the words within the parenthesis are not cut off.
2) Open administrative command prompt and copy and paste all at one time:
3) 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 threadCode:bcdedit /enum all bcdedit | find "osdevice" reagentc /info diskpart lis dis lis vol sel dis 0 det dis lis par sel par1 det par sel par2 det par sel par 3 det par sel par 4 det par sel par 5 det par sel dis 1 det dis lis par sel par1 det par sel par2 det par sel par 3 det par sel par 4 det par sel par 5 det par sel dis 2 det dis lis par sel par1 det par sel par2 det par sel par 3 det par
4) 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
5) 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
6) 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
-
New #24
1) Attached below. Sorry about that.
2)
"Microsoft Windows [Version 10.0.18363.628]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>bcdedit /enum all
Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{509ccb72-47bf-11ea-a90c-806e6f6e6963}
{b57162fe-4aee-11ea-9b92-806e6f6e6963}
{b57162ff-4aee-11ea-9b92-806e6f6e6963}
{b5716300-4aee-11ea-9b92-806e6f6e6963}
timeout 1
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume5
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {be4c0e9c-4967-11ea-bdc9-f853f4686079}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Firmware Application (101fffff)
-------------------------------
identifier {509ccb72-47bf-11ea-a90c-806e6f6e6963}
description Hard Drive
Firmware Application (101fffff)
-------------------------------
identifier {b57162fe-4aee-11ea-9b92-806e6f6e6963}
description UEFI:CD/DVD Drive
Firmware Application (101fffff)
-------------------------------
identifier {b57162ff-4aee-11ea-9b92-806e6f6e6963}
description UEFI:Removable Device
Firmware Application (101fffff)
-------------------------------
identifier {b5716300-4aee-11ea-9b92-806e6f6e6963}
description UEFI:Network Device
Windows Boot Loader
-------------------
identifier {820eb7fe-3034-11ea-b6c9-b17b32b786fa}
device ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{820eb7ff-3034-11ea-b6c9-b17b32b786fa}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{820eb7ff-3034-11ea-b6c9-b17b32b786fa}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {820eb7fe-3034-11ea-b6c9-b17b32b786fa}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {be4c0e9c-4967-11ea-bdc9-f853f4686079}
nx OptIn
bootmenupolicy Standard
Resume from Hibernate
---------------------
identifier {be4c0e9c-4967-11ea-bdc9-f853f4686079}
device partition=C:
path \WINDOWS\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {820eb7fe-3034-11ea-b6c9-b17b32b786fa}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume5
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes
EMS Settings
------------
identifier {emssettings}
bootems No
Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Local
RAM Defects
-----------
identifier {badmemory}
Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}
Device options
--------------
identifier {820eb7ff-3034-11ea-b6c9-b17b32b786fa}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume3
ramdisksdipath \Recovery\WindowsRE\boot.sdi
C:\WINDOWS\system32>bcdedit | find "osdevice"
osdevice partition=C:
C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 820eb7fe-3034-11ea-b6c9-b17b32b786fa
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
C:\WINDOWS\system32>diskpart
Microsoft DiskPart version 10.0.18362.1
Copyright (C) Microsoft Corporation.
On computer: DESKTOP-45A0HFF
DISKPART> lis dis
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 223 GB 1024 KB *
Disk 1 Online 223 GB 1024 KB *
Disk 2 Online 1863 GB 0 B
DISKPART> lis vol
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C Sandisk SSD NTFS Partition 222 GB Healthy Boot
Volume 1 NTFS Partition 860 MB Healthy
Volume 2 Recovery NTFS Partition 450 MB Healthy
Volume 3 E Crucial SSD NTFS Partition 223 GB Healthy
Volume 4 FAT32 Partition 99 MB Healthy System
Volume 5 F Seagate HDD NTFS Partition 1863 GB Healthy
DISKPART> sel dis 0
Disk 0 is now the selected disk.
DISKPART> det dis
SanDisk SDSSDA240G
Disk ID: {57607477-6B51-4DF4-B425-F40F5BA994CE}
Type : SATA
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1700)#ATA(C00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C Sandisk SSD NTFS Partition 222 GB Healthy Boot
Volume 1 NTFS Partition 860 MB Healthy
DISKPART> lis par
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Reserved 128 MB 17 KB
Partition 2 Primary 222 GB 129 MB
Partition 3 Recovery 860 MB 222 GB
DISKPART> sel par1
Microsoft DiskPart version 10.0.18362.1
DISK - Shift the focus to a disk. For example, SELECT DISK.
PARTITION - Shift the focus to a partition. For example, SELECT PARTITION.
VOLUME - Shift the focus to a volume. For example, SELECT VOLUME.
VDISK - Shift the focus to a virtual disk. For example, SELECT VDISK.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel par2
Microsoft DiskPart version 10.0.18362.1
DISK - Shift the focus to a disk. For example, SELECT DISK.
PARTITION - Shift the focus to a partition. For example, SELECT PARTITION.
VOLUME - Shift the focus to a volume. For example, SELECT VOLUME.
VDISK - Shift the focus to a virtual disk. For example, SELECT VDISK.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel par 3
Partition 3 is now the selected partition.
DISKPART> det par
Partition 3
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : No
Required: Yes
Attrib : 0X8000000000000001
Offset in Bytes: 239153971200
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 6 NTFS Partition 860 MB Healthy Hidden
DISKPART> sel par 4
The specified partition is not valid.
Please select a valid partition.
There is no partition selected.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel par 5
The specified partition is not valid.
Please select a valid partition.
There is no partition selected.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel dis 1
Disk 1 is now the selected disk.
DISKPART> det dis
CT240BX200SSD1
Disk ID: {44CB6FDE-BADC-4D27-91C7-01A534B92AEE}
Type : SATA
Status : Online
Path : 1
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1700)#ATA(C01T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 2 Recovery NTFS Partition 450 MB Healthy
Volume 3 E Crucial SSD NTFS Partition 223 GB Healthy
Volume 4 FAT32 Partition 99 MB Healthy System
DISKPART> lis par
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Recovery 450 MB 1024 KB
Partition 2 System 99 MB 451 MB
Partition 3 Primary 223 GB 550 MB
DISKPART> sel par1
Microsoft DiskPart version 10.0.18362.1
DISK - Shift the focus to a disk. For example, SELECT DISK.
PARTITION - Shift the focus to a partition. For example, SELECT PARTITION.
VOLUME - Shift the focus to a volume. For example, SELECT VOLUME.
VDISK - Shift the focus to a virtual disk. For example, SELECT VDISK.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel par2
Microsoft DiskPart version 10.0.18362.1
DISK - Shift the focus to a disk. For example, SELECT DISK.
PARTITION - Shift the focus to a partition. For example, SELECT PARTITION.
VOLUME - Shift the focus to a volume. For example, SELECT VOLUME.
VDISK - Shift the focus to a virtual disk. For example, SELECT VDISK.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel par 3
Partition 3 is now the selected partition.
DISKPART> det par
Partition 3
Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden : No
Required: No
Attrib : 0000000000000000
Offset in Bytes: 576716800
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 3 E Crucial SSD NTFS Partition 223 GB Healthy
DISKPART> sel par 4
The specified partition is not valid.
Please select a valid partition.
There is no partition selected.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel par 5
The specified partition is not valid.
Please select a valid partition.
There is no partition selected.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel dis 2
Disk 2 is now the selected disk.
DISKPART> det dis
ST2000DM 006-2DM164 SCSI Disk Device
Disk ID: F9C9DA78
Type : USB
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 5 F Seagate HDD NTFS Partition 1863 GB Healthy
DISKPART> lis par
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 1863 GB 1024 KB
DISKPART> sel par1
Microsoft DiskPart version 10.0.18362.1
DISK - Shift the focus to a disk. For example, SELECT DISK.
PARTITION - Shift the focus to a partition. For example, SELECT PARTITION.
VOLUME - Shift the focus to a volume. For example, SELECT VOLUME.
VDISK - Shift the focus to a virtual disk. For example, SELECT VDISK.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel par2
Microsoft DiskPart version 10.0.18362.1
DISK - Shift the focus to a disk. For example, SELECT DISK.
PARTITION - Shift the focus to a partition. For example, SELECT PARTITION.
VOLUME - Shift the focus to a volume. For example, SELECT VOLUME.
VDISK - Shift the focus to a virtual disk. For example, SELECT VDISK.
DISKPART> det par
There is no partition selected.
Please select a partition and try again.
DISKPART> sel par 3
The specified partition is not valid.
Please select a valid partition.
There is no partition selected.
DISKPART> det par "
4) I'm doing this right now, but I have to leave for work in a little bit. I was able to check one disk, another says it'll have to be done with a restart, and the HDD is being checked right now. This is going to take a while so I might have to see the results when I get back from work.
5) Will do that once it's done
6) I was able to make another V2 file, but I can't find the memory dump file that you talked about.
-
New #25
1) Find a flash drive that you can format (> or = 8 GB)
2) Create a bootable Windows 10 iso
https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10
3) Post share link reports for each drives chkdsk /r /v report
4) Perform an in place upgrade repair:
Repair Install Windows 10 with an In-place Upgrade
5) Run these modified commands: (all at the same time and post a share link)
Code:bcdedit /enum all bcdedit | find "osdevice" reagentc /info diskpart lis dis lis vol sel dis 0 det dis lis par sel par 1 det par sel par 2 det par sel par 3 det par sel par 4 det par sel par 5 det par sel dis 1 det dis lis par sel par 1 det par sel par 2 det par sel par 3 det par sel par 4 det par sel par 5 det par sel dis 2 det dis lis par sel par 1 det par sel par 2 det par sel par 3 det par
6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
7) After the in place upgrade repair post new images of:
a) startup and recovery system failure and virtual memory/page file settings
b) Ccleaner settings for windows tab: system and advanced boxes
8) Plan to test the computer in safe mode with networking for several days or more.
(The longer the continuous testing period the better the testing environment)
9) Comment into the thread whether BSOD happen or do not happen while in safe mode.
10) Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance
11) 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
Code:Event[1696]: Log Name: System Source: disk Date: 2020-02-08T23:12:37.052 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR3 during a paging operation. Event[1697]: Log Name: System Source: disk Date: 2020-02-08T23:12:41.052 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR3 during a paging operation.
Code:Event[1695]: Log Name: System Source: disk Date: 2020-02-08T23:11:53.179 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: The IO operation at logical block address 0x0 for Disk 2 (PDO name: \Device\0000008b) was retried.
Code:Event[1693]: Log Name: System Source: UASPStor Date: 2020-02-08T23:10:55.178 Event ID: 129 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: Reset to device, \Device\RaidPort2, was issued. Event[1694]: Log Name: System Source: UASPStor Date: 2020-02-08T23:11:43.177 Event ID: 129 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: Reset to device, \Device\RaidPort2, was issued.
Code:Event[1672]: Log Name: System Source: Ntfs Date: 2020-02-08T23:05:21.783 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: {Delayed Write Failed} Windows was unable to save all the data for the file F:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Event[1673]: Log Name: System Source: Ntfs Date: 2020-02-08T23:05:21.784 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: {Delayed Write Failed} Windows was unable to save all the data for the file F:\$Extend\$UsnJrnl:$J. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Event[1674]: Log Name: System Source: Ntfs Date: 2020-02-08T23:05:21.784 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: {Delayed Write Failed} Windows was unable to save all the data for the file F:\SteamLibrary\steamapps\workshop\downloads. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Event[1675]: Log Name: System Source: Application Popup Date: 2020-02-08T23:05:21.786 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-45A0HFF Description: Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 Event[1676]: Log Name: System Source: Application Popup Date: 2020-02-08T23:05:21.787 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-45A0HFF Description: Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 Event[1677]: Log Name: System Source: Application Popup Date: 2020-02-08T23:05:21.787 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-45A0HFF Description: Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 Event[1678]: Log Name: System Source: Ntfs Date: 2020-02-08T23:05:21.786 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: {Delayed Write Failed} Windows was unable to save all the data for the file F:\$BitMap. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Event[1679]: Log Name: System Source: Ntfs Date: 2020-02-08T23:05:21.786 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: {Delayed Write Failed} Windows was unable to save all the data for the file F:\SteamLibrary\steamapps. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Event[1680]: Log Name: System Source: Application Popup Date: 2020-02-08T23:05:21.787 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-45A0HFF Description: Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 Event[1681]: Log Name: System Source: Application Popup Date: 2020-02-08T23:05:21.788 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-45A0HFF Description: Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 Event[1682]: Log Name: System Source: Ntfs Date: 2020-02-08T23:05:22.287 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: {Delayed Write Failed} Windows was unable to save all the data for the file F:\SteamLibrary\steamapps\workshop\downloads\ .. 5462101\Gladio_Outfit_jumper_outfit.ffxvbinmod. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Event[1683]: Log Name: System Source: Application Popup Date: 2020-02-08T23:05:22.287 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-45A0HFF Description: Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 0x7ff85a592d58 Event[1684]: Log Name: System Source: Ntfs Date: 2020-02-08T23:05:22.296 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: {Delayed Write Failed} Windows was unable to save all the data for the file F:\SteamLibrary\steamapps\workshop\downloads\ .. 5462101\Gladio_Outfit_jumper_outfit.ffxvbinmod. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Event[1685]: Log Name: System Source: Ntfs Date: 2020-02-08T23:05:22.297 Event ID: 50 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: {Delayed Write Failed} Windows was unable to save all the data for the file F:\SteamLibrary\steamapps\appmanifest_637650.acf. The data has been lost. This error may be caused by a failure of your computer hardware or network connection.Code:Event[1658]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.449 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1659]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.466 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1660]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.470 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1661]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.474 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1662]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.478 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1663]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.478 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1664]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.479 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1665]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.482 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1666]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.486 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1667]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.486 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1668]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.490 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1669]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.493 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.) Event[1670]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2020-02-08T23:05:21.517 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2235244097-369554782-922184630-1002 User Name: DESKTOP-45A0HFF\Marquela Nunes Computer: DESKTOP-45A0HFF Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.)
Code:Event[1650]: Log Name: System Source: disk Date: 2020-02-08T23:05:17.376 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. Event[1651]: Log Name: System Source: disk Date: 2020-02-08T23:05:17.376 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. Event[1652]: Log Name: System Source: disk Date: 2020-02-08T23:05:21.377 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. Event[1653]: Log Name: System Source: disk Date: 2020-02-08T23:05:21.377 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. Event[1654]: Log Name: System Source: disk Date: 2020-02-08T23:05:21.377 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. Event[1655]: Log Name: System Source: disk Date: 2020-02-08T23:05:21.377 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. Event[1656]: Log Name: System Source: disk Date: 2020-02-08T23:05:21.377 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. Event[1657]: Log Name: System Source: disk Date: 2020-02-08T23:05:21.377 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
Code:Event[1587]: Log Name: System Source: volmgr Date: 2020-02-08T23:01:46.185 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-45A0HFF Description: Dump file creation failed due to error during dump creation.
-
New #26
The code for the 5) of my previous post:
Microsoft Windows [Version 10.0.18363.628]
(c) 2019 Microsoft Corporation. All rights reserved.
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) chkdsk /r /v C:
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) y
This volume will be checked the next time the system restarts.
C:\WINDOWS\system32> chkdsk /r /v E:
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) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is Crucial SSD.
Stage 1: Examining basic file system structure ...
174592 file records processed.
File verification completed.
32 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
4 reparse records processed.
180992 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
4 reparse records processed.
Stage 3: Examining security descriptors ...
Cleaning up 40 unused index entries from index $SII of file 9.
Cleaning up 40 unused index entries from index $SDH of file 9.
Cleaning up 40 unused security descriptors.
Security descriptor verification completed.
3201 data files processed.
CHKDSK is verifying Usn Journal...
36388112 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
174576 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
22872995 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
233866239 KB total disk space.
142076568 KB in 55981 files.
14072 KB in 3202 indexes.
0 KB in bad sectors.
283615 KB in use by the system.
65536 KB occupied by the log file.
91491984 KB available on disk.
4096 bytes in each allocation unit.
58466559 total allocation units on disk.
22872996 allocation units available on disk.
C:\WINDOWS\system32> chkdsk /r /v F:
The type of the file system is NTFS.
Volume label is Seagate HDD.
Stage 1: Examining basic file system structure ...
900352 file records processed.
File verification completed.
3198 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
3124 reparse records processed.
989088 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
3124 reparse records processed.
Stage 3: Examining security descriptors ...
Cleaning up 162 unused index entries from index $SII of file 9.
Cleaning up 162 unused index entries from index $SDH of file 9.
Cleaning up 162 unused security descriptors.
Security descriptor verification completed.
44369 data files processed.
CHKDSK is verifying Usn Journal...
41315728 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
900336 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
27838610 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
1953512447 KB total disk space.
1840983852 KB in 356976 files.
107396 KB in 44370 indexes.
0 KB in bad sectors.
1066755 KB in use by the system.
65536 KB occupied by the log file.
111354444 KB available on disk.
4096 bytes in each allocation unit.
488378111 total allocation units on disk.
27838611 allocation units available on disk.
C:\WINDOWS\system32>"
Drive C: will be inspected shortly. I should mention that I left this running all day and nothing's crashed yet
- - - Updated - - -
The code for the 5) of my previous post:
Microsoft Windows [Version 10.0.18363.628]
(c) 2019 Microsoft Corporation. All rights reserved.
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) chkdsk /r /v C:
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) y
This volume will be checked the next time the system restarts.
C:\WINDOWS\system32> chkdsk /r /v E:
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) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is Crucial SSD.
Stage 1: Examining basic file system structure ...
174592 file records processed.
File verification completed.
32 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
4 reparse records processed.
180992 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
4 reparse records processed.
Stage 3: Examining security descriptors ...
Cleaning up 40 unused index entries from index $SII of file 9.
Cleaning up 40 unused index entries from index $SDH of file 9.
Cleaning up 40 unused security descriptors.
Security descriptor verification completed.
3201 data files processed.
CHKDSK is verifying Usn Journal...
36388112 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
174576 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
22872995 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
233866239 KB total disk space.
142076568 KB in 55981 files.
14072 KB in 3202 indexes.
0 KB in bad sectors.
283615 KB in use by the system.
65536 KB occupied by the log file.
91491984 KB available on disk.
4096 bytes in each allocation unit.
58466559 total allocation units on disk.
22872996 allocation units available on disk.
C:\WINDOWS\system32> chkdsk /r /v F:
The type of the file system is NTFS.
Volume label is Seagate HDD.
Stage 1: Examining basic file system structure ...
900352 file records processed.
File verification completed.
3198 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
3124 reparse records processed.
989088 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
3124 reparse records processed.
Stage 3: Examining security descriptors ...
Cleaning up 162 unused index entries from index $SII of file 9.
Cleaning up 162 unused index entries from index $SDH of file 9.
Cleaning up 162 unused security descriptors.
Security descriptor verification completed.
44369 data files processed.
CHKDSK is verifying Usn Journal...
41315728 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
900336 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
27838610 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
1953512447 KB total disk space.
1840983852 KB in 356976 files.
107396 KB in 44370 indexes.
0 KB in bad sectors.
1066755 KB in use by the system.
65536 KB occupied by the log file.
111354444 KB available on disk.
4096 bytes in each allocation unit.
488378111 total allocation units on disk.
27838611 allocation units available on disk.
C:\WINDOWS\system32>"
Drive C: will be inspected shortly. I should mention that I left this running all day and nothing's crashed yet
-
New #27
UPDATE: So I went out and bought new RAM. Stress tested the ram for 8 hours as I slept and everything was fine, no errors. Then I try to play Sims 4, I play for 15 minutes before I crash. my BSOD still can't generate any dump files and stays at 0%.
I'm going to test this with another game. If Sims 4 ends up being the culprit I'll be pretty sad (I love that game). For now I've attached another crash log.
-
New #28
Free up space on C: drive so that there is > 30 GB free space:
Code:------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 12.3 GB Total Space: 227.9 GB File System: NTFS Model: SanDisk SDSSDA240G Drive: E: Free Space: 89.3 GB Total Space: 228.4 GB File System: NTFS Model: CT240BX200SSD1 Drive: F: Free Space: 99.5 GB Total Space: 1907.7 GB File System: NTFS Model: ST2000DM 006-2DM164 USB Device
Indicate the progress with the in place upgrade repair.
Read these links on Windows driver verifier: (do not use the tool until it is communicated in the thread)
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983
-
-
New #29
-
New #30
Please update the progress with each step in post #25.
1) Run setupdiag > post a share link into the thread
https://docs.microsoft.com/en-us/win...rade/setupdiag
2) Make a new restore point:
Create System Restore Point in Windows 10
3) Learn the methods to run the reset and bootmode commands to turn off the tool
4) Start Windows driver verifier with the 3 customized test settings in the TF link
5) If there are no BSOD then increase the number of simultaneous customized test settings by 3 - 5 / hour up to the 19 displayed in the Microsoft link
6) Plan to run the tool for48 hours and then for an additional 36 hours after the last BSOD
7) If there are performance problems or slow boot the customized settings can be modified
8) 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
