NotHereToPlayGames

Technically, I shouldn't say that PEOPLE (it implies multiple) keep INSISTING that I do not need. There is only TWO PEOPLE and they are RELENTLESS in this pursuit. Downright RELENTLESS.

Agreed! I'm honestly not finding much of anything. But I can report with 123,456,789.0% accuracy that the ONLY ONLY ONLY time that I get these FIRST LAUNCH CRASHES is when I take the advice of removing "vulkan" .dll's. That advice always comes from "users" and NEVER "developers". No offense. Again, I can only report WHAT I WITNESS. And sure, Thorium and Supermium and 360Chrome and Ungoogled are "usable" without these "vulkan" files. But I hibernate several times per day! And having to go into the OS's Task Manager to "kill" a process just to relaunch it after a CRASH is something I really have no interest in doing "for the sake of removing two .dll's that people keep insisting I do not need".

I didn't see that it was locked. Thanks. I was googling for vulkan issues on XP x64 and that thread was in the top three results.

nVidia web sites also confirm. They post a guide on configuring "power management support". Not sure if I will get around to testing, to be honest. My primary OS is now Win10. But I do have multiple XP machines, no partitions, just XP. But those computers are SSSLLLLLLOOOOOOOOOWWWWWW - when I retire, I'll have all the time in the world to sit and wait... and wait... and wait... LOL

I can report that I'm finding several LINUX reports of the same (Chrome/Chromium crashes on first launch after reboot, additional launches work just fine). The LINUX crowd is suggesting --use-gl=desktop but I suspect this to be a Linux-Only Chrome/Chromium flag. Seems to date back to Chrome v85 and only with nVidia (my home computer is nVidia). Linux crowd reports v84 to be just fine. Another suggestion is to open Chrome's "task manager" and to END TASK for GPU Process. I have not tried that, when Thorium or Supermium or 360Chrome or Ungoogled, EACH AND EVERY ONE OF THEM, crashes, I just assumed that the browser's task manager was also crashed.

Vulkan has been backported to XP and 2003 -- https://msfn.org/board/topic/176697-vulkan-backport/ Perhaps UPSTREAM has embedded these into the Chromium BASE? And anything forked from them (Thorium, Supermium, 360Chrome, Edge, Brave, Vivaldi, Opera, Ungoogled, cromite, Arc, Yandex, Kiwi, Iridium, Iron, Fulguris, Cent, you get the point) will all behave identically. I just wish that you had XP x64 so that you could WITNESS this phenomenon firsthand.

Same here. Not in my VM, but on my real hardware (I would have to verify the 2019 version or not). Thorium works for me both with these and without these.

They are required in XP x64. I will NEVER convince you otherwise. NOT my fight! I can only tell you what I have witnessed in Thorium and in 360Chrome and in Supermium and in Ungoogled. ALL OF THEM !!! XP x64 only. This is YOUR fight, not MINE. Please contact the DEVELOPER if you wish to dive deeper. Granted, my ONLY issue "when I take your advice" and remove these, the ONLY issue is FIRST LAUNCH after a reboot or coming out of hibernate. Without these, in XP x64, Thorium crashes on first launch after reboot, 360Chrome crashes on first launch after reboot, Supermium crashes on first launch after reboot, Ungoogled crashes on first launch after reboot. Again, please contact the DEVELOPER, they are there for a REASON and you ASSUME that just because Chrome-based works for YOU on YOUR system WITHOUT these, "then it must work for everyone". I can only tell you what I have witnessed. In Thorium. In 360Chrome. In Supermium. In Ungoogled. ON MY SYSTEM. In XP x64 only. Contact the developer. Ask him/her WHY these vulkan files are NEEDED for first launch after reboot or hibernate. I REALLY DON'T CARE. You are just trying to prove your "advice" correct. Your advice DOES NOT WORK in XP x64. First launch after reboot or hibernate. MY computer. Go out and buy a Dell XPS 8700, install XP x64. Or contact the developer. This "I get the last word" or "I'm always right" is kind of UNCALLED FOR.

It's definitely older and definitely on-topic.

Awesome! I'm hoping you find the root cause. I'm an engineer. My engineering mind says your issue has NOTHING to do with POSReady. If you lived within a 100-mile radius, I would personally volunteer to borrow your computer and install all of those POSReady updates ONE AT A TIME. Yes, I was under the impression that your radar was targeting POSReady as a "requirement" to run Thorium SSE2.

That's why! These "vulkan" files (as far as I have WITNESSED) are only needed for XP x64. They're not needed for XP x86. They're not needed in Vista. They're not needed in Win7. They're not needed in Win10. I do not have any 8.1 machines to test whether they are needed or not. But it is a VERY SAFE assumption that they are NOT needed based on Vista/7/10.

What OS are you running?

No, sorry, you are reading too much into it. It was only after running it for SEVERAL hours that I was able to WITNESS the NEGATIVE side effects (YouTube would pause all audio/video for half a second or so once per hour or so). This is a great flag for sessions of one-hour or LESS. But I cannot advocate "for" it for users that keep something like YouTube open for HOURS upon HOURS.

Listen, BOTH you and I are no "dummines" when it comes to computers. We BOTH know our way around computers! Firefox is a telemetry nightmare. Firefox forces the user to go through extreme firewall rules due to its "loopback" quote-unquote "feature". MOST users are CLUELESS when it comes to FIREWALL RULES SETUP (I do NOT include you in this subset of "users"). MOST users when faced with a "firewall poppup" upon launch of Firefox just click the STUPID dialog where the firewall asks "is this a WEB BROWSER" or the firewall just ASSUMES "yes, this is FIREFOX, so I'll just use default "web browser" rules. No offense to these "users", but this really is the STUPIDEST thing I have ever witnessed over the years - "just let Firefox make ANY connection it wants to, I'll accept the default firewall rules, I trust Firefox". THIS TRUST IS MISPLACED! Firefox really is the biggest telemetry nightmare I have ever come across! AND THAT INCLUDES A CHINESE/RUSSIAN REPACK OF 360CHROME !!! This "loopback" (1 byte several times each and every second) was referred to as a *BUG* in the days of Windows 2000, it's just "accepted" as 'normal behavior' by Firefox users today that DO NOT CARE (nor KNOW HOW to monitor these "loopback connections"). A CPU cycle is a CPU cycle. Make it perform a task and that means other tasks are delayed. I am NOT a Chrome/Chromium "fanboy". This world is full of "lesser of two EVILS". All OT regarding Thorium, of course. But let's be perfectly honest, if THORIUM (or 360Chrome!) made the HUNDREDS (literally!) of telemetry connections that FIREFOX does (esp FIRST LAUNCH), none of us would turn a blind eye !!! YET ALL FIREFOX USERS TURN A BLIND EYE REGARDING FIREFOX TELEMETRY CONNECTIONS !!! Firefox users "today" really are VERY different from those that used it in the 90s. Tout privacy and security but clueless that they have "sold their soul". "Do as I say, don't do as I do." But I digress...

While I have no doubts of that (I myself used to be a DIE-HARD "Firefox Only") type of computer guy, for every "2.7" of those people that you claim have switched to Firefox, I can show you 65.4 that tried Firefox, hated it, and opt for Chrome. Go to the computer store and look at the desktop icons. Especially ACER computers - for the past eight years, those ACER computers come with FIREFOX PREINSTALLED! Hasn't budged the needle one "millibtye" in Firefox's Doomsday Marketshare. Again, I myself used to be a DIE-HARD "Firefox Only" type of computer guy. Dating back to when it was called PHOENIX.

My only suggestion, if you really REALLY want to PROVE that POSReady is the REASON for Thorium WORKING on your POSReady partition, then despite the time that this will entail, you must install those POSReady updates ONE AT A TIME and test Thorium before and after each and every one of them. Scientific Method

I am HIGHLY interested in the "root cause". I am hereby on record claiming that your Thorium issus is NOT RELATED TO POSREADY. *DATA* is inconclusive, but even you as a mathematician must admit that the *DATA* is steering in that direction. Has the developer of Thorium been asked if s/he runs POSReady? Has the developer of Thorium even TESTED on SSE2?

Nobody else has the same issue. We have multiple users citing no issues with Thorium on non-POSReady. You are the ONLY one. By all means, track down WHY and keep us posted. It seems to me that perhaps a BIAS is creeping in towards POSReady being your "saviour" yet it has saved no one else.

No it isn't. You have something blocking connections to i.imgur.com. His attachments are working just fine. You cannot compare to other posts unless you are also verifying that those attachments are hosted at i.imgur.com.

I reinstall my XP at least three times per year! I know EXACTLY the state of my XP. What I'm hearing you say (if I recall correctly) is that you do NOT install this often. So no offense, but I really do not believe for one second that you can "remember" what you did to the registry 5 years ago, let alone 20. I *DO* think that something you did in your registry 20 years ago is *WHY* your POSReady is not behaving the same as your non-POSReady as far as Thorium is concerned. How many "default" browsers did you install and uninstall in those 20 years? Did they have MALFORMED registry entries such as the Thorium .reg file? (I do not use the Thorium .reg file, I have no clue if this claim of inaccuracy is correct or not.)

I really REALLY don't think it's that "easy" to deduce/conclude. Have you ever MANUALLY edited the registry in your POSReady? Have you ever ran Malwarebytes in your POSReady and it removed registry entries that a "default XP install" places there that Malwarebytes sees as "malware"? Did you REPEAT those registry tweaks/fixes/cleans/optimizations in your non-POSReady? Didn't you say your XP partition was first installed DECADES ago and that you do not reinstall often, that you can keep your XP running smooth by fixing registry entries? Don't you really have to perform "all of that" in the non-POSReady before claiming that POSReady is the "only changed variable in this multi-variable equation"?

Regarding --enable-low-end-device-mode --- I have officially ABANDONED its usage. I listen to YouTube all day long here at work and with this mode, my audio stops about once an hour for only a second or so, but IRRITATING AS H#LL. Even if I only hear 6 to 8 of those "stops" throughout a work day, that's 6 to 8 too many.

Interesting indeed. But if I am keeping track properly, there has been THREE reports of Thorium WORKING without POSReady to ONE report of Thorium NOT working without POSReady. My statistics classes in college would refer to the ONE as the OUTLIER.

It says "no" for my work computer (no surprise). Will have to see what the home computers say. My hunch is that my home i7 is also a "no" but that anything single-core is a (resounding) "yes".

I am "fairly certain" that I have tried this flag IN THE PAST and witnessed the same - no effect in XP. I would have to retest in XP, to be honest, it was too long ago, but I am certain that I did try it. And I also removed it and perhaps even "unconsciously" discredited those that suggested it. It is working in Win10 - but that serves no purpose for this thread, THANKS FOR REPORTING YOUR XP TRIAL.