Windows 10: BSOD after windows upgrade and hw changes

Hello for about 5 days I'm experiencing very weird computer actions.
Everything started while testing cap of maximum OC for i5-4670k pc didn't boot up and BIOS corrupt message appeared but fixed itself and when random BSOD crashes started including kb drivers crashing on me etc... Restoring BIOS to default seems temporary fixed that problem.
For now I upgraded my old windows 7 to windows 10 and installed new GPU(gtx 1080) to my computer but new errors keeps attacking already got 5 in about 1day also did RAMS test using mem86 and prime95 about 2h run for cpu everything worked well with tests...

:)

 

activation after change hw.

A motherboard change alone is usually enough.

 

activation after change hw.

Hi, I had a Windows 7 1-2 years ago. I updated to Windows 10 and the activation was OK. Now, I had to change my mainboard. Because of new type, I had to change CPU and RAM also.

I started my windows 10, and activation is out. I tried to use generated key, but nothing. I tried to TROUBLESHOTTING and pressed "change hardware" But still nothing.

I still have error 0x803f7001.

 

The BSOD mini dumps were debugged.
There was 1 misbehaving hardware driver.

1) open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
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) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the Nvidia website.
When using the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
https://www.wagnardsoft.com/
Display Driver Uninstaller Download version 17.0.7.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA


Code: Event[521]: Log Name: System Source: Display Date: 2017-11-25T02:34:51.602 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-D45125K Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: 11/25/2017 2:22 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 0 P3: 501 P4: 500 P5: fffff8023f285370 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4703-01.dmp \\?\C:\WINDOWS\TEMP\WER-6687-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28F4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2905.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_449fd950e61ae51d4b2ecdad1c15fc8ce3bc2c74_00000000_cab_1b1c2a3c Analysis symbol: Rechecking for solution: 0 Report Id: 83f2fd9e-7df3-4830-b740-9224de26304f Report Status: 2049 Hashed bucket:11/25/2017 2:22 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 0 P3: 501 P4: 500 P5: fffff8023f285370 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4703-01.dmp \\?\C:\WINDOWS\TEMP\WER-6687-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28F4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2905.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_449fd950e61ae51d4b2ecdad1c15fc8ce3bc2c74_00000000_02bc2904 Analysis symbol: Rechecking for solution: 0 Report Id: 83f2fd9e-7df3-4830-b740-9224de26304f Report Status: 4 Hashed bucket:11/25/2017 2:04 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 0 P3: 0 P4: 0 P5: ffffab832e5efdc0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4656-01.dmp \\?\C:\WINDOWS\TEMP\WER-8937-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D2A.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D3A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D3B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_35e9be2ca0382b1cedb3510d2aeee57e02ef9df_00000000_cab_1c942da7 Analysis symbol: Rechecking for solution: 0 Report Id: 1d7002b8-4a22-4448-bd6a-a0dd8b8698be Report Status: 2049 Hashed bucket:11/25/2017 2:04 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 0 P3: 0 P4: 0 P5: ffffab832e5efdc0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4656-01.dmp \\?\C:\WINDOWS\TEMP\WER-8937-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D2A.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D3A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D3B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_35e9be2ca0382b1cedb3510d2aeee57e02ef9df_00000000_02b82d49 Analysis symbol: Rechecking for solution: 0 Report Id: 1d7002b8-4a22-4448-bd6a-a0dd8b8698be Report Status: 4 Hashed bucket:11/25/2017 5:07 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffffdc02d4fbf6c0 P4: ffffdc02d4fbf618 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4750-01.dmp \\?\C:\WINDOWS\TEMP\WER-6890-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E63.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E72.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E92.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_6695a349bb768b239b23e1a6446c205d5430e0_00000000_cab_0e243095 Analysis symbol: Rechecking for solution: 0 Report Id: faf2996d-1920-4728-897e-2d5c5d34aa3c Report Status: 2049 Hashed bucket:11/25/2017 5:07 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffffdc02d4fbf6c0 P4: ffffdc02d4fbf618 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4750-01.dmp \\?\C:\WINDOWS\TEMP\WER-6890-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E63.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E72.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E92.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_6695a349bb768b239b23e1a6446c205d5430e0_00000000_02ac2e91 Analysis symbol: Rechecking for solution: 0 Report Id: faf2996d-1920-4728-897e-2d5c5d34aa3c Report Status: 4 Hashed bucket:11/25/2017 5:14 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: fffff30356163f30 P4: fffff30356163e88 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4609-01.dmp \\?\C:\WINDOWS\TEMP\WER-10171-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32C8.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32D7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32D8.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_5c3d4f917f1056b99482dbb0e49675a791dd5b51_00000000_cab_1adc3335 Analysis symbol: Rechecking for solution: 0 Report Id: 8d830c2b-ac9f-47da-9b42-bf457582e746 Report Status: 2049 Hashed bucket:11/25/2017 5:14 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: fffff30356163f30 P4: fffff30356163e88 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4609-01.dmp \\?\C:\WINDOWS\TEMP\WER-10171-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32C8.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32D7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32D8.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_5c3d4f917f1056b99482dbb0e49675a791dd5b51_00000000_02b432e7 Analysis symbol: Rechecking for solution: 0 Report Id: 8d830c2b-ac9f-47da-9b42-bf457582e746 Report Status: 4 Hashed bucket:11/25/2017 1:04 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: ffffe98ea727dc40 P3: 0 P4: fffff802797f655b P5: 2 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4671-02.dmp \\?\C:\WINDOWS\TEMP\WER-6640-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2819.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2829.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2839.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_3fa444d085aeb2476f8e8326fd5359280010ce_00000000_cab_1a7c2952 Analysis symbol: Rechecking for solution: 0 Report Id: a8af29f2-6df7-4497-a641-33d97e8c7d82 Report Status: 2049 Hashed bucket:11/25/2017 1:04 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: ffffe98ea727dc40 P3: 0 P4: fffff802797f655b P5: 2 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4671-02.dmp \\?\C:\WINDOWS\TEMP\WER-6640-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2819.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2829.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2839.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_3fa444d085aeb2476f8e8326fd5359280010ce_00000000_02b02838 Analysis symbol: Rechecking for solution: 0 Report Id: a8af29f2-6df7-4497-a641-33d97e8c7d82 Report Status: 4 Hashed bucket:11/25/2017 11:07 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: be P2: fffff6fffff9ffe8 P3: 8a00000003b00121 P4: ffffdd0c6c2a5910 P5: a P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4671-01.dmp \\?\C:\WINDOWS\TEMP\WER-6750-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A2C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A3C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A3D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_be_95f4ca307499ba775a114d6a34e5a3bfcbbe6a45_00000000_cab_09c42cdc Analysis symbol: Rechecking for solution: 0 Report Id: 80c710a7-9125-4a54-9330-2966d3a27788 Report Status: 2049 Hashed bucket:11/25/2017 11:07 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: be P2: fffff6fffff9ffe8 P3: 8a00000003b00121 P4: ffffdd0c6c2a5910 P5: a P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\112517-4671-01.dmp \\?\C:\WINDOWS\TEMP\WER-6750-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A2C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A3C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A3D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_be_95f4ca307499ba775a114d6a34e5a3bfcbbe6a45_00000000_02b42a3c Analysis symbol: Rechecking for solution: 0 Report Id: 80c710a7-9125-4a54-9330-2966d3a27788 Report Status: 4 Hashed bucket:[/quote] Code: Name NVIDIA GeForce GTX 1080PNP Device ID PCI\VEN_10DE&DEV_1B80&SUBSYS_33621462&REV_A1\4&1286464&0&0008 Adapter Type GeForce GTX 1080, NVIDIA compatible Adapter Description NVIDIA GeForce GTX 1080 Adapter RAM (1,048,576) bytes Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll Driver Version 23.21.13.8813 INF File oem7.inf (Section136 section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1080 x 143 hertz Bits/Pixel 32 Memory Address 0xF2000000-0xF2FFFFFF Memory Address 0xE0000000-0xFEAFFFFF Memory Address 0xF0000000-0xF1FFFFFF I/O Port 0x0000E000-0x0000EFFF IRQ Channel IRQ 16 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\driverstore\filerepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvlddmkm.sys (23.21.13.8813, 16.15 MB (16,936,048 bytes), 11/24/2017 8:26 PM)[/quote]

 

So I did things in your guide and attaching another dump files because got some more of BSODs... But after drivers re-install computer was stable in heavy gaming session for about 6 hours w/o any issues and after that not sure if it was game related issue but game freeze(not responding) and crashed giving me some re-connection issues followed by BSOD in few minutes...
Code: Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:\WINDOWS\system32> sfc /scannow Beginning 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. PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.64 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. PS C:\WINDOWS\system32> chkdsk /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 287744 file records processed. File verification completed. 6557 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 292 reparse records processed. 392564 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 292 reparse records processed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 52411 data files processed. CHKDSK is verifying Usn Journal... 36049056 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 487813211 KB total disk space. 107672580 KB in 228462 files. 178520 KB in 52412 indexes. 0 KB in bad sectors. 407247 KB in use by the system. 65536 KB occupied by the log file. 379554864 KB available on disk. 4096 bytes in each allocation unit. 121953302 total allocation units on disk. 94888716 allocation units available on disk. PS C:\WINDOWS\system32>[/quote]

 

1) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
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 16 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.


2) 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


3) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials

 

So I disabled fast boot and did 8 passes with all 16gb memory took me 16h...(hopefully I understand your guide right and only need to do each ram slot testing if I get any error) few more BSOD appeared before that testing one was about realtek so I tried update LAN drivers to newest version but seems problems still persist...

 

That were 8 passes 0 errors with 16 GB RAM using Memtest 86+ version 5.01 = PASS

The 2 BSOD mini dump files today were debugged and displayed 1 misbehaving hardware driver.
rt640x64 Realtek PCIe GBE Family Controller driver
Using device manager update rt640x64.sys:
Updating a driver. - Microsoft Community



Code: rt640x64 Realtek RT640 NT Drive Realtek RT640 NT Drive Kernel Manual Running OK TRUE FALSE 4,096 933,888 0 6/27/2017 11:42:46 AM C:\WINDOWS\system32\drivers\rt640x64.sys 8,192[/quote] rt640x64.sys
Realtek NICDRV 8169 PCIe GBE Family Controller driver
Realtek

 

Genuine Windows and/or Office?

 

Open administrative command prompt and type or copy and paste:
1) slmgr /dlv

Post an image or share link for the results (one drive or drop box) into the thread.