Skip to content

Conflict with NVDIA driver then causing BSOD on Windows 10? #10066

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zhiyong-ft opened this issue Jun 23, 2021 · 4 comments
Open

Conflict with NVDIA driver then causing BSOD on Windows 10? #10066

zhiyong-ft opened this issue Jun 23, 2021 · 4 comments

Comments

@zhiyong-ft
Copy link

zhiyong-ft commented Jun 23, 2021

Describe the Issue

I have been fighting this BSOD problem on my laptop with I7-1165G7 + GeForce MX450. BSOD happens once every couple of days, and all were traced down to NVIDIA's driver module (Nvlddmkm.sys)via WinDbg. At first I thought this was purely a driver issue on NVDIA's part or overheat of graphic card IC. Then I recall for the last 3 times, BSOD all happened when I tried to switch to Postman (clicking on taskbar to bring it to front). And Postman has this weird concept that only discrete card counts as hardware while integrated card like Iris Xe doesn't, which by the way is pretty good. Then NVIDIA's PhyX software is set to control which graphic card to use. To me, this sound a perfect setup to cause BSOD. Postman insists on using discrete card while NVIDA's driver demands to let it select which one to use.

Steps to Reproduce

Since this is BSOD we are talking about, the following steps may reproduce the problem but I cannot guarantee.

  1. Find a computer with both integrated and discrete graphic cards. Such as those with I7-1165G7 + GeForece MX450.
  2. Enable in BIOS both graphic cards or select switchable as Lenovo called in their Ideapad 5.
  3. Leave Hardware-Accelerated GPU Scheduling as default/off in Windows 10 graphic settings.
  4. Set PhysX processor in NVIDIA's control panel as default/auto select.
  5. Start Postman with default Hardware Acceleration checked.
  6. Do other stuff like goofy around Internet in general or Reddit.
  7. Click on Postman in taskbar to bring it front.
  8. Repeat step 6 and 7.

Screenshots or Videos

Environment Information

  • Platform Type: AMD X64, I7-1165G&+GeForece MX450
  • Postman Version: 8.6.2
  • Operating System: Windows 10 21H1

Additional Context

This may be related to another issues:
#8605
#8848

@zhiyong-ft
Copy link
Author

Just forwarded developer logs to [email protected] and timestamp of BSOD. Hope this will help somehow. Cannot believe I spent so much time on this but I guess this is part of life.

@zhiyong-ft
Copy link
Author

At this point, I am quite sure the BSODs were caused by Postman. It just happened right in front of my eyes minutes ago. The moment I clicked on Postman in taskman to bring it front, the UI started to black out then BSOD. Well played, Postman team. Well played indeed.

@zhiyong-ft
Copy link
Author

I just happened again. I am uinstalling Postman.

@michalmocarski
Copy link

Can we reproduce this? I am using Windows and have nVIDIA GPU, so if there are updated repro steps I could try investigating this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants
@jviotti @zhiyong-ft @DannyDainton @michalmocarski and others