Windows 10: BSOD when waking from sleep mode and randomly when starting PC

(PS when I tried to post this once it didn't show up so if it's like a moderator has to see this and this was submitted twice, really sorry!!)

Hello all, my PC is crashing when it wakes up from sleep mode lately. I know it is a driver for sure, I've been told it's a driver going outside its boundaries and muffing up stuff, but I don't know what driver it is and WinDBG hasn't helped. (I might be totally wrong... I am not so good at computers oops)

WinDBG has said it is memory corruption and the culprit is NTOSKRNL. I know it isn't my RAM, I have had faulty drivers in the past (two drivers which were for virtualization of disk drives, Windows 10 hates them, and two drivers for a PS4 controller to be detected as a XBOX One controller, Windows 10 also hates them, and Daemon Tools) all successfully removed and went on clean streaks with no BSODs... which appeared to be NTOSKRNL and memory corruption as well at first.

I don't know what driver it is anymore, or how to fix it. I think it might be my USB 3.0 drivers which I had a problem with in the past but there has not been any updates for my USB 3.0 drivers since 2015 from ASUS (thanks ASUS) so not sure how to fix. I am hoping it is another driver. *Sad

It first happened when my sister was playing Sims 3. From there on it has just been happening when the PC wakes up from sleep mode, even during a Windows update it did this. It is really annoying. I hope that someone can please help. Thank you so much for reading!

PPS: Sorry if I sound entitled or anything, I don't mean to, I hope that anyone who reads this knows... I have no clue what I'm doing lol *cry


♡♡♡ Thank you for anyone who reads! ♡♡♡


Attachment 144269

:)

 

BSOD when wake up from sleeping mode. HELP!!!! Mostly 0x1a, but 0x7e, 0x1e, 0x1b, 0x50, 0x139 and more.

Thx ZigZag,

I am running your 1st test. I did what you say in the wiki. And after reboot, my PC can run but my mouse indicator is shaking... I don't know if the test is running after reboot or not. I type verifier /querysettings and it says many of the selected
driver is verified, I don't know when this test will end but my operation is kind of lagging together with when the mouse is shaking. And as my BSOD cause is waking up from sleep mode, can I keep doing sleep and wake? Will the Verifier still work after a round
of sleep and wake? What if it just like this? I cannot use my PC like this stuck situation for 36 hrs....

BTW, start from today, the BSOD often happens when sleep more than 30 mins. And sometimes it won't become BSOD and just system halted. Pls tell me what to do. Thx.

 

Computer boots from start when coming out of sleep mode

When I hit my keyboard or move my mouse when my pc is in sleep mode it does not just wake up like my pc at work? My home PC boots from start, I can see the bios and the windows screen etc just like I would if I hit the power button to turn it on.

Is there a way to get the pc to wake from sleep without it booting from start?

 

HI technodos,

Welcome to the BSOD forum.


Debugging the bsod minidupm files indicated 3 misbehaving drivers:
ASMedia USB3.1 Hub Ser asmthub3.sys
Intel RST (Rapid Storage Technology) driver iaStorA.sys
AiChargerDT.sys
There were frequent faulting applications noted for Nvidia



Open administrative command prompt and type or copy and paste:


1) sfc /scannow

2) dism /online /cleanup-image /restorehealth

3) chkdsk /scan

4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread

5) perform windows updates and post any failed kb# with error code

6) Using device manager upadate:ASMedia USB3.1 Hub Ser asmthub3.sys or find an updated driver on the Asus web site using the computer's serial or product number and the operating system.

7) AiChargerDT.sys was not seen on our driver list but appears to be an Asus charger driver. Update this driver using the Asus web site using the computer's serial or product number and the operating system.

8) Using the Asus web site download an updated version of: Intel RST (Rapid Storage Technology) driver iaStorA.sys

9) Uninstall all Nvidia drivers/softwareThe best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from the Asus web site or from the NVidia website.
The computer manufacturer approved drivers are preferred.
If you use the Nvidia web site be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download

10) Run memtest86+ version 5.01 for at least 8 runs. This may take many hours so plan to run it overnight.Memtest86+ - Advanced Memory Diagnostic Tool
When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 BSOD Tutorials






Code: BugCheck 9F, {3, ffffaf8f485cd8d0, fffff803a5124870, ffffaf8f485b1ab0}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: 0: kd> !drvobj \Driver\usbccgpfffff803a2be2b60: Unable to get value of ObpRootDirectoryObjectDriver object \Driver\usbccgp not found0: kd> !drvobj \Driver\HidUsbfffff803a2be2b60: Unable to get value of ObpRootDirectoryObjectDriver object \Driver\HidUsb not found0: kd> !drvobj \Driver\HidUsbfffff803a2be2b60: Unable to get value of ObpRootDirectoryObjectDriver object \Driver\HidUsb not found[/quote] Code: BugCheck 9F, {3, ffff90076e7658d0, ffffcc0148387c40, ffff90076e794ab0}Probably caused by : usbccgp.sys[/quote] Code: 3: kd> !drvobj \Driver\usbccgpfffff803a8dd6b00: Unable to get value of ObpRootDirectoryObjectDriver object \Driver\usbccgp not found3: kd> !drvobj \Driver\HidUsbfffff803a8dd6b00: Unable to get value of ObpRootDirectoryObjectDriver object \Driver\HidUsb not found3: kd> !drvobj \Driver\HidUsbfffff803a8dd6b00: Unable to get value of ObpRootDirectoryObjectDriver object \Driver\HidUsb not found[/quote] Code: BugCheck 9F, {3, ffffe7806e9b0060, ffffb480c2d07870, ffffe7806e9ac010}Probably caused by : usbccgp.sys[/quote]

Code: ffffb480`c2d07138 fffff809`ffc76eb9*** WARNING: Unable to verify timestamp for iaStorA.sys*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys iaStorA+0x86eb9[/quote] Code: iaStorA iaStorA iaStorA Kernel Boot Running OK TRUE FALSE 4,096 696,320 0 9/13/2016 10:45:46 C:\WINDOWS\system32\drivers\iaStorA.sys 4,096[/quote]
iaStorA.sys Intel RST (Rapid Storage Technology) driver Drivers & Software XP
Code: BugCheck 9F, {3, ffff818eb9daa2e0, fffff80230f24870, ffff818eaca6cab0}Unable to load image \SystemRoot\SysWow64\drivers\AiChargerDT.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for AiChargerDT.sys*** ERROR: Module load completed but symbols could not be loaded for AiChargerDT.sys*** WARNING: Unable to verify timestamp for asmthub3.sys*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sysProbably caused by : asmthub3.sys[/quote] Code: Event[213]: Log Name: System Source: Service Control Manager Date: 2017-07-13T16:12:26.753 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Cuddles Description: A service was installed in the system. Service Name: AiChargerDT Service File Name: SysWow64\drivers\AiChargerDT.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:[/quote] These were the most similar drivers to asmthub3.sys identified on the list of drivers:
AiCharger.sys Asus Charger Driver
Likely BSOD cause - haven't seen recently (15Jan2013) http://support.asus.com/download/opt...x?SLanguage=en AiChargerPlus.sys Asus Charger Driver
Likely BSOD cause - haven't seen recently (15Jan2013) http://support.asus.com/download/opt...x?SLanguage=en

Code: asmthub3 ASMedia USB3.1 Hub Ser ASMedia USB3.1 Hub Ser Kernel Manual Running OK TRUE FALSE 8,192 102,400 0 4/11/2016 02:16:03 C:\WINDOWS\system32\drivers\asmthub3.sys 4,096[/quote] Code: Event[133]: Log Name: System Source: Service Control Manager Date: 2017-07-13T16:03:33.880 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Cuddles Description: A service was installed in the system. Service Name: ASMedia USB3.1 Hub Service Service File Name: \SystemRoot\System32\drivers\asmthub3.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:[/quote] asmthub3.sys ASMedia USB 3.0 Hub driver http://www.asmedia.com.tw/eng/e_prod...3&cate_index=0

Code: >[ 16, 2] 0 e1 ffff818eb9daa2e0 00000000 fffff80cb4f408b0-ffff818eb65021b0 Success Error Cancel pending \Driver\asmthub3 AiChargerDT Args: 00041100 00000001 00000001 00000002 [ 16, 2] 0 e0 ffff818eb6502060 00000000 00000000-00000000 \Driver\AiChargerDT Args: 00041100 00000001 00000001 00000002 [ 16, 2] 0 e1 ffff818eba61a060 00000000 fffff8022e7bbea0-ffff818ebddde760 Success Error Cancel pending \Driver\usbccgp nt!PopRequestCompletion Args: 00041100 00000001 00000001 00000002 [ 0, 0] 0 0 00000000 00000000 00000000-ffff818ebddde760[/quote] Code: BugCheck 9F, {3, ffffe70fc6ae9060, fffff800f5924870, ffffe70fb7d2a130}Probably caused by : usbccgp.sys[/quote] Code: Args: 00000000 00000000 00000000 00000000>[ 16, 2] 0 e1 ffffe70fc6ae9060 00000000 fffff803325268a0-ffffe70fc61bcb90 Success Error Cancel pending \Driver\usbccgp ks!CKsDevice::CompleteDevicePowerIrp Args: 00041100 00000001 00000001 00000002 [ 16, 2] 0 1 ffffe70fc236dcb0 00000000 00000000-00000000 pending \Driver\usbaudio Args: 00041100 00000001 00000001 00000002 [ 16, 2] 0 e1 ffffe70fc6be0060 00000000 fffff800f3136ea0-ffffe70fb7c97180 Success Error Cancel pending \Driver\ksthunk nt!PopRequestCompletion Args: 00041100 00000001 00000001 00000002 [ 0, 0] 0 0 00000000 00000000 00000000-ffffe70fb7c97180[/quote] Code: BugCheck 9F, {3, ffff9901b48a38d0, ffffb0808a7fd870, ffff9901b487d010}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: ffffb080`8a7fd138 fffff809`51097c00*** WARNING: Unable to verify timestamp for iaStorA.sys*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys iaStorA+0x87c00[/quote]
Code: Args: 00000000 00000000 00000000 00000000>[ 16, 2] 0 e1 ffff9901b48a38d0 00000000 fffff80957382520-00000000 Success Error Cancel pending \Driver\usbccgp hidusb!HumPowerCompletion Args: 00041100 00000001 00000001 00000002 [ 16, 2] 0 e0 ffff9901b486d060 00000000 fffff809573035c0-ffff9901b486d1b0 Success Error Cancel \Driver\HidUsb HIDCLASS!HidpFdoPowerCompletion Args: 00041100 00000001 00000001 00000002 [ 16, 2] 0 e1 ffff9901b486d060 00000000 fffff803bd5baea0-ffff9901b4894130 Success Error Cancel pending \Driver\HidUsb nt!PopRequestCompletion Args: 00041100 00000001 00000001 00000002 [ 0, 0] 0 0 00000000 00000000 00000000-ffff9901b4894130[/quote] Code: 7/11/2017 1:04 AM Application Error Faulting application name: NVIDIA Web Helper.exe, version: 6.9.5.0, time stamp: 0x58fa0ea2 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x2030 Faulting application start time: 0x01d2f9e19b5b8fa7 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NvNode\NVIDIA Web Helper.exe Faulting module path: unknown Report Id: 6ef6ebe5-67cc-4e51-a620-d4a7ee04ad9c Faulting package full name: Faulting package-relative application ID:7/11/2017 1:28 AM Application Error Faulting application name: NVIDIA Web Helper.exe, version: 6.9.5.0, time stamp: 0x58fa0ea2 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x196c Faulting application start time: 0x01d2f9e4fed680e8 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NvNode\NVIDIA Web Helper.exe Faulting module path: unknown Report Id: 11074389-1e08-497e-ae04-26e2fb94dc64 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:26 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x4660 Faulting application start time: 0x01d2f9e4c9c1bdd8 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: 3223fac1-f240-425f-9eaf-cb727312aa14 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:03 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x4260 Faulting application start time: 0x01d2f9e188f9cb29 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: 5f6829c8-f5ac-44e1-9919-3e901ae2e012 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:02 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x4180 Faulting application start time: 0x01d2f9e167b624a0 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: 64b5e5bb-f75d-4383-addb-dc451d4edf3b Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:26 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x3d64 Faulting application start time: 0x01d2f9e4c06895fc Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: 56d856e9-f658-440b-bc20-a6903a1ed8a0 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:04 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x39a8 Faulting application start time: 0x01d2f9e1b43948da Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: 0628c08c-95cc-4f42-974b-7a035575d3ee Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:03 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x380c Faulting application start time: 0x01d2f9e1739d4937 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: 2f9c0bda-f646-4d48-8646-ab5b140f6ad3 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:02 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x36e4 Faulting application start time: 0x01d2f9e15c60c37e Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: e0d1bd87-c110-4611-97b9-7c90c63f37d2 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:16 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x3340 Faulting application start time: 0x01d2f9e36344b12f Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: 8c5b4a84-2173-4864-93b5-0b3622784c07 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:27 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x2b74 Faulting application start time: 0x01d2f9e4de62bf0f Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: 6e05c2c8-e9a1-4ced-8af2-959d16a5e841 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:03 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x29f8 Faulting application start time: 0x01d2f9e17ced20ba Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: f786e3a2-b53e-48b1-8310-e8a5ae16f31d Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:27 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x27e0 Faulting application start time: 0x01d2f9e4d3bce084 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: eaed6086-1ba3-4089-b13c-127764616f78 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:29 AM Application Error Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6 Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x1a5c Faulting application start time: 0x01d2f9e51c2bd3b1 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: bf1b04cc-d26c-4eca-92f1-8459311647ee Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:27 AM Application Error Faulting application name: NVIDIA GeForce Experience.exe, version: 56.2924.1538.1, time stamp: 0x590a368e Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x4644 Faulting application start time: 0x01d2f9e4d6d80124 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: 882b05d6-bf59-4b5b-a888-4c234a28306b Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:05 AM Application Error Faulting application name: NVIDIA GeForce Experience.exe, version: 56.2924.1538.1, time stamp: 0x590a368e Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x2c3c Faulting application start time: 0x01d2f9e1d53104d5 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: b0ba313b-b1cb-4992-a70a-518cc2897d30 Faulting package full name: Faulting package-relative application ID: 7/11/2017 1:29 AM Application Error Faulting application name: NVIDIA GeForce Experience.exe, version: 56.2924.1538.1, time stamp: 0x590a368e Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8 Exception code: 0x80000003 Fault offset: 0x00e64389 Faulting process id: 0x28b8 Faulting application start time: 0x01d2f9e5178a85d3 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll Report Id: f105f14b-c999-4b34-bcf6-4138837b92af Faulting package full name: Faulting package-relative application ID: 6/19/2017 6:47 PM Application Error Faulting application name: nvcontainer.exe, version: 1.4.2206.1309, time stamp: 0x590900b0 Faulting module name: _NvMdnsPlugin.dll, version: 7.1.2206.1309, time stamp: 0x59090b4b Exception code: 0xc0000005 Fault offset: 0x0000000000076080 Faulting process id: 0xea0 Faulting application start time: 0x01d2e92c5610efbe Faulting application path: C:\Program Files\NVIDIA Corporation\NvContainer\nvcontainer.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NvContainer\plugins\LocalSystem\GameStream\Discovery\_NvMdnsPlugin.dll Report Id: bd049840-1ca6-47ed-96dc-9c680a30a2e3 Faulting package full name: Faulting package-relative application ID:[/quote]

 

@zbook
have a closer look first on the "blocked irp" line where the arrow > is. The most likely cause with the stopcode 0x9F starts at the line with the arrow:
Code: >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffe7806e9b0060 00000000 fffff80a05502520-00000000 Success Error Cancel pending \Driver\usbccgp hidusb!HumPowerCompletion Args: 00041100 00000001 00000001 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e0 ffffe7806e9b3060 00000000 fffff80a05e935c0-ffffe7806e9b31b0 Success Error Cancel \Driver\HidUsb HIDCLASS!HidpFdoPowerCompletion Args: 00041100 00000001 00000001 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffe7806e9b3060 00000000 fffff8001c336ea0-ffffe7806e9ad900 Success Error Cancel pending \Driver\HidUsb nt!PopRequestCompletion Args: 00041100 00000001 00000001 00000002[/quote] Code: >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff818eb9daa2e0 00000000 fffff80cb4f408b0-ffff818eb65021b0 Success Error Cancel pending \Driver\asmthub3 AiChargerDT Args: 00041100 00000001 00000001 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e0 ffff818eb6502060 00000000 00000000-00000000 \Driver\AiChargerDT Args: 00041100 00000001 00000001 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffff818eba61a060 00000000 fffff8022e7bbea0-ffff818ebddde760 Success Error Cancel pending \Driver\usbccgp nt!PopRequestCompletion Args: 00041100 00000001 00000001 00000002[/quote]
Your suggestions are correct. But this should be the first step with 0x9F.

 

Hi ZBOOK. There hasn't been any updates for the USB 3.1 buggy driver since 2015.


Thank you for the information about what is causing the crashes.
I was able to update the driver for the ASMEDIA USB hub 3.0, only 3.1, though I updated 3.1 so atleast there's that I guess. I cannot update the AICharger, it is nowhere on their website and I've searched like crazy. Just like you don't know of it, it also seems ASUS forgot about it, as usual and typical of them. >*Sad

Do you think it holds any real worth on my system? I could just get rid of it if it's something odd. My PC is part laptop (motherboard and RAM), it always says it's "100%" charged, but doesn't have a battery? Someone once said it's for Apple devices to charge faster. I don't know.

Why do I need to reinstall my NVIDIA drivers if they aren't doing anything wrong according to the crash dumps? Just wondering. Never had an issue with them before but I can see some stuff about some really useless NVIDIA stuff like GeForce Experience. I know it in particular is separate, but are the other two? If so I will just get rid of them.

How to run MEMTEST without a USB handy? I hate to say I am extremely poor but it is true I can't even get a pepsi right now and thriving on ramen so can't pick up a USB right now.

Here, though, if this helps at all!:
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.
C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows.
Stage 1: Examining basic file system structure ... 1307648 file records processed.
File verification completed.
38416 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ... 1568624 index entries processed.
Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...Security descriptor verification completed. 130489 data files processed.
CHKDSK is verifying Usn Journal... 41866008 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
1952882687 KB total disk space.
872857240 KB in 1085958 files.
624048 KB in 130490 indexes.
0 KB in bad sectors.
1494675 KB in use by the system.
65536 KB occupied by the log file.
1077906724 KB available on disk.
4096 bytes in each allocation unit.
488220671 total allocation units on disk.
269476681 allocation units available on disk.

Thanks ZBOOK! You are a wonderful person or are several wonderful multiple people. Unfortunately not much has currently changed crash-wise. But it's really nice to know what is at all, it was eating me alive haha.

 

You'r welcome. The Asus charge driver was not on the list of drivers and the most similar drivers were not reported for more than 4 years. So consider an email to Asus support to see if they have any comments.

Once you find that you have a stable computer environment perform the following steps:
1) create a new restore point
2) find a way to back up files to the cloud or a second drive or both
3) use Macrium Macrium Software | Your image is everything to create a free image of the drive. And save this image to the cloud. Microsoft, Dropbox, Google etc may each have some free space allotments.

 

Hi ZBOOK. You are real great. Yes, the AiCharger.sys driver is apparently to charge phones faster (oh my god, how useless).
I am going to call them today. You're a real pro, so I'm sure you have heard of how bad their support is... please, cross your fingers for me. I'm crossing my toes as well, extra luck maybe. Last time I called the guy on the phone told me "yeah, ASUS sucks, sorry".

So far waking up from sleep mode has produced no crashes at all, so on that end, you've totally fixed it! You're my hero. I am concerned about that AiCharger.sys though, I have had problems with it before, as well as my USB drivers which one hasn't had updates since 2015. Is there anything I can do, or am I doomed?

You are really smart.
Thank you for all the help!

 

For drivers there are generally two sources to use for updates:
1) The computer manufacturer (Asus)
2) The part manufacturer
The web sites that update drivers can be sources of future problems and we recommend that you do not use them. It is possible that any misbehaving driver would lead to future costly services from that website.
The computer manufacturer approved drivers are always preferred as they have been tested to work with the computer's configuration and operating system. The part manufacturer drivers may not have the modifications to the driver that were made by the computer manufacturer.
If you open the Asus web site and enter your computers serial or product number and the operating system you should be able to view all of the latest approved drivers for your configuration. Drivers can be updated at any time by downloading from the Asus website.
Every once in a while there can be a problematic driver even from the computer manufacturer and once this is identified a driver can be rolled back to an older edition of the driver.