Windows 10: BSOD while surfing with chrome of youtube

Dear all,
Merry Christmas to you!
I am geeting very frequent "dcp watchdog violation" BSODs while browsing the web, watching youtube or playing video of any sort. Here are the files for the errors that reliability report of windows 10 :
https://1drv.ms/f/s!Asmz5_w6vGbY00qKfTJRQwIak2q4

:)

 

IRQL_NOT_LESS_OR_EQUAL Windows 10 stop code 0x0000000A

I have also noticed it will BSOD when I use Itunes sometimes. Sometimes when I use Youtube and Chrome at the same time. When we use Netflix and chrome sometimes it BSOD. Once in awhile when I restart it it will automatically BSOD.

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (Netwbw02.sys)

BSOD while using Youtube or watching videos on IE or Chrome. I'm using Windows 10. I bought Dell i7567 Inspiron. I had this BSOD and got my laptop replaced. After one week of use the new laptop has same BSOD. This happens only while watching Videos.

I tried reinstalling OS, Updating Drivers, contacted Dell and they updated drivers manually and nothing has worked. Any idea on how to resolve this ?

 

Please use the BSOD posting instruction to provide the Dumpfile BSOD - Posting Instructions - Windows 10 Forums

 

OP updated.
Apologies and thank you!
Merry Christmas mate!

 

The last dumpfile blames your geforce drivers but in both dumpfiles also a few mentioning of HAL= hardware abstraction layer appears.
Code: STACK_TEXT: 94703274 81b51d1e 00000133 00000001 00001e00 nt!KeBugCheckEx 947032a4 81a4408c 00030fdd 00000002 00000000 nt! ?? ::FNODOBFM::`string'+0x9eb2 94703370 8203c6b7 94dfa577 00000000 9470349c nt!KeClockInterruptNotify+0x36c 94703380 8204dcdb 00000002 000000d1 00000000 hal!HalpTimerClockInterruptCommon+0x3f 94703380 94dfa577 00000002 000000d1 00000000 hal!HalpTimerClockInterrupt+0x1f7 WARNING: Stack unwind information not available. Following frames may be wrong. 9470348c ca68baa8 0000000b ca68bbd0 947034b8 nvlddmkm+0xba577 9470349c 95558262 00000000 00000070 ca68baa8 0xca68baa8 947034b8 94e5e2a7 00000000 00000000 91b7e000 nvlddmkm+0x818262 94703594 94e0a1bf 947036d4 ca68b008 ca68baa8 nvlddmkm+0x11e2a7 94703608 94e09c3a 947036d4 00000000 91b7e000 nvlddmkm+0xca1bf 947036b4 94e0a842 947036d4 91b7e000 94703c38 nvlddmkm+0xc9c3a 94703b80 94d96471 94703c38 00000000 94703c38 nvlddmkm+0xca842 94703ba0 93074cef 94d9636f ca68b008 a2827000 nvlddmkm+0x56471 94703bcc 93024a52 94703c38 94703c90 9688724c dxgkrnl!ADAPTER_RENDER:diSubmitCommandVirtual+0x7f 94703bd8 9688724c a2826008 94703c38 00000001 dxgkrnl!ADAPTER_RENDER_DdiSubmitCommandVirtual+0x10 94703c90 968adeea a2827000 b18c1d58 ca682920 dxgmms2!VidSchiSendToExecutionQueue+0x50c 94703d58 968d2b12 00000000 a2832b80 00000000 dxgmms2!VidSchiSubmitRenderVirtualCommand+0x39a 94703d78 81a30f58 a2827000 901eb798 00000000 dxgmms2!VidSchiWorkerThread+0x224 94703db0 81b44445 968d28ee a2827000 00000000 nt!PspSystemThreadStartup+0x4a 94703dbc 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x15 STACK_TEXT: 827bdb74 81965cce 00000133 00000000 00000501 nt!KeBugCheckEx 827bdba4 8185808c 0016f536 00000002 827bdc00 nt! ?? ::FNODOBFM::`string'+0x9e62 827bdc70 81e506b7 8185a64f 827bdc90 827bddf0 nt!KeClockInterruptNotify+0x36c 827bdc80 81e61cdb 827bdc02 000000d1 00000000 hal!HalpTimerClockInterruptCommon+0x3f 827bdc80 8185a64f 827bdc02 000000d1 00000000 hal!HalpTimerClockInterrupt+0x1f7 827bdd88 81870ffa 000001f4 c97eb8bc d0dca2a7 nt!KxWaitForSpinLockAndAcquire+0x1f 827bde00 8185609a 89db15f0 89db15c8 f5907a65 nt!KfAcquireSpinLock+0x2a 827bdec0 81855c59 827bdf18 00000000 beb86b80 nt!KiExecuteAllDpcs+0x20a 827bdff4 81957c5e d4e08924 00000000 00000000 nt!KiRetireDpcList+0xd9 d4e08944 81e4d861 d4e089f8 00000000 00000000 nt!KiDispatchInterrupt+0x2e d4e08958 81e61d60 00000000 d4e089f8 00000000 hal!HalEndSystemInterrupt+0xc1 d4e08958 00000000 00000000 d4e089f8 00000000 hal!HalpTimerClockInterrupt+0x27c[/quote] I assume you have installed the 32bit geforce driver version as you are running windows 10 pro 32bit.

And in the WER there are a few mentioning of
Code: +++ WER3 +++: Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type 0 Event Name: LiveKernelEvent[/quote] STOP*0x00000141: VIDEO_ENGINE_TIMEOUT_DETECTED*

Start with testing your GPUcard.
*Videotest Furmark
To test your GPU you can use Furmark see this tutorial FurMark - GPU Stress Test - Windows 10 Tutorials
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test (Looks like it's "BURN-IN test" now)
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
If the temperature gets above 100ºC, quit the test - the video card is overheating.
- Click "Quit" to exit

What you are looking for:
- excessive heat from the GPU (report back with anything over 90ºC)
- problems with the video display (picture is distorted or jumbled, picture turns black, etc)
- problems reported by the program (I haven't seen this, but "just in case")
*

 

Thank you for your input !
I suspected the GPU as well.
It kept climbing until 89 degrees Celsius but maxed out at that.
pic shows 25 mins but i let it run for 40 mins. (forgot to take new pic)
2016-12-24 (1).png

 

Le bump of desperation

 

Make sure you are you running the latest driver release for your GTX 650.

If you are still getting blue screens, try rolling back to a previous version to see if the problems persist.

It also never hurts to use compressed air to dust out your graphics card, as well as re-seating the card in the slot.

 

Currently running the latest..how can i tell which ones are the trouble free? I was always updating to the ones most up to date

 

It's largely going to be trial and error.

I'd try the last three releases: 376.19, 376.09, and 375.95.

 

Oh damn....ouch....lets get to it then...grah