Can you replicate the issue in Incognito window with all of your scripts and extensions/VPN turned off?

I'll give it a go today.

Yep, still crashed just now.

Incognito, all extensions off. Just sitting there on the scamming page.

I >thought< it was tired to actually having a scam read and in progress but i was only searching for new scams and... black screen.

So weird.

Can you please check what errors are showing up in your browser console?

The crash this morning didn't even show up (as is usually the case with these because chrome has no chance to write anything).

Ok, newest weird wrinkle...

Scamming page in Edge... runs fine. Open for hours with no issues.

Fine, maybe chrome is the issue?

Scamming page in Edge... Chrome open WITHOUT TORN... Runs fine for hours.

But...

The INSTANT I open Torn in Chrome (https://www.torn.com/index.php not the scamming page)... >>POOF!< BSOD/shutdown.

Like... the windows BSOD??

If so, that's a bug much deeper than torn itself, either chrome or windows or something in between. Try reinstall chrome and see if that fixes the issue? I get it's a pain, but a site shouldn't be able to BSOD your computer at all...

What stopcode are you getting?

Sorry... BLACK SCREEN... not Blue Screen. So most of the time the only code is after the fact complaining about a "no power button shutdown".

And yeah, I get you. I'm a CS nerd (BS in CS, MS in Cyber, A+ Sec+ CISSP... blah blah blah) I've had the machine level courses web dev courses, etc... 

I know this machine has got some underlying power issues. Windows SHOULD "sacrifice" Chrome to save itself. But some weird ass shit is going on for it to ONLY happen on torn.com scamming page AND ONLY when Chrome is running (regardless of what browser scamming page is open on).

PLENTY of other people complain about how laggy it is so it's not JUST my buggy ass machine.

I'm pretty sure it's something with the graphic background and how chrome accesses the video card. Because the crash happens even with no scams going.

I am at a loss as to why scamming on Edge + Torn on Chrome (any Torn page) = crash. But I never went deep enough into web design and resource calls and all that. I'm just testing different stuff to see what triggers it.

I did reinstall Chrome. When I saw the bug wouldn't replicate in Edge (or mobile Chrome).

SEEMS like it's Chrome's GPU pipeline.

chatGPT FTW: Bottom Line: You're likely dealing with a Chrome → GPU → WebGL rendering issue specific to that Torn page's content.

This seems to have stopped the bug for the moment (scamming page open right now on Chrome):

Step 1: Disable Chrome Hardware Acceleration

• In Chrome:

  • Go to: chrome://settings/system

  • Disable "Use hardware acceleration when available"

  • Restart Chrome.

• Then try loading the Torn page again.

👉 If this resolves it — it's very likely a GPU rendering issue specific to Chrome's hardware acceleration path.

Highly likely root cause:

Chrome, with hardware acceleration enabled, was tripping over some combination of:

• Chromium’s WebGL / ANGLE rendering pipeline

• NVIDIA’s Laptop Ada driver (4080 mobile GPUs have a few known quirks esp. with dynamic power switching)

• Windows 11's new GPU Hardware Scheduling (HAGS) + WDDM 3.2+ stack

• Torn.com’s rendering (possibly heavy dynamic canvas or WebGL-based rendering on that scamming page)

The interaction between Chromium → ANGLE (DirectX backend) → NVIDIA Optimus/Dynamic MUX → Windows 11 HAGS is where this kind of thing tends to happen.

Why Edge works:

Even though Edge is Chromium-based, Microsoft ships a slightly different graphics pipeline with more fallback paths, and it may handle memory/resource contention differently than Chrome’s pure upstream Chromium build.

TLDR: Hey Torn, could we have a "disable fancy rendering" button? Cause it makes the page laggy as heck, even for a BEAST of a system.

edit: I'm just going to leave HW accel off for now... I doubt anything I do on the web really NEEDS it, and a game touted as being lightweight/easily accessible certainly shouldn't NEED it.

Holy shit, you did good writing this up as I’m ridiculously invested in this now 🍿🍿🍿

ChatGPT did the heavy lifting

FYI... D3D9 seems to be working

D3D9 DID NOT WORK... just made it take a little longer to crash.

My expert recommendation for your exact situation:

Since D3D11 (default) is where the bug appeared, and OpenGL isn’t stable on Windows Chromium:

Test path:

1️⃣ Try forcing D3D9 first:

• This is your "most likely to fix it" candidate.

• D3D9 is often surprisingly stable when there’s a Chromium → NVIDIA → DirectX 11 pipeline bug.

2️⃣ If D3D9 works without black screening, great — you’ve found a working config.

3️⃣ If D3D9 fails or causes rendering issues, try D3D11on12 next:

• D3D11on12 is Chromium's more experimental rendering backend.

• On Windows 11 + Ada GPUs + WDDM 3.2, it can sometimes work better than D3D11 — or worse (depends on your driver).

• Your hardware fully supports this path.

Where's the setting

chrome://flags/

(WARNING TO OTHERS... YOU CAN SERIOUSLY MESS UP CHROME IN FLAGS!!!)

"Choose ANGLE graphics backend"

Trying D311on12 now.

Best story/post in the Torn forums this month.

11on12 also fukt

No more time to mess with this right now... back to just disabling.

edit: Who TF am I kidding??

GPT's advice:

What can you do now? (The “hardening config” I promised)

1️⃣ Keep Hardware Acceleration disabled in Chrome for now.
This is fully safe; you lose very little real-world performance unless you're playing high-end video or running complex 3D web apps.

2️⃣ Stay fully updated:

• Keep NVIDIA drivers updated — especially once WHQL 555.x / 560.x branch matures.

• Monitor Chromium versions — many of these bugs are being actively worked on for M126 / M127.

3️⃣ Optional advanced workaround (works for some Ada owners):

• Disable HAGS in Windows (sometimes helps even with HW Accel on):

  • Settings → System → Display → Graphics → Default graphics settings → Hardware-Accelerated GPU Scheduling → Off

• Disable MPO (Multiplane Overlay) via registry tweak:

  • Can eliminate compositor crashes for some users.

  • Safe to try; fully reversible.

If you want — I can write you a safe script to toggle MPO on/off for testing. Many high-end laptop owners on Ada are doing this.

--

screw it... script kiddie to the rescue!