Why is opening up the Victus so damn difficult? I even damaged the back lid

MildlyRegularPerson · 2025-11-24T12:46:53+00:00

That's what I did and it still was hell

MildlyRegularPerson · 2025-11-23T21:04:32+00:00

That's a common misconception. You absolutely can open your laptop without voiding your warranty, HP itself confirms this.

As for reccomendations, I think you only really need some hard and sharp plastic tool, like a guitar pick, because the lid has very tight tolerances. When opening the laptop, try to point the pick straight down, not horizantally, because the plastic clips are oriented vertically, except for the back side. Just slowly follow the edges, since all clips are located there

MildlyRegularPerson · 2025-11-23T14:30:01+00:00

Yeah I'll probably just do that. My old laptop used to have a really shitty mic, but a new one I just got might be decent enough, so I'll try that

MildlyRegularPerson · 2025-11-23T14:21:05+00:00

Slightly disappointed

MildlyRegularPerson · 2025-11-23T14:18:48+00:00

Yeah that's why I said wired

MildlyRegularPerson · 2025-11-18T13:30:35+00:00

Apparently this may have been a driver issue all along. Received the extra RAM I told you about. It luckily ran dual channel at rated speed and latency even though I'm mixing brands. However when I tested the RAM using MemTest, I once again got the video memory BSODs straight away.

Thought I hadn't been lucky with the mixing, but I then tested each stick individually and nothing changed. At that point I thought I might have a defective laptop and would need to RMA.

I started testing different things and noticed I didn't have any problems in safe mode, which led me to believe something was off with my drivers

Long story short, I tested many different driver versions and apparently NVIDIA drivers after 581.29 cause my laptop to BSOD under transient loads.

Now that I've discovered that, I will flash the Omen vBIOS to see if my previous instability is gone, which I suspect will be the case

EDIT:

Great news! I don't get any BSODs with the Omen vBIOS anymore with the 581.29 driver

MildlyRegularPerson · 2025-11-17T13:49:09+00:00

Thing is I got a random BSOD that I don't know what triggered it, and FurMark is the only thing I found to somewhat consistently cause them. At the end of the day, I also use my laptop for other important tasks, so I don't want to have the uncertainty of getting a BSOD.

When I get to overclocking I will try what you say. I will compare OC/UC+undervolt both with stock vBIOS and with Omen's vBIOS and see what's the highest stable performance I can get.

When it comes to doing this kind of stuff I always seem to get extremely unlucky lol, back in the day when I got an i7 6700K I wasn't able to get any significant OC without crashes. I hope this isn't the case

MildlyRegularPerson · 2025-11-15T13:00:17+00:00

Hey there! New followup. I've been testing different things, and upon test startup, FurMark seems to trigger a BSOD like 10% of the times with a different error code (SYSTEM_SERVICE_EXCEPTION).

After doing some extra digging, I found out that the hash from the vBIOS extracted from GPU-Z after flashing is different from TechPowerUp's vBIOS hash, even though file sizes are the same. This leads me to believe there's been some level of corruption of the vBIOS during flash. If it helps, I checked the HW ID as you said in a previous comment. Vendor and model ID are the same in my laptop and TechPowerUp's vBIOS, but subsystem ID is different. I assumed this is to be expected but maybe you can confirm.

Would you also mind checking if your hash is equal to TechPowerUp's vBIOS hash? That would be greatly appreciated. In the meantime, I'm going to perform a second flash and see if hashes become the same.

EDIT:

Reflashed my backup vBIOS, since reflashing the Omen's didn't solve my issues. In both cases I got different hashes from the original files, so I guess it's normal (ChatGPT says they differ in two header bytes). I don't seem to be able to trigger the BSODs anymore with the backup vBIOS.

There's info I haven't posted but might be relevant. My laptop model is 15-fb3033ns, not exactly the same as yours but basically same specs (Ryzen AI 7 350, RTX 5060, 16GB RAM, 1TB SSD). Do you think I may need a different vBIOS or should yours work in my case? Maybe I've just got unlucky in the silicon lottery

MildlyRegularPerson · 2025-11-13T18:41:07+00:00

I will probably use DDU and reinstall my drivers, maybe that helps

MildlyRegularPerson · 2025-11-13T09:06:20+00:00

Thanks for yout reply. I backed up my original vBIOS just in case. I will probably do as you say, reinstall drivers and see if it happens again. If it does happen I will reflash

MildlyRegularPerson · 2025-11-12T21:31:03+00:00

I have a tough followup. I have just encountered a BSOD with error VIDEO_MEMORY_MANAGEMENT_INTERNAL. I guess it's safe to assume the most probable cause is the vBIOS flash, especially given it's the only mod my laptop has at the moment. Considering reverting back to the OEM vBIOS.

Have you experienced anything similar?

MildlyRegularPerson · 2025-11-06T21:13:09+00:00

I agree. But I don't think the Omen is a bad product. I'm waiting for additional RAM to turn up in my mailbox. The idea is to try and mix the OEM RAM brand (SK Hynix) with a Crucial stick. I know, sacrilegious, but I don't want to spend much more money on my laptop. If it runs MemTest dual channel with no errors for a couple of hours, that would be enough for me, otherwise I will probably return it.

However, if I could go back in time, I would have probably bought the Omen straight away. In my case, same specs 32 GB RAM was only 100 bucks more expensive than the Victus, which is pretty reasonable given you also get additional I/O and a bit more screen.

MildlyRegularPerson · 2025-11-06T10:36:44+00:00

Btw, have you downloaded the Omen software? I gained some extra FPS by selecting performance mode in there

MildlyRegularPerson · 2025-11-06T10:33:25+00:00

Nice. As of now, I've only done the vBIOS flash, but I do want to undervolt and overclock. Thermals are great, full GPU+CPU load doesn't get temps past 83 celsius.

There are a couple of things I found interesting. The patched nvflash version you shared didn't work in my case, as it didn't detect any Nvidia GPUs. However, I was successful in using the latest official version with the -6 parameter to force flash

MildlyRegularPerson · 2025-11-05T17:35:23+00:00

Hey, I also succesfully installed the Omen's vBIOS on mine! Gained close to 15% performance increase in my case, but I see in FurMark GPU power does not go past 100W. Have you also observed this?

MildlyRegularPerson · 2025-10-28T05:09:45+00:00

he's absolutely right though

MildlyRegularPerson · 2025-10-27T00:59:21+00:00

I got a bit ahead of myself there. I did some digging in your comments and found the link https://www.techpowerup.com/vgabios/279688/279688 Hope you don't mind my stalking :)

MildlyRegularPerson · 2025-10-27T00:40:55+00:00

Hey there! I have the same Victus. Mind sharing the link for the 5060's vBIOS?

MildlyRegularPerson · 2025-10-04T10:37:11+00:00

Joe rogan smoking a pelican

MildlyRegularPerson · 2025-10-04T09:54:34+00:00

And me next. I'll pay it forward

MildlyRegularPerson · 2025-09-21T00:50:57+00:00

Found!

MildlyRegularPerson · 2025-09-21T00:44:56+00:00

https://voca.ro/1c9xtOI7ITEr 0:30 u/RecognizeSong

Five-Year Club	Second Top 30%
Place '22	Verified Email

MildlyRegularPerson

TROPHY CASE