Question BSOD on occasional boot and more frequently on waking from sleep (AMD AMD Ryzen 7 2700X no overclocked)

Feb 14, 2019
16
0
10
0
I get BSOD multiple times with different type of BSOD (Kerenel excepts, Page out of index, IQL, etc). They only happens on two occurrence: When I boot and when I wake up the computer up from sleep. The first time I noticed it was much more common, so I did a fresh reinstall of Windows (The issue causing was an iTunes and iPhone driver). It reduced the amount I see the BSOD which makes sense because I always install tons of drivers and once and reboot. Second time around I installed drivers one at a time and I didnt notice it. But last 2 weeks I have started to notice them more and more.

I've done a memory test, and it came up clean. I will run another tonight and update post in the morning.
I've been monitoring my CPU voltages on boot and when waking from sleep. This is what I noticed: --on boot voltage starts at around 1.2-1.26 and then stabilizes at 1.35/1.36. --on wake the voltage spikes to 1.41+ and then jumps between 1.2 to 1.39 before stabilizing to 1.35/1.36

Specs:
CPU: AMD Ryzen 7 2700X Core Speed: 4124.0 MHz Base frequency (cores): 100.0 MHz Base frequency (ext.): 99.9 MHz
Motherboard: X470 AORUS GAMING 7 WIFI-CF (0x000006CC - 0xCA332D98)
RAM: (4 of these sticks with a total of 32GB) Memory type: DDR4
Module format: UDIMM
Manufacturer (ID): G.Skill (7F7F7F7FCD000000000000)
Size: 8192 MBytes
Max bandwidth: DDR4-2132 (1066 MHz)
GPU: MSI NVIDIA GeForce GTX 1080 (Core clock: 1708.5 MHz Memory clock: 5054.4 MHz)


DUMP Reports form the last 3 BSOD:
==================================================
Dump File : 021419-8562-01.dmp
Crash Time : 2/14/2019 9:08:20 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 000000000000017b
Parameter 2 : 00000000
00000002
Parameter 3 : 0000000000000001
Parameter 4 : fffff801
74738880
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1b1b40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.17763.253 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1b1b40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021419-8562-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 17763
Dump File Size : 1,423,140
Dump File Time : 2/14/2019 9:09:05 AM
==================================================

==================================================
Dump File : 021419-9500-01.dmp
Crash Time : 2/14/2019 9:05:10 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffffc0000005
Parameter 2 : fffff803
713bcd46
Parameter 3 : fffffc84a4489f48
Parameter 4 : fffffc84
a4489790
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+dc3e3
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.17763.1 (WinBuild.160101.0800)
Processor : x64
Crash Address : Ntfs.sys+dcd46
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021419-9500-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 17763
Dump File Size : 1,665,116
Dump File Time : 2/14/2019 9:08:09 AM
==================================================

==================================================
Dump File : 021419-8640-01.dmp
Crash Time : 2/14/2019 9:04:08 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffaf86f54d2028
Parameter 2 : 00000000
00000000
Parameter 3 : fffff80628def4e2
Parameter 4 : 00000000
00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1b3440
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.17763.253 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1b3440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021419-8640-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 17763
Dump File Size : 1,374,692
Dump File Time : 2/14/2019 9:04:55 AM
==================================================

==================================================
Dump File : 021419-9718-01.dmp
Crash Time : 2/13/2019 6:45:38 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000c0000005
Parameter 2 : fffff800
6734e890
Parameter 3 : ffffdb0640cdded0
Parameter 4 : 00000000
00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+1e3c9
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.17763.1 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1b1b40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021419-9718-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 17763
Dump File Size : 1,170,988
Dump File Time : 2/14/2019 9:02:43 AM
==================================================

Mini Dumps: https://drive.google.com/drive/folders/1ZrnOXFakK6ML61GGL-D8gEEkmPBdvnGd?usp=sharing
 
Last edited:

Colif

Win 10 Master
Moderator
is ram on Asus web site for motherboard?

Likely to be driver errors.

Can you follow option one on the following link - here

and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read
 
Feb 14, 2019
16
0
10
0
is ram on Asus web site for motherboard?

Likely to be driver errors.

Can you follow option one on the following link - here

and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read
What do you mean on Asus website?

I'll follow those steps. I do have the DUMP files which the text at the bottom of the post were generated from. I'll follow those steps and create minidump and upload them on next BSOD
 

gardenman

Admirable
Herald
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/9Lwc.html

File information:021919-9187-01.dmp (Feb 19 2019 - 18:54:45)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: DisplayFusion.)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 42 Sec(s)

File information:021919-8859-01.dmp (Feb 19 2019 - 18:50:35)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: OAWrapper.exe)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 27 Sec(s)

File information:021919-11765-01.dmp (Feb 19 2019 - 18:49:37)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:USBXHCI.SYS (Process: System)
Uptime:4 Day(s), 7 Hour(s), 25 Min(s), and 51 Sec(s)

Possible Motherboard page: https://www.gigabyte.com/Motherboard/X470-AORUS-GAMING-7-WIFI-rev-10#kf
There are 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).

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.
 

Colif

Win 10 Master
Moderator
So i normally look at old drivers (anything before July 2015 isn't a win 10 driver), not saying its to blame but this sure is getting old now
Mar 12 2009 gdrv.sys GIGABYTE Tools (motherboard and graphics cards) driver

almost its 10th birthday soon. It maybe part of a Gigabyte App center whihc you can run to check updated drivers

Sep 27 2016 ScpVBus.sys Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver http://forums.pcsx2.net/

can cause BSOD - and I see one of yours is the USB drivers, so I would look at this.

though a USB based error could be the below ones as well
Dec 12 2016 iLokDrvr.sys USB iLok Device Driver (PACE Anti-Piracy, Inc.)
Jul 31 2018 audientusbaudio.sys Audient USB Audio driver
Jul 31 2018 audientusbaudioks.sys Audient USB Audio driver
Sep 25 2018 ksUSBa64.sys Sound BlasterX Katana USB driver (Creative Technology Ltd.)

BIOS update could help as well.

Perhaps update your chipset driver as it seems to be dated 2016 - https://www.gigabyte.com/Motherboard/X470-AORUS-GAMING-7-WIFI-rev-10#support-dl-driver-chipset
 

gardenman

Admirable
Herald
I ran the dump file through the debugger and got the following information: https://pste.eu/p/Kuus.html

File information:022319-9671-01.dmp (Feb 23 2019 - 10:26:54)
Bugcheck:INTERRUPT_EXCEPTION_NOT_HANDLED (3D)
Probably caused by:nvlddmkm.sys (Process: System)
Uptime:2 Day(s), 20 Hour(s), 28 Min(s), and 20 Sec(s)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.
 
Feb 14, 2019
16
0
10
0
Update:

After fresh install, got another DUMP. PC started to act up right after I installed my current version of nVidia driver. IT wasn't having any issues prior to that. I'll post dump tonight if I can get access to it .
 

gardenman

Admirable
Herald
It may be a few days before Colif can reply. Maybe someone else will jump in and help out before then. I'll go ahead and post the dump info.

Debugger Results: https://pste.eu/p/tHbn.html

File information:022719-6937-01.dmp (Feb 26 2019 - 20:21:46)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Probably caused by:ntkrnlmp.exe (Process: svchost.exe)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 19 Sec(s)

File information:022619-6125-01.dmp (Feb 26 2019 - 19:27:15)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 10 Sec(s)

File information:022619-10046-01.dmp (Feb 26 2019 - 19:38:06)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 29 Sec(s)

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.
 

Colif

Win 10 Master
Moderator
Try running memtesst86 on each of your ram sticks, one stick at a time, up to 8 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

bsod surviving a fresh install makes me think its hardware

if you could run without the nvidia card, I would suggest it.. but you can't.

I won't be around much for 4 days as going away, but if this still going then, I sure will try to get to bottom of it.
 
Feb 14, 2019
16
0
10
0
So far tan 2 sticks through memtest86 and they are clean so far. However, I did notice that my GPU was fairly hot after running those two sticks of RAM.

I still have my old gtx 780 that I will try out after finishing the memtest. It seems its the GPU that is causing issues, and if the old GTX 780 still causes issues, I think it's the motherboard causing problem :/
 

ASK THE COMMUNITY

TRENDING THREADS