New
#11
No, return to normal boot, then enable Driver Verifier. If Driver Verifier is already enabled, disable it, boot normally then enable Driver Verifier.
Sorry, my directions could have been clearer.
Varios BSOD errors - Crash at any point
-
-
New #12
No problem, it is the weekend after all!
I’ll return it to normal boot and enable Driver Verifier. Do you want me to post the .dmp once i get a BSOD using Verifier?
-
-
New #14
Here's the latest zip, I think the penultimate .dmp will be the Verifier, as I got a BSOD when I logged back into Windows. Before creating the zip file.
-
New #15
I maybe way off base but I've been following this thread. I am not a BSOD analyst, see what Rich has to say.
Think you said you loaded new BIOS. Did you load default values and save? You don't have any physical switches set on MB to anything other than normal operation. (I'm not familar with MB)
Is it safe to assume you are not overclocking anything.
I went to AMD and found the latest chipset drivers are dated Aug 13/18, version 18.10.0813. I may be looking at wrong chipset so you have to confirm. Is this the same level you are running? Wish these providers would provide details as to why they were issued.
https://www.amd.com/en/support
-
New #16
Hi Ken,
Thanks for this, yeah i made sure i loaded the defaults and saving before loading back into W10. And yes there are currently no overclocks on the CPU/GPU.
I did forget one important thing though, and that was the Asrock disk for the MB, currently installing all the drivers from that. So thank you for reminding me!
Downloading the drivers for the chipset too!
Hopefully have some more info once these are installed!
-
New #17
New dumps are all different, again. Some say hardware, some say memory, some say video.
Let's see what Driver Verifier shows us.
If nothing useful we can give some of the stress test programs a try:
===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums
===================================================
Follow this tutorials to stress test your GPU:
FurMark - GPU Stress Test - Windows 10 Forums
-
New #18
I installed drivers and apps from MB disk, still had BSOD’s. Then I installed the latest chipset drivers, still had BSOD’s.
However once these were installed, an error popped up, every time i logged in. It referred to .NET Framework 3.5 needed to be installed as my current driver may not be compatible. Managed to download/installed this after quite a few BSOD’s. Looked in device manager and my Enron USB 3.0 Host Controllers needed updating. After this it seems like the BSOD’s don’t occur as often.
Sorry I didn’t see your post there Rich, i’ll do some more Driver Verifier tomorrow and post again, then i’ll take a look at the stress test.Last edited by Wild Fires; 01 Sep 2018 at 20:06.
-
-
-
New #20
Looks like I need a little more of that luck. I've been trying to start the verifier, but the rate at which I'm getting BSODs is too high (every 2-5 minutes), so I don't think I'm going to get a very good result.
Quote
Related Discussions
