SYSTEM_SERVICE_EXCEPTION BSOD just after waking up from hybernation

Code:

0: kd> .cxr 0xfffffb0a38717010
rax=0000000000000000 rbx=fffff13a40932000 rcx=fffffb0a38717a68
rdx=000000000000003c rsi=0000000000000348 rdi=0000000000000000
rip=fffff8002f49bea3 rsp=fffffb0a38717a18 rbp=fffffb0a38717ec0
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffffb0a38717950 r12=0000000000000000 r13=000000001a22fda0
r14=0000000000000410 r15=000000001a32e918
iopl=0         nv up ei pl zr ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050256
nt!RtlInitUnicodeString+0x23:
fffff800`2f49bea3 66833c4200      cmp     word ptr [rdx+rax*2],0 ds:002b:00000000`0000003c=????

It's a null pointer reference error which is causing the crash. Based on the other findings, I suspect that the most likely likely culprit is the Huawei driver, have you checked for any updates from the OEM support page?

zinou said:

The Huawei driver is old and may be causing some issues, but I don't think it's the culprit.

I rather suspect Calibre-parallel.exe as the culprit!It's maybe calling some graphical functions that led to the crash.
I'll try to check if there is an update for my Dell monitor.



@zbook
running the driver verifier resulted in a boot loop with the system trying to repair

Don't forget XMind.exe was alos causing a BSOD.

First of all, the Huawei driver is responsible for your hibernation issues, so I would suggest updating that driver. Secondly, if calibre-parallel.exe and/or XMind.exe is passing in a null pointer to the system service call, then system can crash in kernel mode leading to a BSOD, especially if there is no validation prior to making the call. It may be worthwhile updating or removing those programs at least for troubleshooting purposes.

The AsusCusDat.zip displayed 1 Data error: AsusCusDat.zip

Total size 2574


For any new BSOD please post a new V2 and zipped memory dump.
If possible please do not use rar.

How did you break the boot loop?
Were you able to boot to a Windows 10 iso and run each reset or bootmode commands?
Or were you able to perform a system restore?
Another method is to modify the registry.


When available please update the progress with the steps in post #6.

zinou said:

@zbook
I don't have Asus machine ! maybe you are refering to another Thread


I restarted in the safe mode and cleared the verifier config.



I don't like to run scripts that changes my config.

I think there is enough information in the Memory.dmp file that will permit to someone who knows how to deeply debug a crash dump file to identify the root cause of the crash.




- - - Updated - - -


There is no update for the Huawei driver. I don't use the router so often, so I can live without it.

For the Calibre and xmind I can't remove them, because I use them, unless I'm certain that it's one of those programs that's causing the issue.
The chances that the two are causing the crash is very minimal.

What was suspicious for me was the fact that your system kept BSODing on a function call to your external monitor. It could be the case that the HDMI port/cable is dodgy, or the driver for the HDMI port is old. Have you seen the BSOD happen with your external monitor disconnected?

If you don't have an external monitor, I'd then ask why is your monitor identified as HDMI?