Can you review the BSOD dump file together?
Can you review the BSOD dump file together?
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 quite challenging to form a diagnosis from just one dump, but it would be simpler if you
download and execute the V2 log collector
and then upload the generated zip file to the cloud with a public link here. This approach consolidates all troubleshooting information at once. Please be aware that there is no personally identifiable data present, nor any sensitive information that should be shared publicly.
When such data isn't available, the dump you've provided indicates a failure in the storage drive processing. We observe the Windows ntfs.sys filesystem driver being called repeatedly, suggesting it's interacting with the drive cache in some way.
Thank you for your prompt response! I’m currently away but will handle the v2 log data as soon as possible. I recently set up Windows on a new crucial M2 drive in a new slot—it was done before on the old M2 drive, which was placed in the faster PCIe slot. I installed the Nicosia drivers and DaVinci Resolve, and it still works well for testing, though usage has become less frequent now. It started again as before without any additional installations.
I also read about possible drive issues. In the DMP, a drive check showed a 4TB disk with overheating concerns. I disconnected it, thinking it was the problem, but it didn’t stop working. My guesses are that the power supply might fail under heavy GPU usage, or maybe the motherboard is causing problems when connecting large-capacity USB external drives without external power connectors—they sometimes disconnect unexpectedly.
Thank you again; I hope with the complete data it will be easier to identify the issue.
It seems you're looking for a way to access the V2 log zip file through Google Drive.
Hey there! So, I ran a full scan on my Samsung NVMe drives, and they're all in good working condition. Just to give you a little background, I used to have a 500GB drive as my main drive, but I replaced it with a 2TB drive that's now in the fastest Pcie slot on my motherboard. However, I didn't get rid of the 500GB drive just yet because I still had some important data on it that I needed to recover( so ran dual boot with win 10). I did the same thing with my Corsair drive, which I added to my system to perform a clean Windows installation on a new SSD that I took from an unused laptop.
The bsod was on the old Windows install which I still have access to if I set the 2tb as the boot drive ,problem is it never created a minidump file I even tried taking out the automatic restart. and still nothing ~
So I'm beginning to think that the NVMe issue is a one-off and the real culprit is yet to be found, also cause I've had several bsod on this win install already.
I could try to use the v2 on the old win11 install but as I said noo minidump file there I just checked
And yes reseated the drive I have 2 on the motherboard and one though an expansion card
I recently attempted to export a video and bsod within the initial two minutes, but the mini dump file remains unchanged from the version dated 21/11/2023 without any updates.