Question ntoskrnl.exe - BSOD in IDLE mode only ?

Jan 30, 2021
6
0
10
0
Hello,My Windows 7 x64 Desktop is crashing randomly in IDLE mode.

Here is the Report:


==================================================
Dump File : 013121-20326-01.dmp
Crash Time : 31.01.2021 03:16:14
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a03960e000
Parameter 2 : 00000000
00000000
Parameter 3 : fffff800036d746a
Parameter 4 : 00000000
00000000
Caused By Driver : AmdTools64.sys
Caused By Address : AmdTools64.sys+342a1000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+93ea0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\013121-20326-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 296.864
Dump File Time : 31.01.2021 03:17:02
==================================================

==================================================
Dump File : 012421-20748-01.dmp
Crash Time : 24.01.2021 10:47:38
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a00e971000
Parameter 2 : 00000000
00000000
Parameter 3 : fffff8000368c46a
Parameter 4 : 00000000
00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+93ea0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.24545 (win7sp1_ldr_escrow.200102-1707)
Processor : x64
Crash Address : ntoskrnl.exe+93ea0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012421-20748-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 276.048
Dump File Time : 24.01.2021 10:51:10
==================================================

==================================================
Dump File : 010921-21309-01.dmp
Crash Time : 09.01.2021 16:18:08
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a00e3d1000
Parameter 2 : 00000000
00000000
Parameter 3 : fffff8000368c46a
Parameter 4 : 00000000
00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+93ea0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.24545 (win7sp1_ldr_escrow.200102-1707)
Processor : x64
Crash Address : ntoskrnl.exe+93ea0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\010921-21309-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 275.992
Dump File Time : 09.01.2021 16:22:05
==================================================

System Information:
Graphics Chipset - AMD Radeon R9 200 Series
Memory Size - 2048 MB
Memory Type - GDDR5
Core Clock - 1050 MHz
Windows Version - Windows 7 (Service Pack 1) (64 bit)
System Memory - 16 GB
CPU Type - AMD Ryzen 5 2600X Six-Core Processor


Graphics Card Manufacturer - Powered by AMD
Graphics Chipset - AMD Radeon R9 200 Series
Device ID - 6810
Vendor ID - 1002
SubSystem ID - 9275
SubSystem Vendor ID - 1682
Revision ID - 00
Bus Type - PCI Express 3.0
Current Bus Settings - PCI Express 3.0 x16
BIOS Version - 015.041.000.000
BIOS Part Number - 113-270XCDF-22-W8
BIOS Date - 2014/01/15 02:59
Memory Size - 2048 MB
Memory Type - GDDR5
Memory Clock - 1400 MHz
Core Clock - 1050 MHz
Total Memory Bandwidth - 179 GByte/s
Memory Bit Rate - 5.60 Gbps
2D Driver File Path - /REGISTRY/MACHINE/SYSTEM/CurrentControlSet/Control/Class/{4d36e968-e325-11ce-bfc1-08002be10318}/0000
OpenGL® API Version - 4.6
OpenCL™ API Version - 1.2

I have been uninstalling the AMD drivers and going back to an older version for testing, i still get random BSODs while in IDLE.
There are no (noticable?) problems when gaming Warframe or Genshin Impact.

Ive been running Scannow test as well as Heaven Benchmark 4.8 and OCCT.

No errors.

I am really out of options now...
 

Colif

Win 10 Master
Moderator
can you go to C:\Windows\Minidump
Open Windows File Explorer

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .
 
Jan 30, 2021
6
0
10
0
can you go to C:\Windows\Minidump
Open Windows File Explorer

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .
 

gardenman

Admirable
Moderator
I ran the dump files through the debugger and got the following information: https://jsfiddle.net/uecx97rp/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:020721-19812-01.dmp (Feb 6 2021 - 19:00:02)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for ene.sys
*** WARNING: Unable to verify timestamp for aswSP.sys
Probably caused by:ene.sys (Process: sdiagnhost.exe)
Uptime:0 Day(s), 17 Hour(s), 19 Min(s), and 25 Sec(s)

File information:013121-20326-01.dmp (Jan 30 2021 - 21:16:14)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for ene.sys
*** WARNING: Unable to verify timestamp for aswSP.sys
Probably caused by:ene.sys (Process: sdiagnhost.exe)
Uptime:4 Day(s), 6 Hour(s), 32 Min(s), and 46 Sec(s)

File information:012421-20748-01.dmp (Jan 24 2021 - 04:47:38)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for ene.sys
*** WARNING: Unable to verify timestamp for aswSP.sys
Probably caused by:ene.sys (Process: smss.exe)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 35 Sec(s)

File information:010921-21309-01.dmp (Jan 9 2021 - 10:18:08)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for ene.sys
*** WARNING: Unable to verify timestamp for aswSP.sys
Probably caused by:ene.sys (Process: smss.exe)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 14 Sec(s)
Possible Motherboard page: https://www.gigabyte.com/Motherboard/B450M-DS3H-rev-1x#kf
You are on BIOS F1. If you are using Revision 1 of the motherboard, there are 14 BIOS updates available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
I can't say I ever seen one BSOD blame 2 files, and yet it happened 4 times for you

ene.sys = rgb drivers.
aswSP.sys = Avast

I would uninstall Avast and maybe update rgb fusion

your lan drivers are from 2016, that might set off Avast
download 3rd driver under the Windows header - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software

wonders what this is for
Feb 08 2011VirtDiskBus64.sys3TB+ Unlock Bus Enumerator driver (Giga-Byte Technology CO., LTD.)
 
Jan 30, 2021
6
0
10
0
Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
Not sure if it is rev.1x as i do not have a document about it, the mainboard itself just says: B450M-DS3H
i would have to visit my cellar to fine the package if i still have that
 

gardenman

Admirable
Moderator
As for the Revision: There is a debugger command which is new to me and it might show for some motherboards, but it doesn't for this one (probably not unusual).
6: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.8, DMIVersion 40, Size=2285]
BiosMajorRelease = 5
BiosMinorRelease = 13
BiosVendor = American Megatrends Inc.
BiosVersion = F1
BiosReleaseDate = 06/06/2018
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = B450M DS3H
SystemFamily = Default string
SystemVersion = Default string
SystemSKU = Default string
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = B450M DS3H-CF
BaseBoardVersion = x.x
As Colif said, it should be on the board (top/left). This might help:
https://www.gigabyte.com/Support/FAQ/864
 

Colif

Win 10 Master
Moderator
its right on the corner. If you on that version, update the bios (NOTE TO EVERYONE - There is only 1 revision, he can't be on any other board)

However, you need to do it in a particular order
1. Update chipset drivers to latest version - https://www.gigabyte.com/Motherboard/B450M-DS3H-rev-1x/support#support-dl-driver-chipset
2, Install BIOS version F32 - https://www.gigabyte.com/Motherboard/B450M-DS3H-rev-1x/support#support-dl-bios
  1. Install BIOS version F40
  2. Install F60
 
Thread starter Similar threads Forum Replies Date
V Systems 29
Similar threads
[SOLVED] ntoskrnl BSOD

ASK THE COMMUNITY

TRENDING THREADS