Recently I have built a 3D rendering station for a client of mine. The machine runs, but crashes about once or twice a day with a BSOD (watchdog violation 1x133. Blue Screen View mentions either nvlddmkm.sys or ntoskrnl.exe as culprit. Things I have tried so far: Clean install Windows 10 Clean install Windows 7 DDU removal of graphics drivers latest nVidia drivers older nVidia drivers extensive RAM testing Specs: Asus X99-WS 10G E Intel 6850K 7x Zotac 1080ti Blower Edition (transformed to water cooling) 64GB RAM Samsung 960 Pro 512GB (system drive) 3x WD Red in RAID 0 (data drive) 2x Cooler Master V1200 PSU Custom EK watercooling loop Obsidian 900D Speccy Snapshot: http://speccy.piriform.com/results/qchWoHD0m7mueWTEVccxFlD Any help or insight on this issue would be greatly appreciated, as this issue now causes great delays in my client's workflow.

Thank you for this insight, very helpful to know that this is happening somewhere else as well. Regarding driver 382.53, unfortunately, it failed as well. System crashes with the difference of recovering two times before BSOD. No recovering like TDR recovery. Just hang, cursor & sound freeze, then cursor & sound back, then freeze again, then finally dies. Reverted to 378.92. Stable with Win 10 v1703. Quick question, which version of Win 10 are you running with 382.53?

Only NVIDIA can determine what's going on within its driver. That's because, besides new features, NVIDIA has to also accommodate changes made in the Windows Kernel by Microsoft. I've read that Windows 7 doesn't suffer from the same issues. Its kernel is stable and the NVIDIA driver is well tested on that OS. Windows 8, 8.1 and, now Windows 10 are a mess. There are major changes in how hardware resources are managed and application developers can't fix kernel related issues; they can only report them to Microsoft and wait for fixes to be applied in the next patch, which often breaks something else. That's the problem of continuous updates in Windows 10. We were served a half baked, buggy OS and now suffer from the consequences of poorly coordinated, continuous changes. Currently, in Windows 10, 3D rendering professionals suffer from GPU-related system crashes, and audio professionals suffer from audio dropouts and pops caused by high DPC Latency.

Yeah, I'm now well aware of the whole process, thank you! I'm now running with the 382.53 Driver, and so far, no issue with couple of Benchmark. Will know more tomorrow. Thanks! Is there a way to know what is changing / causing the issue between the different version of drivers? https://us.download.nvidia.com/Windows/382.53/382.53-win10-win8-win7-desktop-release-notes.pdf

You can use DDU utility from Windows Safe Mode, to clean you machine from current display driver files, then install the driver that you need, selecting Custom Installation and Clean Installation.

Ok thank you for your input, I'm going to test this out. I'm also wondering if maybe it has to do with the resolution. I'm using two monitors of 32' 4K (BenQ 32-Inch IPS 4K BL3201PH) on DisplayPort Cable (Cable Matters Gold Plated Cable 10 Feet) both using a different card. 1004 + 1007 https://www.amazon.com/gp/product/B00O1B5M9I/ref=oh\_aui\_search\_detailpage?ie=UTF8&psc=1 https://www.amazon.com/gp/product/B005H3Q5E0/ref=oh\_aui\_search\_detailpage?ie=UTF8&psc=1 In win 7, I'm using them at the resolution of 2560 x 1440 as the rendering in Win 7 at 150% is horrible and 125% too small. In win 10, I'm using them a the recommended resolution, 4k (3840 x 2160) with the nice rendering sharp pixel, down to 150%. Not sure if that would make a difference, but who knows? :)

PC crashing - BSOD Watchdog violation 1x133 (possibly nVidia issue)

Anonymous

Recently I have built a 3D rendering station for a client of mine. The machine runs, but crashes about once or twice a day with a BSOD (watchdog violation 1x133. Blue Screen View mentions either nvlddmkm.sys or ntoskrnl.exe as culprit.

Things I have tried so far:

Clean install Windows 10
Clean install Windows 7
DDU removal of graphics drivers
latest nVidia drivers
older nVidia drivers
extensive RAM testing

Specs:

Asus X99-WS 10G E
Intel 6850K
7x Zotac 1080ti Blower Edition (transformed to water cooling)
64GB RAM
Samsung 960 Pro 512GB (system drive)
3x WD Red in RAID 0 (data drive)
2x Cooler Master V1200 PSU
Custom EK watercooling loop
Obsidian 900D

Speccy Snapshot: http://speccy.piriform.com/results/qchWoHD0m7mueWTEVccxFlD

Any help or insight on this issue would be greatly appreciated, as this issue now causes great delays in my client's workflow.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

87 answers

Anonymous

2018-03-08T19:28:13+00:00

Thank you for this insight, very helpful to know that this is happening somewhere else as well.

Regarding driver 382.53, unfortunately, it failed as well. System crashes with the difference of recovering two times before BSOD. No recovering like TDR recovery. Just hang, cursor & sound freeze, then cursor & sound back, then freeze again, then finally dies.

Reverted to 378.92. Stable with Win 10 v1703.

Quick question, which version of Win 10 are you running with 382.53?
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-08T07:40:43+00:00

Only NVIDIA can determine what's going on within its driver. That's because, besides new features, NVIDIA has to also accommodate changes made in the Windows Kernel by Microsoft.

I've read that Windows 7 doesn't suffer from the same issues. Its kernel is stable and the NVIDIA driver is well tested on that OS.

Windows 8, 8.1 and, now Windows 10 are a mess. There are major changes in how hardware resources are managed and application developers can't fix kernel related issues; they can only report them to Microsoft and wait for fixes to be applied in the next patch, which often breaks something else.

That's the problem of continuous updates in Windows 10. We were served a half baked, buggy OS and now suffer from the consequences of poorly coordinated, continuous changes.

Currently, in Windows 10, 3D rendering professionals suffer from GPU-related system crashes, and audio professionals suffer from audio dropouts and pops caused by high DPC Latency.
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-08T07:27:46+00:00

Yeah, I'm now well aware of the whole process, thank you!

I'm now running with the 382.53 Driver, and so far, no issue with couple of Benchmark. Will know more tomorrow. Thanks!

Is there a way to know what is changing / causing the issue between the different version of drivers?

https://us.download.nvidia.com/Windows/382.53/382.53-win10-win8-win7-desktop-release-notes.pdf
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-08T07:15:32+00:00

You can use DDU utility from Windows Safe Mode, to clean you machine from current display driver files, then install the driver that you need, selecting Custom Installation and Clean Installation.
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-08T06:30:40+00:00

Ok thank you for your input, I'm going to test this out.

I'm also wondering if maybe it has to do with the resolution.

I'm using two monitors of 32' 4K (BenQ 32-Inch IPS 4K BL3201PH) on DisplayPort Cable (Cable Matters Gold Plated Cable 10 Feet) both using a different card. 1004 + 1007

https://www.amazon.com/gp/product/B00O1B5M9I/ref=oh\_aui\_search\_detailpage?ie=UTF8&psc=1

https://www.amazon.com/gp/product/B005H3Q5E0/ref=oh\_aui\_search\_detailpage?ie=UTF8&psc=1

In win 7, I'm using them at the resolution of 2560 x 1440 as the rendering in Win 7 at 150% is horrible and 125% too small.

In win 10, I'm using them a the recommended resolution, 4k (3840 x 2160) with the nice rendering sharp pixel, down to 150%.

Not sure if that would make a difference, but who knows? :)
Was this answer helpful?

0 comments No comments