Windows 10: Numerous BSODs Since Before/After Upgrading To Win10

I realise the title isn't greatly descriptive but that's because nearly every BSOD I get is a new one so trying to pinpoint a particular bugcheck seems like a wasted effort. For clarity, my specs are as follows:

OS: Windows 10 Home 64 Bit
CPU: AMD FX-8120
RAM: 16GB Dual Channel DDR3 671MHz (Team Group Inc)
MoBo: Gigabyte GA-970A-D3 Rev 1.0 (latest beta BIOS)(BSODs happened with the same frequency on the previous F12 BIOS too)
GPU: 4GB Zotac GeForce GTX 1050Ti
HDD: Seagate ST2000DM001-1CH164 (2TB)

It's difficult to say when these BSODs usually occur, most of the time it's while I'm playing something but that's predominantly what I do on this PC regardless. They have happened numerous times while watching videos or quite literally doing nothing though.

I'd honestly appreciate any help as this is an issue I've been wrestling with for years. I upgraded from Windows 7 in 2015 and I was getting these even before that.

:)

 

Numerous BSODs after upgrading the CPU

807`b3aae000 cdrom cdrom.sys Thu Jul 20 18:39:41 1972 (04CCA32D)

fffff807`b1850000 fffff807`b1868000 CEA CEA.sys Wed Dec 16 23:50:10 1970
(01CDB102)

fffff807`b1240000 fffff807`b12e8000 CI CI.dll Sat Aug 27 15:22:09 2016 (57C1E861)

fffff807`b2730000 fffff807`b2795000 CLASSPNP CLASSPNP.SYS Mon May 4 12:41:45 1992 (2A056949)

fffff807`b1000000 fffff807`b1065000 CLFS CLFS.SYS ***** Invalid (A746E82D)

fffff807`b1140000 fffff807`b1220000 clipsp clipsp.sys Sat Mar 18 00:54:13 2017 (58CCBD75)

fffff807`b81e0000 fffff807`b81f6000 CMHDAudioV64 CMHDAudioV64.sys Tue Oct 27 22:32:55 2015 (563033D7)

fffff807`b1220000 fffff807`b122e000 cmimcext cmimcext.sys ***** Invalid (FF4D5961)

fffff807`b12f0000 fffff807`b1392000 cng cng.sys ***** Invalid
(F2E91F26)

fffff807`b4d90000 fffff807`b4da1000 CompositeBus CompositeBus.sys *****
Invalid (A29FEBD9)

fffff807`b3ab0000 fffff807`b3ac2000 condrv condrv.sys Wed Jun 25 21:27:43 2031
(73A5288F)

fffff807`b27c0000 fffff807`b27db000 crashdmp crashdmp.sys Mon Jun 7 22:16:33 1993 (2C13F681)

fffff807`b4c00000 fffff807`b4c8f000 csc csc.sys Sat Jul 4 16:47:41 2037 (7EFA9C6D)

fffff807`b4cf0000 fffff807`b4d1b000 dfsc dfsc.sys Sat Mar 4 05:04:07 2023 (64031797)

fffff807`b2710000 fffff807`b272e000 disk disk.sys Sat Mar 28 14:37:28 2009 (49CE6E68)

fffff807`b6e70000 fffff807`b6e91000 drmk drmk.sys ***** Invalid (A01C1986)

As you can see above, there is an issue of file corruption. The dates on your system files are wrong or invalid. Cause? Don't know.

You can try running the she system file checker tool {SFC} and DISM, to see if they can be corrected.

Fix Windows Update errors by using the DISM or System Update Readiness tool.

https://support.microsoft.com/en-us...-by-using-the-dism-or-system-update-readiness

Using System File Checker in Windows 10.

https://support.microsoft.com/en-us...a40be/using-system-file-checker-in-windows-10

If no joy, a reset is your next best option.

Recovery options in Windows 10.

Mini dump and random crash help please

 

Numerous BSODs after upgrading the CPU

Oh well, no corruption found. I guess it's time to try the reset.

 

Hi there,

I can see a lot of problems your system has. First of all we should start with the analysis results of the BSOD dumps.

memory_corruption and network driver are shown on those dumps:

Code: 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED (14.08.2017 22:20:15) [Windows 10] CAUSED BY: memory_corruption rt640x64.sys [23.03.2017] * Realtek NICDRV 8169 PCIe GBE Family Controller driver * => Realtek ndis.sys [12.07.2017] * NDIS 6.20 Wrapper Driver (Windows System File) PROCESS: iw3mp.exe[/quote] Code: 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED (8.08.2017 21:15:05) [Windows 10] CAUSED BY: memory_corruption PROCESS: System[/quote] Code: 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA (20.07.2017 04:27:49) [Windows 10] CAUSED BY: memory_corruption PROCESS: chrome.exe Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS[/quote]
1) So, at first step u should start with testing the memory:





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums







Note MemTest86+ V5.01 needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

More Info here: Microsoft Community


Make a photo of the result and post it.

 

2) When memory testing is done you should update or roll back the realtek network driver:
rt640x64.sys [23.03.2017] * Realtek NICDRV 8169 PCIe GBE Family Controller driver * => Realtek

There are a lot of errors in the windows eventlog which indicate a problem with the network device or network driver:
Code: 2017-07-01 14:24:25 Warning: WLAN Extensibility Module has stopped. Module Path: C:\WINDOWS\System32\bcmihvsrv64.dll 2017-07-01 14:25:57 Warning: WLAN Extensibility Module has stopped. Module Path: C:\WINDOWS\System32\bcmihvsrv64.dll 2017-07-01 14:36:01 Warning: The network interface "NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver detected that its hardware has stopped responding to commands. 2017-07-01 14:36:03 Warning: The network interface "NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver detected that its hardware has stopped responding to commands. 2017-07-01 14:43:05 Error: Miniport PdaNet Broadband Adapter, {E13B511F-8C4F-48FA-8F5B-B4B3DAE787A7}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)[/quote]
3) U should also reinstall the newest NVIDIA GPU driver because there was an error message too:
Code: 2017-08-02 13:36:33 Warning: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Please use DDU for reinstalling the GPU driver:


Display Driver Uninstaller: How to use
Display Driver Uninstaller (DDU) is a small software that can help the user to uninstall the display driver from the users PC. It can uninstall the driver for all the lead display chip developers, viz. Nvidia, AMD and Intel.
4) Please uninstall EVGA Software, because its known for causing bluescreens:
- EVGA PrecisionX 16


​

 

5) Since are a few filesystem errors too u should also do an filesystem repair and HDD testing.

Code: 2017-05-08 15:53:59 Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. 2017-05-27 16:18:54 Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. 2017-06-04 23:08:53 Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. 2017-06-07 14:09:26 Error: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\config\DRIVERS' was corrupted and it has been recovered. Some data might have been lost. 2017-06-07 14:11:57 Error: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\config\DRIVERS' was corrupted and it has been recovered. Some data might have been lost. 2017-07-03 19:37:19 Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. 2017-07-16 18:07:05 Error: The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied. 2017-07-20 15:30:55 Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. 2017-07-26 23:02:42 Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. 2017-07-27 14:15:37 Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. 2017-08-06 14:15:50 Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. 2017-08-15 13:28:29 Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit.[/quote] Start with checking your Seagate harddisk:





Diagnostic Test

HDD TESTS


Run HDTune to check health and scan for errors.







Note It may take some time, but look for signs of any errors or failure.

You can also run a disk or health check using chkdsk. Refer to the tutorial for details of how to do this.

Take Screenshots of it and post it here.

 

6) Its very important to have an clean file system. So do steps below:

Repair Windows Filesystem:

1. Open an elevated command prompt.
2. In the elevated command prompt, type these five commands below, and press Enter:

dism /Online /NoRestart /Cleanup-Image /RestoreHealth
dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
sfc /scannow
chkdsk C: /F /R /X
fsutil dirty set C:

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...

 

That's a lotta steps, but I will try to start with that MemTest tonight, though from memory I did try to do that once before and apparently my PC actively refuses to boot from USB.

 

Boot from USB Drive on Windows 10 PC Windows 10 Installation Upgrade Tutorials



Note
If you have fast boot or ultra fast boot enabled in your UEFI firmware settings, then you will need to temporarily disable fast boot or ultra fast boot to be able to boot from a USB.



How to Enable Fast Boot or Ultra Fast Boot in UEFI Firmware Settings for Windows

1. Try another USB stick
2. Try all USB ports (2.0 and 3.0)
3. Maybe when using UEFI Bios u have temporarly switch to Legacy in BIOS settings
4. Turn off temporarily fast boot, secure boot, CSM if enabled

 

Alrighty. So I ran MemTest for 3 passes and it came up with no errors. I do realise you said 8 and that 3 passes are relatively inconclusive but it did those 3 passes in about 10 hours overnight and I need access to my PC so I can't really let it do nothing for 24 hours+ right now.

I also got rid of PrecisionX and did a clean install of the Nvidia drivers, as well as installing a newer version of the Realtek driver though I'm not truly sure if it was the right now (nothing seems broken so I assume it was).

I'll use HDTune next and run those file system commands next, however last night before I ran the MemTest I had another BSOD. I'll attach the minidump for it here if that's alright, unless you need me to run the tool again and upload that instead.

 

Attachment 149160Attachment 149161Attachment 149162Attachment 149163

 

Please post the results of the chkdsk /x /f /r test:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

When you have completed the above tests please run Sea tools for windows on your drive using SMART, short and long generic tests. When the studies have completed please post images into the thread.

How to use SeaTools for Windows
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows
http://www.seagate.com/support/downloads/seatools/

 

Before I get to chkdsk I wanted to get through BSODHunter's list of commands, the first one:

dism /Online /NoRestart /Cleanup-Image /RestoreHealth

Came up with nothing.

The second one however:

dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup

Gave me this:

Error 2 - The System cannot find the file specified

The DISM log file can be found at C:\WINDOWS\logs\DISM\dism.log

I'm attaching the log here.

Edit: I should also probably add that just now my computer froze without a BSOD. It just made the characteristic audio stuttering sound and locked up. The image stayed as it was and I had to strangle it unconscious to shut it down.

 

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /checkhealth
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) chkdsk /scan
6)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

 

I am so sorry for the awful formatting, copying and pasting from the command prompt into here disregards all formatting so I had to fix this myself as best as I could.
Microsoft Windows [Version 10.0.14393](c) 2016 Microsoft Corporation. All rights reserved.

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.
C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth
Deployment Image Servicing and Management toolVersion: 10.0.14393.0
Image Version: 10.0.14393.0
No component store corruption detected.The operation completed successfully.
C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth
Deployment Image Servicing and Management toolVersion: 10.0.14393.0
Image Version: 10.0.14393.0
[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management toolVersion: 10.0.14393.0
Image Version: 10.0.14393.0
[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.
C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Stage 1: Examining basic file system structure ... 1203200 file records processed.
File verification completed.
31282 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
1494336 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Security descriptor verification completed. 145569 data files processed.
CHKDSK is verifying Usn Journal...
36319376 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
1952949247 KB total disk space.
1735430584 KB in 936318 files.
496320 KB in 145570 indexes.
0 KB in bad sectors.
1373687 KB in use by the system.
65536 KB occupied by the log file.
215648656 KB available on disk.
4096 bytes in each allocation unit.
488237311 total allocation units on disk.
53912164 allocation units available on disk.