[SOLVED] Trying to determine root cause of rather regular BSODs.

esbowman

Distinguished
Mar 29, 2012
18
1
18,515
0
I can't figure out what the issue is, but I'm having fairly regular BSODs at inopportune times. Have had important zoom meetings and work lost due to BSODs. I'm at my boiling point with this rig, but would like to get advice before I part it out and build new.

First off, the specs:
Motherboard: ASUS Rampage V Edition 10 running version 2101 BIOS
CPU: i7 6850K 3.6GHz
RAM: 128GB DDR4 / Using XMP profile
OS Drive: Samsung Pro nvme...can't remember specific model
Projects Drive: Samsung SSD Pro...again...not sure specific model.
GPU: Actually have 3 currently, but have tried multiple configurations, and each card independently. Currently have 2 x 1080tis, and 1 x 2080 installed with Nvidia Studio Driver v451.77
PS: EVGA Supernova 1300 G2 (went large, as I had 4 GPUs installed a year ago)
Windows Version: Windows 10 Pro 64bit, Build 19042.572, version 20H2 and Windows Feature Experience Pack 120.2212.31.0

Errors:
Here is a copy/paste from the last crash (using BlueScreenViewer):
Code:
110320-23421-01.dmp    11/3/2020 9:51:46 AM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    fffff807`4abfe8c0    00000000`00000002    00000000`00000000    fffff806`56b244e1    ntoskrnl.exe    ntoskrnl.exe+3f45a0    NT Kernel & System    Microsoft® Windows® Operating System    Microsoft Corporation    10.0.19041.572 (WinBuild.160101.0800)    x64    ntoskrnl.exe+3f45a0                    C:\WINDOWS\Minidump\110320-23421-01.dmp    12    15    19041    2,634,548    11/3/2020 9:53:12 AM
Every single crash has been associated with ntoskrnl.exe, and it typically states IRQL_NOT_LESS_OR_EQUAL, or DPC WATCHDOG VIOLATION. From what I'm reading on the errors (and going to the links from the QR code on the BSOD) it could be anything from drivers to bad hardware.

What I've tried:
  • Removed each individual memory module and used MemTest on a flash drive to verify/test each module. All have passed the test in slot 1.
  • Ran each GPU in other machines, independently, and in different configurations. They all seem totally fine.
  • Updated to the latest version of Windows 10, and used their new driver updating tool which found a number of new updated drivers. Was hopeful this would fix it, but the errors are still happening.
  • Turned off all overclocking in the BIOS of the ASUS board.
  • Tried the last 5 or 6 Nvidia Studio Driver versions, using clean installs for each version. Landed on 451.77 based on colleagues suggesting it for Redshift and Octane use.
When do the crashes happen?:
It varies. It crashes sometimes when I'm on a video call, other times in the middle of a complex C4D 3D scene, or After Effects project. Sometimes it crashes overnight when I'm literally doing nothing and no apps are running. There seems to be no rhyme or reason.

Advice?
Would love to know a few other things I can try to start narrowing down if this is truly a software/driver related issue or bad hardware. I'm in need of an upgrade, but until I can get my hands on a 3080 or 3090 I'm going to see if I can make this rig more reliable in the meantime.

Thanks so much!
 

gardenman

Admirable
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/0hfredms/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:110320-23421-01.dmp (Nov 3 2020 - 10:51:46)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:3 Day(s), 20 Hour(s), 42 Min(s), and 42 Sec(s)

File information:103020-23250-01.dmp (Oct 30 2020 - 14:08:16)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 4 Hour(s), 52 Min(s), and 54 Sec(s)

File information:102620-23890-01.dmp (Oct 26 2020 - 17:41:06)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:4 Day(s), 21 Hour(s), 24 Min(s), and 50 Sec(s)

File information:092920-20968-01.dmp (Sep 29 2020 - 16:02:07)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 18 Hour(s), 56 Min(s), and 32 Sec(s)

File information:092820-23421-01.dmp (Sep 28 2020 - 21:04:46)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 12 Hour(s), 07 Min(s), and 03 Sec(s)

File information:092820-20843-01.dmp (Sep 28 2020 - 08:56:50)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:1 Day(s), 9 Hour(s), 07 Min(s), and 58 Sec(s)

File information:092220-20515-01.dmp (Sep 22 2020 - 11:55:21)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:5 Day(s), 9 Hour(s), 00 Min(s), and 27 Sec(s)

File information:091720-22906-01.dmp (Sep 17 2020 - 02:53:57)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:8 Day(s), 0 Hour(s), 24 Min(s), and 35 Sec(s)
Crashing driver:
Oct 27 2016IntelNit.sysIntel(R) Turbo Boost Max Technology 3.0 driver

BIOS info was not included in the dump file. This can mean an outdated BIOS is being used.

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

Colif

Win 10 Master
Moderator
can you go to c:/windows/minidump
copy the files from here to another folder
upload the copies from the new folder to a file sharing website
show link here.

IRQ errors can just be drivers, we see what you have.
 

esbowman

Distinguished
Mar 29, 2012
18
1
18,515
0
Thanks Colif, as requested here is a link to a few of the mini dump files.

https://www.dropbox.com/s/5p5cp8wp2eg3afa/mini dump files.zip?dl=0

One other thing I should note, I am using an old Microsoft LifeCam Cinema Webcam. Only reason I mention it, one of my colleagues said they had issues with their webcam software causing crashes, but I wouldn't think Microsoft's own webcam would cause an issue. Also using a Wacom tablet, but don't have it (or anything) connected to the PC USB ports other than an external drive I need and a Logitech Unifying receiver.
 

gardenman

Admirable
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/0hfredms/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:110320-23421-01.dmp (Nov 3 2020 - 10:51:46)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:3 Day(s), 20 Hour(s), 42 Min(s), and 42 Sec(s)

File information:103020-23250-01.dmp (Oct 30 2020 - 14:08:16)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 4 Hour(s), 52 Min(s), and 54 Sec(s)

File information:102620-23890-01.dmp (Oct 26 2020 - 17:41:06)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:4 Day(s), 21 Hour(s), 24 Min(s), and 50 Sec(s)

File information:092920-20968-01.dmp (Sep 29 2020 - 16:02:07)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 18 Hour(s), 56 Min(s), and 32 Sec(s)

File information:092820-23421-01.dmp (Sep 28 2020 - 21:04:46)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 12 Hour(s), 07 Min(s), and 03 Sec(s)

File information:092820-20843-01.dmp (Sep 28 2020 - 08:56:50)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:1 Day(s), 9 Hour(s), 07 Min(s), and 58 Sec(s)

File information:092220-20515-01.dmp (Sep 22 2020 - 11:55:21)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:5 Day(s), 9 Hour(s), 00 Min(s), and 27 Sec(s)

File information:091720-22906-01.dmp (Sep 17 2020 - 02:53:57)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by:memory_corruption (Process: System)
Uptime:8 Day(s), 0 Hour(s), 24 Min(s), and 35 Sec(s)
Crashing driver:
Oct 27 2016IntelNit.sysIntel(R) Turbo Boost Max Technology 3.0 driver

BIOS info was not included in the dump file. This can mean an outdated BIOS is being used.

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

Colif

Win 10 Master
Moderator
Thats not fair, why can't all BSOD be so easy?

Anyway, I could bet Intel Turbo Boost Max Tech driver isn't a win 10 driver. I can't see it listed on your motherboard? wonder how it got there? Have you run any 3rd party driver updating tools?
Updated to the latest version of Windows 10, and used their new driver updating tool which found a number of new updated drivers.
what tool?

you want to uninstall it as I don't think its needed.

I can find a newer one on Dell website but not from Intel...

if you can't find a way to uninstall it, you can use autoruns to stop it from loading at startup but if anything uses it, it will load again - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
 

esbowman

Distinguished
Mar 29, 2012
18
1
18,515
0
Colif, I used the Intel driver and support assistance utility. It found two new drivers that Windows wasn't catching.

So, I've uninstalled the Turbo Max 3 software via Add / Remove programs. The i7 6850k (my cpu) supports the technology I'm pretty sure.

Now that I've rebooted after uninstalling the Turbo Boost Max 3 software, I have a question mark in Device manager > Other devices. I clicked on Properties > Hardware Ids and see this:
ACPI\VEN_INT&DEV_3510

That points right to the Turbo Boost Max 3 technology, and I found this forum post: https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware-winpc/unknown-device/68d2b626-8c47-4339-a1ab-84dd6483dbe2?page=1

If my memory serves me well, I remember noticing the hardware with a question mark when i first built the machine. I installed that software and the question mark went away. Unfortunately, I can't find anywhere to download it again, and a Windows update does nothing as well.

Additionally, I've found a few reports about this being a problematic piece of software, and some people say to disable the Intel Turbo Max tech in the ASUS BIOS. I just did that.

So, now it's annoying that I can't find the ITBM software to get rid of the question mark in device manager, but I'm also wondering if I should install it again anyway?

UPDATE: Found the Turbo Boost Max 3 driver on ASUS' site. Will install again, but keep it disabled I think. Intel doesn't have it in the download center anymore.
 
Last edited:

esbowman

Distinguished
Mar 29, 2012
18
1
18,515
0
So, I installed the version from the ASUS site since I couldn't find a newer version. Ran a search for updated drivers, and looked via Windows update as well. Says the best drivers are already installed. It does however have an exclamation now that states it was unable to start, which is probably due to me disabling it in the BIOS. I think I'll keep it that way. If I can keep that driver from running whatsoever, that would be great.
 

Colif

Win 10 Master
Moderator
well, this used to be a link to the driver - https://downloadcenter.intel.com/download/25994/Intel-Turbo-Boost-Max-Technology-3-0 but it doesn't work now

whats worse, a ? in device manager or BSOD? the software was the cause of every BSOD above, its not often they are so obvious.

First time i looked for motherbaord it took me to a local asus site that doesn't have that driver. I got sick of it as its slow, so swapped to US site and now I see it is on motherboard listing...

its a hard driver to find, not even the Intel site describing technology has it as a download choice.
 

esbowman

Distinguished
Mar 29, 2012
18
1
18,515
0
Yup, I hear ya. I think for now I'm going to leave the driver installed, but inactive. With the BIOS disabling it, I think I'll be ok. The software used to launch automatically when i started Windows 10, and that's gone now as well...probably due to it being disabled in BIOS.

If it still acts up after that, I'll remove the driver and never install again.

So far, no BSODs today. Hoping it continues that way.
 

Colif

Win 10 Master
Moderator
Windows can't change BIOS settings, drivers can change some settings (such as fan speeds, CPU speed, etc) if the feature is on in bios but I don't think they can turn on features if they off in there. Pretty sure of it in fact.
 

ASK THE COMMUNITY

TRENDING THREADS