netflix forcing pc restart

Netflix is not software. If it is the app from the Windows Store, then it id something from changes that you have made that are causing this or hardware issues. Dump logs do not lie.

All the evidence points to a graphics problem, either with the driver or the card. In your position I would run a graphics stress test using something like FurMark to find out wether this is graphics instability - as the evidence suggests.

ubuysa said:

All the evidence points to a graphics problem, either with the driver or the card. In your position I would run a graphics stress test using something like FurMark to find out wether this is graphics instability - as the evidence suggests.

why every game runs fine at ultra settings? prime video runs fine. Its only netflix

Who knows? All we can tell you is where the hard evidence is pointing. Not only that, but graphics driver problems are amongst the commonest source of BSODs. I still suggest you run a stress test on your graphics card and driver.

tushar4544 said:

why every game runs fine at ultra settings? prime video runs fine. Its only netflix

are you using netflix the app or netflix in a browser?

if the app, try the browser and send a bug report to netflix.

if the browser, try the app and send a bug report to whatever browser maker you are using

tomdsr said:

video driver caused it, your video driver is from last year. the current one from feb of this year is here.

relevant info highlighted below

ok so i was browsing edge browser and suddenly after closing it, Pc hanged and then restarted. Here is v2 log file link

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

The May 15th BSOD was caused when an exception occurred whilst handling a previous exception (an exception double-fault). This was also caused by your graphics driver nvlddmkm.sys...

Code:

1: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffd281`de2cdd28 fffff805`4400fd29     nt!KeBugCheckEx
01 ffffd281`de2cdd30 fffff805`4400a43d     nt!KiBugCheckDispatch+0x69
02 ffffd281`de2cde70 fffff805`6f6e320b     nt!KiDoubleFaultAbort+0x2bd
03 ffffb902`08e28e70 00000000`00000000     nvlddmkm+0x9320b

I can see that you have updated the graphics driver since the last set of BSODs, which might suggest that the problem lies with the graphics card itself. However, in your system log I can see you installing the PunkBuster anti-cheat tool, a couple of seconds later there is a failure in the graphics card driver, followed by a series of error messages for nvlddmkm.sys.

Code:

Event[7365]:
  Log Name: System
  Source: Service Control Manager
  Date: 2023-05-11T18:43:25.6640000Z
  Event ID: 7045
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-LQSPC3M
  Description: 
A service was installed in the system.

Service Name:  PnkBstrB
Service File Name:  C:\Windows\system32\PnkBstrB.exe
Service Type:  user mode service
Service Start Type:  auto start
Service Account:  LocalSystem

Event[7366]:
  Log Name: System
  Source: Display
  Date: 2023-05-11T18:45:49.3200000Z
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-LQSPC3M
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.

Event[7367]:
  Log Name: System
  Source: nvlddmkm
  Date: 2023-05-11T18:45:48.4230000Z
  Event ID: 0
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-LQSPC3M
  Description: 
N/A

All anti-cheat tools have been observed causing BSODs. I would suggest that you uninstall PunkBuster and see whether these BSODs stop.

This could potentially also be a problem with your graphics card. If uninstalling PunkBuster (an any other anti-cheat tools) doesn't stop the BSODs then try temporarily pluging your monitor into the motherboard and use the iGPU in your Intel processor. Graphics performance will be dire of course, but if there are no BSODs then it's your graphics card that's at fault.

ubuysa said:

The May 15th BSOD was caused when an exception occurred whilst handling a previous exception (an exception double-fault). This was also caused by your graphics driver nvlddmkm.sys...

Code:

1: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffd281`de2cdd28 fffff805`4400fd29     nt!KeBugCheckEx
01 ffffd281`de2cdd30 fffff805`4400a43d     nt!KiBugCheckDispatch+0x69
02 ffffd281`de2cde70 fffff805`6f6e320b     nt!KiDoubleFaultAbort+0x2bd
03 ffffb902`08e28e70 00000000`00000000     nvlddmkm+0x9320b

I can see that you have updated the graphics driver since the last set of BSODs, which might suggest that the problem lies with the graphics card itself. However, in your system log I can see you installing the PunkBuster anti-cheat tool, a couple of seconds later there is a failure in the graphics card driver, followed by a series of error messages for nvlddmkm.sys.

Code:

Event[7365]:
  Log Name: System
  Source: Service Control Manager
  Date: 2023-05-11T18:43:25.6640000Z
  Event ID: 7045
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-LQSPC3M
  Description: 
A service was installed in the system.

Service Name:  PnkBstrB
Service File Name:  C:\Windows\system32\PnkBstrB.exe
Service Type:  user mode service
Service Start Type:  auto start
Service Account:  LocalSystem

Event[7366]:
  Log Name: System
  Source: Display
  Date: 2023-05-11T18:45:49.3200000Z
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-LQSPC3M
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.

Event[7367]:
  Log Name: System
  Source: nvlddmkm
  Date: 2023-05-11T18:45:48.4230000Z
  Event ID: 0
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-LQSPC3M
  Description: 
N/A

All anti-cheat tools have been observed causing BSODs. I would suggest that you uninstall PunkBuster and see whether these BSODs stop.

This could potentially also be a problem with your graphics card. If uninstalling PunkBuster (an any other anti-cheat tools) doesn't stop the BSODs then try temporarily pluging your monitor into the motherboard and use the iGPU in your Intel processor. Graphics performance will be dire of course, but if there are no BSODs then it's your graphics card that's at fault.

maybe gtx 1650 is not enough for 32 inch 4k 60hz monitor?

The graphics card is perfectly adequate, that's not the problem.

As I wrote above, PunkBuster is way more likely to be involved. Although it doesn't appear in the dump it does appear in the System log, two seconds later you get a graphics driver problem. That's a big clue right there.

Perhaps I wasn't being very clear, I strongly suggest that you uninstall PunkBuster, and any other anti-cheat tools that you have installed, and then see how stable the system is. It's only if it continues to BSOD, with no anti-cheat tools installed, that you might suspect the graphics card.

i play multiplayer games like battlefield 3 and 4, so punkbuster is necessary to be running