[SOLVED] Help troubleshooting Daily BSOD

[maomaobear]

Hi all, been getting BSODs once or twice a week on my build for the last few months. Last week I upgraded my CPU cooler and cleaned out the PC and have been getting the BSODs more frequently, about once a day. And the temperature is down from 50-80C to 30-60C instead, which confuses me!

The BSOD can happen during gaming, or closing a Microsoft Word file, or it seems at any time almost. All the errors are different, from IRQL NOT LESS OR EQUAL, to MEMORY MANAGEMENT, to KERNEL FAILURE (or something).

I ran a Prime95 test and it passed the Small FFTs, but failed the Large FFTs with a "Rounding error". So I'm thinking it may be the memory. What's weird is that it always fails on one worker within 2-3 minutes, but then the test runs perfectly fine for the next hour or more. A couple times the crash even resulted in a no POST and I had to reseat the CMOS battery to get to the bios.

Down-clocking the memory from 3200mhz to 3133mhz (timings same) seems to reduce the issue of Prime95 rounding error. However, I still got crashes/BSODs.

I also re-installed windows and all the drivers, including running DDU and reinstalling graphics drivers from AMD. No luck.

Today I've down-clocked all the way to 2133mhz (same settings as if XMP was never enabled), and no crashes for a while just crashed while editing this post

It SEEMS like a memory problem to me, but before I get it RMAed, wondering if you guys could help shed light into the problem more. Could voltages be the cause, and if so which voltages should I increase? Could it be the motherboard DIMM slots, how would I test that if my motherboard manual specifically states to slot in RAM in a certain order/slots? Is it most definitely not a CPU issue?

How do I 100% confirm its the RAM so I don't RMA it and still have the issues?

Appreciate any help. PC Specs below.

Cheers,
Pin

MSI X570 Gaming Plus
AMD Ryzen 5 3600X - no overclock
2x 8GB Corsair Vengeance LPX DDR4 3200mhz
Sapphire Pulse Radeon 5700XT
EVGA Supernova G3 550
Windows 10 Pro

RAM Timings
16-20-20-20-38
Voltage Settings:
MEM VDDIO 1.35v
MEM VTT Auto
VDDCR SOC 1.1v
CLDO VDDP 0.9v
CLDO VDDG 1.1v

All other motherboard settings on auto (no PBO)

 

[Colif]

prime 95 rounding errors can be fixed by increasing voltage to CPU or memory

 

[maomaobear]

Hey Colif, thx for the heads up.

How would I increase voltage to CPU? Don't the Ryzen 5 CPUs automatically draw as much voltage as they want? I see my voltage numbers on CPU go all the way up to 1.43+ sometimes. Any resources on how to manually set the voltage? Ryzen master doesn't even have an option for it.

I also increased my memory voltage up to 1.4v but crash happened just the same.

Latest crash logs: https://drive.google.com/drive/folders/1wODaEBGauBf6CuNgHhbLH9BGCPxITTeC?usp=sharing

 

[maomaobear]

Update:

Moved RAM around to slots 1/3 from the recommended 2/4 (resulting in a warning but still booted) and ended in more BSOD. In this configuration the Prime95 Large FFTs test failed even faster and with multiple workers failing.

I am currently running with one stick of RAM in slot 4 only, initially at 1067mhz, and now at 1600mhz single channel. 6 hours now with no BSOD, fingers crossed. Once my USB dongle arrives I will also run memtest86 on my RAM sticks, individually and together, and also in various slots.

Wondering if I may have a problem with my chipset memory controller? If single-channel RAM alleviates the issue... very weird that my recent upgrade to a better CPU cooler would result in more frequent issues. More performance from cooling = more stress on memory controller?

Unfortunately its a 1-month diagnosis/replacement schedule from my motherboard seller... so I'm hoping its actually just a bad RAM instead. But how to identify bad RAM kit vs bad DIMM or bad memory controller?

 

[Colif]

memory controller is on the CPU, not motherboard

So I would check the cpu and make sure you don't have any bent pins. That might explain why swapping cooler made the difference

you would increase votages in the bios

its possible the cause is a bad CPU?

 

[maomaobear]

Haha, its on the CPU! I'm an idiot

I am currently running memtest86 on the RAM, first stick passed in slot 4, running the second stick right now. But yes, I'm beginning to suspect its the CPU as well. I've done a lot of googling and a lot of the people having intermittent BSOD issues and having trouble diagnosing, failing large FFT test but passing memory diagnostic/memtest86, etc. the common point is a Ryzen 3600 or 3600X. Could be a coincidence but I did see it fix one person's problem, and I PM'ed another user on here with very similar issues and they replied saying the CPU was indeed the issue.

Hoping its not the CPU, since getting it fixed will take a month also and I'll probably end up just buying a new one.

EDIT: BTW after memory tests whether all pass or I find errors I will definitely reseat the CPU which I have not done in like 2 years and take a good look while I'm at it... thx for the advice Colif

 

[Colif]

I have a 3600XT, not overly joyed to hear an error follows them around

 

[maomaobear]

So I ran two memtest86 tests with stick A and stick B in DIMM slot 4. Both passed. No BSODs using the computer for 2 days in both these configurations.

Then I ran a test wih stick A in DIMM slot 2 and stick B in DIMM slot 4. Also passed.

So maybe time to reassess. If it was a CPU memory controller or motherboard wouldn't the problem show up in memtest86 also?

Maybe I blew away some obstructing thing in one of the slots while doing these tests and the problem will be gone now. Will await the next BSOD...

 

[Colif]

Moved RAM around to slots 1/3 from the recommended 2/4 (resulting in a warning but still booted) and ended in more BSOD. In this configuration the Prime95 Large FFTs test failed even faster and with multiple workers failing.

that makes sense as there is a reason they recommend 2/4 for 2 sticks, its how its wired up. only meant to use 1/3 once you have more than 2 sticks. Not before

if it returns, run Prime again and if you get rounding errors still, I find out how to increase voltage on your board, or find someone who knows.

 

[maomaobear]

Updated BIOS, BSOD did in fact return with two sticks of memory in.

Now I've just done the following:

• Re-seated the CPU -- didn't see any bent pins while I was at it but honestly it would be hard for me to tell if one was slightly off
• Re-installed the cooler and didn't tighten it down as much
• Double-checked all power supply connections for full connectivity, obstructions
• Re-seated the RAM again, checked for obstructions
• Turned off "Eco Mode" for my PSU
• GPU - reversed power supply cable connection
• Unplugged an old HDD from roughly a decade ago (two SSDs left)

My main thinking here: PC has been running pretty much fine for two whole years. It did in fact BSOD, but it was like once every 2 months. It was only after installing a new cooler and cleaning the case that things seemed to get worse. And things got even more worse after re-applying thermal paste a second time for cooler (and tightening down). Possible ideas:

• CPU needed a re-seat after so long (never re-seated it since 2 years ago). I remember for one period of time the computer would turn off when I bumped into it. And that symptom is linked to a bad CPU/mobo connection
• Maybe the new, heavier cooler exacerbated this problem, and even moreso when I re-applied paste and tightened the springs all the way
• Possibly when cleaning (I re-installed everything) I messed up a connection somewhere in the power cables
• Possibly a GPU or PSU problem? Memory problem unlikely with memory test passing. CPU problem still possible due to increase in BSODs since upgrading cooler and Prime95 Large FFT fail (maybe it stresses memory controller more than memtest86 does)

So, after doing all this crap and booting, the BIOS reset to 2033mhz on the RAM and I noticed there were now two XMP profiles instead of one (both the same). Maybe it was just the BIOS update for this.

I'm also running a Prime95 Large FFTs test right now and no errors for 20 minutes, whereas before on XMP it would show an error every time at 2-3 minutes.

Can you imagine if it was re-seating the CPU that fixed everything? Would piss me off... but fingers crossed... would rather that then the whole RMA process!

 

[maomaobear]

A full day of use has passed without BSOD... may the all-father bless me with his thunder

 

[maomaobear]

Well, day and a half of use with no BSOD.

I have had, however, a couple browser tab crashes and also had a weird stutter while gaming. For about half a second the sound choked up and repeatedly rapidly like a drill. Had that before in some crashes leading to freeze needing manual PC reset.

Wondering if this is a milder symptom of the same underlying problem?

Today I checked my main 12v 5v 3.3v voltages under load during Prime95 test and they were rock solid. So pretty sure we can eliminate the PSU.

My voltages for the CPU are pretty high. They are very frequently over 1.43v, though mostly during idle or low-load times.

Maybe something to do with the Ryzen 3000 processor dynamically pulling power too fast? It was suggested for me to play around with something called Load Line Calibration... maybe I'll give that a shot?

 

[Colif]

Could see if newer sound drivers

Your votages are lower than mine - I have a 3600XT no OC so cpu are very similar.

I wouldn't worry about it. I have no reason to suspect my Seasonic PX 750 is doing anything wrong, so you are probably okay.
My CPU fan isn't a fan, its a pump. I wonder where it gets that speed from as AIO software shows a different speed... almost half what HWINFO sees

the spikes are from how Ryzen works. Ryzen CPU for most part leave cores asleep unless a process needs another, it will then wake it, boost it to speed it needs to be to carry out operation, and then it will put core back to sleep. that is why it spikes and temps are almost always changing unless you track CPU CCD1 (Tdie) as that temp ignores the constant spikes.

 

[maomaobear]

OK, in that case I will give it a couple days before updating the post and closing with solution.

Know its only 2 days in but feels amazing to have a PC that doesn't crash again.

 

[maomaobear]

The BSOD has returned. On day 4 I have booted up in the morning and immediately greeted with a BSOD after windows loaded.

Uploaded the latest dump file here: https://drive.google.com/file/d/1Ex7SgbRwpBwWY4oYBHROiwgEk_p_YUg8/view?usp=sharing

The failing files for BSOD were Ntfs.sys and ntoskrnl.exe

Checking the event log these warnings could be clues:

Kernel-PnP	The driver \Driver\WudfRd failed to load for the device HID\VID_B58E&PID_9E84&MI_03&Col02\a&293df4a1&0&0001.
storahci	Reset to device, \Device\RaidPort0, was issued.

Google says the WudfRd could be related to device drivers, especially USB. Trying to figure out what that ID is pointing to.

Analysis from Windbg of the dump below:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80025aee3dd, Address of the instruction which caused the BugCheck
Arg3: ffff8208d723d560, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2952

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 42435

    Key  : Analysis.Init.CPU.mSec
    Value: 312

    Key  : Analysis.Init.Elapsed.mSec
    Value: 282189

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 81


FILE_IN_CAB:  112021-7375-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80025aee3dd

BUGCHECK_P3: ffff8208d723d560

BUGCHECK_P4: 0

CONTEXT:  ffff8208d723d560 -- (.cxr 0xffff8208d723d560)
rax=00007ffddda18cf9 rbx=0000000000000005 rcx=587983483175d98b
rdx=00007ffddda18d91 rsi=0000000000000000 rdi=ffff8208d723e4c0
rip=fffff80025aee3dd rsp=ffff8208d723df68 rbp=0000000000000000
r8=ffffb80bac143620  r9=ffffe50717004760 r10=ffffb80bac143740
r11=ffffe50717004760 r12=000000000000ffff r13=0000000000000200
r14=ffffe50717004760 r15=0000000000000400
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
Ntfs!NtfsIsFileStillValid+0x4d:
fffff800`25aee3dd 8b4918          mov     ecx,dword ptr [rcx+18h] ds:002b:58798348`3175d9a3=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  mongod.exe

STACK_TEXT:
ffff8208`d723df68 fffff800`25af2a21     : 00000000`00000000 00000000`00000005 ffff8208`d723e000 00000000`00000005 : Ntfs!NtfsIsFileStillValid+0x4d
ffff8208`d723df70 fffff800`25ae53ed     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8208`d723e490 : Ntfs!NtfsCommonCleanup+0x4631
ffff8208`d723e420 fffff800`2108f6f5     : ffffe507`090c4a20 fffff800`1f8d48e6 ffffe507`12eb7a20 ffffe506`fa615d60 : Ntfs!NtfsFsdCleanup+0x1bd
ffff8208`d723e770 fffff800`1f8d6c5f     : ffffe507`170047f8 00000000`00000101 ffffe507`12eb7a01 ffffe507`090c4a20 : nt!IofCallDriver+0x55
ffff8208`d723e7b0 fffff800`1f8d4673     : ffff8208`d723e840 00000000`00000000 00000000`00000000 ffffe507`064650c0 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffff8208`d723e820 fffff800`2108f6f5     : ffffe507`17004760 fffff800`2108fc0d 00000000`00000000 00000000`00000204 : FLTMGR!FltpDispatch+0xa3
ffff8208`d723e880 fffff800`21475eba     : 00000000`00000001 ffffe507`17004760 00000000`00000000 00000000`00043042 : nt!IofCallDriver+0x55
ffff8208`d723e8c0 fffff800`213f39cf     : ffffe507`064650c0 00000000`00000001 ffffb80b`00000000 ffffe507`17004730 : nt!IopCloseFile+0x17a
ffff8208`d723e950 fffff800`213f79ac     : 00000000`000006ac 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObCloseHandleTableEntry+0x51f
ffff8208`d723ea90 fffff800`21208cb8     : 0000020c`5f769600 ffffe507`00000000 ffff8208`d723eb80 ffffe507`0850e5b0 : nt!NtClose+0xec
ffff8208`d723eb00 00007ffd`ddc0cf54     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000007e`67cff418 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`ddc0cf54


SYMBOL_NAME:  Ntfs!NtfsIsFileStillValid+4d

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr 0xffff8208d723d560 ; kb

BUCKET_ID_FUNC_OFFSET:  4d

FAILURE_BUCKET_ID:  0x3B_c0000005_Ntfs!NtfsIsFileStillValid

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c8f14e71-de7c-e06b-b180-d151ba2a0322}

Followup:     MachineOwner
---------

 

[maomaobear]

Ideas:

Looks like the PROCESS_NAME from the analysis was mongod.exe. Could it be the mongo db service? Uninstalling that just in case...

It seems that HID\VID_B58E&PID_9E84&MI_03&Col02 is pointing to my Blue Yeti USB microphone. I got this a month ago... it may coincide with when I started getting more BSODs. However I did test unplugging it previously and got BSOD before. There was a windows update a couple nights ago which could be the culprit. This microphone also uses Windows drivers and doesn't have its own drivers from the manufacturer.

This is the first time I've BSODed right after startup. Since it has been 4 days and not 4 hours since last BSOD, my last efforts must have done something. Perhaps this is a different problem? Or a less frequent version of the same problem?

Other USB devices that I have not really accounted for yet in testing:

• My Logitech M320 wireless mouse
• My Logitech K120 keyboard

Since it was an ntfs.sys crash, I checked my Samsung Magician. Looks like firmware is up-to-date and both drives are "healthy" (850 evo and 860 evo drives)

I've updated every driver from my X570 Gaming Plus motherboard from this page: https://www.msi.com/Motherboard/support/MPG-X570-GAMING-PLUS#down-driver&Win10 64 But I did re-install windows so maybe I need to update again? (Was an in-place upgrade)

 

[Colif]

The process named was the victim, not cause. its what PC was running at time it crashed.

error stack makes me think its a driver to blame

not sure if inplace upgrade changes drivers.

I just upgraded my chipset drivers tonight - https://www.amd.com/en/support/chipsets/amd-socket-am4/x570

what samsung drive do you have? if its an nvme, should use the samsung nvme drivers.

if you want to check driver versions, the dumps will show at least the dates of the drivers, if you want more
download and run Driverview - http://www.nirsoft.net/utils/driverview.html

All it does is looks at drivers installed; it won't install any (this is intentional as 3rd party driver updaters often get it wrong)

When you run it, go into view tab and set it to hide all Microsoft drivers, will make list shorter.

Now its up to you, you can look through the drivers and try to find old drivers, or you can take a screenshot from (and including)Driver name to (and including)Creation date.

upload it to an image sharing website and show link here

All I would do is look at driver versions (or dates if you lucky to have any) to see what might have newer versions.

 

[maomaobear]

Here's the driver list. I've uninstalled the Netease_UU_TAP device and drivers which seem to be the only ones that are old. Only other one is the SteamStreamingSpeakers one.

Full day's use of the PC with no BSODs btw. Maybe it is indeed a different problem than the one I started the thread with.

Earlier, other than uninstalling the victim process, I also ran a SFC and CHKDSK. The SFC didn't pick up anything and the CHKDSK didn't show any bad sectors.

View: https://i.imgur.com/KkzHnP7.png

 

[Colif]

wonder what used Netease.
clearly you only get the steam streaming stuff if you actually stream. I don't recall seeing them crash before.

WudfRd

Windows driver framework is a set of tools for making drivers = https://en.wikipedia.org/wiki/Windows_Driver_Frameworks

HID\VID_B58E&PID_9E84

HID - Human Interface device.
rest of code? Its some sort of USB composite device

do you have a microphone? Blue Yeti?

 

[maomaobear]

The Netease drivers were for a Chinese VPN called UU.

Yes I do have a Blue Yeti!!!

 

[maomaobear]

And another BSOD. Went for lunch and returned to the blue screen.
Dump here: https://drive.google.com/file/d/1KvDMUqETJJ5XaCot9rGy5tARYZPOItvb/view?usp=sharing

Error this time was PAGE_FAULT_IN_NONPAGED_AREA and again ntfs.sys

Don't see any errors or warnings pre-crash this time in the Event Viewer

WinDbg analysis:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff8c8f184ffff8, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff8044352a7e8, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 2546

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 4561

    Key  : Analysis.Init.CPU.mSec
    Value: 327

    Key  : Analysis.Init.Elapsed.mSec
    Value: 50975

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 80


FILE_IN_CAB:  112121-11078-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  50

BUGCHECK_P1: ffff8c8f184ffff8

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8044352a7e8

BUGCHECK_P4: 0

READ_ADDRESS: fffff80440cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffff8c8f184ffff8

MM_INTERNAL_CODE:  0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  ffff8502b2b5ad60 -- (.trap 0xffff8502b2b5ad60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff8c8f18380000 rbx=0000000000000000 rcx=000000000000ffff
rdx=000000000002fffd rsi=0000000000000000 rdi=0000000000000000
rip=fffff8044352a7e8 rsp=ffff8502b2b5aef0 rbp=0000000000009218
r8=000000000001a4c4  r9=0000000000001087 r10=ffff8c8ef33cabf4
r11=ffff8c8f1b2fb5d2 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
Ntfs!NtfsInsertCachedLcnAtIndex+0x288:
fffff804`4352a7e8 66440164d010    add     word ptr [rax+rdx*8+10h],r12w ds:ffff8c8f`184ffff8=????
Resetting default scope

STACK_TEXT:
ffff8502`b2b5aab8 fffff804`4044a81f     : 00000000`00000050 ffff8c8f`184ffff8 00000000`00000002 ffff8502`b2b5ad60 : nt!KeBugCheckEx
ffff8502`b2b5aac0 fffff804`4029f390     : ffffa081`7575d9f8 00000000`00000002 ffff8502`b2b5ade0 00000000`00000000 : nt!MiSystemFault+0x18d46f
ffff8502`b2b5abc0 fffff804`4040545e     : ffff8502`b2b5b120 00000000`00000090 00000000`00000000 ffffa081`73010000 : nt!MmAccessFault+0x400
ffff8502`b2b5ad60 fffff804`4352a7e8     : ffff8c8e`f33a3c78 00000000`00009218 00000000`0000e2e9 ffff8c8e`f33967c4 : nt!KiPageFault+0x35e
ffff8502`b2b5aef0 fffff804`43440678     : 00000000`00f30bb3 ffff8c8e`f33a3c78 00000000`00000345 00000000`00000000 : Ntfs!NtfsInsertCachedLcnAtIndex+0x288
ffff8502`b2b5af60 fffff804`43421ad0     : ffff8c8e`f33a3c28 00000000`00000100 ffffa081`75b99218 00000000`00000448 : Ntfs!NtfsRemoveCachedLcn+0x1eb88
ffff8502`b2b5afe0 fffff804`43525a88     : ffffa081`840c8018 ffff8c8e`00000000 ffff8c8e`f33a3c28 00000000`00000000 : Ntfs!NtfsRemoveCachedRunInTier+0x50
ffff8502`b2b5b080 fffff804`434152c1     : 00000000`00000100 ffffa081`840c8018 ffffa081`7575d180 00000000`00f30ab3 : Ntfs!NtfsRemoveCachedRun+0xb0
ffff8502`b2b5b100 fffff804`435257eb     : ffffa081`840c8018 00000000`00f30bb3 00000000`00000000 00000000`00000000 : Ntfs!NtfsProtectClusters+0x65
ffff8502`b2b5b130 fffff804`43529ab9     : ffffa081`840c8018 00000000`00000100 ffffa081`840c8018 00000000`00000100 : Ntfs!NtfsAddDelayedAllocation+0xd3
ffff8502`b2b5b1a0 fffff804`434cd160     : 00000000`00000100 00000000`00000004 ffffa081`840c8018 ffff8c8f`1a341050 : Ntfs!NtfsPreAllocateClusters+0x139
ffff8502`b2b5b1f0 fffff804`434cc4c7     : ffffa081`755addd0 ffff8502`b2b5b558 ffffa081`7fc48138 ffff8502`b2b5b598 : Ntfs!NtfsDefragFileInternal+0xc1c
ffff8502`b2b5b4b0 fffff804`43532596     : ffff8502`00000000 ffffa081`8ef55c70 ffff8c8f`1a1e95a0 ffffa081`7575d180 : Ntfs!NtfsDefragFile+0x203
ffff8502`b2b5b550 fffff804`4353208d     : ffffa081`840c8018 00000000`00000001 00000000`00000000 00000000`00000008 : Ntfs!NtfsUserFsRequest+0x1e6
ffff8502`b2b5b5d0 fffff804`4028f6f5     : ffffa081`7fc48050 fffff804`3d2948e6 ffffa081`80b5b5e0 ffff8502`b2b56000 : Ntfs!NtfsFsdFileSystemControl+0x17d
ffff8502`b2b5b6f0 fffff804`3d296c5f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffff8502`b2b5b730 fffff804`3d2cd1a4     : ffff8502`b2b5b7c0 00000000`00000000 00000000`000000e0 fffff804`405f5f01 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffff8502`b2b5b7a0 fffff804`4028f6f5     : 00000000`0000000a ffffa081`80b5b5e0 00000000`00000002 00000000`00000001 : FLTMGR!FltpFsControl+0x104
ffff8502`b2b5b800 fffff804`40675a68     : ffff8502`b2b5bb80 ffffa081`80b5b5e0 00000000`00000001 ffffa081`83b88080 : nt!IofCallDriver+0x55
ffff8502`b2b5b840 fffff804`40675335     : 00000000`00090074 ffff8502`b2b5bb80 00000000`00000005 ffff8502`b2b5bb80 : nt!IopSynchronousServiceTail+0x1a8
ffff8502`b2b5b8e0 fffff804`406e2ce6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5e5
ffff8502`b2b5ba20 fffff804`40408cb8     : 00000000`00000230 0000022b`1536eb60 fffff804`40cf3980 fffff804`3bdbe180 : nt!NtFsControlFile+0x56
ffff8502`b2b5ba90 00007ffc`778cd494     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000b8`e8efde98 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`778cd494


SYMBOL_NAME:  Ntfs!NtfsInsertCachedLcnAtIndex+288

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  288

FAILURE_BUCKET_ID:  AV_W_(null)_Ntfs!NtfsInsertCachedLcnAtIndex

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f9551961-6fa5-d64e-df45-66481d28499d}

Followup:     MachineOwner
---------

 

[maomaobear]

I've bumped up CPU voltage with the minimum offset (+0.0125v)

Ran Prime95 again with no errors (though there were no errors last time either). Funny thing is that setting a + offset to voltage reduced the minimum voltage dramatically. Temperature has increased a few degrees but nothing problematic.

Will report back if this solves the problem.

 

[maomaobear]

Another BSOD, dump here: https://drive.google.com/file/d/1Ix1lQgKq7EM8oj444qH6NY00ytfaUwJF/view?usp=sharing

Resetting the voltage on CPU, will try turning off SMT as the next experiment.

EDIT: And a second BSOD 30 minutes later. Very similar to the last pattern of BSOD I experienced: one a minute after startup, and a second shortly after.

What I'm having trouble wrapping my head around is why these problems started happening after a change in the CPU cooler. Is it worth trying to reinstall the stock cooler? Seems kind of like an insane thing to do.

 

[Colif]

some indication this is a virus

Nov 29 2017

WeGameDriver764.sys

I would run an anti virus scan if you don't know what it is.

I am not sure what these are

Jun 30 2021	ACE-BASE.sys
Jun 30 2021	ACE-GAME.sys

Seems they part of Expert Anti cheat

latest dump mentions npfs.sys, just to be different. Its Named Pipe FIle system, its used for networking
Download Win10/Win11 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

 

[maomaobear]

I opened up my computer earlier to adjust the CPU cooler pressure. Closed up everything. Since then, I've had 4 BSODs!!

It has gotta be hardware-related and something to do with a bad connection somewhere.

When I went to pull out the displayport cable on my second monitor, the cable just came apart!! Any chance a bad displayport cable could cause a BSOD???? Sounds unlikely... Currently running on one monitor with the other cable.

WeGame is like Steam in China, run by Tencent. The Anti-Cheat stuff is packaged with it I believe. Maybe I can try uninstalling those and seeing if it helps.

some indication this is a virus
Nov 29 2017WeGameDriver764.sys I would run an anti virus scan if you don't know what it is.