Skip to content

Blue Screen of Death (Windows 10) #8848

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

Closed
ShamanFromSiberia opened this issue Jul 28, 2020 · 7 comments
Closed

Blue Screen of Death (Windows 10) #8848

ShamanFromSiberia opened this issue Jul 28, 2020 · 7 comments
Assignees
Labels
bug platform/windows Windows specific issues

Comments

@ShamanFromSiberia
Copy link

Describe the bug
Running Postman on my Windows 10 laptop always leads to system crash with the blue screen of death. Also there're some annoying graphic artifacts between crashes.The artifacts and blue screens could be seen in the screenshots section below. There are three BSD error codes so far: MEMORY_MANAGEMENT, BAD_POOL_CALLER, KMODE_EXCEPTION_NOT_HANDLED

To Reproduce
It happens unexpectedly, with only one condition - Postman window is active. Graphioc artifacts are there constantly, just moving from one place to another.
Please don't blame my graphic adapter or drivers - all is checked and every other program works fine.

Expected behavior
There should be stable working process without artifacts and blue screens. Every other application on my laptop works smoothly.

Screenshots
Artifacts: {469A59A3-F706-4F08-8CFE-922C3B6E9D9F} png
BSD MEMORY_MANAGEMENT: photo_2020-07-28_21-11-39
BSD BAD_POOL_CALLER: photo_2020-07-28_21-11-45
BSD KMODE_EXCEPTION_NOT_HANDLED: photo_2020-07-28_21-11-33

App information (please complete the following information):

  • Native App
  • Postman v7.29.1
  • OS: Windows 10 1909

Additional context
Laptop ASUS N56DY

@kamalaknn
Copy link
Member

kamalaknn commented Aug 3, 2020

Hey @ShamanFromSiberia

  1. Could you forward the logs from View -> Developer -> View logs in Explorer to [email protected], to help us debug the issue better?

  2. Could you try launching Postman with GPU disabled? You can find the steps to disable GPU here

@ShamanFromSiberia
Copy link
Author

  1. Is it possible to access the logs out of Postman?

  2. I'll try it and will let you know of the results.

@kamalaknn
Copy link
Member

@ShamanFromSiberia You can find the logs in C:\Users\<user>\AppData\Roaming\Postman directory.

@ShahinKohan

This comment has been minimized.

@numaanashraf
Copy link
Member

@ShamanFromSiberia

We haven't gotten a response to further triage and debug this issue. With the information that is currently in the issue, we don't have enough details to take action. I'm going to close this but don't hesitate to reach out if you have or find the answers we need, we'll be happy to reopen the issue.

@zhiyong-ft
Copy link

Please let me know what information you need. I think I am running into the same issue now, can help gather whatever information you guys need.

@jviotti
Copy link

jviotti commented Jul 1, 2021

Does the issue remain if you disable "Hardware Acceleration" from the "Help" menu? If you can't manage to access this setting before it crashes, can you run setx POSTMAN_DISABLE_GPU 1 on a cmd.exe instance and then run the application?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug platform/windows Windows specific issues
Projects
None yet
Development

No branches or pull requests

8 participants