Tons of BSOD with new computer. Please help!

Momergil

Momergil

Member
Joined
Apr 8, 2020
Posts
9
Hi!

I'm glad I found this website; I hope you guys will help me with a year-old problem.

At the start of 2019, I finished assembling a computer with the following specifications:
* Ryzen 7 1800X
* MOBO ASUS PRIME X370-PRO
* Corsair Vengeance LPX 2x8Gb CMK16GX4M2B3200C16
* Samsung SSD 970 EVO 250GB
* PSU EVGA Supernova 750 G3

Since then, I've experienced an abnormal quantity of BSODs both while playing videogames as well as just using my PC normally. Later I found out I didn't have all the drivers updated and with the help of those classic "update all your drivers" Softwares, I managed to solve that problem (I guess). Well, the BSODs are now not as frequent, but they still occur too much. Eventually, I started getting some related to memory and I found out one of my 8Gb memory sticks was faulty; since then I removed it and I'm still in the process of asking Corsair for a replacement. Nevertheless, the frequent BSODs still occur, not to mention videogames crashing all the time no matter which I play. Theses BSODs come in a variety of forms: some times is the NVIDIA driver crashing during a game, some times is some random stuff. And now I don't know if I'm still having driver problems or if my problem is hardware.

Some things to notice here:
* The memory I'm using is not formally compatible with my MOBO. I bought it because my Noctua NH-D15 required small memory sticks and the other options were too big. Moreover, this link suggests my particular type of memory is actually bad to be used with Ryzen, but apart of the BSODS, I'm not having any problem related to the memory; for example, I managed to use it at full 3200MHz.
* While searching for solutions in the web, I discovered the "Driver Verifier" utility. Then I ran it in some suggested configuration and with that on, I was incapable of accessing W10 again; it just wouldn't start. Later I found out this was precisely DV telling some of my drivers was faulty; the problem is I didn't know how to solve it, not even how to detect which was the faulty driver, so I just pretended I didn't see it ^^
* Because of the need to ask for Corsair for a replacement, I bought a new 8Gb 2400MHz CMK8GX4M1A2400C16 and it is still under the 7 days period which I'm able to send it back to the seller without a problem. So if by any means the resulting conclusion is: "your problem is memory and you're gonna have to choose a non-Corsair replacement", it would be great if I could solve the mystery quickly before the 7 days expire.
* Some times, after a BSOD, a memory dump is not created: even this is eventually crashing! xD

Finally, links for memory dumps of some of the lastest BSODs:

* Compilação de dump
* Compilação de minidump
* CS GO Crashes: Compilação outros dump

Any help solving these problems will be very appreciated! And if somebody suggests running Driver Verifier again, please send me some guidelines. Different websites tell different ways of configuring it and that makes me lost :T
 
MrPepka said:
Uninstall Diebold Network Monitor
Update Intel LAN driver - Download Intel® Ethernet Adapter Complete Driver Pack
Click to expand...

Hi! Thanks for the reply!

Regarding uninstalling Diebold Netwrk Monitor, I have no idea how to do that. In fact, I didn't even know what it was before googling for it and discovering it is related to Gas Technologies' Warsaw product, which is a security system some Brazillian banks use for accessing their webpages. Curiously enough, even though I already used this product in my PC before (I need it for rent tax calculations), I normally uninstall it after that. So now I went to Uninstall Applications and didn't find it on the list, suggesting I didn't forget to uninstall it, which leads to me asking how do you know it is still roaming somewhere on my PC and, of course, how do I uninstall this already uninstalled product :| I searched a little and a page suggested Warsaw may actually not get uninstalled normally and I would have to use Revo Uninstaller or the like to actually eliminate it from my PC. Regarding this, any suggestion will be welcomed. (Curiously, I was about to INSTALL this software since now is the period to make the rent tax declaration in Brazil ^^)

Regarding the Intel LAN Driver, I downloaded the package you pointed out and installed. Now the Intel PROSet Adapter Configuration Utility is pointing out my driver version is 12.18.9.6. I suppose everything went OK.
 
There is no uninstaller in the folder where the program was (or is still installed)? If this is not the case then it is actually better to use Revo Uninstaller
 
MrPepka said:
There is no uninstaller in the folder where the program was (or is still installed)? If this is not the case then it is actually better to use Revo Uninstaller
Click to expand...

Well, I uninstalled with Revo and, indeed, it was letting some trash inside the PC after the uninstallation. Since then I have activated Driver Verifier in accordance with these guidelines and so far so good. Does anybody have any comments regarding the dump files?

As bonus info, I have frequent videogame crashes which not always produce BSODs. I gave some dump files of CS GO, but the best example is the Mu Online server I play and in which I experience recurring window crashing. Other players report having that as well, but not as frequently as I experience.
 
Hi,

after more than 24h using Driver Verifier, no BSOD happened and I shut It down. I tried to 'stress' my computer playing videogames, one of the common situations when BSODs normally happen (even though many are not while playing them) and no BSOD happened. Now today after waking up I had just login into my W10 and while I had only Chrome open, my PC crashed and restarted. Unfortunately, this time no BSOD was produced: Event Viewer reported 'volmgr error' saying that was a failure while creating the dump file. In fact, this is a common issue here: quite often a crash happens and no BSOD is created, a problem I'ld like to fix as well if possible.

bsod.png

In the image above, all are failed BSODs.

Moreover, another error that happened and also common was with Perflibin perfts.dll in the service LSM. I can't say if this is what caused the crash, but I definitely got an error here to be fixed. Searching the web I got this and this links telling to run these commands at the Windows folder. This link also gives some insights into possible causes and solutions. So I'll be running those commands, but nevertheless any comment or help will be once again appreciated. It's clear that uninstalling Diebold Network Monitor and updating the Intel LAN driver wasn't the whole solution to the BSODs.
 
A complementary question here: searching on a website a thread noticed that sometimes failing to creating BSODs is a PSU problem: it's not giving proper voltage to the components. Well I never changed my PSU configuration in BIOS or anywhere, but it's interesting to notice that I'm using my memories in full 3200MHz clock. Could it be I needed to increase the memory voltage for using the memory at its top speed?
 
Maybe this will help regarding the issue of proper Memory voltage. I took some pictures of my BIOS showing how the voltages are configured. Below is when my memory is set to 2133 MHZ:

1 2100.jpg

Now the image below is what happens when I configure it for full 3200MHz, what I desire. Notice that only the VDDCR SOC Voltage is changed to 1100 V. I read here that this may be a little insufficient for this configuration.
2 3200.jpg

Finally, the following panel notices (and for both memory frequencies) the memory voltage is 1.200V:
3 mem col.jpg
I'm curious to know if this value shouldn't have changed to a higher one when I put it to 3200MHz.

So what do you guys thing? For now, I'll be using at 2133 MHz to see if there is any correlation between the memory clock and my BSOD.
 
One more hint: I tried to run Driver Verifier again, but this time I set almost all of the possible verifications on in accordance with this guideline. When that happened, my computer just wouldn't restart again and I had to use the restore point to log back to Windows. Is this a bad sign or have I done something wrong? Unfortunately I couldn't find any new minidump or memory.dmp update.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top