About one in ten times, W10 Pro (64-bit) shuts down instead of auto-sleeps. This began after a z390a motherboard was replaced by an identical board.
Every suggestion at this site has been tried. SFC is clean. The latest Intel MEI is installed. Video driver is up-to-date.
After a shutdown, this .dmp file was created. Perhaps those versed in analysis can take a moment to look it over.
Thanks.
Last edited by borgus; 07 Aug 2020 at 12:54.
Are you certain that the PC is shutting down and just not being woken up by the keyboard and mouse?
Have you made sure that the driver for the keyboard/mouse have been set to not run in Power Saving mode?
Yes, it shuts down. MS Keyboard management is set to wake on mouse movement. Allow PC to turn off device is unchecked.
How about a quick easy check of 'powercfg lastwake' using an Administrative Command Prompt?
The crash was a DPC Watchdog violation 0x133-
In general this stop code is caused by faulty driver code that under certain conditions, does not complete its work within the allotted time frame.
The apparent cause was
CAXHWBS3.sys
That is often some manner of modem - connexant - driver problem
but I cannot see why you would have such on that board
The date of the driver is
Tue Jun 30 21:01:57 2009
I suspect you have acquired such with some software download
Last edited by Macboatmaster; 26 Jul 2020 at 15:53.
Event Viewer errors, in addition to the bugcheck generation are...
"The previous system shutdown at 7:52:39 PM on 7/25/2020 was unexpected."
"Windows failed to resume from hibernate with error status 0xC0000001."
Thanks for the analysis. That is the Connexant soft modem, which has perfored for over a decade without incident.
Will look into this further and report findings...
The fact it has performed Ok before, does not mean that it is not the cause.
The driver is ancient - dated as you can see 2009
I did not know that it could be used on 10 without problems, but what IMHO is certain is that that listed driver cannot be the correct one for 10
and this in event viewer
would be consistent with the driver for the connexant being the problem"The previous system shutdown at 7:52:39 PM on 7/25/2020 was unexpected."
"Windows failed to resume from hibernate with error status 0xC0000001."
Last edited by Macboatmaster; 28 Jul 2020 at 07:06.
Yup, a very old device, with no recent driver updates. Some reports state that softmodems cannot be used in Windows 10." That's obviously not the case; it faxes well and connects at the appropriate speed..
Agree: the fact that it used to work doesn't mean it always will. Still, it is odd that the occasional shutdown issue did not exist until the MB, originally installed in 12/18, was replaced with an identical model. The sole difference is a newer BIOS (1502).
Keeping an eye out ... over the long term.
The dump, may not of course be directly related to the shut down, instead of sleep.
However as I said the cause of the crash was most certainly that driver.
As it is only a one in ten occurrence it will be difficult to diagnose
If you wish send the V2log as here
BSOD - Posting Instructions
Quote