Frequent crashes

porro91

New member
Joined
Dec 10, 2020
Posts
3
Hey guys,


I'm experiencing alot of crashes lately on my high end desktop which I've built myself. I can't figure out what's causing them tho...


Specs:

Operating System
Windows 10 Pro 64-bit
CPU
AMD Ryzen 7 3700X 33 °C
Matisse 7nm Technology
RAM
32,0GB Dual-Channel Unknown @ 1596MHz (16-18-18-38)
Motherboard
ASUSTeK COMPUTER INC. PRIME X570-PRO (AM4) 33 °C
Graphics
ROG PG278QE (2560x1440@144Hz)
4095MB NVIDIA GeForce RTX 2070 SUPER (MSI) 38 °C
Storage
465GB Samsung SSD 970 EVO Plus 500GB
Powersupply
Corsair RM750x


Attached is the zip file you asked.

Hopefully you can help lead me in the right direction. Thanks in advance.


Kind regards.
porro
 

Attachments

Hi porro91 ,

The logs displayed no recent BSOD dump files.

a) The collected dump file dated 8/5/2020 was bugcheck 113: VIDEO_DXGKRNL_FATAL_ERROR
The misbehaving driver was nvlddmkm.sys.

b) an old BIOS version at that time was 1201 and is currently 2802

c) BSOD occurred on 11/18, 10/18, 10/4, 8/23 however Windows did not create dump files

d) The logs displayed crashes related to the headset



Please perform the following steps:



1) Open administrative command prompt (ACP) and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}


12) 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 edit then copy > paste into the thread


13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread


14) Create a new restore point

15) Upgrade the BIOS: 2802 > 3001
PRIME X570-PRO|Motherboards|Motherboards / Components |ASUS Global

16) Consider upgrading Windows: 10.0.18363 > 20H2

17) Read this link on Windows Driver Verifier (WDV):
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista | Sysnative Forums




Code:
Event[13]:
  Log Name: System
  Source: Microsoft-Windows-DriverFrameworks-UserMode
  Date: 2020-12-10T17:18:57.938
  Event ID: 10111
  Task: User-mode Driver problems.
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Provoost
  Description:
The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 4 more times.  Please contact the device manufacturer for more information about this problem.
 
Last edited:
Minidump date: 5 Aug 2020 (too old).
RAM g.skill F4-3200C16D-32GVKA ? Not present in MoBo QVL, present in product QVL.
Ram freq: 3200MHz.
Windows can be updated.
New nvidia driver is available (nvidia website).
Items available on your MoBo support webpage:
- New non-beta bios 3001 released yesterday.
- New audio driver.
- New Intel I211 LAN driver.
- New (not sure) Armoury Crate software (2020/11/13).
- New (not sure) AMD Chipset Driver.

I was not able to find SSD firmware.
I was not able to find its current firmware on samsung website.
It is managed by samsung magician software, available on the product webpage.
There is a NVMe Driver Version 3.3 on the product webbage.
In msinfo32 (system information), components, storage, scsi:
- there is "Standard NVM Express Controller"
- Driver: C:\WINDOWS\SYSTEM32\DRIVERS\STORNVME.SYS
- windows version: 10.0.18362.1110
- I'm not sure if samsung NVMe driver will substitute this one, if installed.
 
Rich (BB code):
VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress.  By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000019, The subtype of the bugcheck:
Arg2: 0000000000000001
Arg3: 00000000000010de << Vendor Id
Arg4: 0000000000001e84 << Device Id

For those who are curious, the third and fourth parameters are the vendor Id and the device Id respectively. Both of which point to the graphics card.

PCI Lookup

Rich (BB code):
15: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff804`8e680000 fffff804`8fd51000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e0a5a1b06de180e3\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Mar 18 03:32:09 2020 (5E719639)
    CheckSum:         0166127C
    ImageSize:        016D1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

As the others have suggested, the first point of call, would be to check for a graphics card driver update.
 
Please perform the following steps:



1) Open administrative command prompt (ACP) and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

Microsoft Windows [Version 10.0.18363.1256]
(c) 2019 Microsoft Corporation. All rights reserved.

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 found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1139

Image Version: 10.0.18363.1256

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1139

Image Version: 10.0.18363.1256

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

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>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
512512 file records processed.
File verification completed.
13900 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
217 reparse records processed.
750134 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
217 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
118812 data files processed.
CHKDSK is verifying Usn Journal...
38962600 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

487726079 KB total disk space.
238394108 KB in 377789 files.
250196 KB in 118813 indexes.
0 KB in bad sectors.
636291 KB in use by the system.
65536 KB occupied by the log file.
248445484 KB available on disk.

4096 bytes in each allocation unit.
121931519 total allocation units on disk.
62111371 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\PROVOOST\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\PROVOOST\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}


C:\Windows\system32>


EDIT:
Added screenshots of the startup and recovery & virtual memory window.
 

Attachments

  • Screenshot 2020-12-11 161000.png
    Screenshot 2020-12-11 161000.png
    19.9 KB · Views: 3
  • Screenshot 2020-12-11 161221.png
    Screenshot 2020-12-11 161221.png
    17.2 KB · Views: 2
Last edited:
Hey guys,


I did everything you've asked and Windows Driver Verifier is currently running.

Also I noticed that alot of times it crashed it was after I bumped my desk or something. Then my screen would go black, fans start running at 100% and nothing happens until I manually reboot.
Is it possible a bad connector or something like that is causing this?
 
First scannow:
Code:
Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:
Code:
Windows Resource Protection did not find any integrity violations.


For any BSOD > run the Sysnative log collector > upload results into the thread
 
Open administrative command prompt (ACP) and type or copy and paste:

verifier /querysettings

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 edit then copy > paste into the thread
 
I've had another look at the dump file and the crash was certainly caused by the graphics card driver not supporting the surprise removal IRP which was issued. However, since a surprise removal is essentially the device being removed (logically and/or physically) then it could possibly be due to an ill-fitted graphics card. Have you had any issues since?

Rich (BB code):
15: kd> !drvobj ffffa381e49ceba0 7
fffff8047fe47b58: Unable to get value of ObpRootDirectoryObject
fffff8047fe47b58: Unable to get value of ObpRootDirectoryObject
Driver object (ffffa381e49ceba0) is for:
 \Driver\nvlddmkm

Driver Extension List: (id , addr)

Couldn't read extension at 0xffffa381e5426570

Device Object list:
ffffa381e8195b20  ffffa381e8194b20: Could not read device object


DriverEntry:   fffff8048fd191b8    nvlddmkm
DriverStartIo: 00000000    
DriverUnload:  fffff8048e758960    nvlddmkm
AddDevice:     fffff8048e755ba8    nvlddmkm

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff8048e755fb8    nvlddmkm+0xd5fb8
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff8048e755fb8    nvlddmkm+0xd5fb8
[02] IRP_MJ_CLOSE                       fffff8048e755fb8    nvlddmkm+0xd5fb8
[03] IRP_MJ_READ                        fffff8048e755fb8    nvlddmkm+0xd5fb8
[04] IRP_MJ_WRITE                       fffff8048e755fb8    nvlddmkm+0xd5fb8
[05] IRP_MJ_QUERY_INFORMATION           fffff8048e755fb8    nvlddmkm+0xd5fb8
[06] IRP_MJ_SET_INFORMATION             fffff8048e755fb8    nvlddmkm+0xd5fb8
[07] IRP_MJ_QUERY_EA                    fffff8048e755fb8    nvlddmkm+0xd5fb8
[08] IRP_MJ_SET_EA                      fffff8048e755fb8    nvlddmkm+0xd5fb8
[09] IRP_MJ_FLUSH_BUFFERS               fffff8048e755fb8    nvlddmkm+0xd5fb8
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff8048e755fb8    nvlddmkm+0xd5fb8
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff8048e755fb8    nvlddmkm+0xd5fb8
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff8048e755fb8    nvlddmkm+0xd5fb8
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff8048e755fb8    nvlddmkm+0xd5fb8
[0e] IRP_MJ_DEVICE_CONTROL              fffff8048e755fb8    nvlddmkm+0xd5fb8
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff8048e755fb8    nvlddmkm+0xd5fb8
[10] IRP_MJ_SHUTDOWN                    fffff8048e755fb8    nvlddmkm+0xd5fb8
[11] IRP_MJ_LOCK_CONTROL                fffff8048e755fb8    nvlddmkm+0xd5fb8
[12] IRP_MJ_CLEANUP                     00000000    
[13] IRP_MJ_CREATE_MAILSLOT             00000000    
[14] IRP_MJ_QUERY_SECURITY              00000000    
[15] IRP_MJ_SET_SECURITY                00000000    
[16] IRP_MJ_POWER                       00000000    
[17] IRP_MJ_SYSTEM_CONTROL              00000000    
[18] IRP_MJ_DEVICE_CHANGE               00000000    
[19] IRP_MJ_QUERY_QUOTA                 00000000    
[1a] IRP_MJ_SET_QUOTA                   00000000    
[1b] IRP_MJ_PNP                         00000000
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top