BSOD issues on PC for a couple of Months | PCSPECIALIST

BSOD issues on PC for a couple of Months

Hi all

I have been having BDOS issues with my computer not long after I got it for a gift around Christmas time. These issues include SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, KERNEL_DATA_INPAGE_ERROR, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, and MEMORY MANAGEMENT. I have tried updating my drivers, ran a full virus check and a memory check but nothing has come up wrong. Any thought on what i can do to fix the issues?

Specs

OS Name: Microsoft Windows 10 Home
Version: 10.0.19041 Build 19041
Other OS Description: Not Available
OS Manufacturer: Microsoft Corporation
System Name: DESKTOP-8JBPD9A
System Manufacturer: PC Specialist LTD
System Model: Amd Sff Gaming
System Type: x64-based PC
System SKU: 1872719
Processor: AMD Ryzen 3 3100 4-Core Processor, 3593 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date: American Megatrends Inc. F51d PI, 01/06/2020
SMBIOS Version: 3.2
Embedded Controller Version: 255.255
BIOS Mode: UEFI
BaseBoard Manufacturer: Gigabyte Technology Co., Ltd.
BaseBoard Product: B450 I AORUS PRO WIFI-CF
BaseBoard Version: x.x
Platform Role: Desktop
Secure Boot State: Off
PCR7 Configuration: Binding Not Possible
Windows Directory: C:\windows
System Directory: C:\windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.19041.488"
Username DESKTOP-8JBPD9A\james
Time Zone GMT Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 9.66 GB
Total Virtual Memory 19.8 GB
Available Virtual Memory 10.6 GB
Page File Space 3.88 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware No
Hyper-V - Data Execution Protection Yes
 
Yeah sorry about the lack of specs, I didn't order the pc so it's not my account with the info on it. Thanks for the link to the post. I think I have compiled some of the information mentioned in the post and I'll link them below if that's any help.

Application File: https://drive.google.com/file/d/1QiQWjSb-3sJRJaDKg8uZv5O9CaLig9qM/view?usp=sharing
System File: https://drive.google.com/file/d/1oOt1PoOh2-6sZJPhtM7MQAu_kzOysdir/view?usp=sharing
Memory Dump file: https://drive.google.com/file/d/1OZ7Fq0OH8YwYK_40lHybb8GzvMrIEHDz/view?usp=sharing
 

ubuysa

The BSOD Doctor
Moderator
Yeah sorry about the lack of specs, I didn't order the pc so it's not my account with the info on it. Thanks for the link to the post. I think I have compiled some of the information mentioned in the post and I'll link them below if that's any help.

Application File: https://drive.google.com/file/d/1QiQWjSb-3sJRJaDKg8uZv5O9CaLig9qM/view?usp=sharing
System File: https://drive.google.com/file/d/1oOt1PoOh2-6sZJPhtM7MQAu_kzOysdir/view?usp=sharing
Memory Dump file: https://drive.google.com/file/d/1OZ7Fq0OH8YwYK_40lHybb8GzvMrIEHDz/view?usp=sharing
We don't have the full specification and that's a BIG problem. How many RAM sticks do you have (two or four) and what speed is your RAM? I ask because this error in your System log suggests that you're experiencing the known problem of having four (or sometimes just two) RAM sticks in an AMD build. The kernel dump tells a much simpler story however, but this potential AMD/RAM issue is something to bear in mind.....

Clipboard01.jpg


The kernel dump has a stop code of CRITICAL_STRUCTURE_CORRUPTION with an exception code indicating a function modification - that's typically a driver failure.

The active thread stack trace is the shortest I've ever seen, it just shows an immediate bug check as soon as the kernel is called - that has to be a driver error.

In the list of driver calls for the active thread is this (very common) error:

Code:
ffffd400`4f8f79e8  fffff804`87670fa9 Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_272b5c540127d6d2\nvlddmkm.sys, Win32 error 0n2
nvlddmkm+0x1c0fa9

The nvlddmkm.sys driver is the Nvidia graphics driver and this is a common source of problems. Even more common is a known conflict between the Nvidia audio driver and the Realtek audio driver. In your kernel dump I can see the drivers nvhda64v.sys and nvvad64v.sys loaded. These are the Nvidia audio drivers (the first is the HDMI audio driver and the second the virtual audio driver). You also have RTKVHD64.sys loaded an that's the regular Realtek audio driver, so I'm pretty confident that you're seeing the known audio driver conflict issue.

Uninstall the Nvidia graphics driver with DDU (see https://www.pcspecialist.co.uk/foru...aller-to-fully-remove-graphics-drivers.79324/) and then reinstall the latest Nvidia graphics driver being careful to NOT select any audio components.
 
We don't have the full specification and that's a BIG problem. How many RAM sticks do you have (two or four) and what speed is your RAM? I ask because this error in your System log suggests that you're experiencing the known problem of having four (or sometimes just two) RAM sticks in an AMD build. The kernel dump tells a much simpler story however, but this potential AMD/RAM issue is something to bear in mind.....

View attachment 23289

The kernel dump has a stop code of CRITICAL_STRUCTURE_CORRUPTION with an exception code indicating a function modification - that's typically a driver failure.

The active thread stack trace is the shortest I've ever seen, it just shows an immediate bug check as soon as the kernel is called - that has to be a driver error.

In the list of driver calls for the active thread is this (very common) error:

Code:
ffffd400`4f8f79e8  fffff804`87670fa9 Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_272b5c540127d6d2\nvlddmkm.sys, Win32 error 0n2
nvlddmkm+0x1c0fa9

The nvlddmkm.sys driver is the Nvidia graphics driver and this is a common source of problems. Even more common is a known conflict between the Nvidia audio driver and the Realtek audio driver. In your kernel dump I can see the drivers nvhda64v.sys and nvvad64v.sys loaded. These are the Nvidia audio drivers (the first is the HDMI audio driver and the second the virtual audio driver). You also have RTKVHD64.sys loaded an that's the regular Realtek audio driver, so I'm pretty confident that you're seeing the known audio driver conflict issue.

Uninstall the Nvidia graphics driver with DDU (see https://www.pcspecialist.co.uk/foru...aller-to-fully-remove-graphics-drivers.79324/) and then reinstall the latest Nvidia graphics driver being careful to NOT select any audio components.

Hi

I managed to get hold of my specs and ill post them below. I did what you recommended and reinstalled my Nvidia driver expect for the audio drivers. However I have had a BDOS issues happen again since (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED). If you think it will helpful I can send the new memory dump info.

1615659684388.png 1615659702481.png1615659721338.png1615659745327.png1615659764315.png1615659784524.png
 

ubuysa

The BSOD Doctor
Moderator
Thanks for the specs. Please upload the dump.

You might also remove your graphics card and reseat it fully. Stuff does sometimes move in transit.
 

ubuysa

The BSOD Doctor
Moderator
The BSOD stop code here is a common one; SYSTEM_THREAD_EXCEPTION_NOT_HANDLED with an exception code of a memory access violation. These types of BSOD are common and are always caused by a driver screwing up its buffer allocations or pointers. In this case the driver tried to read from address 0xffffffff ffffffff - a clearly invalid address.

There is no obvious error in the active thread driver list for this exception because the error wasn't caught until the kernel attempted to process the data and parameters returned by the driver. The key to the driver that caused this is in the stack trace for the active thread. Here is a small part of the stack trace showing just the system function calls......
Code:
nt!HalPutDmaAdapter+0xe
nt!PsDereferenceImpersonationToken+0xe
avgntflt+0x23f5e
FLTMGR!DoReleaseContext+0x82
FLTMGR!FltpDeleteContextList+0xc1

You read a stack trace from the bottom up (it's a push-down or LIFO stack). The FLTMGR calls are the Filter Manager (a Windows filter driver) and the nt! calls are kernel functions. In between them, and immediately after the Filter Manager, is a calls to avgntflt.sys - and this is a filter driver for the Avria Antivirus product.

This BSOD was caused by Avira Antivirus. This is far from the first time I've seen a BSOD caused by a third-party anti-malware product and TBH I don't know why people pay for tools that cause BSODs. Windows Defender is all you need these days - and it's free!
 
Update on the status of my BDOS's. Think that getting rid of my anti virus has helped reduce the number of Blue screens I'm getting but I did get another a few days ago. This time a memory management BDOS, I'll post the dump file if your interested in looking over it.

File Link: https://drive.google.com/file/d/1Qp_jQLk38uYZJy_adb4tonJOPsRMymoj/view?usp=sharing

Cheers for all the help so far btw I realise it's not that fun trouble shooting this stuff and I do appreciate it.
 

ubuysa

The BSOD Doctor
Moderator
Cheers for all the help so far btw I realise it's not that fun trouble shooting this stuff and I do appreciate it.
Are you kidding?! I love delving into a dump - memory ones of course... :poop:

It's downloading now but I might not get to it until tomorrow (we're 2 hours ahead of the UK here).
 

ubuysa

The BSOD Doctor
Moderator
I've looked at your kernel dump and I've seen this exact same set of circumstances before, and only a few weeks ago. I'm pretty sure that you have a RAM issue. The previous user had PCS swap his RAM and the issue was solved. (The previous thread is here for anyone interested).

It's actually quite scary how similar the two dumps are, both systems failed in exactly the same way; when cleaning up an address space after the process was closed. The bug check happened during the delete address space function call - nt!MiDeleteVa and at the same offset - 0x153a. I did at first think they were the same dump! They're not though, the owning process is different (ctfmon.exe in your case, chrome.exe in the other dump). Interestingly too, yours is an AMD system and the other one is an Intel system. You don't have the exact same RAM either - yours is Corsair Vengeance 3200MHz (2 x 8GB) and the other is Corsair Vengeance RGB Pro 3200MHz (2 x 8GB).

I'm quite amazed that two such different systems would fail in the exact same way. The other system definitely was fixed by swapping the RAM so I'd suggest you download Memtest, extract the tool from the downloaded archive, use the tool to make a bootable USB stick and then boot that USB stick. Memtest will start running. Let it run until it's completed all four iterations of the 13 tests. If it generates no errors run it again.

Lets see whether that finds any RAM problems. Even if it doesn't I'd suggest you contact PCS, point them to this thread and the previous one (and especially both kernel dumps) and ask them to swap your RAM. Be sure to keep the dump file safe somewhere, if you need to contact PCS they may want to see it. (I have them both in any case).
 
Last edited:
Top