[SOLVED] Devices intermittently not working on boot- reboot solves-various BSOD
- Thread starter jhine5588
- Start date
Perform a SFCFix Scan only:
- Double-click SFCFix.exe to run the tool. A dialog may come up asking for approval. If it does go ahead and allow.
- On completion a log file (SFCFix.txt) will be opened. Copy and Paste its content into your next reply.
SFCFix ran-
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-09-26 12:33:40.139
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Font-TrueType-Tai_Le and file taile.ttf. File is reported as corrupt by SFC.
CORRUPT: taile.ttf of component Microsoft-Windows-Font-TrueType-Tai_Le.
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Font-TrueType-Tai_Le and file taileb.ttf. File is reported as corrupt by SFC.
CORRUPT: taileb.ttf of component Microsoft-Windows-Font-TrueType-Tai_Le.
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 3
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2020-09-26 12:34:13.508
----------------------EOF-----------------------
Jeremy
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-09-26 12:33:40.139
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Font-TrueType-Tai_Le and file taile.ttf. File is reported as corrupt by SFC.
CORRUPT: taile.ttf of component Microsoft-Windows-Font-TrueType-Tai_Le.
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Font-TrueType-Tai_Le and file taileb.ttf. File is reported as corrupt by SFC.
CORRUPT: taileb.ttf of component Microsoft-Windows-Font-TrueType-Tai_Le.
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 3
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2020-09-26 12:34:13.508
----------------------EOF-----------------------
Jeremy
What do you mean by "Check Windows Update"?
Would you like me to try and repair my Win7 install or attempt to upgrade to Win10?
Jeremy
It looks like you quoted my message #14. Please respond to message #26.
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
Step 2:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
- Download the attachment fixlist.txt and save it to your desktop.
- Right-click on FRST64.exe and select "Run as administrator".
- Press the Fix button.
- The tool will now process fixlist.txt.
- If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
- When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
- Post the logfile Fixlog.txt as attachment in your next reply.
Step 2:
- Double-click SFCFix.exe to run the tool. A dialog may come up asking for approval. If it does go ahead and allow.
- On completion a log file (SFCFix.txt) will be opened. Copy and Paste its content into your next reply.
Steps performed in order requested:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-09-27 17:51:36.324
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Font-TrueType-Tai_Le and file taile.ttf. File is reported as corrupt by SFC.
CORRUPT: taile.ttf of component Microsoft-Windows-Font-TrueType-Tai_Le.
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Font-TrueType-Tai_Le and file taileb.ttf. File is reported as corrupt by SFC.
CORRUPT: taileb.ttf of component Microsoft-Windows-Font-TrueType-Tai_Le.
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 3
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2020-09-27 17:52:02.758
----------------------EOF-----------------------
Jeremy
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-09-27 17:51:36.324
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Font-TrueType-Tai_Le and file taile.ttf. File is reported as corrupt by SFC.
CORRUPT: taile.ttf of component Microsoft-Windows-Font-TrueType-Tai_Le.
WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Font-TrueType-Tai_Le and file taileb.ttf. File is reported as corrupt by SFC.
CORRUPT: taileb.ttf of component Microsoft-Windows-Font-TrueType-Tai_Le.
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 3
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2020-09-27 17:52:02.758
----------------------EOF-----------------------
Jeremy
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
- Download the attachment SFCFixScript.txt and save it on your desktop.
- Save any work you have open, and close all programs.
- Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
- SFCFix will launch, let it complete.
- Once done, a file will appear on your desktop, called SFCFix.txt.
- Open the file, then copy and paste its content in your next reply.
Completed:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-09-28 21:16:16.412
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Jeremy\Desktop\SFCFixScript.txt [0]
FileScan::
[0: 2] C:\Windows\winsxs\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taile.ttf
Expected: r4WHhbjvb0ULewP0OrR3M5qTs7bwCS38T2Ll9Q8YNl4=
Expected: 6.1.7600.16385 Found: Version number not available.
Successfully traced component amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4.
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery
[C:\Windows\Fonts\taile.ttf]
[1: 2] C:\Windows\winsxs\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taileb.ttf
Expected: 9VhvRKeFTPmbLmlnMAMGwHKGnbkiZSfyvqSI/peLYNA=
Expected: 6.1.7600.16385 Found: Version number not available.
Successfully traced component amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4.
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery
[C:\Windows\Fonts\taileb.ttf]
[2: 1] C:\Users\Jeremy\Desktop\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taile.ttf
File is untraceable.
Found: r4WHhbjvb0ULewP0OrR3M5qTs7bwCS38T2Ll9Q8YNl4=
Version number not available.
Trace not available.
[3: 1] C:\Users\Jeremy\Desktop\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taileb.ttf
File is untraceable.
Found: 9VhvRKeFTPmbLmlnMAMGwHKGnbkiZSfyvqSI/peLYNA=
Version number not available.
Trace not available.
[4: 1] C:\SFCFix\Backups\C\Windows\winsxs\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taile.ttf
File is untraceable.
Found: r4WHhbjvb0ULewP0OrR3M5qTs7bwCS38T2Ll9Q8YNl4=
Version number not available.
Trace not available.
[5: 1] C:\SFCFix\Backups\C\Windows\winsxs\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taileb.ttf
File is untraceable.
Found: 9VhvRKeFTPmbLmlnMAMGwHKGnbkiZSfyvqSI/peLYNA=
Version number not available.
Trace not available.
FileScan:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2020-09-28 21:16:20.645
Script hash: OLov33QQCsEuMFDq/UHNnyrtsLvF6WcPvpCHL2Lq6kM=
----------------------EOF-----------------------
Jeremy
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-09-28 21:16:16.412
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Jeremy\Desktop\SFCFixScript.txt [0]
FileScan::
[0: 2] C:\Windows\winsxs\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taile.ttf
Expected: r4WHhbjvb0ULewP0OrR3M5qTs7bwCS38T2Ll9Q8YNl4=
Expected: 6.1.7600.16385 Found: Version number not available.
Successfully traced component amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4.
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery
[C:\Windows\Fonts\taile.ttf]
[1: 2] C:\Windows\winsxs\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taileb.ttf
Expected: 9VhvRKeFTPmbLmlnMAMGwHKGnbkiZSfyvqSI/peLYNA=
Expected: 6.1.7600.16385 Found: Version number not available.
Successfully traced component amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4.
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery
[C:\Windows\Fonts\taileb.ttf]
[2: 1] C:\Users\Jeremy\Desktop\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taile.ttf
File is untraceable.
Found: r4WHhbjvb0ULewP0OrR3M5qTs7bwCS38T2Ll9Q8YNl4=
Version number not available.
Trace not available.
[3: 1] C:\Users\Jeremy\Desktop\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taileb.ttf
File is untraceable.
Found: 9VhvRKeFTPmbLmlnMAMGwHKGnbkiZSfyvqSI/peLYNA=
Version number not available.
Trace not available.
[4: 1] C:\SFCFix\Backups\C\Windows\winsxs\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taile.ttf
File is untraceable.
Found: r4WHhbjvb0ULewP0OrR3M5qTs7bwCS38T2Ll9Q8YNl4=
Version number not available.
Trace not available.
[5: 1] C:\SFCFix\Backups\C\Windows\winsxs\amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4\taileb.ttf
File is untraceable.
Found: 9VhvRKeFTPmbLmlnMAMGwHKGnbkiZSfyvqSI/peLYNA=
Version number not available.
Trace not available.
FileScan:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2020-09-28 21:16:20.645
Script hash: OLov33QQCsEuMFDq/UHNnyrtsLvF6WcPvpCHL2Lq6kM=
----------------------EOF-----------------------
Jeremy
The file scan looks normal.
Remove the folder amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4 from your desktop.
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log.
System Update Readiness Tool (SURT)
Remove the folder amd64_microsoft-windows-font-truetype-tai_le_31bf3856ad364e35_6.1.7600.16385_none_8b27023f8ebb68a4 from your desktop.
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log.
- Download SURT for your system. (Windows 7 SP1 x64)
- Once downloaded, execute the installer, and go through the installation (this process can take around 15-20 minutes).
- On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log.
- Attach this log to your next reply.
System Update Readiness Tool (SURT)
FRST Scan:
- Right-click the file FRST64.exe to run the tool as administrator.
- Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
- Press the Scan button.
- Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
- Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
Step 1:
Download
CrystalDiskInfo.zip and save it on your desktop.
Extract the .zip file into a new folder.
In this new folder, run the tool DiskInfo.
When the tool is finished, it will show some information about the hard disc.
Note: Resize the window so that all information is visible.
Take a screenshot. Read this on how to take a screenshot.
Upload the image file to a file-sharing site and post the download link.
Step 2:
Download
WhoCrashed and move the executable to your desktop.
Double-click "whocrashedSetup.exe" to install the tool.
'WhoCrashed' will start automatically when the installation is finished. Click the button Analyze.
When done, copy and paste the content in the window "Report" in your next reply.
Download
Extract the .zip file into a new folder.
In this new folder, run the tool DiskInfo.
When the tool is finished, it will show some information about the hard disc.
Note: Resize the window so that all information is visible.
Take a screenshot. Read this on how to take a screenshot.
Upload the image file to a file-sharing site and post the download link.
Step 2:
Download
Double-click "whocrashedSetup.exe" to install the tool.
'WhoCrashed' will start automatically when the installation is finished. Click the button Analyze.
When done, copy and paste the content in the window "Report" in your next reply.
Results of CrystalDisk is here
Results of WhoCrashed as follows:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 10/1/2020 7:00:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100120-19110-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880077D79F8, 0xFFFFF880077D7250, 0xFFFFF80002C5CEEC)
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 10/1/2020 7:00:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880077D79F8, 0xFFFFF880077D7250, 0xFFFFF80002C5CEEC)
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Mon 9/28/2020 9:26:44 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092920-16302-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x50 (0xFFFFF7FB7DA00000, 0x0, 0xFFFFF80002C3B2AE, 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 Tue 9/29/2020 8:20:16 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092920-16863-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0xA (0xFFFFF680001FE0D0, 0x0, 0x0, 0xFFFFF80002DD3C87)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 9/29/2020 8:16:38 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092920-17160-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80057175B0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred. A page table page has been corrupted.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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 9/27/2020 8:44:39 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092720-20763-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1BD5)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Tue 9/22/2020 9:52:29 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092220-19796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8005717580, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred. A page table page has been corrupted.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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 9/13/2020 12:01:26 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091720-20170-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880, 0x8, 0xFFFFF880)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 9/12/2020 7:03:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091220-17862-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C59DE9, 0xFFFFF88009A40DE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Sat 9/12/2020 8:46:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091220-15241-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0xD1 (0xFFFFF8800599C330, 0x5, 0x8, 0xFFFFF8800599C330)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 23 crash dumps have been found. Only 10 have been analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Jeremy
Results of WhoCrashed as follows:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 10/1/2020 7:00:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100120-19110-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880077D79F8, 0xFFFFF880077D7250, 0xFFFFF80002C5CEEC)
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 10/1/2020 7:00:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880077D79F8, 0xFFFFF880077D7250, 0xFFFFF80002C5CEEC)
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Mon 9/28/2020 9:26:44 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092920-16302-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x50 (0xFFFFF7FB7DA00000, 0x0, 0xFFFFF80002C3B2AE, 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 Tue 9/29/2020 8:20:16 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092920-16863-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0xA (0xFFFFF680001FE0D0, 0x0, 0x0, 0xFFFFF80002DD3C87)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 9/29/2020 8:16:38 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092920-17160-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80057175B0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred. A page table page has been corrupted.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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 9/27/2020 8:44:39 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092720-20763-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1BD5)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Tue 9/22/2020 9:52:29 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092220-19796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8005717580, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred. A page table page has been corrupted.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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 9/13/2020 12:01:26 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091720-20170-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880, 0x8, 0xFFFFF880)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 9/12/2020 7:03:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091220-17862-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C59DE9, 0xFFFFF88009A40DE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Sat 9/12/2020 8:46:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091220-15241-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0xD1 (0xFFFFF8800599C330, 0x5, 0x8, 0xFFFFF8800599C330)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 23 crash dumps have been found. Only 10 have been analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Jeremy
ChkDsk Scan
- Click on Start - All programs - Accessories.
- Rightclick on Command-prompt and select Run as administrator.
- When command prompt opens, typ chkdsk into it, then press enter.
- Wait for this to complete.
- Download ListChkdskResult.exe by SleepyDude and save it on your desktop.
- Rightclick ListChkdskResult.exe and select Run as administrator. Notepad will open the file ListChkdskResult.txt on completion. (The file ListChkdskResult.txt can be found on your desktop.)
- Copy and paste its content in your next reply.
Has Sysnative Forums helped you? Please consider donating to help us support the site!