Random BSODs out of nowhere.

Joined
Nov 3, 2020
Posts
19
Hey. A guy on Reddit pointed me towards this site when i asked for help with my BSOD, said the people here are pretty helpful and knowledgeable.
Here are the answers to the questions on the posting instructions.
  • N/A - Custom Build.
  • Desktop.
  • N/A - Custom Build.
  • Windows 10 Pro.
  • x64.
  • N/A - Windows 10.
  • Windows 10.
  • I'm... Not sure. It certainly didn't come with the system, but I just had a friend with some licenses install it for me, so now i don't have the watermark. Yay.
  • Eleven months.
  • Eleven months.
  • No.
  • Intel Core i3-9100f.
  • 1x8GB, 2400hz, DDR4, HyperX RAM, installed on slot n°2. HX424C15FB3/8 Model.
  • RX580 8GB VRAM.
  • H310M H 2.0.
  • 450W 80+ Bronze, non-modular PSU. EVGA, i think.
  • It's currently off, as far as i know.
  • I'm not using any third party antivirus, firewall, etc. Window's ones are on though.
  • No.
  • Not right now. Used one recently, however.
  • No.
    I also put some additional information on my original Reddit post. It's kinda long, sorry about that, but here it is:
    I'm getting random BSODs, usually after a few hours of having the PC turned on. (although one was only a few minutes in) I already tried updating graphics card's drivers (up to date on AMD Software), disabling fast startucorrupted system files with "scannow" (cmd), SSD with "chkdsk" and CrystalDiskInfo (healthy, 98%), Windows is up to date, what can I do now?
    The BSOD type was unexpected_store_exception.
    I bought this setup in late 2019, but I only got my hands on the parts in january. The problem has been happening since last month's second week, if I remerber correctly. The BSOD occours, on average, every other day, maybe a bit less often, often enough, however, to keep me worried. Due to the random-ish nature of the ocourence, troubleshooting is troublesome. Please try to avoid solutions that include replacing hardware, (Though I guess if you suggest them it means other, more simple solutions won't do) as it would be very difficult for me to buy new stuff. I live in Rural Brazil, so considering the fact that a dollar is worth 5.7 Brazillian Real, the pandemic, ( some parts were up to 50% more expensive than when i bought mine) and that there are no delivery services that reach my house, it would be tough as hell to get a replacement. Needless to say, English is not my first language, so please excuse me if there are any mistakes, or ifI was inarticulate and there is need for clarification in certain parts. Leave a comment and I will rectify the error right away.
    Thank you for your time.
    Addendum: When I was running the program to get the SysnativeFileCollectionApp file, it stated "Waiting for SystemInfo". Is that normal/expected, or do I need to fix that?
 

Attachments

Hi Pipocaramelisada,

There does not look to be a record of any crashes, and it also appears that the installation is less than a day old. I presume you reinstalled Windows.

At this moment, we will have to wait for new crashes to occur for something to work with. Please upload a new Sysnative zip file once at least a few crashes have occurred.

There are a few things I want to ask you NOT to do
- do not perform any drastic actions, like reinstalling Windows. These actions do not always work and could, in fact, make things much worse.
- do not run any utility that deletes files. Any sort of utility that deletes files, like CCleaner or disk cleanup, tend to remove logs and files that are crucial for us to help you.
 
Hi Pipocaramelisada,

There does not look to be a record of any crashes, and it also appears that the installation is less than a day old. I presume you reinstalled Windows.

At this moment, we will have to wait for new crashes to occur for something to work with. Please upload a new Sysnative zip file once at least a few crashes have occurred.

There are a few things I want to ask you NOT to do
- do not perform any drastic actions, like reinstalling Windows. These actions do not always work and could, in fact, make things much worse.
- do not run any utility that deletes files. Any sort of utility that deletes files, like CCleaner or disk cleanup, tend to remove logs and files that are crucial for us to help you.
That's surprising. I didn't reinstall windows. However, yesterday I installed a windows update, the update took several hours to download and install completely, and when it finally ended, i noticed my wallpaper was gone. That may be it. I don't know why the wallpaper was deleted, and I do not know if the update fixed the BSODs. So far so good, in that regard, although earlier today, I was playing CS and my pc froze for like, maybe 40 seconds. I seriously thought it was going to be a BSOD. You think this may be related at all?
 
Hi!

Retrieve System Information, using speccy
  • Download Speccy portable (click)
    (current version at the time of this post is 1.32.740, but it will change in the future... The link should always point to the newer version, by the way)
  • Unzip/decompress it and put it on your desktop.
  • When the program opens, it will retrieve some information regarding your system.
  • Once it's done, select the File menu and choose Publish snapshot. Answer Yes to the confirmation message.
  • On the next screen that comes up, choose the Copy to Clipboard button and paste this link in your next reply.
 
That may be a feature update, in which case you may have Windows.Old folder containing dumps in the Minidumps folder. If you do, please do the following
- copy the minidumps to a different folder
- in this other folder, create a zip file from the minidumps (select all > right click > send to > compressed (zipped) folder)

Upload the zip file.
 
That was the case. Here is the file, there was only one .dmp in the minidump folder, so I just zipped it up. Don't know if it was necessary to do so, though.
Is it possible that the update fixed the BSODs? I didn't get one since I updated.
 

Attachments

That's possible yes, there's always a chance an update could resolve a problem.

The dump itself is not too revealing, it is hinting to a USB device, but I'm refraining from providing any suggestions as I do not see a point in giving any at this moment.
 
Hello again. It's been a long time. I spent a long time without any problems, but i got another BSOD. I was talking to my friends on discord, and we could still hear each other, but my browser was unresponsive.
I tried doing the same as last time, and looked for a windows update. I installed it and no problems for a long period of time. Untill now.
I've attached a new sysnative (and speccy, since i forgot in the other posts and xilolee asked for it), since it's been a long time since the last ones, and because my system has changed, I added another stick of ram i bought form my friend, it's the same frequency, amount, and both are DDR4, but his is on a different timing (CL16 VS CL 15), but i don't think that's at all related, it's more likely to be the disk.

http://speccy.piriform.com/results/vSE1k3uatPAMnb4cTrkx8vI
 

Attachments

I'm not finding any record of a recent BSOD, I'm not saying it didn't happen but that the system did not record it. Did you get a chance to see the code displayed on the blue screen?

Regarding the RAM, generally you need to use a matched pair otherwise you can get hardware related BSODs. Your RAM is not matched and this would concern me.
 
The 0xEF code does often end up being RAM or disk related so it could be the mismatched RAM triggering this.

The motherboard settings on Auto generally do a good job of setting the clock speeds but if the two sticks do not work well together as they should in a dual mode then you can get problems. However, without the crash dumps it is difficult to be sure.
 
I find it unlikely, because the time that i installed the second stick of RAM does not coincide with the BSODs, and the ones that i'm getting right now are of the same nature of the ones I got when I used single channel RAM.
I guess I will have to wait for another one so I can have the minidumps to get better insight.
I will also temporarily remove the extra stick untill i get another BSOD.
 
The BIOS: Versão/data do BIOS American Megatrends Inc. F12, 13/08/2019

1) Upgrade the BIOS: F12 > F14a


H310M H 2.0 (rev. 1.0) Support | Motherboard - GIGABYTE U.S.A.

Code:
Improve DDR compatibility
Workaround beta BIOS to improve Kingston DDR4-2666 stability concern on some specific memory chip suppliers
Add NTFS format support for Q-Flash™





2) These were not seen on the Qualified Vendor List (QVL):
a) TEAMGROUP-UD4-2400
b) KHX2400C15/8G

H310M H 2.0_DDR4-QVL-20191128 (gigabyte.com)



3) When purchasing RAM:
a) Select RAM modules displayed on the QVL
b) Purchase in pairs with matching SKU
c) Consider RAM manufacturers that guarantee compatibility
d) Consider RAM manufacturers that have lifetime warranties



4) If there are any future BSOD please change the default language to English so that the logs can be scanned:
Add, Remove, and Change Display Language in Windows 10
Change Display Language in Windows 10
 
I will consider updating the bios, but not right now, as it can be a drastic measure, and I don't have too much information on the BSOD.
I didn't buy a ram stick from the QVL because Hardware prices are very high in my area right now. I bought it from my friend, and so far, it seems to be performing as expected, with significant improvements in framerates.
I'm changing the default language right now.
 
I have come once again for your help. I Got a BSOD while AFK - it stated "driver verifier detected violation".
Any advice on possible actions is welcome.
 
How come Windows Driver Verifier (DV) was turned on?

Post a new Sysnative log collector attachment with English as the default language:

Add, Remove, and Change Display Language in Windows 10
Change Display Language in Windows 10

SysnativeBSODCollectionApp | Sysnative Forums


Code:
TEAMGROUP-UD4-2400
KHX2400C15/8G



BIOS Version                  F12



0: kd> .time
Debug session time: Wed Jan 27 17:37:57.824 2021 (UTC - 6:00)
System Uptime: 0 days 11:48:36.509


0: kd> .bugcheck
Bugcheck code 000000C4
Arguments 00000000`00091001 fffff804`4d640960 ffffb601`f0a7c910 ffffb601`f0a7c958
 
Rich (BB code):
0: kd> lmvm VBoxNetLwf
Browse full module list
start             end                 module name
fffff807`ad860000 fffff807`ad8b6000   VBoxNetLwf T (no symbols)           
    Loaded symbol image file: VBoxNetLwf.sys
    Image path: VBoxNetLwf.sys
    Image name: VBoxNetLwf.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Oct 16 16:33:18 2020 (5F89BD3E)
    CheckSum:         00046F32
    ImageSize:        00056000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Could you please check for an updated version of Virtual Box? Otherwise, I would suggest removing the program now and seeing if the system remains stable.
 
So, yesterday night the problem was kind of different from ususal, the crashes were consistent and very immediate, I couldn't spend a minute after startup and i'd get a crash, so I just went to sleep. Today I just did some basic troubleshooting in safe mode, uninstalled some programs (to x BlueRobot, when I tried uninstalling Vbox from control panel, I got a different BSOD, "System Verifier Detected Violation", could be just a coincidence, but the timing was perfect. I left a minidump attached, if anyone's curious, but I don't know if this one's is the right one.) Slowly I got to startup with more and more things enabled and i think things are relatively stable now. The issue may have been solved already,and i'm very grateful to everyone in this thread, though I have a sneaking suspicion that i'll get another BSOD sooner or later due to a disk issue.

To zbook, I have already changed my system language the way you specified, but some things still seem to remain in Portuguese, I don't know why, and it's very intermittent too, like windows will say "Bem-vindo" (welcome) upon startup but if i right click on the taskbar, all of the options will be in english.
 

Attachments

Please open a Command Prompt and then the following command:

Code:
verifier /query

Could you please let us know if you get a message like:

Code:
No drivers are currently verified.
 

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

Back
Top