Zooolz
@Zooolz
3
Reputation
5
Topics
40
Posts
1
Profile views
0
Followers
0
Following
Best posts made by Zooolz
-
in Player Support by Zooolz
I never needed the " Guaranteed Assassination "
( but it does not work anyway )
GAME PLOT BROKEN
unable to assassinate
Power Level 404
All assassination's runes applied.
All poison applied.
They just laugh at me --- as I wait for the " video sequence" to end .....
--- then Button 1 kill them.
Is there a way to un-apply this 1.1.2 patch ?
( or stop the patches from being automatically applied ? )
We cant complete " Core " assignation challenges.
I can also say I picked up "the book" on the river raids EXE .
I think they are correct. -
@semplerfi " Do you know how long it takes to get killed at 325 hours in, level 406 with 86 Mastery points "
Hah ! yes ... the hardest part is keeping in the same area when being thrown, beaten, and gored.
For those still having issues at the Farm, --- fast travel home, wait, and go back....
This is NOT a fast process - and bodies do not always appear.
Also, try leaving a corpse. Exit the game. Go Back. -
@azullFR
I also have this happening .... Zoom ! ... get your Dramamine !
Been happening since the last patch IIRC.
Usually a teleport in / to the 1st obstacle in the direction of movement.
So, yes. Sometimes I do travel quite far.
Latest posts made by Zooolz
-
@ubi-borealis
I fixed my problem.
Deleted the game.
I'm tired of turning my RGB off anyway.
Cant diagnose with no log files.
Cant risk O/S corruption.
Cant risk hardware damages.
My new 1000w Platinum did not fix anything.
12 hours Prime95 stable at 74.9C at default voltages.
Every stress test passed.
Going back to my overclock now.
( bye UbiSoft ) -
@azullFR
I also have this happening .... Zoom ! ... get your Dramamine !
Been happening since the last patch IIRC.
Usually a teleport in / to the 1st obstacle in the direction of movement.
So, yes. Sometimes I do travel quite far. -
@kormac67 ---- I think your right. Had another shutdown without logs this time. I picked up a 1000w. My 750w was old anyway.
-
Spent all day benchmarking and testing ... no other issues.
However, I launched the game without error a few minutes ago.
Everything seems Ok during gameplay so far.
Only 2 launches so far .. -
No other games or programs are generating this error.
I just got my BEST stress test results at 3Dmark @ 99.7 percent ( phenomenal )
https://www.3dmark.com/tsst/2086728
Running memory stress tests now. -
Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\LiveKernelReports\WHEA\WHEA-20210712-1251.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19043 MP (24 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff807`48200000 PsLoadedModuleList = 0xfffff807`48e2a3d0 Debug session time: Mon Jul 12 12:51:53.936 2021 (UTC - 5:00) System Uptime: 0 days 0:00:14.535 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list For analysis of this file, run !analyze -v nt!LkmdTelCreateReport+0x13e: fffff807`48b7e686 488b03 mov rax,qword ptr [rbx] ds:002b:ffffcb83`fc3fc470=???????????????? 14: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffcb83f0d91c00, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000bea00000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000108, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2281 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2343 Key : Analysis.Init.CPU.mSec Value: 249 Key : Analysis.Init.Elapsed.mSec Value: 8324 Key : Analysis.Memory.CommitPeak.Mb Value: 76 DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump BUGCHECK_CODE: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffffcb83f0d91c00 BUGCHECK_P3: bea00000 BUGCHECK_P4: 108 PROCESS_NAME: smss.exe STACK_TEXT: ffffc600`a8582150 fffff807`48b5992f : ffffcb83`f0d91be0 00000000`00000000 ffffcb83`f0d91c00 00000000`00000022 : nt!LkmdTelCreateReport+0x13e ffffc600`a8582690 fffff807`48b59826 : ffffcb83`f0d91be0 fffff807`00000000 000000a8`00000000 000000a8`d547f6e0 : nt!WheapReportLiveDump+0x7b ffffc600`a85826d0 fffff807`489be669 : 00000000`00000001 ffffc600`a8582b40 000000a8`d547f6e0 00000000`000002f4 : nt!WheapReportDeferredLiveDumps+0x7a ffffc600`a8582700 fffff807`487cf5f7 : 00000000`00000000 ffffcb83`f80c3030 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59 ffffc600`a8582730 fffff807`486077b8 : ffffcb83`f8a90000 ffffcb83`f8a735b0 ffffc600`a8582b40 ffffcb83`00000000 : nt!NtSetSystemInformation+0x1f7 ffffc600`a8582ac0 00007ffa`9f090254 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 000000a8`d547f688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`9f090254 MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD.sys STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f59f17e7-f24e-04f5-3f16-e9425b2acba5}
No game launch at all.
Launch generates WHEA 18 error ( instant reboot )
( 1st time seen on this PC ) -
This is the last straw for me.
My system reboots today on game launch.
Verified Game Files thru UBI support.
All drivers up to date.
No system changes.
Reboot on every attempt to diagnose the problem.
This is not a windows error, its a hardware reset invoked on game launch.
Sometimes I can get to the " continue " screen, but, crash on the " Tip screen " always REBOOTs my system.
No Windows Error Report generated.
I'm going to " wait and see " if this is UBI related, since we had no update today. -
My RGB on my DDR is turned ON every startup and exit from the game now.
I have launched MSI control center to turn it off after it's turned ON, then quit the game, and the RGB is turned ON again.
So, the problem is WORSE now.
No matter what I do, RGB is turned ON on game launch and exit now. -
@semplerfi " Do you know how long it takes to get killed at 325 hours in, level 406 with 86 Mastery points "
Hah ! yes ... the hardest part is keeping in the same area when being thrown, beaten, and gored.
For those still having issues at the Farm, --- fast travel home, wait, and go back....
This is NOT a fast process - and bodies do not always appear.
Also, try leaving a corpse. Exit the game. Go Back. -
the empty boxes are empty ... was that way since the release. I ignored it. Yes its annoying.
What bugs me ... is how stupid the Jomsviking are ... standing in the middle ... getting shot and burned .... the enemy knows how to hide and cover ... why cant ours ...?
AND, THEY BURN THEMSELVES !!! ..... after the raid completion ... they run around burning everything and themselves. ( I let them burn and die now - not worth the effort reviving cuz they do it again )
