Question Getting BSODs over and over again ?

[Limette]

Hello, everyone.

I have problems with my system since my build 2019.

BSODs with different error codes occur again and again. Sometimes daily or 1-2 days apart.

For example. IRQL NOT LESS OR EQUAL, KERNEL STACK LOCKED AT EXIT etc. pp.

My current system consists of the following components:


• Ryzen 3600
• MSI B450 Tomahawk MAX (latest Bios)
• Crucial Ballistix Sport LT 3200 (XMP 1 – 1.4v) or the crucials since christmas
• Nvidia GTX 1060
• 500W BeQuiet power supply

The RAM test was performed without results and even a fresh Windows installation 3 days ago did not help. I have already exchanged the Ram with a new set which is currently installed (Corsair Vengeance LPX 3200 16GB Kit) which was not a solution, because the problems are still there.
The chipset driver, the BIOS and all other drivers are up-to-date.

Maybe someone of you has the same system and could solve the problem ?

I have attached old dump files as well as the new ones after the reinstallation on Wednesday.

Old Dumpfiles from 2021: https://1drv.ms/u/s!AmInb2vWcioJcY2qMNvnfQbmsEk?e=Vsg5MQ
New Files from the last 3 days: https://1drv.ms/u/s!AmInb2vWcioJcq31j-HKW8lcAuk?e=3CLgh2


I would be happy to receive tips from you!

All the best from Germany!
Limette

 

[Limette]

I will borrow a long ethernet cable from a friend on the weekend. Do you mean the Chrome browser? It was actually always open when it crashed. . . . Maybe I should test Firefox.

 

[Colif]

chrome is the victim. Its really rare for programs to cause BSOD. Unless they have their own drivers, which chrome doesn't.

 

[Limette]

Hi @Colif

I finally had the opportunity to test everything with an Ethernet cable unfortunately this has not solved the problem. In the meantime, I had installed the system freshly on w11 (20th february) and loaded the current drivers including the right bios. The problem remains.

Initially I had it running for 4-5 days without a problem and it got worse since that. Currently i get 3-4 bsods a day. There is actually only the graphics card or its driver as a trigger for the problem left, right?

Here are the last 5 dumpfiles: https://www.dropbox.com/sh/xm5ef4e76wn0vid/AADyATFWoBSOs_HGdDWsuFNMa?dl=0

Thanks for your help so far!

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://jsfiddle.net/L4af5p0t/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	033122-8687-01.dmp (Mar 31 2022 - 07:49:29)
Bugcheck:	DRIVER_OVERRAN_STACK_BUFFER (F7)
Probably caused by:	memory_corruption (Process running at time of crash: Teams.exe)
Uptime:	0 Day(s), 4 Hour(s), 06 Min(s), and 23 Sec(s)

File information:	033122-8515-01.dmp (Mar 31 2022 - 03:42:27)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	memory_corruption (Process running at time of crash: lghub_agent.exe)
Uptime:	0 Day(s), 0 Hour(s), 11 Min(s), and 33 Sec(s)

File information:	033122-8421-01.dmp (Mar 31 2022 - 03:30:12)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 1 Hour(s), 37 Min(s), and 09 Sec(s)

File information:	033122-8296-01.dmp (Mar 30 2022 - 13:59:54)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:	*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by:	Unknown_Image (Process running at time of crash: https://www.google.com/search?q=)
Uptime:	0 Day(s), 0 Hour(s), 25 Min(s), and 33 Sec(s)

File information:	033022-8062-01.dmp (Mar 30 2022 - 13:26:22)
Bugcheck:	REFERENCE_BY_POINTER (18)
Probably caused by:	memory_corruption (Process running at time of crash: nvcontainer.exe)
Uptime:	0 Day(s), 0 Hour(s), 25 Min(s), and 47 Sec(s)

Comment: 3 new AMD Raid drivers showed up in these dumps.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

whats almost every victim got in common?
teams
lghub_agent
nvcontainer

LAN drivers, or at least, they all use internet.
But its unlikely to be drivers on 2 different installs. And you got same errors even using the WIFI card...

Ryzen 3600
• MSI B450 Tomahawk MAX (latest Bios)
• Crucial Ballistix Sport LT 3200 (XMP 1 – 1.4v) or the crucials since christmas
• Nvidia GTX 1060
• 500W BeQuiet power supply

did you take the WIFI card out?
raid drivers? did you install StoreMI?

passes Prime95
used 2 different types of ram
Did I ask what storage drives you have?

could be its the motherboard

 

[Limette]

I took the WIFI card out, its just a USB-Stick. I dont know where the raid drivers came from, im pretty sure havent installed the StoreMi. But when ive set up the system on w11 i installed somekind of new msi command center to check the RAM timings withougt going in to the bios. I currently have 3 active drives.

A Kingston SA2000M8/1000G M.2 from late december 2021 (Windows is installed on this drive)
A standard samsung 1tb ssd for everything work related (I think i bought it in 2020)
And a older HDD for Documents, Musics and other stuff.

 

[Colif]

try running this on Kingston drive - https://www.kingston.com/en/support/technical/ssdmanager
Samsung Magician - https://semiconductor.samsung.com/consumer-storage/support/tools/
should check hdd but as I don't know brand, can use crystaldiskinfo (blue buttons) - https://crystalmark.info/en/
don't have to do anything for crystaldiskinfo - its results will just show up, Magician has tests... not sure about Kingston

probably MSI center. I see MSI redesigned their website.
it includes live update and all the adjustments you mentioned - https://download.msi.com/archive/mnu_exe/mb/MSICENTERv1.2.pdf
if you not careful with those updaters sthey install things you don't want. Mostly utilities.

 

[Limette]

So looks like StoreMI was installed. Because all 3 tools couldnt read out the drive data. Ive just uninstalled and checked the drives. The Kingston is fine and needed a firmware update (which i just did) the Samsung and the toshiba are good as well according to crystal disc for the toshiba and samsung magician for the Samsung 860.

I made some screenshots and exportet the SMART Data from the Kingston-Tool: https://www.dropbox.com/sh/ojih607t6dsnsh8/AADzKN1HTmMDfITfLC_PNO3Ya?dl=0

 

[Colif]

that doesn't help... i am running out of places to look.

crash 1,2 & 5 have all the same operations in them. they all have server communications. I had to figure out what
RemoveW32TlsData might mean
tls is https://en.wikipedia.org/wiki/Transport_Layer_Security
which is network related again... so I wasn't mad. Just curious.

All 3 BSOD have same lines. its too much for me to ignore.


I am tired tonight but I will see if I can figure this out tomorrow. I will see if I can figure out more of the similarities.

I am starting to wonder if its CPU or Motherboard. I would be tempted to get PC looked at by repair store and see if they can figure it out. They might have spare hardware they can swap in to try parts.

do you have any problems if you don't use VPN?

 

[Limette]

NordVPN is just installed if i want to watch some british or american tv shows i wasnt using it while it crashed. The weird thing is that i got worse in september last year. All the years/months before ive only had a bsod once a week. But i havent changed anything in september.

 

[Colif]

i have had 2 bsod in 6 years, so once a week is one too many.

I would have asked for help at one a week.

A driver overran a stack-based buffer (or local variable) in a way that would have overwritten the function's return address and jumped back to an arbitrary address when the function returned. This is the classic "buffer overrun" hacking attack and the system has been brought down to prevent a malicious user from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the buffer overrun handlers and bugcheck call is the one that overran its local variable(s).
and so we did...

STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase
ffffb4b8c06bc7ef-ffffb4b8c06bc7f0 2 bytes - win32kbase!RemoveW32TlsData+1f
and it shows same line on 3 different errors... the other 2 just don't have any info on that line
error 4 is a little buggy itself, doesn't know what cause is.

its hardware of some kind. I just can't narrow down what. Its either CPU or Motherboard I think... CPU passes Prime. I have no tests for motherboards.
Its why we check everything else, and once I am at that stage I suggest a repair store as I don't like guessing.

You have run malwarebytes or similar to check for infections?

 

[Limette]

Good morning, ive just run malwarebytes without a result. Looks like i have to send in the motherboard to msi maybe there is still warranty on it.

 

[mdd1963]

Has the entire system been tested with RAM running at lower clock speeds, say, 2666 MHz for starters? (Not every 3000 series CPU was/is necessarily capable of /stable at 3200 MHz speeds, and, just because we tested 2 different kits does not rule a simple 'RAM will not work at 3200 MHz' issue, but, this does not mean the RAM itself is at fault)

Certainly, testing for stability at lower RAM speeds might then allay fears of worrying over 1 or more assorted driver packages, Norton, a particular WIn10 or 11 update, etc...

 

[Limette]

@mdd1963 ive had it running without an active xmp profile on 2400mhz the standard clock speed that my bios is giving the ram and had the same problems. Some guys suggested to give it more volts.

 

[Colif]

i found someone yesterday who is getting an error identical to your clock watchdog timeout, down to the actions PC was taking... and it struck me as too much of a coincidence.
Only similarity your PC's has is to theirs is Windows 11 and its an AMD CPU.

I might have to see if I can someone else to look at dumps - its a matter of finding him and I don't see any recent posts by him anyway so might take a while. I could just be seeing a pattern that doesn't exist.

 

[Colif]

So looking over all your crashes, some of them make me think its ram.

The RAM test was performed without results and even a fresh Windows installation 3 days ago did not help. I have already exchanged the Ram with a new set which is currently installed (Corsair Vengeance LPX 3200 16GB Kit) which was not a solution, because the problems are still there.

even though you did this
Its mainly because what its blaming keeps moving, it bounces between GPU or Internet

reference by pointer can be a ram error.

I would take PC to a repair store and ask them to work it out.
You tried 2 different types of ram and it still looks like a ram problem... I assume no bent pins? It might be the motherboard or CPU.

I can't locate the person I was going to ask. He hasn't been on other sites for a few months now.


there is one thing we haven't tried - https://forums.tomshardware.com/threads/driver-verifier-instructions.3686888/
it will check if it is a driver.

 

[Limette]

Ive done everything according to instructions and he caused a bsod right away. After that I went directly into the safe mode and have the first dumpfile backed up on a usb stick.

Of course, the system was then in the bootloop and I was able to save the system after several attempts via the safe mode. At the try there were of course still several BSODs because the driver verifier was still active.

That’s why I backed up the first dumpfile externally: https://www.dropbox.com/sh/obkbrijrd2h0gwf/AAAbtYYKiPM-AlFyMvkAyedUa?dl=0

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/eLdvx1pj/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	040422-5000-01.dmp (Apr 4 2022 - 10:36:59)
Bugcheck:	DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:	*** WARNING: Unable to verify timestamp for nordlwf.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 03 Sec(s)

Crashing driver:

Jul 08 2020

nordlwf.sys

NordVPN LightWeight Firewall driver (NordVPN)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

take nord off, see what it blames next

 

[Limette]

And here we have the next victims 😀 : https://www.dropbox.com/sh/7l63hvdmabgmm9k/AAD1qILvfCdPjX5-UaJUAuaka?dl=0

The interesting thing was that the bsod appeared when he allready booted on to the desktop. So he wasnt creating one while booting only after he finnished it. Thats the 2 files.

 

[gardenman]

I ran the new dump files through the debugger and got the following information: https://jsfiddle.net/x6yjaek9/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	040522-4859-01.dmp (Apr 5 2022 - 07:21:26)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 02 Sec(s)

File information:	040522-26296-01.dmp (Apr 5 2022 - 07:19:52)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 02 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

i was expecting driver verifer errors

is it still running?

both of those crashes mention HIDCLASS.sys. Its used for mice/keyboards/WIFI adapters among other things

obvious choices being

Sep 13 2021	logi_joy_bus_enum.sys	Logitech Joystick driver
Sep 13 2021	logi_joy_vir_hid.sys	Logitech Joystick driver
Sep 13 2021	logi_joy_xlcore.sys	Logitech Joystick driver

or

Jul 29 2019

rtwlanu.sys

Realtek WLAN USB NDIS Driver https://www.realtek.com/en/

Is this the card you had in before?

 

[Limette]

Its currently running and i havent had a bsod after i deactivated the driver verifier. Im going to test it a little bit and see what will happen. The Wifi-Card is currently running with the standard realtek driver so it should be the one you´ve mentioned.

 

[Colif]

could be nord was problem all along.
I don't want to jinx you (which I feel I do just typing posts like this)

 

[Limette]

Im here for a quick update. I havent had a BSOD since 5 Days. Today i got the first one since removing nordvpn. So my system ran for 5 Days without a problem. Maybe today i got the one i get every now and then. Maybe you can still see a pattern? Ive uploaded it here: https://www.dropbox.com/sh/obkbrijrd2h0gwf/AAAbtYYKiPM-AlFyMvkAyedUa?dl=0