Random BSODs (WIN10)

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Status
Not open for further replies.
G

Geke

PCHF Member
Jul 31, 2020
51
0
25
Hello everyone!
I've been having a lot of issues with BSODs. It started when i tried to install WIN10 and the pc would just turn off or give a BSOD while running the installation. I could finish the installation by using an old usb stick that had a previous version of WIN10 that somehow worked.
From there i would get all kinds of BSODs 40 seconds or so after turning the pc on. Managed to kind of fix this by updating the BIOS and installing the gpu drivers while on safe mode and now the BSODs are random, could be 5 in a day or none.

(But as it gave BSODs earlier when windows was trying to update its drivers now Windows Update can't install the (KB4565483) actualization and gives Error 0x80070002, of course i tried fixing this with the ISO method and DISM commands but couldn't fix it. When i try DISM /Online /Cleanup-Image /RestoreHealth it freezes at 90.9% and gives this: Error: 0x800f081f).

I tried all this but didn't fix it:

Sfc /scannow and chkdsk give no errors.
Ran memtest once and gave no errors.
Tried reinstalling windows and it's the same all over again, maybe could avoid the Windows Update error but i don't really think that is the problem.
Updated all my drivers and removed the hidden ones in device manager.
Removed all USB devices.

If anyone can help me i would be really grateful. Thanks a lot and sorry for my english it's not my first language.

Maybe one or two of the dumpfiles are incomplete but for sure 2 are good.

1596230204650.png
 

Attachments

Your two latest crash dmps suggest that there is a security issue, this could be related to your AV and/or your internet connection.

Can we have the actual Speccy url.
 
The cause of the latest crash was indeed a security issue and namely Memory_Corruption Large, what this is, why it is dangerous and how to resolve the issue is explained here, this for information purposes only and not suggesting that you download anything from the link.

The suggested fix is to update update Windows but you seem unable to install updates for some reason, Windows was installed on 28/6/2020 but only the one Windows update has been successfully installed.

What type of Windows media was used for the install, Windows DVD or a downloaded ISO etc and from where was the media obtained.

Download MiniToolBox and save the file to the Desktop.

Close the browser and run the tool, check the following options;

List last 10 Event Viewer Errors
List Installed Programs
List Devices (Only Problems)
List Users, Partitions and Memory size

Click on Go.

Post the resulting log in your next reply for us if you will.

You are welcome btw :)
 
Ok, i see. The media used for the windows install was an old downloaded ISO that was in a pendrive that i had because the pc would shut down while installing windows with another ISO that i had downloaded that day, so i don't know where that old ISO was obtained from but im quite sure it was from microsoft.

Maybe i could try reinstalling windows 10 but before making the 28/6/2020 installation i had the same BSODs and the Windows Update issue wasn't there so i don't know if this would fix it.

Here goes the MiniToolBox file.
 

Attachments

Thanks (y)

All your latest issues are Windows related mostly with photos but Skype is in there but more importantly is the problem with Windows updates.

Error: (08/02/2020 07:49:17 AM) (Source: Service Control Manager) (User: )
Description: The Windows Update service did not shut down properly after receiving a preshutdown control.

We should see if we are able to repair Windows, if not able to you will need to download and install the latest ISO and your MB drivers, chipset drivers to be installed first after Windows.

Download then run the Windows All in One Repair tool from here, disregard the malware guidance but follow the other steps to the letter and in particular ensuring that you first create a new restore point and perform a proper Windows clean boot before running the repair, details for the clean boot here.
 
I did it but the error persists, i'll keep trying to solve it but i wait for your response.
 
Phill, i could update windows! I downloaded the Windows 10 Update Assistant from microsoft and twice my pc shutted down while running it but in the third try it worked. Now i have the latest 2004 version. What do you suggest i do now?
 
Once Windows has been installed, you install the necessary drivers for the MB and other hardware and then leave well alone.

Some additional info regarding drivers.

The first drivers that need to be installed are the chipset drivers for the MB, these need to be installed from a disk that shipped with the MB or be downloaded from the MBs own support site, they are not available from Microsoft as the drivers are specific to your MB.

Drivers should not be allowed to auto update and you should never update any driver/s unless the new drivers are intended to resolve a specific issue that you are having, installing new drivers unnecessarily can actually cause you the very issues that any new drivers are intended to resolve and uninstalling the new drivers may not resolve the problem/s that installing the new drivers has caused.

Depending on priority it can take many months before the driver provider releases any fix and they sometimes do not even bother.
 
Thank you very much for your help phill. I have installed the drivers for the 2004 version, if i have more problems with the BSODs i'll post it, but so far so good.
 
The latest crsh dmp is not driver but hardware related but can I just make sure that after clean installing Windows you then installed the chipset drivers for the MB.

We could do with the following;

Knowing what the computer was being used for when it crashed.

A new MTB log.

A new Speccy url.
 
Skype and Steam are flagged up in your latest dmp, both could be as a result of a problem with the internet security/Windows Defender.

Speccy shows a Windows update as being in progress, let that complete then follow the steps below, no rush on my behalf as I may not be around tomorrow due to previous arrangements.

Power Profile
Active power scheme: AMD Ryzen High Performance

I suggest that you change the Windows Power Plan to Balanced, High Performance is a form of overclocking that is known to cause stability and overheating issues and the setting should only be used for gaming type notebooks that have a discrete GPU that needs the extra power.

Get rid of CCleaner, it is no longer recommended as it installs both adware and spyware as well as deleting custom settings in folks browser add-ons, Windows Defender is also known to detect it as a PUP - Potentially Unwanted Program.

A fix below suggested in your MTB log;

Name: Microsoft Hyper-V Virtualization Infrastructure Driver
Description: Microsoft Hyper-V Virtualization Infrastructure Driver
Class Guid: {4d36e97d-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: Vid
Device ID: ROOT\VID\0000
Problem: : This device is disabled. (Code 22)
Resolution: In Device Manager, click "Action", and then click "Enable Device". This starts the Enable Device wizard. Follow the instructions.
 
Ok, i've changed the power plan and enabled the hyper-v driver. Also i uninstalled ccleaner.

I just had 3 bsod in like 7 minutes that didn't generate a dmp and then this fourth:
 

Attachments

I tried disabling hyper-v driver again and trying the AMD Ryzen High Performance again because i was getting BSODs every 2 minutes and i got this.
 

Attachments

After that last one it looks more stable, like before, the 1 BSOD per minute cycle stopped, so maybe it has to do with the PSU? sorry for the spam phill, i'll wait for your response, cheers!
 
Are you overclocking at all, on a computer that was using stock settings the two latest crash dmps would not bear any relevance to the changes that you previously made.

Npfs.sys was flagged in the first of the latest two and ndis.sys the second, the first concerns among other things Windows graphic drivers and the second network miniport drivers.
 
Status
Not open for further replies.
Top Bottom