Basically, I am making a last effort to resolve things before I return this thing for a refund. To give a quick idea of what's going on, here's the BlueScreenView report...
Windows version = 21H1 (OS Build 19043.1415)
Log file from the V2 tool here.
Any help would be appreciated because I don't really want to deal with the return process!
Hi, littleraskol.
In the ‘Caused by driver’ column of the table, have you updated / downloaded all of those files? A quick google search for them will help you find all of them.
-James
The thing that really concerned me is that one of them (ntoskrnl.exe) appears to be the Windows kernel. All the others (NETIO.sys, afd.sys, Ndu.sys) are associated with network drivers that I did update. I have also updated my video drivers. Between them and the network drivers, it seems to have helped since I have not BSODed since then... just having it crash three times in one day spooked the hell out of me.
Hi,
Considering that out of 4 crashes, 3 are clearly network related I'd say updating the network drivers was definitely the right call.
The 4th is from the 27th and at first sight doesn't look to be network related, but nothing to worry about though.Code:1: kd> knL # Child-SP RetAddr Call Site 00 fffff886`6e60e0c8 fffff802`4b8120be nt!KeBugCheckEx 01 fffff886`6e60e0d0 fffff802`4b7ccf32 nt!PspSystemThreadStartup$filt$0+0x44 02 fffff886`6e60e110 fffff802`4b7fff92 nt!_C_specific_handler+0xa2 03 fffff886`6e60e180 fffff802`4b6e6eb7 nt!RtlpExecuteHandlerForException+0x12 04 fffff886`6e60e1b0 fffff802`4b6e5ab6 nt!RtlDispatchException+0x297 05 fffff886`6e60e8d0 fffff802`4b8091ac nt!KiDispatchException+0x186 06 fffff886`6e60ef90 fffff802`4b805343 nt!KiExceptionDispatch+0x12c 07 fffff886`6e60f170 fffff802`a0683cef nt!KiPageFault+0x443 08 fffff886`6e60f300 fffff802`a06835c4 Ndu!NduHandleNblContextRemoved+0x63f 09 fffff886`6e60f3f0 fffff802`4f1d1116 Ndu!NduNblNotifyCallback+0xf4 0a fffff886`6e60f450 fffff802`4ef5930e fwpkclnt!FwppNetBufferListEventNotify+0xd6 0b fffff886`6e60f530 fffff802`4ead46be tcpip!WfppTaggedContextFree+0x1e 0c fffff886`6e60f560 fffff802`4e973599 NETIO!WfpNblInfoCleanup+0x4e 0d fffff886`6e60f5a0 fffff802`5c22895f ndis!NdisFreeCloneNetBufferList+0x239 0e fffff886`6e60f6d0 fffff802`5c262caf wdiwifi!CAdapter::FreeCopiedNetBufferLists+0xcb 0f fffff886`6e60f720 fffff802`5c262ee7 wdiwifi!CPort::FreeTxWfcFrame+0x13f 10 fffff886`6e60f790 fffff802`5c2280ca wdiwifi!CPort::SendCompleteNetBufferLists+0xb3 11 fffff886`6e60f7f0 fffff802`5c219f71 wdiwifi!CAdapter::SendCompleteNbl+0x12a 12 fffff886`6e60f860 fffff802`5c219b73 wdiwifi!CTxMgr::CompleteNdisNbl+0xdd 13 fffff886`6e60f8c0 fffff802`5c216746 wdiwifi!CTxMgr::CompleteNBLs+0x5b 14 fffff886`6e60f900 fffff802`5c207f70 wdiwifi!CTxMgr::TxTransferCompleteInd+0x68a 15 fffff886`6e60f9c0 fffff802`5cafe07b wdiwifi!AdapterTxTransferCompleteInd+0x10 16 fffff886`6e60f9f0 ffffdd06`6aa30000 mtkwl6ex+0xe07b 17 fffff886`6e60f9f8 ffffdd06`7b3f0a40 0xffffdd06`6aa30000 18 fffff886`6e60fa00 ffffdd06`6956f658 0xffffdd06`7b3f0a40 19 fffff886`6e60fa08 fffff802`5cb092c8 0xffffdd06`6956f658 1a fffff886`6e60fa10 ffffdd06`6ad9472c mtkwl6ex+0x192c8 1b fffff886`6e60fa18 ffffdd06`69917378 0xffffdd06`6ad9472c 1c fffff886`6e60fa20 00000000`00000600 0xffffdd06`69917378 1d fffff886`6e60fa28 ffffdd06`6ada0028 0x600 1e fffff886`6e60fa30 00000000`00000002 0xffffdd06`6ada0028 1f fffff886`6e60fa38 fffff802`5cb297d8 0x2 20 fffff886`6e60fa40 ffffdd06`6b500028 mtkwl6ex+0x397d8 21 fffff886`6e60fa48 fffff802`5cc25000 0xffffdd06`6b500028 22 fffff886`6e60fa50 00000000`00030000 mtkwl6ex+0x135000 23 fffff886`6e60fa58 00000000`c0000001 0x30000 24 fffff886`6e60fa60 00000000`00000000 0xc0000001 1: kd> lmvm mtkwl6ex Browse full module list start end module name fffff802`5caf0000 fffff802`5cd2c000 mtkwl6ex T (no symbols) Loaded symbol image file: mtkwl6ex.sys Image path: \SystemRoot\System32\drivers\mtkwl6ex.sys Image name: mtkwl6ex.sys Browse all global symbols functions data Timestamp: Sat Oct 9 03:00:52 2021 (6160E9C4) CheckSum: 0015DAF3 ImageSize: 0023C000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:
Well, it just crashed again... one of the network-related drivers that caused a prior crash again.
I don't know if the drivers I got from the laptop manufacturer website are actually the most up to date or how to get a better one. But I don't know if just reinstalling them over and over will work. Is there anything else I can do?Code:KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff801`ca1c4425 ffffaa07`e5c9db88 ffffac80`fcde0920 Ndu.sys Ndu.sys+4425
Drivers from the laptop vendor are rarely up to date, but that's not a concern because newer is not always better. Looking at GPU driver history there have been plenty drivers that were known to be buggy yet were the most recent available.
For anyone to give proper input with BSOD crashes, the newest data must be investigated first. Please upload either a new minidump file or post a new share link with a new V2 log collection.
I do have a hunch looking back at my previous investigation where I did not share a detail because I didn't think it was important. I noticed some driver activity from Avast in one dump, but as I saw driver activity from the network drivers across multiple dumps I did not think much of it. I still don't because a variety of multiple dumps usually implies something else, a possible hardware problem. But as I mentioned, this is just a (educated) hunch.
Okay, here's the latest V2 log result: FREEHOLD-(2022-01-02_10-10-15).zip - Google Drive
Have you added exceptions in Malwarebytes for Avast and in Avast for Malwarebytes by any chance? If you have not, I recommend doing this.
For Malwarebytes: https://support.malwarebytes.com/hc/...es-for-Windows
For Avast: How to exclude files or websites from scans in Avast Antivirus | Avast
Malwarebytes is designed to run with other antivirus programs, but from time to time things can go wrong and simply adding exceptions resolves the problems.
Well, one week without a crash and I'd hoped the issue was the Avast/Malwarebytes thing (which I did), but...
Haven't seen this error before.. I appreciate all those who've chimed in and am hoping that there's still some other underlying issue to be found if anyone can take a look at the latest V2 log result: FREEHOLD-(2022-01-11_07-57-14).zip - Google DriveCode:DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000`00000003 ffff878e`f02becd0 ffffe483`cc8df810 ffff878e`f02a4010 ntoskrnl.exe ntoskrnl.exe+3f70d0
This one is relatively easy, a driver is taking too long to change the power state of a device object to, for example, wake it up.
What you can see below is that a driver rtkvhd64.sys, connected to a driver object labeled IntcAzAudAddService, is the current location where the IRP was being processed when the system crashed. Presumably, this would mean that the Realtek audio driver caused the crash. I would check ASUS for driver updates or reinstall the drivers.
Code:Bugcheck code 0000009F Arguments 00000000`00000003 ffff878e`f02becd0 ffffe483`cc8df810 ffff878e`f02a4010 Debug session time: Tue Jan 11 01:13:21.458 2022 (UTC + 1:00) System Uptime: 9 days 7:20:40.836 12: kd> !irp ffff878ef02a4010 Irp is active with 10 stacks 8 is current (= 0xffff878ef02a42d8) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context .... [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)] 0 0 ffff878ef02becd0 00000000 fffff8072ae48a90-ffff878ef03981a0 \Driver\HDAudBus portcls!PowerIrpCompletionRoutine Args: 00000000 00000000 00000000 00000000 >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 1 ffff878ef0398050 00000000 00000000-00000000 pending *** WARNING: Unable to verify timestamp for RTKVHD64.sys \Driver\IntcAzAudAddService Args: 00000000 00000001 00000001 00000000 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff878ef03d7e00 00000000 fffff807199789d0-ffff878ef04151e8 Success Error Cancel pending \Driver\ksthunk nt!PopRequestCompletion Args: 00000000 00000001 00000001 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffff878ef04151e8 Args: 00000000 00000000 00000000 00000000 12: kd> lmvm RTKVHD64 Browse full module list start end module name fffff807`2be60000 fffff807`2c477000 RTKVHD64 T (no symbols) Loaded symbol image file: RTKVHD64.sys Image path: \SystemRoot\system32\drivers\RTKVHD64.sys Image name: RTKVHD64.sys Browse all global symbols functions data Timestamp: Tue Feb 23 11:15:58 2021 (6034D5DE) CheckSum: 00620E7A ImageSize: 00617000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:
Quote