6 ms·

I would not recommend opening the linked PDF file. The link above to the PDF file is causing a BSoD on my fully patched Windows 10 sandbox. I've tested it three

by Randor 6y ago

I would not recommend opening the linked PDF file. The link above to the PDF file is causing a BSoD on my fully patched Windows 10 sandbox. I've tested it three times, firing up WinDbg to see if I can locate the cause.

raxxorrax 6y ago
And the author knows about hacking hardware! Cannot confirm this however, I am still on 1903 though.
deleted 6y ago
[deleted]
taneq 6y ago
What are you opening it in?
- Shared404 6y ago
  Do not know what GP is opening it in, but it appears to be causing issues for GitHub's renderer.
  - wltprgm 6y ago
    The last time I opened a pdf file in Chrome/Firefox in Github PDF renderer, the computer ran out of RAM. The pdf file I opened definitely didn't require so much RAM at all. Alternative solution: download and open it locally
chrisstan 6y ago
PDF works fine with chrome browser internal pdf viewer.
- jve 6y ago
  Win 10 v2004 and Chrome viewer works. Also saw first 2 pages listed on github before I hit download.
mrfredward 6y ago
Poorly behaved graphics drivers maybe? It would be quite a surprise to see an intentional exploit used on a pdf with such a narrow appeal.
mmm_grayons 6y ago
Crashed my Firefox on Android, too.
pabs3 6y ago
Hmm, works fine on Linux with evince. Sounds like a pretty serious Windows kernel bug?
- dialamac 6y ago
  Or just maybe the poster has bad memory or other faulty hardware... oh but of course much more likely there’s a kernel more bug in Windows.
AceJohnny2 6y ago
No problem on Firefox 82.0b1 on Windows 10 19041.508
ColanR 6y ago
Working fine for me on Win 10 and firefox.
colejohnson66 6y ago
Isn’t Windows not supposed to blue screen from user applications? Only kernel level stuff should crash it. Someone else mentioned that it could be graphics drivers?
- fulafel 6y ago
  Sure, assuming no bugs. Always a safe assumption :)
- _0ffh 6y ago
  I thought they threw the GFX drivers out of the kernel quite some time ago, exactly for the reason that they were causing too many blue screens?

by Randor 6y ago

raxxorrax 6y ago

And the author knows about hacking hardware! Cannot confirm this however, I am still on 1903 though.

deleted 6y ago

[deleted]

taneq 6y ago

What are you opening it in?

Shared404 6y ago
Do not know what GP is opening it in, but it appears to be causing issues for GitHub's renderer.
- wltprgm 6y ago
  The last time I opened a pdf file in Chrome/Firefox in Github PDF renderer, the computer ran out of RAM. The pdf file I opened definitely didn't require so much RAM at all. Alternative solution: download and open it locally

chrisstan 6y ago

PDF works fine with chrome browser internal pdf viewer.

jve 6y ago
Win 10 v2004 and Chrome viewer works. Also saw first 2 pages listed on github before I hit download.

mrfredward 6y ago

Poorly behaved graphics drivers maybe? It would be quite a surprise to see an intentional exploit used on a pdf with such a narrow appeal.

mmm_grayons 6y ago

Crashed my Firefox on Android, too.

pabs3 6y ago

Hmm, works fine on Linux with evince. Sounds like a pretty serious Windows kernel bug?

dialamac 6y ago
Or just maybe the poster has bad memory or other faulty hardware... oh but of course much more likely there’s a kernel more bug in Windows.

AceJohnny2 6y ago

No problem on Firefox 82.0b1 on Windows 10 19041.508

ColanR 6y ago

Working fine for me on Win 10 and firefox.

colejohnson66 6y ago

Isn’t Windows not supposed to blue screen from user applications? Only kernel level stuff should crash it. Someone else mentioned that it could be graphics drivers?

fulafel 6y ago
Sure, assuming no bugs. Always a safe assumption :)
_0ffh 6y ago
I thought they threw the GFX drivers out of the kernel quite some time ago, exactly for the reason that they were causing too many blue screens?