Crash without Blue screen but has error code

Question

Crash without Blue screen but has error code

s 0

Didn't even get a screen that was blue. Just a huge thing that said the PC needed to be restarted.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x000000000043d59b, 0x0000000000000002, 0x216c9c0000196c9c). A dump was saved in: C:\Windows\Minidump\022226-11640-01.dmp. Report Id: f43928fb-e464-4281-b4f0-b8adc775d744.

Machine made an ERRRRRRRR sound while doing it.

Crash Dump files. Windows memory diagnostic extended says there is no memory errors
https://1drv.ms/u/c/5f8c262ae59032fc/IQDQvLG2GE3xS6HENzg0-mZHAYUUb5jjXg22RESEbOlmpuw?e=09JNbr

2 answers

Your answer

Answer 1

Jonathan Deives 68,395 Independent Advisor

The minidump file indicates the cause is "dxgkrnl.sys", usually GPU related.

Use the DDU tool to uninstall the current graphics card driver, go to the manufacturer's website and download the latest driver.

s 0 Reputation points

2026-03-01T00:48:54.7833333+00:00

Did this yesterday.

One application just crashed earlier with the ERRRRRR sound but no error message or blue screen.

Now concerned the GPU has a problem. anything you can suggest to diagnose this?
Jonathan Deives 68,395 Reputation points Independent Advisor

2026-03-01T00:51:06.27+00:00

Ideally, you should perform a clean reinstallation of the driver. If the problem occurs again, it may be a hardware issue.
s 0 Reputation points

2026-03-03T04:19:32.38+00:00

Is it poossible that this crash had anything to do with me not having XMP settings for ram on and running a large # of applications on at the same time that used the GPU?

Answer 2

The event log entry shows a bug check (system crash) with code 0x0000004E. This is a Windows stop code (bug check) that indicates a serious kernel‑mode error. Even if the classic blue screen wasn’t visible, Windows still performed a bug check and created a crash dump at C:\Windows\Minidump\022226-11640-01.dmp.

To investigate and confirm the cause, analyze the dump file with WinDbg:

Make sure the system is configured to generate crash dumps (small, kernel, or complete). A page file on the boot volume is required; for small dumps this is at least 2 MB, for complete dumps the page file must be at least physical RAM + 1 MB.
Copy C:\Windows\Minidump\022226-11640-01.dmp (or C:\Windows\memory.dmp if present) to another Windows 10/11 machine.
Install the Windows 10 SDK and select Debugging Tools for Windows to get WinDbg.
In WinDbg, set the symbol path to the Microsoft public symbol server: https://msdl.microsoft.com/download/symbols.
Use File → Open Crash Dump and open the .dmp file.
Run !analyze -v in the command window to see the detailed analysis, including:
- The stop code and parameters (0x4E and the four values shown in the event).
- The likely faulting driver or module.
- The call stack at the time of the crash.

If the same stop code recurs, use the dump analysis to identify whether a specific driver, device, or software component is responsible, then update, roll back, or remove that component as appropriate.

If crashes continue and the cause isn’t obvious from the dump, follow advanced crash‑dump troubleshooting guidance and consider attaching a kernel debugger for live analysis.

References:

Share via

Crash without Blue screen but has error code

2 answers

Your answer