Windows 10: Bugcheck 7F almost daily after Connected Standby

Started getting these bugchecks ever since I went back to 8.1 (via restoring an old image) then going back to 10 1511.

Seems to occur after connected standby, a string of DCOM errors then it bugchecks 7F. Always occurs when I just leave the tablet around doing nothing. Tablet in question is an Asus VivoTab Note 8.

Thoughts? Last resort I'll do a scratch installation, but I have it setup nicely now and it's a PITA though due to all the I2C and GPIO drivers needed for the touchscreen.

Thanks.

:)

 

windows 10 crashes every 2 days.

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, fffff803c41b0e70, ffffd000588b3ee0, fffff803c211204b}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+13c )

Followup: MachineOwner

If verifier was enabled, it would say BugCheck C4

 

BSOD after update to latest windows version

BugCheck 7F, {8, ffffa201fd926af0, ffffa2020299cff0, fffff802329dd6d2}

UNEXPECTED_KERNEL_MODE_TRAP (7f)

I recommend to temporarily remove the DrRacket development environment and check for BIOS and Driver Updates.

BIOS Update Utility for Windows 10 (64-bit), 8.1 (64-bit), 7 (32-bit, 64-bit) - ThinkPad T550,
W550s

 

Please check your manufacturer, ASUS, for driver updates.
The Broadcom network drivers have been flagged
Code: 8863d024 92813211Unable to load image \SystemRoot\system32\DRIVERS\bcmdhd63.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for bcmdhd63.sys *** ERROR: Module load completed but symbols could not be loaded for bcmdhd63.sys bcmdhd63+0x13211 2: kd> lmvm bcmdhd63 start end module name 92800000 9295f000 bcmdhd63 T (no symbols) Loaded symbol image file: bcmdhd63.sys Image path: \SystemRoot\system32\DRIVERS\bcmdhd63.sys Image name: bcmdhd63.sys Timestamp: Thu Oct 03 04:09:54 2013 (524CD1F2) CheckSum: 000541FB ImageSize: 0015F000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Thanks. I just forced an update on the device via Windows Update, will try the new driver.

 

Gone for a while, and it happened again. Latest dump attached.

 

There are many drivers outdated, mainly Intel drivers.
Please update the ATKPackage drivers which you can find here.

You're sure there are no more driver updates available?

 

I can't use any of those, and I'm already using the latest package Asus puts out, they only have an official package for 8.1. If I use the Windows Update version of those Intel drivers (in particular the GPIO and I2C ones), none of the peripheral hardware work, I'll be out of my touchscreen, pen, sensors, even my power button would stop responding.

 

We could try driver verifier, but I'm questioning if it is worth it with the status of the drivers.

 

OK one last time, this time I caught the spontaneous reboot in action...

Last resort I'll just leave it as is and find a weekend to blow it away completely and install it clean. I asked around in tablet forums, seems like I'm the only one having this issue.

 

Please upload the correct / a new zip file, the latest dump file has already been uploaded.

 

Did you roll back the drivers or have there been no drivers updated?
Code: 2: kd> !irp c35496c0 Irp is active with 7 stacks 5 is current (= 0xc35497c0) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ 16, 0] 0 0 96060030 00000000 8880e952-b7f280e8 \Driver\sdbus ndis!ndisSetDevicePowerOnComplete Args: 00000000 00000000 00000000 00000000 >[ 16, 2] 0 e1 b7f28030 00000000 00000000-00000000 pending Unable to load image \SystemRoot\system32\DRIVERS\bcmdhd63.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for bcmdhd63.sys *** ERROR: Module load completed but symbols could not be loaded for bcmdhd63.sys \Driver\BCMSDH43XX Args: 00000000 00000001 00000001 00000000 [ 16, 2] 0 e1 c352b020 00000000 81f7dbfa-9611f720 Success Error Cancel pending *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys \Driver\vwifibus nt!PopRequestCompletion Args: 00000000 00000001 00000001 00000000 [ 0, 0] 0 0 00000000 00000000 00000000-9611f720 Args: 00000000 00000000 00000000 00000000 2: kd> lmvm bcmdhd63 start end module name 99490000 995ef000 bcmdhd63 T (no symbols) Loaded symbol image file: bcmdhd63.sys Image path: \SystemRoot\system32\DRIVERS\bcmdhd63.sys Image name: bcmdhd63.sys Timestamp: Thu Oct 03 04:09:54 2013 (524CD1F2) CheckSum: 000541FB ImageSize: 0015F000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] The Intel graphics drivers have also been flagged yesterday
Code: 81c3d570 8f461000Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for igdkmd32.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys igdkmd32+0x11000 2: kd> lmvm igdkmd32 start end module name 8f450000 8f747000 igdkmd32 T (no symbols) Loaded symbol image file: igdkmd32.sys Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys Image name: igdkmd32.sys Timestamp: Mon Aug 17 17:34:15 2015 (55D1FEF7) CheckSum: 002EEBFD ImageSize: 002F7000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Yes, I did roll back the driver for the wireless. Figured if it's doing the same with the new and old, I might as well use the old one which gives me less headaches with missing access points, in particular my BlackBerry hotspot.

As for the display driver, I did manually uninstall it, and reinstalled the SoC drivers, thought I give that a try since everyone is using the exact same package from Asus. However shortly after that there was another video driver downloaded by Windows Update, and that's what I've been using.

In those cases, it looks the only real issue with the driver is just it is unsigned? They are the versions provided by Asus, and it seems like I'm the only one having the BSODs.

 

I'd like to give driver verifier a shot to see if any other driver is causing problems, but I'm not sure how it is with tablets.

Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Latest with Verifier. This morning it became completely unresponsive, had to do a force shutdown.