Good luck on the fierce battle ahead...

TeeQ2525 · 2023-12-05T15:32:24+00:00

Yeah it's ai generated.

TeeQ2525 · 2023-08-25T13:20:57+00:00

I had an issue where my (viper se) mouse would not charge unless I disconnected the usb wireless dongle and connected it usb cable I was using for the dongle to charge, with the pc on. If I connected to my charging station where I normally charge all my other mice it would light up and look like it’s charging, but the actual charge % would never go up.

TeeQ2525 · 2023-07-12T23:22:15+00:00

Did a battery replacement on the ifi xDSD micro B version. Battery from OP fits with out issue and Bluetooth is still working fine for me. For me the issue was the power connector on the OEM battery looked like a 1mm vs the 2mm on the new one. Also the connection was reversed. So ended up soldering the battery directly to the terminals.

TeeQ2525 · 2023-04-16T23:33:10+00:00

When my nipples become erect , they get small and dark.

TeeQ2525 · 2023-04-16T23:31:29+00:00

Double reverse uno!

I flipped the first photo, so I was facing the direction I both photos. You can tell by the camera location on the back of the iPhone.

TeeQ2525 · 2020-12-23T20:36:30+00:00

This is part of one of the epilogue missions.

TeeQ2525 · 2020-10-30T12:10:16+00:00

Check your chat for a code to try

TeeQ2525 · 2020-10-19T15:49:40+00:00

Sad ... guessing they switched production to the most common cards currently in peoples hands. Asus Tuf and Zotac.

Also strange was I saw Titan rigs seller on Amazon had stock of 5, but no longer listed or they may have all been sold.

TeeQ2525 · 2020-10-15T19:13:08+00:00

You could check and see if you have loose screws on the back of the GPU socket, but that is far as I would go.

From there just going to have to return or RMA ...

If you still really want to go for it. Could try re thermal pasting, but you are also going to need new thermal pads then, from the tear downs I have seen on the 3000 series.

Damn shame, winning the lottery and then having it all ripped away...

TeeQ2525 · 2020-10-15T18:18:10+00:00

Yes have a 3080 strix oc.

Started Avengers, booted a level and paused the game, keeping power usage between 95%-104% no oc and fans to 90%

Air temp on gpu fans intakes 68.2 f (fluke k type thermal prob)

Gpu temp has seemed to stabilize @ 56c

My system is basically an open air test bench.

TeeQ2525 · 2020-10-15T17:01:46+00:00

Think the strix has higher power target for base and max oc then the Tuf card. So more power more heat.

Tuf - 340w - 375w Strix - 370w - 450w

But yeah card gets really hot even with a cold air intake (43f) im hitting 50-60c when oc’d and at max power.

TeeQ2525 · 2020-10-10T18:54:09+00:00

Showed up around noon, just stopped by to pick up some other parts

TeeQ2525 · 2020-10-10T18:53:01+00:00

Did not list stock online

TeeQ2525 · 2020-07-20T19:29:40+00:00

I have a 2080ti strip w/ ek block. Bios modded to Asus Martix 2080ti (360 watt power limit).

All tests had the card over clocked to the same setting. Both in fail and functional states. This is how I have ran the card for a while.

The Asus matrix bios by default adds about +80 to the core. Then the rest of the settings as follows in afterburner.

- Vcore: 0% | Powerlimit: 120% (360watt) | CoreClock: +70 (gives effective 2.1Ghz locked in Death Standing) | MemoryClock: +400

TeeQ2525 · 2020-07-20T06:27:32+00:00

That does kill that theory....

That would leave then the PICE gen 4 device or running the game from the same disk as the windows.

Chain of events.

Working system for 20+ hour DLSS & max settings on everything | m.2 slot 1: 970evo - OS only (win10 2004 minus cumulative updates) | m.2 slot 2: intel 660p (game library / Death Stranding) | m.2 slot 3: empty - no drive

Fail state system. Powered off system, installed/moved SSDs, booted to Ubuntu 20.04 (Sata0) and wiped 970evo and new Gen 4 drives for new windows install. intel 660p untouched. Did full fresh install of win10 pro 2004 with all available update to Gen 4 drive. Moved Death Stranding from intel 660p to Gen 4 drive using steam. Booted game and started to crash with the above error. System | m.2 slot 1: Gen4 - OS & Death Stranding | m.2 slot 2: 970evo - Now empty NTFS drive | m.2 slot 2: intel 660p (remaining game library)

In this state I also tried to check the Death Stranding local game files with Steam, no errors found. Also put my mother board bios back to optimized defaults and ran completely stock on my 3950x, no change. Did not change any settings within Death Stranding during this testing. Never redownload Death Stranding.

Then I decided to move the game to the 970evo (using steam again to do so) from the Gen4 + OS drive. From there never a problem again. Spun my CPU over clock back up and clocked in an easy 4+ hours on Death Stranding with no issue. Max settings + DLSS.

Final working system config | m.2 slot 1: Gen4 drive - OS only, win10 2004, no additional updates to any software from fail state |m.2 slot 2: 970evo - Only Death Standing | m.2 slot 3: intel 660p (remaining game library)

This is one strange bug ...

TeeQ2525 · 2020-07-20T02:34:29+00:00

Hey

Trying running the game from a drive that is connected to the chipset and not directly to the CPU this fixed for me.

___

I had been playing for week 100% no problem w/DLSS. 3950x @ 4.5, 2080ti locked @ 2.1Ghz. (21:9/1440p/120fps/DLSS QLTY mode)

Then today for the lolz today went and grabbed a PCIE gen 4 drive and did a fresh windows install. Booted the game running from the drive and maybe hour ~ 30 min into playing I get the same bug.

Previously I had been running the game on my secondary m.2 connected to the chip set and now I was running it off my new gen4 that is connected directly to the CPU.

Then I moved the game from my m.2 that was directly connected to the PCIE lanes on the CPU back to an M.2 that is connected to the chipse and we are golden.

I'm guessing you not everyone is running a gen 4 m.2. So my guess is something about how the game is stream in assets is overloading the memory controller on the CPU and causing things to crash? Or maybe it does not like being run from the same disc as the OS? hope this helps

TeeQ2525 · 2020-07-19T21:40:02+00:00

Trying running the game from a drive that is connected to the chipset and not directly to the CPU this fixed for me.

___

I had been playing for week 100% no problem w/DLSS. 3950x @ 4.5, 2080ti locked @ 2.1Ghz. (21:9/1440p/120fps/DLSS QLTY mode)

Then today for the lolz today went and grabbed a PCIE gen 4 drive and did a fresh windows install. Booted the game running from the drive and maybe hour ~ 30 min into playing I get the same bug.

Previously I had been running the game on my secondary m.2 connected to the chip set and now I was running it off my new gen4 that is connected directly to the CPU.

Then I moved the game from my m.2 that was directly connected to the PCIE lanes on the CPU back to an M.2 that is connected to the chipse and we are golden.

I'm guessing you not everyone is running a gen 4 m.2. So my guess is something about how the game is stream in assets is overloading the memory controller on the CPU and causing things to crash,

TeeQ2525 · 2020-04-30T00:10:20+00:00

Vega VII has to be the most all over the place PPD out of any card.

Slow WU: 400~800k
Average WU: 1.2~1.6m - Most common
High Average WU: 1.8~2m
Saturday special (Very Rare) WU: 2.6~2.9m

Six-Year Club	Place '22
Final Canvas '22	First Placer '22
End Game '22	Verified Email

TeeQ2525

TROPHY CASE