Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
PC repair technician of 23 years here and you might not like what I suspect.
The most common cause for something like this, especially since you are getting different stop codes, is corrupt/faulty/failing RAM stick(s).
I would suggest looking up Hiren's BootCD, setting it up to a bootable USB drive, and booting into it to run tests on your RAM. It has various programs for testing memory. I'm drawing blanks right now on exact test names, but in something like Memtest+ you'd wanna run the longest test and do at least 3-4 passes.
You will not be able to use the machine during these tests and they take several hours
If it finds errors, you then are going to have to test 1 stick at a time to figure out which one, or replace all of them.
If it does not find errors the next step would be to stress test your CPU. I can't remember what program I used for this but I'm sure Hiren's has something, and if not or you aren't sure which program to use, Google will be able to assist.
Wouldn't hurt to check the SMART status of your storage as well, since sometimes failing drives can cause BSODs.
The only other time I encountered this issue was when a motherboard of mine had failing VRMs. That took weeks to finally diagnose and I ended up RMA-ing my board because I am not equipped for that kind of repair. That came down to the machine passing every other test I threw at it, from RAM to CPU to Storage, and then finally reaching out to ASUS after talking it over with a colleague.
BSODs are pretty uncommon these days during normal operation, so it is very likely some form of failing hardware; though it's not impossible it's software related, like a corrupt Windows install or some ♥♥♥♥.
And when you say "scan" what are you referring to? What did you use to "scan" the memory?
No worries, just take your time and go over the information I provided.
If you have questions just ask here and I can answer them, I'm subbed to the thread so I will see them at some point and get back to you.