Multiple and varied BSODS on a very frequent basis

J

jzyvoloski

Member
Joined
Jun 3, 2021
Posts
18
Hello,

I came to this website because it was recommended to me by a Microsoft volunteer moderator.

For the last 6 months I have had a severe issue with random BSODS occurring at almost any time. I believe, but am not certain, these issues started around the time I updated Windows to the October update which was around December 2020. Prior to this I had barely ever had any issues with BSODS. These crashes are varied but there are definitely a few that occur more than others. Unfortunately I don't have all the dump files from the past but I do have some recent ones that I can upload. Two of these are related to razer and Logitech and were detected by windows driver verifier. I temporarily solved the razer issue by using a different mouse but id rather that not be a long term solution if possible. As for the Logitech issue I had to stop using my headset which is definitely a problem and would rather not resort to that as well. I'm currently not using verifier because it was making my pc nearly unusable but if I have to re-enable it I will.

As for what I have tried up to this point:
  • I have run memory diagnostic tool with no errors.
  • Tried to run memory diagnostic tool in extended mode but it got stuck on 21% for about 2 hours and my pc became unresponsive. I had to turn it my pc off.
  • Ran Memtest86 with no errors.
  • Replaced Ram with brand new sticks.
  • Tried switching RAM slots on my motherboard from 1&3 to 2&4 but couldn't boot my PC without them being in 1&3.
  • Reset my PC a handful of times deleting all files and starting with a clean install of Windows.
  • I've run sfcscannow commands as well as chkdsk with no errors.

  • System Manufacturer? I would assume this is MSI? I have an MSI X570 Motherboard.
  • Laptop or Desktop? Desktop.
  • Exact model number (if laptop, check label on bottom) I am not sure what this is but my exact motherboard is an MSI X570 Gaming Plus.
  • OS ? (Windows 10, 8.1, 8, 7, Vista) Windows 10 Pro.
  • x86 (32bit) or x64 (64bit)? x64.
  • What was original installed OS on system? I really am not sure about this one, I built my PC in late 2019 so whatever the current Windows OS was then was likely what I had.
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? The OS is full retail version.
  • Age of system? (hardware) Approx. 2 years but some components are newer than that.
  • Age of OS installation? I would assume 2 years?
  • Have you re-installed the OS? Yes, multiple times.
  • CPU: Ryzen 5 3600
  • RAM (brand, EXACT model, what slots are you using?) Currently I'm using TEAMGROUP T-force Vulcan Z DDR4 3200MHz C16 8GBx2
  • Video Card: ASUS ROG STRIX RTX 2080 super
  • MotherBoard - (if NOT a laptop) MSI X570 Gaming Plus.
  • Power Supply - brand & wattage (if laptop, skip this one) EVGA 750 GQ
  • Is driver verifier enabled or disabled? currently disabled but it was recently enabled.
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) not using any third party software. I was using Malwarebytes for a while but haven't reinstalled in since resetting my pc.
  • Are you using proxy, vpn, ipfilters or similar software? no and I am not really certain what these are.
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) I don't believe I am no.
  • Are you currently under/overclocking? Are there overclocking software installed on your system? Not intentionally if I am. I did have a program installed before that was overclocking my system without me knowing but I uninstalled it.
This is my speccy link : http://speccy.piriform.com/results/kfhIOHCqaceco5z1GdprG3F

I would also like to add that when I go to run Windows Verifier and select drivers to test there are a few drivers that have "unknown" in both categories.
 
I thought I followed the instructions, did I miss something? I tried updating the drivers through device manager and it said I already had the best drivers. So, for now I disconnected the devices to avoid the BSOD since I'm running verifier now.
 
Rich (BB code): 
8: kd> lmvm logi_audio_surround
Browse full module list
start             end                 module name
fffff80b`d9290000 fffff80b`d929c000   logi_audio_surround T (no symbols)           
    Loaded symbol image file: logi_audio_surround.sys
    Image path: \SystemRoot\system32\drivers\logi_audio_surround.sys
    Image name: logi_audio_surround.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Feb 26 20:43:30 2021 (60395D72)
    CheckSum:         0001338A
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Rich (BB code): 
8: kd> lmvm RzDev_0078
Browse full module list
start             end                 module name
fffff80e`beec0000 fffff80e`beed0000   RzDev_0078 T (no symbols)           
    Loaded symbol image file: RzDev_0078.sys
    Image path: \SystemRoot\System32\drivers\RzDev_0078.sys
    Image name: RzDev_0078.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Aug 18 04:58:33 2020 (5F3B51E9)
    CheckSum:         0001AC10
    ImageSize:        00010000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

As you've correctly mentioned, the issue does appear to lie with the Logitech and Razer drivers. Interestingly, they both appear to crash for the same reason. I know some of the pool allocation APIs have changed, so I'm assuming the drivers weren't updated correctly to reflect that. They should hopefully be patched.
 
Alright so I went to Logitech's website>Support>Downloads and found a bunch of options. I went with Logitech G HUB because I think that's the most recent program. When I launched it I had a firmware update. I went ahead and updated it but it looks like there is still an "unknown" driver associated with logitech as logi_core_temp.sys when I run through the list of drives on Verifier. There are also others listed and I don't know what they are. Could these unknown drivers be causing the crashes? I'll post a screenshot for reference as well.


Driver Verifier Manager 6_4_2021 1_42_48 PM.png
 
It's probably an unsigned Logitech driver which would come bundled with the driver package.
 
There doesn't appear to be any new dump files? Have you run the file collection tool again?
 
jzyvoloski said:
Is this correct?
Click to expand...
Looks like it 👍

Rich (BB code): 
8: kd> lmvm logi_audio_surround
Browse full module list
start             end                 module name
fffff804`105f0000 fffff804`105fc000   logi_audio_surround T (no symbols)           
    Loaded symbol image file: logi_audio_surround.sys
    Image path: \SystemRoot\system32\drivers\logi_audio_surround.sys
    Image name: logi_audio_surround.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Feb 26 20:43:30 2021 (60395D72)
    CheckSum:         0001338A
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

It's the same driver as before and the exact same cause. If there is no driver updates available, then I would suggest either checking with an older driver, or preferably, removing the driver while you wait for the bug to be patched.
 
Unfortunately, there doesn't appear to be an update. I also tried Logitech's other software but I believe that was even worse as more than one error showed up on bluescreenviewer as opposed to the one before even though they actually have the same firmware. Assuming I can't find an old driver that works how do I go about removing this one? Will my headset still work without it or no?
 

Attachments

If you remove the driver then the headset should revert to a standard Windows driver, however, I can't gurantee all the non-standard features of the headset will work. I'll check the latest crash in a moment for you.
 
So I've actually done a few things to my computer since my last reply. I updated my bios to the latest version through the manufacturers website, changed RAM again, updated windows to the optional update and changed the way I was running verifier. Previously I was referencing a Microsoft wiki to run verifier but then realized it differed from what's recommended here. After running verifier with steps found in the posting instructions here I stopped having Logitech related crashes. But I'm still having crashes. Verifier usually runs for about 12 hours or so before crashing and BlueScreenView just shows ntoskrnl.exe as the reason. If I don't use verifier and instead just use my computer as normal(games, discord, etc.), they occur more frequently and sooner. I have newer and more relevant crash files. If you could look at these instead I would appreciate it. Thank you for your help thus far it is very appreciated.
 

Attachments

Hmm, seems to be a couple of different bugchecks. The latest one is the most useful. It appears that Malwarebytes may be causing some problems while monitoring your registry changes.

Are you on the latest version? If not, then I would suggest updating to the latest version.

Rich (BB code): 
8: kd> lmvm farflt
Browse full module list
start             end                 module name
fffff806`97d80000 fffff806`97dbb000   farflt   T (no symbols)           
    Loaded symbol image file: farflt.sys
    Image path: \SystemRoot\system32\DRIVERS\farflt.sys
    Image name: farflt.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Mar 15 18:03:59 2021 (604FA18F)
    CheckSum:         0003D919
    ImageSize:        0003B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Rich (BB code): 
8: kd> lmvm MbamChameleon
Browse full module list
start             end                 module name
fffff809`b9ac0000 fffff809`b9af8000   MbamChameleon T (no symbols)           
    Loaded symbol image file: MbamChameleon.sys
    Image path: \SystemRoot\System32\Drivers\MbamChameleon.sys
    Image name: MbamChameleon.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Mar 22 14:41:52 2021 (6058ACB0)
    CheckSum:         0004554C
    ImageSize:        00038000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Here's an example of some of the registry entries it was monitoring:

Rich (BB code): 
8: kd> !du ffffa5045be7be10
SOFTWARE\Wow6432Node\MSI\MSI Center\Component\Mystic Light\LED
 
Apparently there was an update. I just updated it. What exactly does monitoring registry entries mean? The program it was monitoring was MSI Center.
 
AV programs will monitor your file system and your registry to check for suspicious looking files or registry entries. Every time something is read or written to your disk, then Malwarebytes will check to see if it is malicious.

jzyvoloski said:
Apparently there was an update. I just updated it.
Click to expand...
That's good, please continue to use the system as you normally would for now.
 
I was able to use my pc normally for a while so there has been some improvement but I had another BSOD even after updating Malwarebytes. Is there any info from the most recent dump file that points toward a specific app or driver? I see mcupdate_authenticAMD in a lot of the recent crashes. If nothing points toward apps or drivers should I start to assume this is a hardware issue rather than a software issue?
 

Attachments

and not too long after the above reply I had two more crashes. My pc went black without an error code, booted up and then blue screened with fltmgr.sys
 

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

Back
Top