Windows 10: BSOD after Win10 fall update.While browsing and Gaming.

Hello and greetings.
I'm having a hard time after this windows fall update.First time i got bsod was while playing pubg and then i kept getting constant bsod while playing games such as Pubg-Dota2-Overwatch. But nothing happens when playing cs:go and heroes of the storm.After few bsod later my windows files are getting corrupted (like start menu not working at all) and losing profile information such as login infos and chrome profiles.Windows kept opennig new users after restarts because it cannot use main admin account.Since i cannot use anything i tried to reset my windows.This didnt help me at all. Still getting bsod,still games crashing. I hope you guys can help me.

:)

 

BSOD - atikmdag.sys & Crtitical Structure Error

I installed Win10. I installed a game which kept causing a BSOD with atikmdag.sys. I fixed the issue by copying the atikmdag.sys DLL from ATI to System32 drivers folder. The game launched after that.

However, now the computer keeps crashing with Critical Structure Error BSOD, and the solutions for them suggests upgrading driver for ATI which again takes me back to the first issue.

 

Bluescreen - win32kfull.sys

I'm still getting this annoying BSOD.

Last thing I did was going back to an older version of Nvidia drivers (385.41), but that did not fix anything.



In the Nvidia forums I found this, which seems similar to my problem:



I am experience everyday BSODs with exception in win32kfull.sys

Mostly when i alt+tab game (Dark Souls 2, for example) and browsing Google Chrome.

Windows Fall Creators Update 16299.19, x64, and the latest nvidia hotfix driver 378.98.



(https://forums.geforce.com/default/...feedback-thread-released-10-17-17-/?offset=49)

 

Please update the system specs in the "My Computer" section:
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums General Tips Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums


The log files report many problems with the drive including:
corruption of the master file table (MFT)
paging errors
failure to flush data
excessive numbers of chkdsk repairs
I/O failure due to hardware error
Unrecoverable recovery failure I/O operation

There were problems with:
low virtual memory
paging file size
crash dump initialization failure
dump file deletion

Bugchecks included:
1a
7a
c4
154
ef


Perform the following steps:
1) Backup all files to another drive or to the cloud
2) Create a brand new restore point
3) Create a backup image of the drive using Macrium:
Macrium Software | Macrium Reflect Free
4) Save the backup image to another drive or to the cloud
5) Run HDTune:
HD Tune website
to check the health,
scan for errors, no quick scan but full scan
run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 General Tips Tutorials

6) Make sure that there is no over clocking while troubleshooting.

7) Sometimes there are problems in the bios that produce bsod.

The BIOS: Version/Date American Megatrends Inc. V20.3, 9/26/2013

8) Please check to see if this is the most up to date version.

9) To ensure that there are no improper bios settings please reset the bios.

10) Sometimes there can be failure to boot after resetting the bios.

11) So please make sure your files are backed up.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings

3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

12) 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.

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.
When Memtest86+ 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 BSOD Tutorials

13) In the left lower corner search type: system > open system control panel > on the left pane click on advanced system settings > on the advanced tab startup and recovery click settings > post an image into the thread
14) on the advanced tab and performance click on settings > click advanced tab > under virtual memory click change > post an image into the thread
Take Screenshot in Windows 10 General Tips Tutorials

15) locate the memory dump file and post into the thread using a one drive or drop box share link:
memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP
Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

16) Open administrative command prompt and type or copy and paste:
17) sfc /scannow
18) dism /online /cleanup-image /checkhealth
19) dism /online /cleanup-image /scanhealth
20) dism /online /cleanup-image /restorehealth
21) 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
22) chkdsk /x /f /r
This may take many hours so plan to run overnight
23) Use the information in this link to find the chkdsk report in the event viewer and post the report into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

Code: Event[1367]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-11-03T23:10:12.958 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-21-2227570398-2871758619-4142871433-1001 User Name: DESKTOP-94V7TPK\wynem Computer: DESKTOP-94V7TPK Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: C:, DeviceName: \Device\HarddiskVolume2.(A device which does not exist was specified.)[/quote] Code: Event[3921]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-11-09T10:45:30.476 Event ID: 98 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: Volume C: (\Device\HarddiskVolume2) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.Event[3922]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:30.498 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-94V7TPK Description: A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.[/quote] Code: Event[3963]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:37.250 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-94V7TPK Description: A corruption was discovered in the file system structure on volume C:.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0xb8000000008853. The name of the file is "\ProgramData\NVIDIA Corporation\NvTelemetry\nvtelemetry.log".[/quote] Code: Event[3973]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:39.773 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-94V7TPK Description: A corruption was discovered in the file system structure on volume C:.A file on the volume is no longer reachable from its parent directory. The parent file reference number is 0x4b00000000bf29. The name of the parent directory is "\Users\wynem\AppData\Local\NVIDIA\NvBackend". The parent index attribute is ":$I30:$INDEX_ALLOCATION". The file reference number of the file that needs to be reconnected is 0x3d70000000000fc. There may be additional files on the volume that also need to be reconnected to this parent directory.[/quote] Code: Event[3969]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:38.848 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-94V7TPK Description: A corruption was discovered in the file system structure on volume C:.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x9600000000888d. The name of the file is "\Users\wynem\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\DeviceSearchCache\AppCache131546870277197422.txt".Event[3970]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:38.856 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-94V7TPK Description: A corruption was discovered in the file system structure on volume C:.A file on the volume is no longer reachable from its parent directory. The parent file reference number is 0x1600000001b9c6. The name of the parent directory is "\ProgramData\NVIDIA Corporation\NvTelemetry". The parent index attribute is ":$I30:$INDEX_ALLOCATION". The file reference number of the file that needs to be reconnected is 0xd8000000000487. There may be additional files on the volume that also need to be reconnected to this parent directory.Event[3971]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:38.863 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-94V7TPK Description: A corruption was discovered in the file system structure on volume C:.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1800000000889a. The name of the file is "\Users\wynem\AppData\Local\Google\Chrome\User Data\Default\Secure Preferences".[/quote] Code: Event[3969]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:38.848 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-94V7TPK Description: A corruption was discovered in the file system structure on volume C:.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x9600000000888d. The name of the file is "\Users\wynem\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\DeviceSearchCache\AppCache131546870277197422.txt".Event[3970]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:38.856 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-94V7TPK Description: A corruption was discovered in the file system structure on volume C:.A file on the volume is no longer reachable from its parent directory. The parent file reference number is 0x1600000001b9c6. The name of the parent directory is "\ProgramData\NVIDIA Corporation\NvTelemetry". The parent index attribute is ":$I30:$INDEX_ALLOCATION". The file reference number of the file that needs to be reconnected is 0xd8000000000487. There may be additional files on the volume that also need to be reconnected to this parent directory.Event[3971]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:38.863 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-94V7TPK Description: A corruption was discovered in the file system structure on volume C:.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1800000000889a. The name of the file is "\Users\wynem\AppData\Local\Google\Chrome\User Data\Default\Secure Preferences".[/quote] Code: Event[1370]: Log Name: System Source: Application Popup Date: 2017-11-03T23:28:56.226 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-94V7TPK Description: Application popup: Windows - Virtual Memory Minimum Too Low : Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help. Event[1371]: Log Name: System Source: Application Popup Date: 2017-11-03T23:29:04.273 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-94V7TPK Description: Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help. Event[1372]: Log Name: System Source: Microsoft-Windows-Resource-Exhaustion-Detector Date: 2017-11-03T23:29:05.237 Event ID: 2004 Task: Resource Exhaustion Diagnosis Events Level: Warning Opcode: Contains the results of the diagnosis. Keyword: Events related to exhaustion of system commit limit (virtual memory). User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TslGame.exe (1156) consumed 5545807872 bytes, MsMpEng.exe (3124) consumed 145788928 bytes, and Battle.ne[/quote] Code: Event[1493]: Log Name: System Source: Service Control Manager Date: 2017-11-03T23:47:35.129 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: The Tile Data model server service failed to start due to the following error: The paging file is too small for this operation to complete.[/quote] Code: Event[1559]: Log Name: System Source: Disk Date: 2017-11-04T00:00:29.855 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1560]: Log Name: System Source: Disk Date: 2017-11-04T00:00:29.855 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1561]: Log Name: System Source: Disk Date: 2017-11-04T00:00:29.855 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1562]: Log Name: System Source: Disk Date: 2017-11-04T00:00:29.855 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1563]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1564]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1565]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1566]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1567]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1568]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1569]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1570]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1571]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1572]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1573]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1574]: Log Name: System Source: Disk Date: 2017-11-04T00:00:30.088 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1575]: Log Name: System Source: Disk Date: 2017-11-04T00:00:37.306 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1576]: Log Name: System Source: Disk Date: 2017-11-04T00:00:37.306 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.Event[1577]: Log Name: System Source: Disk Date: 2017-11-04T00:00:37.306 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.[/quote] Code: Event[2124]: Log Name: System Source: Disk Date: 2017-11-04T20:23:42.021 Event ID: 154 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: The IO operation at logical block address 0x66daa0 for Disk 0 (PDO name: \Device\0000002e) failed due to a hardware error.[/quote] Code: A timeout occurred while waiting for the EHCI host controller Interrupt on Async Advance Doorbell response.[/quote] Code: Event[2333]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-11-06T01:44:50.155 Event ID: 6 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\SystemRoot\System32\Config\SOFTWARE'.[/quote] Code: Event[3945]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:36.162 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: The file system structure on volume C: has now been repaired.Event[3946]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:36.163 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: The file system structure on volume C: has now been repaired.Event[3947]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:36.163 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: The file system structure on volume C: has now been repaired.Event[3948]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:36.164 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: The file system structure on volume C: has now been repaired.Event[3949]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:36.164 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: The file system structure on volume C: has now been repaired.Event[3950]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:36.165 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: The file system structure on volume C: has now been repaired.Event[3951]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:36.165 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: The file system structure on volume C: has now been repaired.Event[3952]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:36.165 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: The file system structure on volume C: has now been repaired.Event[3953]: Log Name: System Source: Ntfs Date: 2017-11-09T10:45:36.165 Event ID: 132 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: Too many repair events have occurred in a short period of time.Temporarily suspending posting of further repair events.[/quote] Code: Event[3983]: Log Name: System Source: Ntfs Date: 2017-11-09T10:47:21.615 Event ID: 133 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: Skipped posting of 60 repair events. Repair event posting will now be resumed. Here are the skipped posting repair events count by repair verbs: BadFRS: 30 OrphanChildFRS: 0 BadClusters: 0 BadFreeClusters: 0 CrossLink: 0 SDEntry: 0 InvalidSecurityId: 0 IndexAttribute: 0 IndexSubtree: 0 IndexOffset: 0 IndexEntry: 30 IndexOrder: 0 Connect: 0 BreakCycle: 0 FRSAllocate: 0 Others: 0[/quote] Code: Event[4003]: Log Name: System Source: Ntfs Date: 2017-11-09T10:56:21.647 Event ID: 133 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-94V7TPK Description: Skipped posting of 23 repair events. Repair event posting will now be resumed. Here are the skipped posting repair events count by repair verbs: BadFRS: 0 OrphanChildFRS: 0 BadClusters: 0 BadFreeClusters: 0 CrossLink: 0 SDEntry: 0 InvalidSecurityId: 0 IndexAttribute: 0 IndexSubtree: 0 IndexOffset: 0 IndexEntry: 18 IndexOrder: 0 Connect: 5 BreakCycle: 0 FRSAllocate: 0 Others: 0[/quote] Code: Event[1521]: Log Name: System Source: volmgr Date: 2017-11-03T23:48:33.717 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: Crash dump initialization failed![/quote] Code: Event[3905]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-11-09T10:43:54.386 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-94V7TPK Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote] Code: 11/3/2017 6:03 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 154 P2: ffffdb085be06000 P3: ffffba86dc5ef6d0 P4: 2 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-5265-01.dmp \\?\C:\WINDOWS\TEMP\WER-16593-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57A5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57C4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57E5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_154_de98dab9450e3bdec9f84885725a5116ae706_00000000_cab_2044588f Analysis symbol: Rechecking for solution: 0 Report Id: 88ac7c9e-dbb0-4da9-a380-28d0e58d9709 Report Status: 2049 Hashed bucket:11/3/2017 6:03 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 154 P2: ffffdb085be06000 P3: ffffba86dc5ef6d0 P4: 2 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-5265-01.dmp \\?\C:\WINDOWS\TEMP\WER-16593-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57A5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57C4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57E5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_154_de98dab9450e3bdec9f84885725a5116ae706_00000000_02fc57f3 Analysis symbol: Rechecking for solution: 0 Report Id: 88ac7c9e-dbb0-4da9-a380-28d0e58d9709 Report Status: 4 Hashed bucket: 11/3/2017 5:01 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 3f P3: 1c88 P4: 1c88 P5: 370d9130 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-4687-01.dmp \\?\C:\WINDOWS\TEMP\WER-20750-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER688D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68AC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68CD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_5086f2569dffbb6ed2c785a835c633f453c198ed_00000000_cab_210469e5 Analysis symbol: Rechecking for solution: 0 Report Id: 4bb5004f-828c-403f-9771-0b123f0f41c9 Report Status: 2049 Hashed bucket: 11/3/2017 5:01 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 3f P3: 1c88 P4: 1c88 P5: 370d9130 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-4687-01.dmp \\?\C:\WINDOWS\TEMP\WER-20750-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER688D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68AC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68CD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_5086f2569dffbb6ed2c785a835c633f453c198ed_00000000_02ec68db Analysis symbol: Rechecking for solution: 0 Report Id: 4bb5004f-828c-403f-9771-0b123f0f41c9 Report Status: 4 Hashed bucket: 11/9/2017 7:43 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 3f P3: 4498 P4: 4498 P5: b062d518 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110917-5187-01.dmp \\?\C:\WINDOWS\TEMP\WER-19406-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61A8.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61C7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61E7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_95adb5d153f88315abb0a4c0da721fbb7110aa95_00000000_cab_25b063da Analysis symbol: Rechecking for solution: 0 Report Id: c1772aa0-9617-4572-a7e7-44aa47669a19 Report Status: 2049 Hashed bucket: 11/9/2017 7:43 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 3f P3: 4498 P4: 4498 P5: b062d518 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110917-5187-01.dmp \\?\C:\WINDOWS\TEMP\WER-19406-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61A8.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61C7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61E7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_95adb5d153f88315abb0a4c0da721fbb7110aa95_00000000_030461e6 Analysis symbol: Rechecking for solution: 0 Report Id: c1772aa0-9617-4572-a7e7-44aa47669a19 Report Status: 4 Hashed bucket: 11/5/2017 9:44 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7a P2: ffff8004b0e94a40 P3: ffffffffc000000e P4: 141a6860 P5: fffff807750206f0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110617-35968-01.dmp \\?\C:\WINDOWS\TEMP\WER-36406-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA1ED.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA20C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA22C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7a_523ef85bb95dfcdd2ebe91222cf859e8332f677b_00000000_cab_1f98a344 Analysis symbol: Rechecking for solution: 0 Report Id: aa55e456-48b0-47fc-b22d-8de41eac2b6d Report Status: 2049 Hashed bucket: 11/5/2017 9:44 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7a P2: ffff8004b0e94a40 P3: ffffffffc000000e P4: 141a6860 P5: fffff807750206f0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110617-35968-01.dmp \\?\C:\WINDOWS\TEMP\WER-36406-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA1ED.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA20C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA22C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7a_523ef85bb95dfcdd2ebe91222cf859e8332f677b_00000000_02f0a23b Analysis symbol: Rechecking for solution: 0 Report Id: aa55e456-48b0-47fc-b22d-8de41eac2b6d Report Status: 4 Hashed bucket: 11/3/2017 5:07 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7a P2: ffffca8fca86b0c0 P3: ffffffffc000000e P4: 4a8ff860 P5: fffff1e020818000 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-4609-01.dmp \\?\C:\WINDOWS\TEMP\WER-13687-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5553.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5582.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55B2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7a_689e15e1232bc3d7deb3e9c7d54aca3daef68d_00000000_cab_23385b2f Analysis symbol: Rechecking for solution: 0 Report Id: 6e8cb191-dd7c-4faf-beb0-4e2cb270cb16 Report Status: 2049 Hashed bucket: 11/3/2017 5:07 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7a P2: ffffca8fca86b0c0 P3: ffffffffc000000e P4: 4a8ff860 P5: fffff1e020818000 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-4609-01.dmp \\?\C:\WINDOWS\TEMP\WER-13687-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5553.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5582.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55B2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7a_689e15e1232bc3d7deb3e9c7d54aca3daef68d_00000000_02f455c1 Analysis symbol: Rechecking for solution: 0 Report Id: 6e8cb191-dd7c-4faf-beb0-4e2cb270cb16 Report Status: 4 Hashed bucket: 11/6/2017 7:40 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7a P2: ffffd88a49b019f0 P3: ffffffffc000000e P4: 1eadc1860 P5: fffff80f01d8efea P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110617-35671-01.dmp \\?\C:\WINDOWS\TEMP\WER-36093-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9DD6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9DF5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E15.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7a_ec397f7b72effca398374606679139e8a5883_00000000_cab_236c9ea1 Analysis symbol: Rechecking for solution: 0 Report Id: 67c9f2f3-3476-4342-9384-5e7a40f49563 Report Status: 2049 Hashed bucket: 11/6/2017 7:40 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7a P2: ffffd88a49b019f0 P3: ffffffffc000000e P4: 1eadc1860 P5: fffff80f01d8efea P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110617-35671-01.dmp \\?\C:\WINDOWS\TEMP\WER-36093-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9DD6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9DF5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E15.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7a_ec397f7b72effca398374606679139e8a5883_00000000_03049e14 Analysis symbol: Rechecking for solution: 0 Report Id: 67c9f2f3-3476-4342-9384-5e7a40f49563 Report Status: 4 Hashed bucket: 11/3/2017 5:43 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff800dac14b94 P4: 0 P5: 774e6350 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-5156-02.dmp \\?\C:\WINDOWS\TEMP\WER-8984-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER343F.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_6d8d1eb4e7b5bd6733b06dac1e1f45def474774_00000000_cab_202adff6 Analysis symbol: Rechecking for solution: 0 Report Id: 8d96907a-afd3-43fc-ba46-a2fa6298347b Report Status: 2049 Hashed bucket: 11/3/2017 5:22 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff800dac14b94 P4: 0 P5: 774e6350 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-5156-02.dmp \\?\C:\WINDOWS\TEMP\WER-8984-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER343F.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_6d8d1eb4e7b5bd6733b06dac1e1f45def474774_00000000_027c344e Analysis symbol: Rechecking for solution: 0 Report Id: 8d96907a-afd3-43fc-ba46-a2fa6298347b Report Status: 4 Hashed bucket: 11/3/2017 5:43 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff80226074b94 P4: 0 P5: 774e6350 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-3156-01.dmp \\?\C:\WINDOWS\TEMP\WER-7796-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3047.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_b8e4ce98968c47f2b97ed85e02b38e6576e4ca_00000000_cab_202adf88 Analysis symbol: Rechecking for solution: 0 Report Id: 4b1c03ec-a80c-4e53-8adc-e9ae5f6b45b7 Report Status: 2049 Hashed bucket: 11/3/2017 5:17 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: c4 P2: 2000 P3: fffff80226074b94 P4: 0 P5: 774e6350 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110317-3156-01.dmp \\?\C:\WINDOWS\TEMP\WER-7796-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3047.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_b8e4ce98968c47f2b97ed85e02b38e6576e4ca_00000000_02783047 Analysis symbol: Rechecking for solution: 0 Report Id: 4b1c03ec-a80c-4e53-8adc-e9ae5f6b45b7 Report Status: 4 Hashed bucket: 11/8/2017 8:14 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffae886e8c3080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110817-43312-01.dmp \\?\C:\WINDOWS\TEMP\WER-44859-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC17B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC19A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC1BA.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_b00207cee729a41f5d1125c5432f8f7f49777_00000000_cab_06c8c275 Analysis symbol: Rechecking for solution: 0 Report Id: fa21fe7d-76d9-4364-8d4b-232450b981db Report Status: 2049 Hashed bucket: 11/8/2017 8:14 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffae886e8c3080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110817-43312-01.dmp \\?\C:\WINDOWS\TEMP\WER-44859-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC17B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC19A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC1BA.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_b00207cee729a41f5d1125c5432f8f7f49777_00000000_030cc1c9 Analysis symbol: Rechecking for solution: 0 Report Id: fa21fe7d-76d9-4364-8d4b-232450b981db Report Status: 4 Hashed bucket: 11/8/2017 10:58 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffb90fd6d71480 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110817-5421-01.dmp \\?\C:\WINDOWS\TEMP\WER-12390-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43EE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43FE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER443D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_e6472f7a53a6b74f842e4e56aa148115488832be_00000000_cab_19ac5256 Analysis symbol: Rechecking for solution: 0 Report Id: ff66a95a-f99e-4d9c-bb60-af9b7d760fae Report Status: 2049 Hashed bucket: 11/8/2017 10:58 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ef P2: ffffb90fd6d71480 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110817-5421-01.dmp \\?\C:\WINDOWS\TEMP\WER-12390-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43EE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43FE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER443D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_e6472f7a53a6b74f842e4e56aa148115488832be_00000000_0304444c Analysis symbol: Rechecking for solution: 0 Report Id: ff66a95a-f99e-4d9c-bb60-af9b7d760fae Report Status: 4 Hashed bucket:[/quote]

 

Hello. Thank you for your detailed guide. I'll gather info for you as much as i can right now












These are the images that you want. I am uploading the memory.dmp right now. Ill post it ass soon as it uploads.I'll do a memtest and update bios later this day.
And finally cmd checks as you want
Microsoft Windows [Version 10.0.16299.19](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism /online /cleanup-image /checkhealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.19No component store corruption detected.The operation completed successfully.C:\WINDOWS\system32>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.19[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.19[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>

 

Please make sure that all partitions/drives are checked with each HD Tune and chkdsk /x /f /r
Model ST3200827AS

For startup and recovery settings uncheck automatic restart so that you have time to view the BSOD windows. Sometimes it may display the misbehaving in the form *.sys in addition to the bugcheck.

Open disk management > widen each column so that all of the contents in each row is in full view > post an image into the thread.

Download and install: Mini Tool partition wizard:
Best Free Partition Manager for Windows | MiniTool Partition Free
Post an image into the thread.

Download and install: cpu-z and make screen shots of each tab:
CPU-Z | Softwares | CPUID
cpu
mainboard
memory
spd*
graphics

spd* shows the details of each RAM module. You can show details by choosing different slots in the left upper corner.
Please make screenshots of each module.


Please open the MSI website for the computers drivers and post the URL into the thread.

 

Hello again. I dont think other hdd has a problem because i put that back to my pc just today. I wasnt using it like 1 year.
As you told i changed automatic restart and gathered images that you asked.
Support For 990FXA-GD65 | MSI Global --> driver and bios page.

I did upload the memory dump --> Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Finally the images that you asked.














By the way i really appreciate and thankful to you helping me out this situation. Im almost at limit of kicking my case and throwing out of the window

 

Hi again. I did chkdsk as you asked. Here is the report
Checking file system on C:The type of the file system is NTFS.A disk check has been scheduled.Windows will now check the disk. Stage 1: Examining basic file system structure ... 443392 file records processed. File verification completed. 28919 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 10431 reparse records processed. 515278 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 10431 reparse records processed. Stage 3: Examining security descriptors ...Cleaning up 44 unused index entries from index $SII of file 0x9.Cleaning up 44 unused index entries from index $SDH of file 0x9.Cleaning up 44 unused security descriptors.Security descriptor verification completed. 35944 data files processed. CHKDSK is verifying Usn Journal... 35276976 USN bytes processed. Usn Journal verification completed.Stage 4: Looking for bad clusters in user file data ... 443376 files processed. File data verification completed.Stage 5: Looking for bad, free clusters ... 13703051 free clusters processed. Free space verification is complete.Windows has scanned the file system and found no problems.No further action is required. 124213247 KB total disk space. 68744264 KB in 133136 files. 89680 KB in 35945 indexes. 0 KB in bad sectors. 567099 KB in use by the system. 65536 KB occupied by the log file. 54812204 KB available on disk. 4096 bytes in each allocation unit. 31053311 total allocation units on disk. 13703051 allocation units available on disk.Internal Info:00 c4 06 00 84 94 02 00 ec 6d 04 00 00 00 00 00 .........m......95 00 00 00 2a 28 00 00 00 00 00 00 00 00 00 00 ....*(..........Windows has finished checking your disk.Please wait while your computer restarts.

 

For CPUZ please post images of all tabs.
Please run chkdsk /x /f /r on all partitions/drives.
Please run HD Tune on all drives and post images into the thread.
Model ST3200827AS
For each of the steps in post #2 please indicate the status with numbers and progress/results.
What is the history of Windows installation/upgrades on each drive C: and D:?

 

Hey. Sorry for late reply.
I'm going to add images of cpuz images that i didn't put before.
I did removed secondary hdd yesterday but still getting bsod while playing and browsing.
For the steps you did write in second post,
I didn't do any backup but i did crate a restore point.Checked health with hd tune and posted pics.
I did clear cmos before all so there were no overclock. I couldn't update bios and do memtest coz my flash drive is with my gf and she forgot at work *Sad .
For the memory.dmp i uploaded and posted it at my last post.
I almost did every step beside creating backup and flash drive needed sections.
By the way i did try each ram in each slots. Single and dual.That really didn't change anything.
Finally i was using windows 8.1 and then upgraded to win 10. Automatic update was always on. Never did format or anything else till i update last big update. After update it started bsod. After few bsod my windows beginning to corrupt and couldn't even use start or settings. Then i decided to reset windows with clean install (not saving files.)
Here are the images of the cpu-z

 

The event log displayed significant problems with a drive.
Please test all drives with chkdsk /x /f /r and post results into the thread.
Please make sure that all drives have > 25 GB free space.
When available please post images of the Memtest86+ version 5.01 testing with 8 or more passes.
Backing up the files and making a backup image should be performed so that you have a margin of safety if you use Windows driver verifier.

 

Just in case it's overlooked you're seem to be running 2 different in both capacity and make RAM modules which can lead to all sorts of unexpected results. Have you tried to run the PC on just one of them to isolate the possibility it's the cause or at least a contributor to the problem

 

How long had you been using the mismatched RAM without problems?

 

Hello there shimshom. Thanks for the advice. Yes i did. I did try each ram in every single slot. Ive been using these together like 2 years without problem.
And here is the latest report of chkdsk. Btw i have 29gb of free space in my ssd right now.
About the backing up files. I dont need to save any file right now. I only have some games that i can download in an hour and some programs to figure out what my problem is. So if its not a must i dont want to backup files.
Final question, is there any better way to copy paste this chkdsk thing so its not look like mess of letters?

Checking file system on C:The type of the file system is NTFS.A disk check has been scheduled.Windows will now check the disk. Stage 1: Examining basic file system structure ...Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x1c8a for possibly 0x12 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x51e8 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x51E8.Attribute record of type 0x80 and instance tag 0x3 is cross linkedstarting at 0x190a17 for possibly 0x17 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x3in file 0xaf6c is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xAF6C.Attribute record of type 0x80 and instance tag 0x3 is cross linkedstarting at 0x3d68 for possibly 0x7 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x3in file 0xaf8d is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xAF8D.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x190a2e for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0xafa0 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xAFA0.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x91698a for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0xafa5 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xAFA5.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x4a2d1c for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0xafbe is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xAFBE.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x4a2d1d for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0xafbf is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xAFBF.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x4a2d1e for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0xafc1 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0xAFC1. 443392 file records processed. File verification completed. 28684 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 9616 reparse records processed. The file reference 0x360000000051e8 of index entry f_000dd3 of index $I30with parent 0x17c is not the same as 0x350000000051e8.Deleting index entry f_000dd3 in index $I30 of file 17C.The file reference 0xb00000000757a of index entry 896e916630b317aad0e45e3dea0cf759eb51f207.cachedmsg of index $I30with parent 0x1536 is not the same as 0xa00000000757a.Deleting index entry 896e916630b317aad0e45e3dea0cf759eb51f207.cachedmsg in index $I30 of file 1536.The file reference 0xb00000000757a of index entry 896E91~1.CAC of index $I30with parent 0x1536 is not the same as 0xa00000000757a.Deleting index entry 896E91~1.CAC in index $I30 of file 1536.The file reference 0x980000000051e3 of index entry c71d8cc0b07c93917da9bfe582448fd10641af7d_fdfc8085fbfd497008c2a846c73f456128ba1e04 of index $I30with parent 0x1c905 is not the same as 0x970000000051e3.Deleting index entry c71d8cc0b07c93917da9bfe582448fd10641af7d_fdfc8085fbfd497008c2a846c73f456128ba1e04 in index $I30 of file 1C905.The file reference 0x980000000051e3 of index entry C71D8C~3 of index $I30with parent 0x1c905 is not the same as 0x970000000051e3.Deleting index entry C71D8C~3 in index $I30 of file 1C905. 517108 index entries processed. Index verification completed.CHKDSK is scanning unindexed files for reconnect to their original directory. 4 unindexed files scanned. Recovering orphaned file 1CC97B~1 (AFD0) into directory file 1C859.Recovering orphaned file 1cc97bf320bfa6d0dc79f392f54a137a57e36f3e_da39a3ee5e6b4b0d3255bfef95601890afd80709 (AFD0) into directory file 1C859. 1 unindexed files recovered to original directory.CHKDSK is recovering remaining unindexed files. 3 unindexed files recovered to lost and found. Lost and found is located at \found.004 9616 reparse records processed. Stage 3: Examining security descriptors ...Cleaning up 31 unused index entries from index $SII of file 0x9.Cleaning up 31 unused index entries from index $SDH of file 0x9.Cleaning up 31 unused security descriptors.Security descriptor verification completed.Inserting data attribute into file 51E8.Inserting data attribute into file AF6C.Inserting data attribute into file AF8D.Inserting data attribute into file AFA0.Inserting data attribute into file AFA5.Inserting data attribute into file AFBE.Inserting data attribute into file AFBF.Inserting data attribute into file AFC1. 36867 data files processed. CHKDSK is verifying Usn Journal...Usn Journal verification completed.Stage 4: Looking for bad clusters in user file data ... 443376 files processed. File data verification completed.Stage 5: Looking for bad, free clusters ... 7690645 free clusters processed. Free space verification is complete.Correcting errors in the master file table's (MFT) BITMAP attribute.CHKDSK discovered free space marked as allocated in the volume bitmap.Windows has made corrections to the file system.No further action is required. 124213247 KB total disk space. 92824936 KB in 141522 files. 93524 KB in 36862 indexes. 0 KB in bad sectors. 532207 KB in use by the system. 65536 KB occupied by the log file. 30762580 KB available on disk. 4096 bytes in each allocation unit. 31053311 total allocation units on disk. 7690645 allocation units available on disk.Internal Info:00 c4 06 00 e1 b8 02 00 95 af 04 00 00 00 00 00 ................99 00 00 00 f7 24 00 00 00 00 00 00 00 00 00 00 .....$..........Windows has finished checking your disk.Please wait while your computer restarts.

 

Drive C: had lots of problems reported in the chkdsk results.
Please open administrative command prompt and run again chkdsk /x /f /r and post results into the thread.