This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 52%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZ%3C/text%3E%3C/svg%3E)
Hello, i've been experiencing BSOD and random freezing lately with my asus zenbook ux331un
specs:
Every time i have to reboot manually because the BSOD is stuck at 0% I think this is also the reason why it seems i can't create any dump file, i searched for three days for them still no way to find any, I have all set right for their creation (also page file settings) in fact if I manually create a BSOD i get the dump file right.
This problem seems to be unrelated to stress, it never happened while gaming but mostly during idle times. It seems to be worsened by laptop being attached to AC.
Thank you in advance for your answers.
nfo: https://www.dropbox.com/s/l13xyspi96ppx46/infos.nfo?dl=0
admin-events: https://www.dropbox.com/s/snpejxs8gyiowl1/events.evtx?dl=0
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Take a look at:
https://support.microsoft.com/en-us/sbs/windows/troubleshoot-blue-screen-errors-5c62726c-6489-52da-a372-3f73142c14ad
Open start and search for feedback and open Feedback Hub app and report this issue and make sure share dump files there.
Hi, thank you for your response, I already followed all steps of the Windows troubleshoot and nothing fixed my problem. As i said in my first message I seemly cannot create a dumpfile for this specific BSOD.
Hello @Zanni ,
Could you configuring your system to create just a "Small memory dump" (remembering that a restart will be necessary before the setting takes effect)?
My thinking is that this dump type might place less demands on the crash dump disk driver and might record some useful information and allow an automatic restart.
Just speculation on my part...
Gary
Thank you anyway, but I already setted it on automatic in fact when I manually created a BSOD it generated both a minidump and a normal dump file. I'll try what you suggest anyway
Hello @Zanni ,
If you get both a normal dump and a mini dump, then I am fairly sure that the minidump is created from the normal dump. The hope would be that, by just requesting a minidump, the contents of the minidump remain in memory until the system restarts (avoiding use of the crash dump disk driver to write memory to the page file before the restart).
Gary
Thank you, I definitely didn't know that, I already set the system as you said, next time I get the BSOD we will find out if it worked!
Hello @Zanni ,
I just found this: Overview of memory dump file options for Windows
A small memory dump records the smallest set of useful information that may help identify why your computer stopped unexpectedly. This option requires a paging file of at least 2 MB on the boot volume and specifies that Windows 2000 and later create a new file every time your computer stops unexpectedly.
So it looks as though the crash dump disk driver will be used, even for a small (mini) dump. We can just "hope" that keeping the data small helps...
Gary
Hello @Gary Nebbett ,
this evening the PC went BSOD again and no minidump file was generated as you correcly pointed out the crash dump disk is used. Thank you anyway!
Hello @Zanni ,
It would only be a very small step on the path to solving your problem, but it would probably be helpful to see the 4 bug check parameters (https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x124---whea-uncorrectable-error).
If you configure the system not to write a dump file of any type (dump file type = "(none)"), then the system might be able to restart automatically (rather than hanging when writing the dump file) and log at least the 4 bug check parameters in the System event log when i comes back up...
Gary
I'll try that and in case come back to you with results.
Thank you!
Hi @Gary Nebbett ,
I can't find the 4 bugcheck codes in the Event Viewer do you know how to?
Thank you!
Hello @Zanni ,
This is where I hope that they can be found:
That is the Critical Kernel-Power event ID 41.
When you look at the details, the bug check parameters will hopefully be present:
Gary
Hello @Gary Nebbett ,
Here it is but unluckily the parameters are all 0x0:
Thank you anyway for the time dedicated
Hello Zanni,
Welcome to Microsoft Q & A
From the error message of 41 abnormal restart, generally this BugcheckParameter with all 0 parameters is caused by hardware problems, we suggest you to check the hardware or seek help from the hardware vendor.
Best regards,
Molly
--------------------------------------------------------------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Molly Lu ,
I've not been clear when I posted the last screenshot sorry.
That is not the error event caused by my problem but the only error event i could find that is Windows telling me that the system as been rebooted in a strange way, this is caused by me actively shutting down the laptop pressing the power button. Sorry again for being not very clear.
Thank you anyway.
Hi Zanni,
Hello, maybe I misunderstood that screenshot is the key to the problem, also sorry for the inconvinience.
Best regards,
Molly