[SOLVED] Variety of BSODs, hard audio loops, and a random restart out of nowhere. WIN 10

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

Made-a-Fool

Reputable
Sep 2, 2019
47
2
4,535
I've had my PC for about 7 months, and it's had it's fair share of issues. Most frustrating, however, are frequent BSODs happening out of random. I've gotten blue screens saying the error DRIVER_IRQL_NOT_LESS_OR_EQUAL twice, one PAGE_FAULT_IN_NON_PAGED_AREA, and one SYSTEM_SERVICE_EXCEPTION, each one paired with an audio loop lasting for as long as the blue screen is up. One time was just the audio loop for a couple of seconds until my PC restarted automatically. No prompt, nothing. It just took me to the boot screen, and to the sign-in screen shortly after. Also, besides the restart out of nowhere, Windows never restarts after a blue screen. The error collecting gets to 100% and freezes from what I can tell.

I've run SFC tests plenty of times, always the same thing, "Windows Resource Protection found corrupt files but was unable to fix some of them." I've also run DISM, and it was unable to find source files. I'm at a loss here. I've called my PC's manufacturer's Tech support, and he had me reinstall Windows. It seemed like it fixed my problem, but the opposite was true. I'm not sure what the issue is coming from. I read somewhere that it could be because of driver issues? It could possibly be due to a program I downloaded both times (before the reinstall, and after) called Voicemeeter Banana. I use the program to split audio from different sources so it's easier to edit when I record. It also uses a virtual audio cable to route said sources. I looked for about an hour to see if anyone else was having the same issue with that specific program, but came up short.

Now, after getting another BSOD, MEMORY_MANAGEMENT, I completely uninstalled Voicemeeter Banana and the virtual audio cable. Did an SFC scan, but there's still corrupted files that it can't fix. I don't know what to do anymore. I just set the thingy to gather a small dump file after the next BSOD, so I'll edit this post then. If there's anything you need me to provide, just let me know. Thank you for any sort of help.

OS: Windows 10
PC: Skytech Oracle X
CPU: AMD Ryzen 7 2700X 8-Core 3.7 GHz (4.3 GHz Max Boost)
Motherboard: ASRock Fatal1ty B450 Gaming K4
Ram: 16GB DDR4 Gaming Memory with Heat Spreader 2400 MHz
Storage: 240GB SSD / 1TB 7200 RPM HDD
GPU: Nvidia RTX 2070 8GB GDDR6
 
Solution
Any error count above zero is too high so you need new ram. You can rma them as failing Memtest is usually all you need to get them to replace it. Since its part of a set, you would need to replace both even though 1 works. Its up to you how you proceed.

I don't think Prime is needed now, its the stick.

it could have been ram all along, causing windows to corrupt. At least you are on latest BIOS now
I ran the new dump files through the debugger and got the following information: https://pste.eu/p/giVc.html

File information:090719-9984-01.dmp (Sep 7 2019 - 08:48:24)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 23 Hour(s), 07 Min(s), and 06 Sec(s)

File information:090719-8906-01.dmp (Sep 7 2019 - 10:58:44)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:0 Day(s), 0 Hour(s), 06 Min(s), and 35 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
neither shows anything I could point at and say thats it... dumps don't mention any drivers by name, as a cause anyway. PLenty of drivers listed but none are obvious problems.

since memory checker in windows already reported problems, lets wait till memtest is complete before going forward.
ram more likely cause of random errors.
 
Last edited:
neither shows anything I could point at and say thats it... dumps don't mention any drivers by name, as a cause anyway. PLenty of drivers listed but none are obvious problems.

since memory checker in windows already reported problems, lets wait till memtest is complete before going forward.
ram more likely cause of random errors.
Yeah, it seems to be. I ran a test with the first stick of RAM using all of my cores and had no problems getting through all four passes. During the testing of the second stick, Memtest closed in what I'm assuming was the second pass, and my pc booted. Both sticks were tested in the same slot. So, I then used only one core for each stick. First one, again, no problems. The second stick, however, had 103 errors. Is that a lot, or is that an average amount for defective RAM? Not that it matters anyway, now I'm pretty confident that the second stick is the culprit behind all the BSODs.

Also Memtest wouldn't detect my keyboard input while testing the second stick, so I couldn't save the error report at the end. I had to force shut down my pc with the power button. I still have yet to run Prime95.
 
Last edited:
Any error count above zero is too high so you need new ram. You can rma them as failing Memtest is usually all you need to get them to replace it. Since its part of a set, you would need to replace both even though 1 works. Its up to you how you proceed.

I don't think Prime is needed now, its the stick.

it could have been ram all along, causing windows to corrupt. At least you are on latest BIOS now
 
Solution
Any error count above zero is too high so you need new ram. You can rma them as failing Memtest is usually all you need to get them to replace it. Since its part of a set, you would need to replace both even though 1 works. Its up to you how you proceed.

I don't think Prime is needed now, its the stick.

it could have been ram all along, causing windows to corrupt. At least you are on latest BIOS now
I'll rma this monday when their support is open. THANK YOU for all the help you've given me. You're my hero.

If anything comes up I'll update.

I ran the new dump files through the debugger and got the following information: https://pste.eu/p/giVc.html

File information:090719-9984-01.dmp (Sep 7 2019 - 08:48:24)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 23 Hour(s), 07 Min(s), and 06 Sec(s)

File information:090719-8906-01.dmp (Sep 7 2019 - 10:58:44)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:0 Day(s), 0 Hour(s), 06 Min(s), and 35 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
Thank you too!!!!
 
  • Like
Reactions: gardenman