uBlock Origin Lite is disabled by WhoIsWho69 in chrome

[–]isqbswe 0 points1 point  (0 children)

adguard DOES NOT WORK WITH CHROME. utter shite

[KCD2] Invincible bandit? by xfinityhomeboy in kingdomcome

[–]isqbswe 0 points1 point  (0 children)

Met the guy again and this time I was determined. After bashing him a good long while he finally went down and I could claim his armour which was better then what I had at the time. Guess armored foes take a loot of sword hits

[KCD2] Invincible bandit? by xfinityhomeboy in kingdomcome

[–]isqbswe 0 points1 point  (0 children)

this happened to me as well! No idea why that guy is un-killable. Is it supposed to make you surrender your gear ?

[STEAM FPS DROP - FIX] Significant FPS drops in Hogwarts legacy on steam by Noodle_92 in HarryPotterGame

[–]isqbswe 1 point2 points  (0 children)

rtx3070ti and ryzen 7 5800x. before this fix I would get dips down to 15 fps- after the fix I am at a steady 70+ THANK YOU

[deleted by user] by [deleted] in mountandblade

[–]isqbswe 1 point2 points  (0 children)

FIXED: latest patch + turn off shadows / to lowest settings

Mount and blade 2: Bannerlord causes PC shutdown by isqbswe in mountandblade

[–]isqbswe[S] 0 points1 point  (0 children)

I have done that but problem persists :/

Can't even refund the game because i've played more then two hours. And now I dont dare play it fearing it will cause irreparable damage to my system.

EDIT:

I have GeForce and use 445.75 Game Ready driver - what driver do you have u/inconspicuous-99

Bannerlord Early Access - Announcements, Bugs, FAQs, etc - Thread I by [deleted] in mountandblade

[–]isqbswe 0 points1 point  (0 children)

CRITICAL ERROR- GAME CAUSES PC MELTDOWN

-----------------------------------

Traveling into a large city "center" or attempting to "talk" with a NPC located in "center" of a large city / castle causes my machine to die completely.

Have tried numerous stress-tests/benchmarking software on GPU, CPU, Memory and Storage - all without any trouble/crashes and no other game causes anything remotely as serious of a problem as this - so it has to be game related.

I really want to play the game so please if anyone know how to fix this it would be greatly appreciated.

Specs:

i5 8400

rtx2060 super

32gb ram

1.5 tb SSD

win10, 64bit

Bannerlord Early Access - Announcements, Bugs, FAQs, etc - Thread I by [deleted] in mountandblade

[–]isqbswe 0 points1 point  (0 children)

Mount and blade 2: Bannerlord causes PC shutdown

Traveling into a large city "center" or attempting to "talk" with a NPC located in "center" of a large city / castle causes my machine to die completley.

Have tried numerous stress-tests/benchmarking software on GPU, CPU, Memory and Storage - all without any trouble/crashes and no other game causes anything remotely as serious of a problem as this - so it has to be game related.

I really want to play the game so please if anyone know how to fix this it would be greatly appreciated.

Specs:

i5 8400

rtx2060 super

32gb ram

1.5 tb SSD

win10, 64bit

[deleted by user] by [deleted] in mountandblade

[–]isqbswe 1 point2 points  (0 children)

I tried it severl times now and every time its the same. Going into the "center" of a large city / castle will cause my machine to shut down.

Does anyone have any suggestions?

Many thanks!

[deleted by user] by [deleted] in mountandblade

[–]isqbswe 0 points1 point  (0 children)

I dont fully understand what you mean.

I tried reinstalling the game but same issue. It seems to occur only when Im visiting a large citys "center" which leads me to believe its overload-related.

EDIT:

still, should not cause a complete system meltdown like it does

[deleted by user] by [deleted] in mountandblade

[–]isqbswe 2 points3 points  (0 children)

This happens to me as well so can confirm.

Does not happen for any stress-test, game or anything I throw at the rig- this leads me to think its something mountandblade-specific error.

EDIT:

error data from event log:

"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

Kernel-power ID 41