Windows 10 Windows 10 64bit crashing often. Ntoskrnl.exe. Most common reasons are: Unexpected kernel mode trap; DPC watchdog violation; Driver IRQL not less or e

  • Thread starter Thread starter Frumenti Dandi
  • Start date Start date
F

Frumenti Dandi

I'm getting fed up with this. I have updated my BIOS, my drivers and run 17hrs of Memtest86+.


I get unexpected Kernel Mode Trap most often when playing games.


DPC watchdog violation when the mouse and keyboard stop responding, usually when using Firefox, then the computer crashes completely.


Driver IRQL not less or equal is less common.


All the failures I have looked at with Who Crashed and BlueScreenView don't give me much to go on as the crash is with ntoskrnl.exe.


Here is a link to a ZIP of my Minidumps (2MB).


The system specs are below.


OS Name Microsoft Windows 10 Pro
Version 10.0.18363 Build 18363
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-VG6EQ9F
System Manufacturer Gigabyte Technology Co., Ltd.
System Model B450 I AORUS PRO WIFI
System Type x64-based PC
System SKU Default string
Processor AMD Ryzen 5 2600 Six-Core Processor, 3400 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. F50, 27/11/2019
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Product B450 I AORUS PRO WIFI-CF
BaseBoard Version x.x
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume3
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.18362.752"
Time Zone GMT Summer Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 16.0 GB
Available Physical Memory 12.3 GB
Total Virtual Memory 33.0 GB
Available Virtual Memory 29.0 GB
Page File Space 17.0 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware No
Hyper-V - Data Execution Protection Yes

I hope someone can help me get to the bottom of this!

Continue reading...
 
Back
Top