Short BSOD alert, need quick fix.
Short BSOD alert, need quick fix.
If the file creation failed, I would first verify there is ample free space on your C: drive. (Free up space)
If sufficient space was available, I would then update the CPU chipset drivers from your motherboard vendors' website. (These updates often improve access to disk space)
For older systems, I would download a tool such as crystaldiskinfo.exe and examine the drive's smart data to ensure its health is normal. (Drive errors can cause memory dump failures, leading to disconnection or sleep issues)
If the drive appears healthy, I would disable Windows virtual memory temporarily and then re-enable it to clear the pagefile.sys and create a fresh one. (This helps with corrupted pagefile problems caused by malware, virtual memory errors, or faulty drivers)
You might also try accessing the Windows Control Panel, Device Manager, and right-click the drive to adjust settings and prevent it from sleeping. (This can resolve certain errors)
If possible, look for a minidump or the parameters for bucheck, as some indicate an error code that we could investigate further.
Completed the extended SSD test for WD Sandisk Dashboard, no issues detected, drive health remains at 100%. Also updated the SSD firmware to the latest version recently.
The drive is 90% empty
CPU Chipset drivers were already updated, checked again
System is 3 years old
Crystaldiskinfo - No prop, drive health 100%
Page File Deleted and a new one created
I will check next time it crashes if any mini dump is created
you can also search for ways to force a window to generate a minidump, adjust registry settings, and then utilize the keyboard to trigger a crash dump on a functional system.
this approach helps confirm the system is properly configured for saving dumps.
having a dump from a working system can also be beneficial.
The CRITICAL_PROCESS_DIED bugcheck usually indicates a hardware issue. You were instructed to start in Safe Mode, and it appears you can do that. Now check if you experience a BSOD while in Safe Mode. Many functions and devices won't operate correctly, and the screen resolution might be lower than expected. This happens because a minimal Windows version is loaded without third-party drivers, usually. If your system still BSODs in Safe Mode, it points to a hardware fault. If you can't force a BSOD in Safe Mode (and you're trying everything), the problem likely lies with software.
you could start the minidump during operation.
a minidump displays only basic bios details and loaded drivers.
for more intricate issues you’d prefer a kernel dump, which reveals all running processes on every CPU, internal logs, and active .exes.
it highlights plug-and-play problems and USB subsystem concerns.
for kernel dumps you need to switch the memory dump type from the default mini dump.
proceed with a mini dump and share it.
i can quickly check for suspicious drivers on the running machine and verify it can generate the file.
please note, you would force the dump, save it to a public server, and provide a link for others to view.