Experiencing exact same network related BSOD after changing parts

flowering · 03 Feb 2022

I was directed here from Toms hardware forums, linking my original post from there: Question - What is continuing to cause my BSOD issues? | Tom's Hardware Forum

A long time ago I started experiencing frequent blue screens. At that time I was using an x570 Gaming X motherboard, a different PSU, a couple of different SSDs, and different RAM. After putting up with them for a while I started digging into what could be their cause. I made multiple posts on Toms Hardware over months and months of troubleshooting and landed on my LAN driver being the issue. My motherboards site was not updated with the latest version of the driver so I went straight to the source, updated it - problem solved for a little bit. Blue screens persisted. I was transitioning to an SFF build and I knew that was coming with a new motherboard so I was just buying my time until the new build.

Around Christmas time I had my new build made. All parts carried over except for cooler, SSD's, and power supply. I kissed my BSOD's goodbye...for a couple of days. They came back stronger than ever. Exact same error codes cycling through, exact same programs were causing it (steam, chrome, discord) pointing me towards network drivers again. I confirmed this with my most recent post that I linked above. I thought it was so odd that I was getting repeat BSODs with a brand new/different motherboard (all drivers up to date dealing with the network).

My only two hunches are:
1. I am using a mesh network. Google fiber is plugged into the main modem and my computer was hard-lined into a 'node' which was basically repeating the signal and would allow me to plug ethernet into it even though it wasn't the main modem (using wifi on my computer right now). So somehow the mesh network is having issues with the LAN network

2. Old build was using G Skill 3200 (16Gb 8x2) new build I was using 3600 same sizes. I have discovered through the BIOS that the sticks part numbers are mislabeled - the sticker on both sticks of ram end with '16GVK' but in the BIOS it ends in '8GVK' which I understand means the RAM though sold as a pair is not technically a pair. It's worth noting that both pairs pass Memtest 86 but fail Karhu. I am now running with a single stick to test out possible crashes none so far but have only been on for an hour or so. Karhu does NOT fail when using one stick

Attaching logs to the post. Windows Version 21H2

- - - Updated - - -

Edit: I think there is potential that G.Skill labels their sticks as 16gb even though bios may read them as 8gb so I may not be looking at the RAM problem correctly - but I do think its curious that Karhu fails when testing both pairs.

axe0 · 03 Feb 2022

Those programs were probably mentioned because they are the processes named, but that merely means during the execution of those processes the problem was noticed. Doesn't mean it caused them. Therefore I don't suspect your network is causing problems, particularly when looking at the below code which indicates there are various different crashes. This typically implies a hardware problem where you may be looking at CPU, motherboard or RAM problems. In exceptional cases it could also be the PSU, but in my opinion this comes down to trial and error to see which part(s) could be causing problems. Ideally you want to use parts that are known good and so I would suggest that you replace one part at a time with a known good part and see if it crashes.

Code:

   2022-02-02T21:18:21.2770000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffcd8e6237ce60, 0x0000000000000000, 0xfffff805340ff00e, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: fac1b30e-75ca-435e-a536-58c4781d7a96.
   2022-02-02T12:50:14.0010000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000be (0xfffff80623540e21, 0x01000003cb0d5121, 0xfffff98024260fb0, 0x000000000000000b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 62bbf4ac-bb34-4263-820f-40b01153a1d3.
   2022-02-02T12:16:35.0140000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80208a0afd1, 0xffff9e0b5d50ff70, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 351abe51-daee-44e6-b4d7-cc384a0ec297.
   2022-02-01T11:35:17.9120000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffff80000000000, 0x0000000000000010, 0xfffff80000000000, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 87ff1e41-e44a-4cbe-a992-990f2dfb434d.
   2022-01-30T22:39:52.4220000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x0000000000000038, 0x0000000000000002, 0x0000000000000000, 0xfffff80029b355f0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 6c59ed56-2dc6-4bbd-a251-e3b6ad0fba1a.
   2022-01-30T21:43:05.3470000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000192 (0xffffc081caab70c0, 0xffffe632807c69c0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 12f5bb21-fbe3-4355-ba59-e58bf59489d3.
   2022-01-30T21:04:13.2080000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000157 (0xffff8e04fccb20c0, 0x0000000000000001, 0x0000000000000002, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 537d71dc-722d-438e-baf8-16eed6bf249a.
   2022-01-30T20:48:13.6880000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000162 (0xffffb603658a80c0, 0xfffff80356248338, 0x00000000ffffffff, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 9e03b02b-52bf-495b-a8f3-23538e54ad70.
   2022-01-30T13:37:42.0060000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8023e5f3e1e, 0xffff8b88381719d0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 1415b5ad-39de-4e19-89c4-0bb527e2d492.
   2022-01-30T13:33:09.7060000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffa985ad962dc0, 0x0000000000000000, 0xfffff804056ff00e, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 075c2ce6-ade5-4770-a91b-22d45c40aa1e.
   2022-01-30T00:21:53.3480000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000050, 0x0000000000000002, 0x0000000000000001, 0xfffff8024129aba9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: bc1b772a-a16d-40a6-8f78-e9943bd6d8ea.
   2022-01-29T23:46:35.2980000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000153 (0xffff8b8f942bf080, 0xffff8b8f942bf730, 0x0000000000000001, 0xffff8b8f837ed270). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 558b7139-e695-4c10-97eb-9900f92fea33.
   2022-01-29T23:37:21.5740000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80559a0d18d, 0xfffff00624f78d80, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 994e8302-1c5e-4afa-8380-78871c7c2a07.
   2022-01-29T23:18:16.0180000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80428086c93, 0xffffc001c5535920, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 27d5faed-af2e-4b4a-bb50-6bbe34d7935c.
   2022-01-29T23:14:20.9390000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80042b1cb42, 0xffffcd888cc36740, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 149e2295-4675-487e-ba66-2c883f8974f7.
   2022-01-29T23:12:07.1460000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000192 (0xffffb68492941040, 0xffffb6848299b050, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: f6f9bdec-c6b9-4127-b1fc-f75540511e91.
   2022-01-15T09:27:16.6690000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000192 (0xffff9a041664a080, 0xffff9a0414b1eb08, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 6fad334d-4e4d-47a0-b3ac-d5280c8a8cbc.
   2022-01-13T22:03:17.5950000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000192 (0xffffa88f3d5c9080, 0xffffa88f34bfe6b0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: bed0cb88-3193-4aea-835a-4fccdbf1a70a.
   2022-01-13T21:46:02.9500000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0xffffb881dbbb4920). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 38290d7d-cacb-41b3-b3cb-fad3055b080b.
   2022-01-13T20:04:37.1820000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8002fe733bb, 0xffff8188848ca6c8, 0xffff8188848c9f00). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c007b2b9-295e-414c-b0f1-a0cf94e61b59.
   2022-01-13T00:09:37.3450000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000044 (0xffffa881f7f157f0, 0x0000000000001232, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c3702878-9d0e-4856-81b4-faded3ecf847.
   2022-01-12T23:21:22.7890000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80508def57e, 0xffffd50dcce67620, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 0582fd55-e949-40b4-b05c-e06bb7b2ef1b.
   2022-01-12T22:58:51.0410000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xffffd00f36d34698, 0x00000000000000ff, 0x0000000000000000, 0xfffff80572522484). A dump was saved in: C:\Windows\Minidump\011222-8156-01.dmp. Report Id: e9033dd6-8084-4d4c-89ee-ca822a0dacd5.
   2022-01-12T17:20:27.8860000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x000000000000000d, 0xffffab0f8be99780, 0x00000000ffffe78b, 0xa10115ba0ad91509). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 50426751-b429-4ec8-bd5f-f3b8d74e58c1.
   2022-01-12T16:59:18.1830000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000e1 (0xfffff802642fb820, 0x0000000000000002, 0x0000000000000000, 0xffff948e23082828). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 4545bc65-2410-4965-a45f-31c80f9b1b9e.
   2022-01-12T16:50:38.4680000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000157 (0xffffd1073279c080, 0x0000000000000004, 0x0000000000000002, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 8709b3f5-7433-48f4-a8be-df2502a7a79b.
   2022-01-12T16:45:08.7360000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000192 (0xffff81857bee1080, 0xffffb28a7dd8db50, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 0b4d593e-3188-41bc-a4a0-78b070cc855e.
   2022-01-12T13:49:01.6560000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000001 (0x00007fff7ffecf14, 0x0000000000000000, 0x00000000ffff0000, 0xffff96811fdcdb80). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 55c7756f-2dda-4325-aa65-34b714fb5e6f.
   2022-01-12T13:28:48.3440000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8065a922484, 0xffffbd8a4b87f758, 0xffffbd8a4b87ef90). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 3e86d12f-91e7-47c5-bd96-ea5c8f91c935.
   2022-01-12T10:35:34.7880000Z		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff804350bf88f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: b06303e7-f327-4910-93db-c68e271074e1.

flowering · 03 Feb 2022

The issues have persisted from the old power supply to the new power supply, the same case for the motherboard. I am still suspect of the RAM and am looking into finding some modules that match the motherboard. If problems persist after that I will look at the processor. Processor is the last thing I want to try and replace right now especially since I will have no clue how to test if it's working.

Would running processor through a prime 95 test expose any potential issues?

zbook · 03 Feb 2022

The log findings are consistent with either incompatible or malfunctioning RAM.

Memtest86 was designed to test for malfunctioning RAM.
It was not designed to test for incompatible RAM.

1) Please open task manager > performance tab > memory > post an image into this thread

2) Run: Crucial System Scanner | Memory Upgrade Scanner | Crucial

3) When purchasing RAM:

a) Select RAM modules displayed on the Qualified Vendor List (QVL)

b) Purchase in pairs with matching SKU

c) Consider RAM manufacturers that guarantee compatibility

d) Consider RAM manufacturers that have lifetime warranties

flowering · 03 Feb 2022

I usually do my best to stick to the QVL list provided by my motherboard but I was having a really tricky time finding anything available checking Newegg and Microcenter in my area.

I was using a third pair G.Skill Trident Z Neo - Ram made for AMD systems but was running into blue screens still and my Karhu test was failing, so when I was looking at my two other pairs I figured I didn't need to keep it around.

Do you have any recommendations on RAM? I have heard the Crucial Ballistix is very compatible with most hardware & they do mention that they have 100% compatibility. I have attached the screenshot you requested.

zbook · 03 Feb 2022

Problems with Crucial RAM have been seen in the forums but it's hard to beat a guarantee.

The first step is to use QVL RAM.

If there are no more BSOD then that completes the troubleshooting.

If there are BSOD despite QVL RAM then it's process of elimination to get to a malfunctioning motherboard.

Most often it's the RAM so start there.

Also check the owner's manual to see whether there are recommended DIMM when using only one RAM module versus two RAM modules.

flowering · 03 Feb 2022

To be clear I am only using one stick right now because I am suspicious running both was causing issues. I have no clue if Karhu tests for incompatibility but I know that it doesn't fail when running a single stick.

Going to do my best and find some RAM from the QVL list on the motherboard website (surprisingly difficult) and move forward from there. Is it okay to trust a RAM manufacturer website if they tell you their RAM works for my specific motherboard? Like when running Crucial scanner and they suggest RAM for me.

zbook · 03 Feb 2022

They have a 45 day guarantee:

Crucial compatibility guarantee | Crucial.com

RAM Memory Installation Troubleshooting Tips | Crucial.com

RMA Start

axe0 · 03 Feb 2022

For CPU tests I have yet to see a test that can say a CPU is faulty 5 out of 10 times. I don't expect prime95, or any similar test, to find any possible issues with the CPU.

flowering · 05 Feb 2022

I picked up RAM that was suggested by Crucial after scanning my system and I ran into the same issues. When in BIOS I noticed it was flickering and after looking into this I suspect this is another suggestion that I am having hardware issues. The CPU is the next suspect I imagine.

While I was at the micro center I was able to chat with one of the guys whose opinion I respect there. He said the next place to consider is something is wrong with the memory controller, so still pointing at the CPU. Interesting that the triggers are so specific (network-related - booting up chrome, steam, discord, rarely mid gaming) - Karhu ram test is always pointing me at an error until I remove a single stick and run a single channel.

Any thoughts as to why switching to single-channel solves the problem?