Do you experience frequent crashes each day with a dump file attached?
Do you experience frequent crashes each day with a dump file attached?
Hi,
I've been trying to troubleshoot frequent crashes on my computer. My PC is crashing multiple times daily. I've recently done a clean reinstall of Windows 11 and the crashes persist. I'm wondering if there is a hardware related issue with my PC. I've ran a memory test and it came back with no errors.
The dump file from my most recent crash is as follows:
OS: Windows 11 Enterprise (Clean reinstall as part of troubleshooting yesterday, issue persists)
PSU: Corsair Vengeance 750M, 750W, probably 7 years old, no apparent issues and PC has always been on a surge protector or UPS.
Original to build (2019 I believe?)
MB: Gigabyte X570 Aorus Ultra
GPU: EVGA GeForce RTX 3080 FTW3
CPU: AMD Ryzen 7 3700X 8 Core Processor, 3600MHZ, 8 cores, 16 logical processors
RAM: 64GB Corsair Vengeance DDR4 (16x4)
Disk Drives:
Samsung 980 PRO 2TB NVMe (x2), OS is installed on one of them (OS drive 723GB free, second drive 893 GB free with partition for Bazzite as I was getting tired of windows crashing constantly)
Seagate Barracuda 4TB (x2), one inside PC connected via SATA, one external connected via USB (internal 3.4TB free, external 747GB free)
WD Black 1TB, internal via SATA (525 GB free)
Network:
Wired via ethernet directly to modem/router combo. T-Mobile Home Internet.
Connected Peripherals:
Logitech G502 Mouse
Logitech G512 Keyboard
ADI-2 DAC (Audio)
Samsung Odyssey G7 28" 4k (x2), via displayport
External HDD via USB, 4TB Seagate Barracuda installed, UGREEN External Hard Drive Enclosure [Purchased from Amazon]
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
https://msdl.microsoft.com/download/symbols
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.343 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 46
Microsoft ® Windows Debugger Version 10.0.29507.1001 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020626-16953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*
https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`da000000 PsLoadedModuleList = 0xfffff804`daef5040
Debug session time: Fri Feb 6 04:16:40.586 2026 (UTC - 6:00)
System Uptime: 0 days 12:15:09.254
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000092`49a88018). Type ".hh dbgerr001" for details
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`da4fbb10 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8184`80556430=0000000000000044
6: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000092`49a88018). Type ".hh dbgerr001" for details
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffab0b07e0c7f0, Address of the IRP
Arg2: 0000000000001312
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1484
Key : Analysis.Elapsed.mSec
Value: 2368
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 25
Key : Analysis.Init.CPU.mSec
Value: 843
Key : Analysis.Init.Elapsed.mSec
Value: 57545
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Analysis.Version.DbgEng
Value: 10.0.29507.1001
Key : Analysis.Version.Description
Value: 10.2511.5.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2511.5.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x44
Key : Bugcheck.Code.TargetModel
Value: 0x44
Key : Dump.Attributes.AsUlong
Value: 0x21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x44_Npfs!NpFsdWrite
Key : Failure.Hash
Value: {947b2e94-712f-fbfc-7620-19ee913c5b76}
Key : WER.System.BIOSRevision
Value: 5.17.0.0
BUGCHECK_CODE: 44
BUGCHECK_P1: ffffab0b07e0c7f0
BUGCHECK_P2: 1312
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 020626-16953-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffab0aebae7080
IRP_ADDRESS: ffffab0b07e0c7f0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: firefox.exe
DEVICE_OBJECT: ffffab0ad563bb00
STACK_TEXT:
ffff8184`80556428 fffff804`da3d6257 : 00000000`00000044 ffffab0b`07e0c7f0 00000000`00001312 00000000`00000000 : nt!KeBugCheckEx
ffff8184`80556430 fffff804`da3d5813 : 00000000`00000000 ffffab0b`00363d10 00000000`00000000 ffffab0a`d3666d50 : nt!IopfCompleteRequest+0xa17
ffff8184`805565b0 fffff804`78f92613 : 00400000`00000000 ffffab0b`07e0c908 00000000`00000001 00000000`00000000 : nt!IofCompleteRequest+0x13
ffff8184`805565e0 fffff804`da2ce84b : ffffab0b`07e0c7f0 fffff804`da27c9b9 ffffab0b`00363da8 00000000`00000001 : Npfs!NpFsdWrite+0xd3
ffff8184`80556650 fffff804`da2ce7c3 : ffffab0a`eba54748 ffffab0a`eba54740 00000000`00000000 00000000`00000000 : nt!IopfCallDriver+0x5b
ffff8184`80556690 fffff804`6bc4bbca : ffffab0b`07e0c7f0 ffff8184`80556840 ffffab0a`d3666d50 00000000`00000000 : nt!IofCallDriver+0x13
ffff8184`805566c0 fffff804`da2ce84b : ffff9880`02df6000 00000000`00062a00 ffffab0b`00363d10 fffff804`da6b27ec : FLTMGR!FltpDispatch+0x2ea
ffff8184`80556760 fffff804`da2ce7c3 : ffffab0b`00363d10 ffffab0b`00363d10 00000000`00000000 ffffab0b`07e0c7f0 : nt!IopfCallDriver+0x5b
ffff8184`805567a0 fffff804`da8c1a75 : 00000000`00000000 ffffab0b`00363d10 ffff8184`80556840 ffffab0a`c97d5cb0 : nt!IofCallDriver+0x13
ffff8184`805567d0 fffff804`da8bfd21 : ffff8184`805568e0 ffff8184`805569b0 00000000`00000000 00000000`00000000 : nt!IopSynchronousServiceTail+0x1c5
ffff8184`80556880 fffff804`da8bf9f2 : ffffab0b`00363d10 ffffab0b`00363ce0 ffffab0b`07e0c7f0 00000000`00000000 : nt!IopWriteFile+0x141
ffff8184`805569a0 fffff804`da6bde58 : 00000000`00000001 00000000`00000000 00000000`00000000 000001a0`33cc8238 : nt!NtWriteFile+0x2d2
ffff8184`80556a70 00007ffa`1e5a1b54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000092`4fb3ed08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`1e5a1b54
SYMBOL_NAME: Npfs!NpFsdWrite+d3
MODULE_NAME: Npfs
IMAGE_NAME: Npfs.SYS
IMAGE_VERSION: 10.0.26100.4202
STACK_COMMAND: .process /r /p 0xffffab0aef406080; .thread 0xffffab0aebae7080 ; kb
BUCKET_ID_FUNC_OFFSET: d3
FAILURE_BUCKET_ID: 0x44_Npfs!NpFsdWrite
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {947b2e94-712f-fbfc-7620-19ee913c5b76}
Followup: MachineOwner
---------
Update your post with complete hardware details and operating system information. Provide the power supply specifications, including voltage, amperage, age, and condition (original, build, refurbished, used). List the disk drive specifications such as make, model, and capacity, along with current usage. Include a description of all connected peripherals. Clarify whether the network connection is wired or wireless.
A 7 year old PSU is definitely a concern.
It’s highly probable it’s close to or past its built-in EOL.
This PSU supplies three distinct voltages (3.3, 5, and 12) to different system parts. Any issues or minor voltage deviations can severely disrupt operations.
What should we do?
My recommendations are:
Make sure all crucial data is saved at least twice in separate locations away from the affected computer, and confirm those backups are accessible and readable.
Check Reliability History/Monitor and Event Viewer for error codes, warnings, or logs recorded just before or during crashes.
An increasing number of different errors often indicates a failing PSU—look for trends.
If feasible, get another known functional PSU to test by swapping it in. Use only the cables provided with the replacement unit.
When clean installed Windows did you verify it prior to installing any third-party applications? If not, it’s possible you reinstalled the issue (I’ve observed that before). But if you confirmed it beforehand, there might be a hardware concern.
I’m having trouble attaching files directly to the forum. Is there a suggested method for sharing dump files?
I thought about PSU problems. I also looked at the Event Viewer for details, but found only general warnings and one critical error—Kernel-Power: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." The warnings in Event Viewer don’t seem linked to the crashing, though I’m seeing repeated error hr=0x800705B4. Not sure if that’s connected.
When crashes happen, Windows shows the standard BSOD screen, and the system doesn’t shut down abruptly with no warning, as if it lost power completely.
Also, while using Bazzite I haven’t seen any crashes even during heavy gaming. Windows 11 seems to crash under light load—like watching YouTube or idling overnight. I’ve ordered a replacement PSU in the meantime, since I don’t have a spare I’m willing to install (all others are outdated and weren’t stored properly).
If you have any other suggestions to try while waiting, I’ll let you know and update accordingly.
The only programs I reinstalled were basic utility software and Steam, along with a few games for the new install (Helldivers 2, Battlefield 6, Warframe). Other apps installed included Firefox, Signal, and the extensions I usually use (ublock origin). I saw firefox.exe in the dump analysis, but I’m keeping my software up to date. Could this be the problem or is it just a distraction?
Share them on a cloud platform (Google Drive, OneDrive, Dropbox, etc.) and make sure they’re public so anyone with the link can access them. Provide the shared connection here.
You shouldn’t be certain you haven’t reinstalled the issue. There might be a glitch in the games, Steam, Firefox, Signal, and especially in browser extensions (which are often problematic).
I recommend trying to launch your browser(s) without any extensions active and checking if the problems persist. It’s likely the cause is related to an extension.
Also, verify that your BIOS is current. You don’t specify the version, but the motherboard manufacturer’s site indicates several updates in the past two years, mostly involving AGESA microcode. This update is essential for AMD systems and should be maintained. If your BIOS is outdated, an update might resolve these concerns.
If neither a browser extension nor the BIOS is the issue, consider a clean installation and remove all UEFI partitions during setup (choose a custom install). When Windows starts, download drivers from your motherboard vendor’s site and directly from Nvidia for the RTX3080.
Do not let Windows install drivers automatically—use the sysdm.cpl command, go to the Hardware tab, click Device Installation Settings, then uncheck the radio button, click Save Changes, and finish.
After that, repeatedly run Windows Update (even after reboots) until no new updates appear. Finally, thoroughly test the system to confirm if the problem reappears. If it does, you likely have a hardware-related issue.
The challenge with Windows driver installations is that hardware manufacturers provide generic drivers for all platforms. These may lack specific customizations needed for your device. The drivers from your motherboard vendor include the required adjustments. Therefore, these are tailored to your hardware instead of the universal drivers Windows installs.