Do you have trouble with Blue Screen of Death (BSOD) messages and need help?
Do you have trouble with Blue Screen of Death (BSOD) messages and need help?
I have been getting BSOD errors on this computer for a while now. It is an ASRock B650E PG Riptide board with a new NVIDIA RTX 4080 GPU, plus an AMD Ryzen 7 7800X3D processor running at 4.20 GHz. I have installed 32 GB of RAM (about 31 GB actually works). The system runs on the x64 architecture and is a 64-bit OS.
I built this PC in December, so it should be relatively new, but things are still acting up. Most apps run fine for me, though they sometimes crash suddenly or randomly trigger these blue screen errors. This has been really stressful lately because I was pretty excited about the build. It is my first time setting everything up myself, and I feel like I went all in on it, so I'm a bit worried that something wrong might be happening.
I don't know how to attach those dmp files yet, which makes me feel like I need more help. If your specs aren't detailed enough, just tell me what you're missing and I'll let you know.
You got two sticks. Take one out and see what happens. Then check the other one too. Make sure you put the first stick in the right slot (you might need to read your motherboard manual for this). 0MHz Unknown Unknown 16384MB 4800MHz Unknown F5-6400J3239G16G 16384MB 4800MHz Unknown F5-6400J3239G16G
Can you choose option one on this link and then follow that next step? Small memory dumps: Have Windows create a small memory dump (minidump) on BSOD to make a file in c:\windows\minidump after the next BSOD happens. Open Windows File Explorer, go to C:\Windows\Minidump, copy those mini-dump files onto your Desktop. Do not use Winzip; instead, use the built-in feature in Windows. Select those files on your Desktop, right-click them and choose "Send to" - Compressed (zipped) folder. Upload the zip file to the Cloud (OneDrive, Dropbox, etc.). Then post a link here to the zip file so we can check it together. Many applications are victims, but this is rare; it's actually the cause that matters most.
When you finish and you've had some blue screen errors, go to C:\Windows\Minidump and upload every file in there to a cloud service. Then share the link with that service here. Make sure they are public so we don't need to log in to get them. Also remember, your apps aren't causing these BSODs - they can't. It's much more likely that a driver you installed is to blame for this. Using the dumps will help us figure out which one is wrong.
Yeah, I've had several BSOD errors. You can try this link: https://1drv.ms/u/s!ApW_3o1-0VV2gq4ISleN-bQ5eeiugA So if the error is because of a driver, what does that mean? Should I delete or update it to fix the problem?
Sure enough, Ubuysa probably sees more in those dumps than I do, but I'll still check them out here for my part. Here are two files from earlier this week: one had a DPC watchdog violation coming from svchost.exe around 32 minutes ago, and the other tried to write to read-only memory due to NVDisplay.Cont running too soon after that first error. Then there was a timestamp verification problem with mtkwl6ex.sys while System was active for over two days. The biggest one though came from GameOverlayUI hitting a page fault in non-paged area, and another one about memory management both stucked on svchost.exe. It looks like your Wi-Fi driver might be causing some of these issues, so you should check that out here to see if it's been updated: https://pg.asrock.com/mb/AMD/B650E PG Riptide WiFi/index.asp#Download MediaTek Wireless Lan driver ver:3.3.0.0702 is the version you need after that. Also, please update your Nvidia drivers too just in case they are involved.
These dumps show pretty clearly that your RAM is in bad shape. One specific dump (0x1000007E) shows a crash where the driver called mtkwl6ex.sys got an error when it tried to do a math calculation on memory. This looks like a problem with the WiFi driver, but since we have other crashes too, it's probably your RAM that is broken. You should definitely update or re-install that specific driver just in case.
The rest of your crash dumps (0xBE, 0x50, and 0x1A) didn't show any third-party software on the stack when they happened; this means the problem is likely with the hardware itself rather than a piece of software trying to run too fast for your memory. The crash at 0xBE happens because a page table got corrupted. You can see in the details that the address points outside normal limits, which usually means bad RAM.
The crash at 0x50 happens when the system tries to read information about an active session from memory but finds something wrong with how that data is stored there. It looks like it's looking for a session ID and ends up hitting a wall because of bad RAM. The other two crashes (the ones labeled 0xBE, 0x1A, and 0x50) were all caused by corrupted page tables, which points directly to your memory sticks being the issue. You should definitely test your RAM by running Memtest86 on a different PC if possible; since you can't trust yours right now, getting another computer to run this test is safe. Just make sure to follow the steps: download the free version of Memtest86, put it onto a USB stick using an imageUSB tool, and then plug that USB into your PC to start testing. If you wait for four full passes through all thirteen tests with no errors showing up, or if Memtest tells you there are even just one single-bit error, then your RAM is definitely failing.
I worried it might be something broken inside the case. Getting in there wasn't really what I wanted to do, but if it had to be done. I'll handle all of this after my shift ends. Also, last night I tried a test on an app that kept crashing with BSODs, and just changing drivers didn't fix it enough. Now that you've read back your message, it makes sense why.