Hi aymanibousi ,
Welcome to the Ten Forums BSOD forum.
There were no BSOD mini dump files.
The logs displayed a very large number of errors during dump creation (approximately 65 from 2/15.2018 to date)
Bugchecks were 3B and A.
So there were only 3 dumps with approximately 65 failures.
And there were no dump files available for debugging.
There were many problems related to drives: IO operation retried, bad block, surprise removed, controller errors.
There was drive corruption or possible corruption.
The GPU stopped responding and recovered.
For all tests / steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.
Perform the following steps:
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) 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
6) chkdsk /x /f /r
Run this command on every partition using the syntax: chkdsk /x /f /r C: or chkdsk /x /f /r D: etc. changing the drive letter to the applicable partition.
This may take many hours so plan to run overnight.
C:\Windows\system32>chkdsk /x /f /r
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
7) Use the information in this link to find the chkdsk reports in the event viewer. Copy and paste the reports > notepad > save to desktop > post a one drive or drop box share link into the thread
8) Run HD Tune on all drives.
Post images into the thread for the results of these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan
9) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
10) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread
11) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 12 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 Tutorials
The tests /steps that can be run overnight:
1) chkdsk /x /f /r
2) HD Tune full error scan
3) Memtest86+ version 5.01
Code:
Event[14932]: Log Name: System Source: Disk Date: 2018-04-09T22:45:02.538 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x1 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14933]: Log Name: System Source: Disk Date: 2018-04-09T22:45:02.538 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x11 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14934]: Log Name: System Source: Disk Date: 2018-04-09T22:45:02.538 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x21 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14935]: Log Name: System Source: Disk Date: 2018-04-09T22:45:09.781 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x1 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14936]: Log Name: System Source: Disk Date: 2018-04-09T22:45:09.781 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x11 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14937]: Log Name: System Source: Disk Date: 2018-04-09T22:45:09.781 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x21 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14938]: Log Name: System Source: Disk Date: 2018-04-09T22:45:16.990 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x1 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14939]: Log Name: System Source: Disk Date: 2018-04-09T22:45:16.990 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x11 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14940]: Log Name: System Source: Disk Date: 2018-04-09T22:45:16.990 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x21 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14941]: Log Name: System Source: Disk Date: 2018-04-09T22:45:40.876 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x1 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14942]: Log Name: System Source: Disk Date: 2018-04-09T22:45:40.876 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x11 for Disk 10 (PDO name: \Device\0000006a) was retried.Event[14943]: Log Name: System Source: Disk Date: 2018-04-09T22:45:40.876 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The IO operation at logical block address 0x21 for Disk 10 (PDO name: \Device\0000006a) was retried.
Code:
Event[2481]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-02-23T07:08:29.193 Event ID: 21 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-G9A3RL4 Description: A corrected hardware error has occurred.Component: AMD NorthbridgeError Source: Corrected Machine CheckError Type: 28Processor APIC ID: 0The details view of this entry contains further information.
Code:
Event[1680]: Log Name: System Source: Ntfs Date: 2018-02-19T08:28:12.864 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-G9A3RL4 Description: A corruption was discovered in the file system structure on volume I:.The exact nature of the corruption is unknown. The file system structures need to be scanned online.
Code:
Event[10789]: Log Name: System Source: Ntfs Date: 2018-04-02T20:32:32.944 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-G9A3RL4 Description: A corruption was discovered in the file system structure on volume D:.The exact nature of the corruption is unknown. The file system structures need to be scanned online.
Code:
Event[14915]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2018-04-09T22:42:29.726 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-G9A3RL4 Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume21.(An operation was attempted to a volume after it was dismounted.)
Code:
Event[14919]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2018-04-09T22:42:55.061 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-G9A3RL4 Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{e97997b1-413c-46dc-bf45-da6e24e02e38}, DeviceName: \Device\HarddiskVolume22.(An operation was attempted to a volume after it was dismounted.)
Code:
Event[14916]: Log Name: System Source: LSI_SAS2i Date: 2018-04-09T22:42:38.857 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The driver detected a controller error on \Device\RaidPort0.Event[14917]: Log Name: System Source: LSI_SAS2i Date: 2018-04-09T22:42:50.202 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The driver detected a controller error on \Device\RaidPort0.
Code:
Event[15019]: Log Name: System Source: Disk Date: 2018-04-09T22:53:39.770 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The driver detected a controller error on \Device\Harddisk8\DR8.Event[15020]: Log Name: System Source: Disk Date: 2018-04-09T22:53:39.770 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The driver detected a controller error on \Device\Harddisk8\DR8.Event[15021]: Log Name: System Source: Disk Date: 2018-04-09T22:53:39.770 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The driver detected a controller error on \Device\Harddisk8\DR8.Event[15022]: Log Name: System Source: Disk Date: 2018-04-09T22:53:39.770 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The driver detected a controller error on \Device\Harddisk8\DR8.
Code:
Event[11921]: Log Name: System Source: Disk Date: 2018-04-05T12:08:25.706 Event ID: 157 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: Disk 6 has been surprise removed.
Code:
Event[14918]: Log Name: System Source: Disk Date: 2018-04-09T22:42:55.059 Event ID: 157 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: Disk 0 has been surprise removed.
Code:
Event[3630]: Log Name: System Source: Display Date: 2018-03-03T15:31:15.455 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: Display driver amdkmdap stopped responding and has successfully recovered.
Code:
Event[8524]: Log Name: System Source: Display Date: 2018-03-22T22:52:06.776 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: Display driver amdkmdap stopped responding and has successfully recovered.
Code:
Event[13105]: Log Name: System Source: Disk Date: 2018-04-08T00:21:55.688 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: The device, \Device\Harddisk5\DR5, has a bad block.
Code:
Event[15375]: Log Name: System Source: volmgr Date: 2018-04-10T00:24:36.071 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP Description: Dump file creation failed due to error during dump creation.
Code:
Event[12460]: Log Name: System Source: volmgr Date: 2018-04-07T17:41:29.915 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: Crash dump initialization failed!
Code:
Event[14913]: Log Name: System Source: Virtual Disk Service Date: 2018-04-09T22:42:03.647 Event ID: 1 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: Unexpected failure. Error code: 2@02000018
Code:
Event[12391]: Log Name: System Source: Virtual Disk Service Date: 2018-04-07T17:35:11.853 Event ID: 25 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: A failure was encountered while retrieving the volume properties. Error code: 0x80070002@020A000DEvent[12392]: Log Name: System Source: Virtual Disk Service Date: 2018-04-07T17:35:11.907 Event ID: 25 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: A failure was encountered while retrieving the volume properties. Error code: 0x80070002@020A000DEvent[12393]: Log Name: System Source: Virtual Disk Service Date: 2018-04-07T17:35:11.931 Event ID: 25 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: A failure was encountered while retrieving the volume properties. Error code: 0x80070002@020A000DEvent[12394]: Log Name: System Source: Virtual Disk Service Date: 2018-04-07T17:35:53.400 Event ID: 25 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: A failure was encountered while retrieving the volume properties. Error code: 0x80070002@020A000DEvent[12395]: Log Name: System Source: Virtual Disk Service Date: 2018-04-07T17:35:53.552 Event ID: 25 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-G9A3RL4 Description: A failure was encountered while retrieving the volume properties. Error code: 0x80070002@020A000D
This was displayed as a problem device:
Code:
EldoS PnP virtual bus ROOT\SYSTEM\0002 Failure using the VxD loader.
Code:
14/03/2018 6:39 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: a
P2: 21
P3: ff
P4: e3
P5: fffff80182ed87b8
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\031418-9218-01.dmp
\\?\C:\WINDOWS\TEMP\WER-18171-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DBC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DBD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DDD.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_c67bdd681e6622dacc6a6e7ab632f773a6358a0_00000000_cab_1af07ed4
Analysis symbol:
Rechecking for solution: 0
Report Id: e358bd1b-f3d4-4399-b7b7-e434fac159a8
Report Status: 2049
Hashed bucket:14/03/2018 6:39 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: a
P2: 21
P3: ff
P4: e3
P5: fffff80182ed87b8
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\031418-9218-01.dmp
\\?\C:\WINDOWS\TEMP\WER-18171-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DBC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DBD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DDD.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_c67bdd681e6622dacc6a6e7ab632f773a6358a0_00000000_02f87dda
Analysis symbol:
Rechecking for solution: 0
Report Id: e358bd1b-f3d4-4399-b7b7-e434fac159a8
Report Status: 4
Hashed bucket:
Code:
Event[806]: Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2018-02-15T18:23:42.177
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-G9A3RL4
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff803a3cb0424, 0xfffff98db226e9a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e5972180-613b-4a0a-9081-5e30b0dd95d8.