BSOD after Win10 fall update.While browsing and Gaming.

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

shimshom said:

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

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.

Nice progress with the testing.
Which test are you planning next the memtest86+ version 5.01 or the repeat chkdsk /x /f /r or HD Tune on the C: drive?

Hello zbook. I did run another chkdsk ,report below. Before that i wanted to try playing dota2. It did run smooth and no freezing. But thats only one game and its like 25min tops. I want to do memtest but still dont have any flashdrive right now. Maybe later today or before bed.I'll keep doing what you told me and fingers crossed :) . I'll play few more games pubg and dota2. Will see if i get bsod again.
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. 28680 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 9616 reparse records processed. 517114 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 9616 reparse records processed. Stage 3: Examining security descriptors ...Cleaning up 7 unused index entries from index $SII of file 0x9.Cleaning up 7 unused index entries from index $SDH of file 0x9.Cleaning up 7 unused security descriptors.Security descriptor verification completed. 36862 data files processed. CHKDSK is verifying Usn Journal... 1675840 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 ... 7689728 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. 92826556 KB in 141580 files. 93524 KB in 36863 indexes. 0 KB in bad sectors. 534255 KB in use by the system. 65536 KB occupied by the log file. 30758912 KB available on disk. 4096 bytes in each allocation unit. 31053311 total allocation units on disk. 7689728 allocation units available on disk.Internal Info:00 c4 06 00 16 b9 02 00 dd 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.

Much better chkdsk scan results.
That was a very very fast scan.
Were you able to run HD Tune on the C: drive?
Health, benchmark, and full error scan

The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.
The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.
If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
Official Display Driver Uninstaller DDU Download
Display Driver Uninstaller Download version 17.0.7.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA

So i did another run of HD Tune. Images are down below.
I did upgrade my gpu from r7 370 to 1060 last month.Used amd cleanup tool and installed chipset drivers and amd overdrive back with nvidia drivers.I was using latest drivers but last one had a problem with Pubg (cannot use fullscreen) and i had to roll it back (i was getting blue screen with latest one too.).Now im using driver version 388.00.If you want me to try again latest one i can do that.
Here are the images of HD tune.
Attachment 163107Attachment 163108Attachment 163109Attachment 163110Attachment 163111

The above HD Tune display the Cosair drive.
Please post the HD results for ST3200827AS


The Nvidia graphics driver was the misbehaving driver debugged from the memory dump file.
Please replace this driver using the information in the prior post.

Code:

Name    NVIDIA GeForce GTX 1060 6GBPNP Device ID    PCI\VEN_10DE&DEV_1C03&SUBSYS_00000000&REV_A1\4&1327A1D7&0&0010Adapter Type    GeForce GTX 1060 6GB, NVIDIA compatibleAdapter Description    NVIDIA GeForce GTX 1060 6GBAdapter RAM    (1,048,576) bytesInstalled Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvldumdx.dllDriver Version    23.21.13.8800INF File    oem88.inf (Section136 section)Color Planes    Not AvailableColor Table Entries    4294967296Resolution    1920 x 1080 x 60 hertzBits/Pixel    32Memory Address    0xFD000000-0xFE0FFFFFMemory Address    0xC0000000-0xD1FFFFFFMemory Address    0xD0000000-0xD1FFFFFFI/O Port    0x0000E000-0x0000EFFFIRQ Channel    IRQ 24I/O Port    0x000003B0-0x000003BBI/O Port    0x000003C0-0x000003DFMemory Address    0xA0000-0xBFFFFDriver    c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvlddmkm.sys (23.21.13.8800, 16.14 MB (16,924,088 bytes), 11/2/2017 4:32 PM)

Other drive is not even connected right now.Unplugged it yesterday to try it out without it. I wasn't using it till 2 days ago. It was the drive of the my older computer. I download latest nvidia driver right now and do clean setup with only physx and graphics driver.

I did install the latest driver of nvidia (388.13). But Pubg problem still continues as you can see picture below. Nothing wrong with borderless window but fullscreen is messed up.There are post about this in nvidia forums people getting same buggy thing. There is no cursor and green thing waving around. I'll keep this driver to try it out with dota2 and so.I'll post again if i get another bsod.Attachment 163116