Hey, can anyone help me check out this BSOD error message? I need some advice on how to fix it right now.
Hey, can anyone help me check out this BSOD error message? I need some advice on how to fix it right now.
Im a video editor and since a while back pc started to blue screen randomly when exporting or doing heavier task but the dask depends on the program mostly in Resolve and Premier Pro. I built the pc myself and recently upgraded the cpu il link the dump file and system specs. I tried meem test stress testing the gpu and cpu without a problem or a crash but when editing it does it every time I also have a fresh Win11 installed.(MB bios up to date for the newer cpu) I have been struggling with this fdor months now using laptop for heavier tasks but its affecting my work hopefully somebody can give me a hand or have an idea about what could be wrong Processor AMD Ryzen 9 5950X 16-Core Processor 3.40 GHz Installed RAM 32.0 GB x470- f Asus motherboard 1080 ti gigabyte aurous water cooled with aio windbg file link @weetransfer ******************************************************************************* * * * 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: ffff9a85a27cd250, memory referenced. Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE. bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the processor decided the fault was due to a corrupted PTE. bit 4 is set if the fault was due to attempted execute of a no-execute PTE. - ARM64: bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the fault was due to attempted execute of a no-execute PTE. Arg3: fffff80038cc882e, 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: 1765 Key : Analysis.Elapsed.mSec Value: 5108 Key : Analysis.IO.Other.Mb Value: 11 Key : Analysis.IO.Read.Mb Value: 17 Key : Analysis.IO.Write.Mb Value: 52 Key : Analysis.Init.CPU.mSec Value: 249 Key : Analysis.Init.Elapsed.mSec Value: 24337 Key : Analysis.Memory.CommitPeak.Mb Value: 103 Key : Bugcheck.Code.LegacyAPI Value: 0x50 Key : Dump.Attributes.AsUlong Value: 1008 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: AV_W_(null)_Ntfs!NtfsGrowLengthInCachedLcn Key : Failure.Hash Value: {6cf3e289-3ff4-490f-2157-adefe365446e} BUGCHECK_CODE: 50 BUGCHECK_P1: ffff9a85a27cd250 BUGCHECK_P2: 2 BUGCHECK_P3: fffff80038cc882e BUGCHECK_P4: 0 FILE_IN_CAB: 112123-12281-01.dmp DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump READ_ADDRESS: fffff8003431d470: 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 ffff9a85a27cd250 MM_INTERNAL_CODE: 0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: fffffe8c005d6bd0 -- (.trap 0xfffffe8c005d6bd0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffff9a85a2680000 rbx=0000000000000000 rcx=0000000000029a48 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80038cc882e rsp=fffffe8c005d6d60 rbp=fffffe8c005d6d98 r8=000000000000de18 r9=0000000000000000 r10=0000000000008b6b r11=ffff9a85bc4b0056 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac pe cy Ntfs!NtfsGrowLengthInCachedLcn+0x132: fffff800`38cc882e 66448954c810 mov word ptr [rax+rcx*8+10h],r10w ds:ffff9a85`a27cd250=???? Resetting default scope STACK_TEXT: fffffe8c`005d69a8 fffff800`33a8c442 : 00000000`00000050 ffff9a85`a27cd250 00000000`00000002 fffffe8c`005d6bd0 : nt!KeBugCheckEx fffffe8c`005d69b0 fffff800`33862d8c : fffffe8c`005d6b49 00000000`00000002 00000000`00000000 ffff9a85`a27cd250 : nt!MiSystemFault+0x1fd1f2 fffffe8c`005d6ab0 fffff800`33a27529 : fffff800`3150b180 00001f80`008600c4 00000000`0000ffff ffff9a85`a2738b80 : nt!MmAccessFault+0x29c fffffe8c`005d6bd0 fffff800`38cc882e : ffff9a85`bc49b000 00000000`00000015 ffff9a85`a271dc80 fffffe8c`005d6de0 : nt!KiPageFault+0x369 fffffe8c`005d6d60 fffff800`38bb95a0 : 00000000`000082c5 fffffe8c`005da833 ffff9a85`92740000 00000000`00006930 : Ntfs!NtfsGrowLengthInCachedLcn+0x132 fffffe8c`005d6de0 fffff800`38bb92e0 : 00000000`00000000 ffff9a85`92746a98 00000000`00000000 ffff840d`00000001 : Ntfs!NtfsInsertCachedLcn+0x29c fffffe8c`005d6e90 fffff800`38cc5454 : 00000000`00000000 ffff9a85`92746a98 ffff9a85`92746a98 00000000`00000000 : Ntfs!NtfsInsertCachedRunInTier+0x5c fffffe8c`005d6f30 fffff800`38cc5238 : 00000000`00000000 fffffe8c`005d74b0 ffff840d`e643a1b0 00000000`03f00480 : Ntfs!NtfsInsertCachedRun+0xac fffffe8c`005d6fb0 fffff800`38ba20be : 00000000`00000000 00000000`00000000 ffff9a85`92b8f690 00000000`00010000 : Ntfs!NtfsAddCachedRun+0x80 fffffe8c`005d7020 fffff800`38bad343 : 000000f7`4a2fc5ba fffffe8c`005d74b0 00000000`00000000 fffffe8c`005d7440 : Ntfs!NtfsMarkUnusedContextPostTrimProcessing+0x426 fffffe8c`005d73b0 fffff800`33834f85 : ffff840d`d8c8bc80 ffff840d`ed496040 ffff840d`d8c8bc80 fffff800`3434aac0 : Ntfs!NtfsMarkUnusedContextPreTrimWorkItemProcessing+0x703 fffffe8c`005d79c0 fffff800`33907287 : ffff840d`ed496040 00000000`00000a18 ffff840d`ed496040 fffff800`33834e30 : nt!ExpWorkerThread+0x155 fffffe8c`005d7bb0 fffff800`33a1b8e4 : ffffbd80`67c81180 ffff840d`ed496040 fffff800`33907230 00007ff9`ddf759c0 : nt!PspSystemThreadStartup+0x57 fffffe8c`005d7c00 00000000`00000000 : fffffe8c`005d8000 fffffe8c`005d1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: Ntfs!NtfsGrowLengthInCachedLcn+132 MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys IMAGE_VERSION: 10.0.22621.2715 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 132 FAILURE_BUCKET_ID: AV_W_(null)_Ntfs!NtfsGrowLengthInCachedLcn OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {6cf3e289-3ff4-490f-2157-adefe365446e} Followup: MachineOwner ---------
It's really risky making a diagnosis based on just one dump, it would be easier if you download and run the V2 log collector and upload the resulting zip file to the cloud with a (public) link to it here. That way we get all the troubleshooting data in one go. Note that there is no personally identifiable data in there, nor any data that you should worry about making public. In the absence of that data, the one dump you have uploaded shows a failure during storage drive processing. We see the Windows ntfs.sys filesystem driver called several times, apparently manipulating the drive cache... Code: 2: kd> knL # Child-SP RetAddr Call Site 00 fffffe8c`005d69a8 fffff800`33a8c442 nt!KeBugCheckEx 01 fffffe8c`005d69b0 fffff800`33862d8c nt!MiSystemFault+0x1fd1f2 02 fffffe8c`005d6ab0 fffff800`33a27529 nt!MmAccessFault+0x29c 03 fffffe8c`005d6bd0 fffff800`38cc882e nt!KiPageFault+0x369 04 fffffe8c`005d6d60 fffff800`38bb95a0 Ntfs!NtfsGrowLengthInCachedLcn+0x132 05 fffffe8c`005d6de0 fffff800`38bb92e0 Ntfs!NtfsInsertCachedLcn+0x29c 06 fffffe8c`005d6e90 fffff800`38cc5454 Ntfs!NtfsInsertCachedRunInTier+0x5c 07 fffffe8c`005d6f30 fffff800`38cc5238 Ntfs!NtfsInsertCachedRun+0xac 08 fffffe8c`005d6fb0 fffff800`38ba20be Ntfs!NtfsAddCachedRun+0x80 09 fffffe8c`005d7020 fffff800`38bad343 Ntfs!NtfsMarkUnusedContextPostTrimProcessing+0x426 0a fffffe8c`005d73b0 fffff800`33834f85 Ntfs!NtfsMarkUnusedContextPreTrimWorkItemProcessing+0x703 0b fffffe8c`005d79c0 fffff800`33907287 nt!ExpWorkerThread+0x155 0c fffffe8c`005d7bb0 fffff800`33a1b8e4 nt!PspSystemThreadStartup+0x57 0d fffffe8c`005d7c00 00000000`00000000 nt!KiStartSystemThread+0x34 Note that this is a push-down stack, so you read it from the bottom up. During this ntfs.sys processing we get a page fault and according to the bugcheck the specified memory should have been in a non-pageable memory pool. If we examine the failing function in more detail... Code: 2: kd> .frame /r 4 04 fffffe8c`005d6d60 fffff800`38bb95a0 Ntfs!NtfsGrowLengthInCachedLcn+0x132 rax=ffff9a85a2680000 rbx=000000000000a833 rcx=0000000000029a48 rdx=0000000000000000 rsi=ffff9a85a271dc80 rdi=ffff9a8592746ae8 rip=fffff80038cc882e rsp=fffffe8c005d6d60 rbp=fffffe8c005d6d98 r8=000000000000de18 r9=0000000000000000 r10=0000000000008b6b r11=ffff9a85bc4b0056 r12=0000000000000001 r13=000000000000ffff r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040246 Ntfs!NtfsGrowLengthInCachedLcn+0x132: fffff800`38cc882e 66448954c810 mov word ptr [rax+rcx*8+10h],r10w ds:002b:ffff9a85`a27cd250=???? You can see at the bottom there that the failing instruction was a MOV (move) instruction using the RAX and RCX registers as a pointer. Both registers appear to contain reasonable values and yet the resulting memory reference is invalid (the ????). Clearly one of those registers contains a bad value, the question is; what set the bad value? It could be a flaky driver that we don't see in this dump (not unusual) - that will take a bit more work to find - or it could be a flaky storage drive. If this drive is an M.2 drive then try removing the drive and re-seating it firmly. I've seen many niggly issues caused by poorly seated M.2 drives. I really can't comment more without seeing the V2 log data.
Thanks for your quick reply! I'm not home right now, but I'll send over the v2 log files as soon as possible. I recently installed Windows on a brand new M.2 drive in a new slot, while my old M.2 drive was sitting in a faster PCIe slot. I also installed Windows Nicosia drivers and DaVinci Resolve just to test them; it worked at first but stopped working less frequently now, so everything started going back to normal without me installing anything else. I read something about drive problems I could tell were worn out. In the dmp file, a drive check found a 4TB disk drive with an overheating issue. So I unplugged the drive and thought maybe that was the problem—but it wasn't. So yes, I don't have any real clues. My guess might be the power supply, which tends to crash when using a lot of resources mostly from my GPU, or maybe the motherboard since I'm having trouble connecting USB external drives with high capacity and no extra power. The cables keep getting disconnected at random. But thanks again! Hopefully, once we have all that data, it will make pinpointing the problem much easier.
There is only one problem because there hasn't been a BSOD since the logs started on November 13th. The specific dump I mentioned likely came from a weak M.2 drive. Now I can see you have two Samsung NVMe drives, a Corsair NVMe drive, and an older SATA SSD. But in your system log, there are errors about those NVMe drives.
Event[2004] shows the driver found a controller error on \Device\RaidPort2.
Event[2005] says an error happened while your system was trying to save data to disk 4 (DR4). It sounds like the issue is with one of those NVMe drives, probably your main drive. Did you try taking them out and putting them back in? You should also download Samsung Magician and run a full test on those Samsung drives, plus check if they need firmware or driver updates.
Corsair doesn't have a built-in diagnostic tool unfortunately. By the way, I notice your boot drive is that Corsair NVMe, but your main system drive is actually a 500GB Samsung 970 EVO Plus. Was that intentional, or did you not mean to make it like this?
Hey there! So, I ran a full scan on my Samsung NVMe drives and they look okay. To give you some background, I used to have a 500GB drive as my main one, but I swapped it for a 2TB drive that sits in the fastest PCIe slot on my motherboard. I didn't take the 500GB drive away yet because I still needed to recover important data from it (so I set up dual boot with Windows 10). I did the same thing with my Corsair drive, which I added to the system to perform a clean Windows installation on a new SSD I got from an unused laptop. The Blue Screen of Death happened on the old Windows install which I still have access to if I switch the 2TB as the boot drive. The problem is it never created a minidump file even though I tried taking out the automatic restart. And nothing has happened so far ~ So I'm starting to think that the NVMe issue might just be one-off and the real culprit hasn't been found yet, also because I've had several BSODs on this Windows install already. I could try using the V2 on the old Win11 install but as I said no minidump file there either; I just checked it myself. And yes, I reseated the drives and have two of them in the motherboard slots and one sitting on an expansion card.
If you plug in more than one drive at once that has different Windows setups, you could get into a mess.