As the title suggests, I'm getting non stop BSOD's on a fresh install of windows and a brand new build.
Let's Start off with the specs and i'll give you guys more insight on what I've done to troubleshoot and the information I've gathered so far.
CPU: Ryzen 5 2600x
GPU: Asus ROG STRIX Radeon RX 570 OC
RAM: Corsair Vengeance RGB Pro 16GB 3000mhz
MOBO: Asrock x470 Master SLI/ac
SSD: Samsung 860 EVO
HDD: Seagate Barracuda 2tb
Don't think the rest of the components matter, but just a KB/M and a Dell Monitor.
I've had to reinstall the OS 3 times. Every time I believe I've fixed it, the next day I'll start getting nothing but a plethora of BSOD's. Up until this point, it's been the same thing over and over.
The first install I figured was my fault because I accidentally installed incorrect drivers. So I said to hell with it, let me just install a fresh copy of the OS and make sure I pay attention to which drivers I'm installing. I'm now onto OS install #2. I update all the drivers, and bam BSOD. After looking at the dump files and thinking back to when the BSOD's happened on my first install I thought it was the Intel WiFi driver. So I used the intel auto detect software to see if any drivers were out of date and voila, the WiFi driver needed an update. I was quite happy, Last sunday, no issues. It seemed to make sense, anytime I was downloading a program and trying to install. I would experience a BSOD. The following day, I've got photoshop running, I attempt to do some work. BSOD. The second install seemed to be a bit wonky, task manager for whatever reason was opening slower than it was on the first install, as were the windows folders and various programs. I attempted to use Driver Verifier to see if it would spit back which drivers were causing the issue. On each restart I'd get a BSOD telling me that the Master Ryzen program was the culprit(I don't plan on overclocking so I don't even really need that program to be honest) It would keep looping and popping that same BSOD, telling me that Master Ryzen was the issue. So, not being able to get back into windows I attempt to disable driver verifier through CMD before it tries to boot. That works, but the BSOD loop continued. At this point, as you could imagine. I'm quite frustrated. So I wipe it again, reinstall the OS. So far it's been fairly good. Programs are opening quickly and I've installed the major programs I need. Windows is running smooth, except for two bluescreens I've gotten since the install about 4-5 hours prior.
BSOD #1 Popped a "SYSTEM_SERVICE_EXCEPTION"
BSOD #2 Popped a "MEMORY_MANAGEMENT"
This is pretty much the same stuff I've been getting on every install. Every time it happens, bluescreen view tells me ntoskrnl.exe is to blame. except on the last bsod I got recently, it said ntfs.sys was the culprit.
Based on my knowledge those are kernels and they likely wouldn't be the issue, and from what I've read its because windows forces the computer into a BSOD so when it generates the dumps, programs like bluescreen view will tell you that it was the culprit. Unless I'm wrong, then feel free to correct me.
At this point, I'm not sure what else to try. I've ran sfc /scannow. I've run memory diagnostics, I've run diagnostics for the ssd and all came back positive. Updated every single driver that needed to be updated. I've flashed the latest bios from Asrock, downloaded the latest chipset driver from amd. yet im still experiencing a bsod. Which seems to happen when something is downloading for the most part.
I'm not very knowledgeable when it comes to reading bug checks and analyzing crash dump reports but I tried my best to gather knowledge from windbg and thought it was the wifi drivers but those are up to date and I still experienced a bsod.
If there is anyway for me to upload what windbg reports, I'll be more than happy to upload the dumps and have someone analyze them as I'm sure there are plenty of you out there with knowledge much superior to my own when it comes to troubleshooting these BSOD's and analyzing the dumps.
I appreciate everyone's time and effort in advance and I hope that someone can help me get to the bottom of this pesky bsod issue.
Let's Start off with the specs and i'll give you guys more insight on what I've done to troubleshoot and the information I've gathered so far.
CPU: Ryzen 5 2600x
GPU: Asus ROG STRIX Radeon RX 570 OC
RAM: Corsair Vengeance RGB Pro 16GB 3000mhz
MOBO: Asrock x470 Master SLI/ac
SSD: Samsung 860 EVO
HDD: Seagate Barracuda 2tb
Don't think the rest of the components matter, but just a KB/M and a Dell Monitor.
I've had to reinstall the OS 3 times. Every time I believe I've fixed it, the next day I'll start getting nothing but a plethora of BSOD's. Up until this point, it's been the same thing over and over.
The first install I figured was my fault because I accidentally installed incorrect drivers. So I said to hell with it, let me just install a fresh copy of the OS and make sure I pay attention to which drivers I'm installing. I'm now onto OS install #2. I update all the drivers, and bam BSOD. After looking at the dump files and thinking back to when the BSOD's happened on my first install I thought it was the Intel WiFi driver. So I used the intel auto detect software to see if any drivers were out of date and voila, the WiFi driver needed an update. I was quite happy, Last sunday, no issues. It seemed to make sense, anytime I was downloading a program and trying to install. I would experience a BSOD. The following day, I've got photoshop running, I attempt to do some work. BSOD. The second install seemed to be a bit wonky, task manager for whatever reason was opening slower than it was on the first install, as were the windows folders and various programs. I attempted to use Driver Verifier to see if it would spit back which drivers were causing the issue. On each restart I'd get a BSOD telling me that the Master Ryzen program was the culprit(I don't plan on overclocking so I don't even really need that program to be honest) It would keep looping and popping that same BSOD, telling me that Master Ryzen was the issue. So, not being able to get back into windows I attempt to disable driver verifier through CMD before it tries to boot. That works, but the BSOD loop continued. At this point, as you could imagine. I'm quite frustrated. So I wipe it again, reinstall the OS. So far it's been fairly good. Programs are opening quickly and I've installed the major programs I need. Windows is running smooth, except for two bluescreens I've gotten since the install about 4-5 hours prior.
BSOD #1 Popped a "SYSTEM_SERVICE_EXCEPTION"
BSOD #2 Popped a "MEMORY_MANAGEMENT"
This is pretty much the same stuff I've been getting on every install. Every time it happens, bluescreen view tells me ntoskrnl.exe is to blame. except on the last bsod I got recently, it said ntfs.sys was the culprit.
Based on my knowledge those are kernels and they likely wouldn't be the issue, and from what I've read its because windows forces the computer into a BSOD so when it generates the dumps, programs like bluescreen view will tell you that it was the culprit. Unless I'm wrong, then feel free to correct me.
At this point, I'm not sure what else to try. I've ran sfc /scannow. I've run memory diagnostics, I've run diagnostics for the ssd and all came back positive. Updated every single driver that needed to be updated. I've flashed the latest bios from Asrock, downloaded the latest chipset driver from amd. yet im still experiencing a bsod. Which seems to happen when something is downloading for the most part.
I'm not very knowledgeable when it comes to reading bug checks and analyzing crash dump reports but I tried my best to gather knowledge from windbg and thought it was the wifi drivers but those are up to date and I still experienced a bsod.
If there is anyway for me to upload what windbg reports, I'll be more than happy to upload the dumps and have someone analyze them as I'm sure there are plenty of you out there with knowledge much superior to my own when it comes to troubleshooting these BSOD's and analyzing the dumps.
I appreciate everyone's time and effort in advance and I hope that someone can help me get to the bottom of this pesky bsod issue.
Facebook
Twitter
Instagram