Windows 10: Constant BSOD. Minidump attached.

Created a new build today. Had numerous BSOD throughout the day.


Fresh install of Windows 10, specs below:

MB - Gigabyte B550 Aorus Pro AX.

CPU - Ryzen 5 3600

RAM - 32GB Corsair Vengence LPX 2*16GB 3600mhz

GPU - 1070 8GB Strix

STORAGE PCIE - 4.0 1TB Sabrent Rocket m.2

PSU - Corsair SF600 Platinum


https://1drv.ms/u/s!Av-b7X2awQ3TkWjGfnbhbUyFSuCv?e=OHEhn6 < Minidump Log


I have also ran Memory Diagnostics and it came back with "The Windows Memory Diagnostic tested the computer's memory and detected no errors"

Can anyone analyze these and help me out?

:)

 

KernelBase.dll is broken constant BSOD's constant game crashing.

Hi Darry,

User Profile corruption is one of the possible reasons why you are experiencing constant BSOD's on your computer. You mentioned that you ran the
System File Checker (SFC) tool, but is still getting a stop code. To further troubleshoot the issue, we suggest that you create a new User Profile and check if the issue persists.

To create a user profile, follow these steps:

• Go to Settings. Click Accounts.
• Select Family & other people.
• Select the Add someone else to this PC tab.
• Name the user as Test.
• Leave the password field blank.
• Hit Next.
• Sign in as Test user.

You may also check this link
to fix BSOD errors. Choose the situation when you experienced the problem and follow the troubleshooting steps.

 

Constant BSOD - Minidump file analysis

Hello,

In the last 2 days I have had countless BSOD, I tried to update all drivers and windows as advised when I googled the stop codes. I was advised to run a verifier in the windows powershell which resulted in constant BSOD when booting. I struggled a long time
trying to fix it but in the end I decided to rescue my files before reinstalling windows again.

During installation I received a couple of BSOD but after a few tries it manages to get installed. Now I can enter the desktop but after 2-3min I receive a BSOD again.

I tried to run a RAM diagnostic but no problems where detected.

I feel like I have tried everything in my power, please help me.

Below is a link to my minidump, system info and log:

https://drive.google.com/drive/folders/1n4S_SF0MqCvhYZrRZKkc6vl2CR7495mY?usp=sharing

 

2.9.0 causing BSOD (minidump analysis attached)

I've been doing the reboot + immediately launch game dance all day (like ... 20+ times), and the only way I can get it to reliably crash is when I launch GPU-Z first.

Here's a Dropbox folder with a bunch of minidumps to analyse: Dropbox - File Deleted

Note that it doesn't always lists GPU-Z as active process when it crashes, but it's always the nvidia driver sys, though.

I've mailed all of this to L: driverfeedback at nvidia.com, and reported it in the Driver Feedback Thread on the Geforce forums too.