Random BSODs, 0xD1, 0x1E, 0x50, 0x3B

BugCheck F7, {4efd97c19f20, 11a4264f3c41, ffffee5bd9b0c3be, 0}


*** WARNING: Unable to verify timestamp for vrtaucbl.sys
*** ERROR: Module load completed but symbols could not be loaded for vrtaucbl.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : portcls.sys ( portcls!CPortPinWavePci::TransferKsIrp+c3 )




BugCheck 3B, {c0000005, fffff80bff3fabef, ffffcc81cf0693a0, 0}


Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGPROCESS::UpdateHandleInstance+eb )




dxgkrnl LDDM Graphics Subsystem c:\windows\system32\drivers\dxgkrnl.sys Kernel Driver Yes Manual Running OK Ignore No Yes






BugCheck 1E, {ffffffffc0000005, fffff801b001159d, 0, ffffffffffffffff}


Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+fd )




tdx NetIO Legacy TDI Support Driver c:\windows\system32\drivers\tdx.sys Kernel Driver Yes System Running OK Normal No Yes






There were 3 failed to analyze with the lates debugging software:
GetContextState failed, 0x8007001E






portcls.sys ( portcls!CPortPinWavePci::TransferKsIrp+c3 )
dxgkrnl.sys ( dxgkrnl!DXGPROCESS::UpdateHandleInstance+eb )
NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+fd )


tdx NetIO Legacy TDI Suppo NetIO Legacy TDI Suppo Kernel System Running OK TRUE FALSE 4,096 86,016 0 C:\WINDOWS\system32\DRIVERS\tdx.sys
DXGKrnl LDDM Graphics Subsyste LDDM Graphics Subsyste Kernel Manual Running OK TRUE FALSE 1,470,464 282,624 0 4/24/2029 12:34:26 AM C:\WINDOWS\system32\drivers\dxgkrnl.sys


Event[1475]:
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 2017-05-29T15:54:28.129
Event ID: 225
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-UUB0HTT
Description:
The application \Device\HarddiskVolume1\Program Files (x86)\Google\Update\1.3.33.5\GoogleCrashHandler.exe with process id 7176 stopped the removal or ejection for the device PCI\VEN_8086&DEV_8C82&SUBSYS_78501462&REV_00\3&11583659&0&FA.




Event[1476]:
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 2017-05-29T15:54:28.129
Event ID: 225
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-UUB0HTT
Description:
The application \Device\HarddiskVolume1\Program Files (x86)\Google\Update\1.3.33.5\GoogleCrashHandler64.exe with process id 7192 stopped the removal or ejection for the device PCI\VEN_8086&DEV_8C82&SUBSYS_78501462&REV_00\3&11583659&0&FA.






Event[199]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-21T05:01:38.858
Event ID: 7000
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The CldFlt service failed to start due to the following error:
The request is not supported.




Event[425]:
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 2017-05-21T19:55:57.624
Event ID: 219
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-UUB0HTT
Description:
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{79bfb205-3d9a-11e7-af87-d8cb8abfa802}#0000000000100000.




Event[565]:
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 2017-05-23T23:08:01.908
Event ID: 219
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-UUB0HTT
Description:
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{79bfb205-3d9a-11e7-af87-d8cb8abfa802}#0000000000100000.




Event[644]:
Log Name: System
Source: Microsoft-Windows-Kernel-Boot
Date: 2017-05-24T17:30:40.638
Event ID: 29
Task: N/A
Level: Error
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-UUB0HTT
Description:
Windows failed fast startup with error status 0xC00000D4.




SWD\WPDBUSENUM


Event[1601]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.563
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The nsi service depends on the nsiproxy service which failed to start because of the following error:
A device attached to the system is not functioning.






Event[1602]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.563
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The Dhcp service depends on the nsi service which failed to start because of the following error:
The dependency service or group failed to start.




Event[1603]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.563
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The Dnscache service depends on the nsi service which failed to start because of the following error:
The dependency service or group failed to start.




Event[1604]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.563
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The Wcmsvc service depends on the nsi service which failed to start because of the following error:
The dependency service or group failed to start.




Event[1606]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.595
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The LanmanWorkstation service depends on the nsi service which failed to start because of the following error:
The dependency service or group failed to start.




Event[1607]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.595
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The mrxsmb service depends on the rdbss service which failed to start because of the following error:
A device attached to the system is not functioning.




Event[1608]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.595
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The mrxsmb20 service depends on the mrxsmb service which failed to start because of the following error:
The dependency service or group failed to start.




Event[1609]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.595
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The IKEEXT service depends on the nsi service which failed to start because of the following error:
The dependency service or group failed to start.




Event[1610]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.595
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error:
The dependency service or group failed to start.




Event[1611]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.595
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The mrxsmb10 service depends on the mrxsmb service which failed to start because of the following error:
The dependency service or group failed to start.




Event[1612]:
Log Name: System
Source: Service Control Manager
Date: 2017-05-29T15:58:09.595
Event ID: 7001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-UUB0HTT
Description:
The NlaSvc service depends on the Dhcp service which failed to start because of the following error:
The dependency service or group failed to start.




5/23/2017 11:48 AM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.0, time stamp: 0x4247e346
Faulting module name: audioeng.dll, version: 10.0.15063.0, time stamp: 0x988907dd
Exception code: 0xc0000096
Fault offset: 0x000000000000d138
Faulting process id: 0x1a5c
Faulting application start time: 0x01d2d365a6147da5
Faulting application path: C:\WINDOWS\system32\AUDIODG.EXE
Faulting module path: C:\WINDOWS\system32\audioeng.dll
Report Id: 9cb524cb-5bcb-4c06-a04c-ea9e0b9bedd5
Faulting package full name:
Faulting package-relative application ID:




5/29/2017 10:59 PM Windows Error Reporting Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.15063.168
P2: 80248007
P3: 70AC589F-B6E6-4BC6-8CE0-637658E3FEC0
P4: Download
P5: 202
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_10.0.15063.168_d327cf80331718d19ba88a4f 50a9c39c98a93b3_00000000_1d143028

Analysis symbol:
Rechecking for solution: 0
Report Id: 4e1d4195-c5d4-41b2-8c03-d525acd151f2
Report Status: 4
Hashed bucket:


Preliminary analysis with Windows Debugger Version 10.0.15063.137 AMD64 provided information about 3 failed system related drivers. There were there minidumps that were not able to be analysed by this version of the debugger.






Open administrative command prompt and run these commands:


1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan


Then right click on the top of the administrative command prompt box then left click on edit then select all. Then right click on the top bar of the administrative command prompt box the left click edit then copy. Then paste into the forum.


Test memory with memtest86+ with 8 or more runs to rule in/out memory problems.

There were a lot of dependency issues in the event viewer. Are you using a VPN?


a. Click Start, type services.msc in the Start search box and hit Enter.b. Locate the “Remote Access Connection Manager” service.c. Right-click the service and select “Properties”.d. Click the “Dependencies” tab.Make a note of the dependency services of “Remote Access Connection Manager” and make sure that these services are started and the startup type is set to “Automatic”.

There was 1 failed fast startup.
Turn off fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

I've already run memtest86+ extensively with no errors, and no I'm not using a VPN.
Changed both what RACM depends on and depends on it to automatic, (Dependant on "Secure Socket Tunneling Protocol Service," and "Routing and Remote Access" depends on it). Fast startup is now off.

Cmd Copy+Paste:

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning 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 /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is SSD.Stage 1: Examining basic file system structure ... 307200 file records processed.File verification completed. 10369 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 366486 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. 29644 data files processed.CHKDSK is verifying Usn Journal... 38716400 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 116751906 KB total disk space. 73733184 KB in 138265 files. 99268 KB in 29645 indexes. 0 KB in bad sectors. 419702 KB in use by the system. 65536 KB occupied by the log file. 42499752 KB available on disk. 4096 bytes in each allocation unit. 29187976 total allocation units on disk. 10624938 allocation units available on disk.C:\WINDOWS\system32>

There were 3 minidump that the latest edition of the Microsoft debugger could not process and produced error code:

GetContextState failed, 0x8007001E

Keep your post active for a while longer so if someone else analyzes the minidump with an older edition that is working we will have more information on the other 3 minidumps.

After the changes that you made if you get any more bsod please post them.

If you find that you are ever in a situation where there are frequent bsod you can download whocrashed and bluescreenview and immediately process bsod. Then uninstall and reinstall the driver(s). Then you can submit the bsod here to see if there is additional information about the processing of the log files. And if you are in a bind you can usually use clean boot to decrease or eliminate bsod until they are debugged.

I believe those dumps just did not compile correctly (which may be indicative of a more serious issue), as others including myself had the same result with them. No crashes since changes, so tentatively resolved, I'll be able to tell for near certain once 48 hours have passed. if anything happens I'll be sure to add it.

In the meantime, thank you so much for your help :)

New BSOD, since it happened I've cleaned up my Registry with WinThruster, though this still poses the possibility of being driver related.

Attachment 137427
hopefully, this one isn't messed up.

sorry for breaking in here but I was interested and analysed too, here are the results:

Code:

0x0000001A:    MEMORY_MANAGEMENT (31.05.2017 06:23:10) [Windows 10] 
 
CAUSED BY:     ntoskrnl    
               rzudd.sys [15.10.2015] * Razer Rzudd Engine Driver * => http://www.razersupport.com/index.php?_m=downloads&_a=view 
               HIDCLASS.SYS [14.08.1991] * Hid Class Library (Windows System File) 
 
PROCESS:       ntoskrnl.wrong.symbols.exe 
 
Usual causes:  Device driver, memory, kernel

1. As u can see the Razer driver is shown in the bsod dump. Try to update or roll back this driver.

2. Memtest is important because the dump shows that too: MemTest86+ - Test RAM Windows 10 BSOD Tutorials

3. There are gpu driver errors too. U should update or roll back the AMD gpu driver

Code:

2017-05-22T21 00:57.585  Display driver amdkmdap stopped responding and has successfully recovered.: .  
2017-05-22T21 00:59.186  Display driver amdkmdap stopped responding and has successfully recovered.: .  
2017-05-24T18 56:01.758  Display driver amdkmdap stopped responding and has successfully recovered.: .  
2017-05-24T18 56:03.401  Display driver amdkmdap stopped responding and has successfully recovered.: .

Figures, Razer's drivers being buggy as usual... I'll rerun my Memtesting while I'm asleep and post results once I wake up/it completes, takes bloody ages.

my AMD drivers seem to be screwed in general, even after running DDU and installing several different releases of the drivers...

9 passes of memtest86+, no errors, AMD drivers updated to 17.5.2 (latest for my card), uninstalled razer synapse and the chroma sdk, reinstalling v2.20.15.1104

3 new BSOD since last post info from DM Log: Attachment 137574

Place the computer in clean boot to reduce the frequency of the bsod until the analysis is completed.

Event[2923]: Log Name: System Source: Service Control Manager Date: 2017-06-01T01:22:41.616 Event ID: 7026 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-UUB0HTT Description: The following boot-start or system-start driver(s) did not load: damEhStorClass

Event[2910]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-06-01T01:22:24.666 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-UUB0HTT Description: The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{79bfb205-3d9a-11e7-af87-d8cb8abfa802}#0000000000100000.

Event[2869]: Log Name: System Source: Service Control Manager Date: 2017-06-01T01:01:06.273 Event ID: 7026 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-UUB0HTT Description: The following boot-start or system-start driver(s) did not load: damEhStorClass


Event[2860]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-06-01T01:01:02.490 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-UUB0HTT Description: The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{79bfb205-3d9a-11e7-af87-d8cb8abfa802}#0000000000100000.


Event[2807]: Log Name: System Source: Service Control Manager Date: 2017-05-31T22:38:14.008 Event ID: 7026 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-UUB0HTT Description: The following boot-start or system-start driver(s) did not load: damEhStorClass

Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64 malfunctioning with GetContextState failed, 0x8007001E


dam.sys
DAM Kernel Driver
Windows Update


EhStorClass.sys
Enhanced Storage Cla
Windows Update

WUDFRd.sys
Windows Driver Foundation - User-mode Driver Framework Reflector
Windows Update