Windows 10 crash screen appears.
Windows 10 crash screen appears.
Hi, I’m having an issue with a BSOD (code: SYSTEM_SERVICE_EXCEPTION). I was downloading the latest NVIDIA driver and had this setup: Ryzen 5 2600, GALAX RTX 2060 B350 Tomahawk Corsair Vengeance LPX 2666Mhz, 8x2 ADATA 512GB, SEAGATE BARRACUDA 2TB Seasonic Focus Gold 550W. The BSOD would appear every time I opened Apex. I’ve checked forums and thought it might be related to RAM, driver updates, or removing old drivers. My English isn’t great, so I hope someone can help.
Consider trying to download Windbg from the Microsoft Store and employ it to examine the dump file generated during a BSOD. When Windows experiences a crash, it typically produces a dump file containing the state of memory at that moment; Windbg enables debugging of this file and reveals the underlying reason for the crash in technical detail. You might share your findings here. To use Windbg effectively: upon launching, it should detect the recent crash automatically. Either via a notification or in the home screen (I’m not sure), it will display the dump file. Once opened, you’ll encounter a console displaying various details about the file. Near the bottom, there should be some highlighted blue text with a command (like “!analyze -v”). Clicking it initiates a download of symbol translations from Microsoft, converting the crash’s bytecode into more readable information, and logs extensive data in the console—providing valuable clues about the cause of the crash.
I'm preparing to download it and will share the findings once received.
Debugging Information:
- Key : Analysis.CPU.mSec Value : 3281
- Key : Analysis.DebugAnalysisManager Value : Create
- Key : Analysis.Elapsed.mSec Value : 13839
- Key : Analysis.Init.CPU.mSec Value : 937
- Key : Analysis.Init.Elapsed.mSec Value : 105299
- Key : Analysis.Memory.CommitPeak.Mb Value : 96
- File in CAB: 021422-13750-01.dmp
- Dump attributes: 0x8
- BUGCHECK_CODE: 3b
- BUGCHECK_P1: c0000005
- BUGCHECK_P2: fffff8057b68adc0
- BUGCHECK_P3: fffff805800e9920
- BUGCHECK_P4: 0
- Context: fffff805800e9920 -- (.cxr 0xfffff805800e9920) rax=006c006e0077006f rbx=ffff81055a844000 rcx=0000000044f2fb7d rdx=006c006e0077006f rsi=ffff810542a02280 rdi=3333333333333333 rip=fffff8057b68adc0 rsp=ffffdb8e9ef1e560 rbp=ffffdb8e9ef1e5d0 r8=0000000000020000 r9=2779a35826cf7dd8 r10=0000000000000000 r11=ffff810542a02290 r12=0000000000000000 r13=0000000000000000 r14=ffff81055a845fc0 r15=00000000000007c4
- Index: 0
- Name: .cxr 0xfffff805800e9920
Verify if the date and time recorded for file (021422-13750) correspond to the BSOD event, not another incident. The crash appears linked to Discord, which doesn't confirm a Discord bug but might indicate a related feature issue. The crash involved Npfs.SYS, possibly due to a driver accessing a named pipe or FIFO, attempting to read data, and then freeing memory before an unexpected step. This analysis is based on available information; further research may clarify the root cause. Additional details can be found at the provided links.
RAM swap might be useful in certain situations. I came across this topic while researching related issues.
Around 5 PM in my time zone, that day occurred three times. Likely one of those instances.
It seems you're trying to trace the cause of crashes related to memory management and FIFO operations. The OS was attempting to free memory for reading from a queue, which led to a crash. You're checking if the stack line provides clues about why this happened. I'll help you analyze the dump files using Windbg step by step. Feel free to share more details about the crashes or the stack traces you're seeing.